From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | neel patel <neel(dot)patel(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Runtime broken on Mac |
Date: | 2016-09-01 16:40:42 |
Message-ID: | CAG7mmozfK0vOdh7E0w+kK65v9n6wAVARBpBKcF3rPm5p=5B2Tw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
This might explain.
https://redmine.postgresql.org/issues/1392
On Sep 1, 2016 21:52, "Dave Page" <dpage(at)pgadmin(dot)org> wrote:
> Neel, Ashesh,
>
> re: https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=commitdiff;h=
> a3e8ba93ae6968f13b331d9218d51b8e2d39f344
>
> it seems that setting PYTHON_HOME breaks the runtime on Mac OSX. Doing
> so means that the system installed Python libraries cannot be found, a
> (large) number of which do not get installed into the virtualenv.
>
> Now I could modify the package build scripts to copy or symlink all
> those extra files and directories into the virtual env (I would
> probably symlink, as that's what happens with the rest of the venv),
> but before I do - can you remind me why we needed to explicitly set it
> anyway?
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2016-09-01 16:42:44 | Re: Runtime broken on Mac |
Previous Message | Dave Page | 2016-09-01 16:22:13 | Runtime broken on Mac |