Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bfVQx-00031W-45 for pgadmin-hackers@arkaria.postgresql.org; Thu, 01 Sep 2016 17:05:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bfVQw-0007mp-Mu for pgadmin-hackers@arkaria.postgresql.org; Thu, 01 Sep 2016 17:05:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bfVQj-0007YX-Cy for pgadmin-hackers@postgresql.org; Thu, 01 Sep 2016 17:05:33 +0000 Received: from mail-wm0-x230.google.com ([2a00:1450:400c:c09::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bfVQg-0003Za-3f for pgadmin-hackers@postgresql.org; Thu, 01 Sep 2016 17:05:32 +0000 Received: by mail-wm0-x230.google.com with SMTP id 1so106077490wmz.1 for ; Thu, 01 Sep 2016 10:05:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/MNGRYw/zHhpYPv+/HmGgd3kzdfoQZKkOQ+zeOYeHNQ=; b=TAYP5uUQzlFBxpD8jIIxWGs6FzRa/je8KB/oby7NI4P12jFdkxmkgvCjNlQmVWMkb7 ioAUrGNfo/I6S6Bxhapv2dSCYstVrztcxRlxTnvR2bKYscGCukXZlGaHEB99GIjyXiMR cCSUHd5WcNu1Nwxaul0bvpa08PaXoClv/v2rJNRE5Aju6y4fjw6uQcMLOXj1nrmoLzCa 37rQx0NpS2fPVG2Zrmm134Drjb3s7ER7atCexOo4MsMq57HH9JCwTYwmarkMe0G8m1vE uLADOD5gIhbfU5Ra+hCWNGpSIhdtE1eAji6WYu/jM9dLYn9UbOYZj/E8gVDcX0Kt2lOq oB3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/MNGRYw/zHhpYPv+/HmGgd3kzdfoQZKkOQ+zeOYeHNQ=; b=g1BHwlTSRpEFNF4aneWN2wAHv/ZRJ072QzxE6AUWOgb5Wy08by2zbXhSRExxj3+TOm 9CiSMOtGv19Cn3ieuqBLv7HWBvr7uvVNjTypdrBx0v05cj2tVz1Ztmpfy+TQAa4HfI+i DEgHD2mK4uneALr2D25QuFk2crVXgjnbkyTU8+QtucOs6iAmeYHTrPI+b5uwk7xLsAes VJ1skX2rMKWF2H6Ns6Es1+YZwJHcqoZ1zXvDYwvSLXEKY7EJGE3TbspzEUkYOn8jKCFz eQLQhPNJlBs7Qj0Ol+I3zdJiTki9YUr404sT8MygXVAhNgi/yYr9pZU4t1ll6fZsdlkC FyBA== X-Gm-Message-State: AE9vXwNo7zTmnPDm8MHY+xvtFCyjoYUnThjboKE3OsKwNxakMVv796sDhyE+6RM5ohtudw== X-Received: by 10.28.10.21 with SMTP id 21mr16781163wmk.3.1472749527422; Thu, 01 Sep 2016 10:05:27 -0700 (PDT) Received: from [100.75.174.29] ([213.205.194.45]) by smtp.gmail.com with ESMTPSA id jq5sm6238167wjc.20.2016.09.01.10.05.24 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 01 Sep 2016 10:05:25 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-B4A5E817-AD5F-4359-BB94-D31C351A97B0 Mime-Version: 1.0 (1.0) Subject: Re: Runtime broken on Mac From: Dave Page X-Mailer: iPhone Mail (13G35) In-Reply-To: Date: Thu, 1 Sep 2016 18:05:23 +0100 Cc: neel patel , pgadmin-hackers Content-Transfer-Encoding: 7bit Message-Id: <96161F16-6577-42F1-8F6B-9DFF65CA3AAE@pgadmin.org> References: To: Ashesh Vashi X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --Apple-Mail-B4A5E817-AD5F-4359-BB94-D31C351A97B0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable It should have fixed 1392, but it broke the community mac package (just afte= r beta 4) --=20 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 wrot= e: >=20 > Also - during beta 4 release the runtime issue was fixed only by setting P= YTHON_HOME. >=20 >=20 >> On Sep 1, 2016 22:10, "Ashesh Vashi" wrot= e: >> This might explain. >> https://redmine.postgresql.org/issues/1392 >>=20 >>=20 >>> On Sep 1, 2016 21:52, "Dave Page" wrote: >>> Neel, Ashesh, >>>=20 >>> re: https://git.postgresql.org/gitweb/?p=3Dpgadmin4.git;a=3Dcommitdiff;h= =3Da3e8ba93ae6968f13b331d9218d51b8e2d39f344 >>>=20 >>> 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. >>>=20 >>> 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? >>>=20 >>> -- >>> Dave Page >>> Blog: http://pgsnake.blogspot.com >>> Twitter: @pgsnake >>>=20 >>> EnterpriseDB UK: http://www.enterprisedb.com >>> The Enterprise PostgreSQL Company --Apple-Mail-B4A5E817-AD5F-4359-BB94-D31C351A97B0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
It should have fixed 1392, but it brok= e the community mac package (just after beta 4)

-- 
Dave Page
Blog: http://pgs= nake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK:http://www.ente= rprisedb.com
The Enterprise PostgreSQL Company

O= n 1 Sep 2016, at 17:42, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:

Also - during beta 4 release the r= untime issue was fixed only by setting PYTHON_HOME.


On Sep 1, 2016 22:= 10, "Ashesh Vashi" <ashe= sh.vashi@enterprisedb.com> wrote:

This might explain.
htt= ps://redmine.postgresql.org/issues/1392


On Sep 1, 2016 21:= 52, "Dave Page" <d= page@pgadmin.org> wrote:
Neel, Ashesh,

re: https://git.postgresql.org/gitweb/?p=3Dpgadmin4.git;a=3Dco= mmitdiff;h=3Da3e8ba93ae6968f13b331d9218d51b8e2d39f344

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
= --Apple-Mail-B4A5E817-AD5F-4359-BB94-D31C351A97B0--