| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | backports.csv |
| Date: | 2017-05-12 12:02:24 |
| Message-ID: | CA+OCxowK7ZAMrpmTn9i5pekhHL7-NSqgVNPe1GZvTtL5V3Ws3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Murtuza,
Your recent addition of backports.csv to the pgAdmin requirements.txt seems
to be causing an interesting problem. Whilst it works fine in a regular
Python environment, in the cut-down environment used by the desktop runtime
it fails because there is no backports/__init__.py file. This seems to be a
well-known, but un-fixed issue in which PIP doesn't install the file as it
should.
Any ideas on how we might fix this? Obviously I can just touch the file
when building the installers, but that doesn't seem ideal.
Thanks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murtuza Zabuawala | 2017-05-12 12:31:31 | Re: backports.csv |
| Previous Message | Surinder Kumar | 2017-05-12 11:49:35 | Re: pgAdmin 4 commit: Improve handling of nulls and default values in the d |