Sorry. Unfortunately - we did not have access to the community build at that time.
We can test the one click installer without setting PYTHON_HOME, if that works - we can unset it only for Mac. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company <http://www.enterprisedb.com> *http://www.linkedin.com/in/asheshvashi* <http://www.linkedin.com/in/asheshvashi> On Thu, Sep 1, 2016 at 10:35 PM, Dave Page <[email protected]> wrote: > It should have fixed 1392, but it broke the community mac package (just > after beta 4) > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK:http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > On 1 Sep 2016, at 17:42, Ashesh Vashi <[email protected]> > wrote: > > Also - during beta 4 release the runtime issue was fixed only by setting > PYTHON_HOME. > > On Sep 1, 2016 22:10, "Ashesh Vashi" <[email protected]> > wrote: > >> This might explain. >> https://redmine.postgresql.org/issues/1392 >> >> On Sep 1, 2016 21:52, "Dave Page" <[email protected]> wrote: >> >>> Neel, Ashesh, >>> >>> re: https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=commitdi >>> ff;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 >>> >>
