From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Colin Beckingham <colbec(at)kingston(dot)net> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pgadmin4 qmake selects python 3 by default? |
Date: | 2016-06-17 10:17:30 |
Message-ID: | CA+OCxoxOSXL1P02SYjK_Ok2COv-JrkH3qhhDz-3OiN9bBV20Zg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Fri, Jun 17, 2016 at 11:02 AM, Colin Beckingham <colbec(at)kingston(dot)net> wrote:
> On openSUSE Leap 42.1, using system with both python2- and python3-config,
> qmake selects python3.
> ---
> qmake
> Project MESSAGE: Building for QT4...
> Project MESSAGE: Building for Linux/Mac...
> Project MESSAGE: Using /usr/bin/python3-config
> Project MESSAGE: Python3 detected.
> ---
> Is this a deliberate choice, determined by my system or random? I am
> accustomed to seeing a default to python2, but if python3 works then not a
> problem.
It was, but on reflection I wonder if it's the best choice, given that
most of us are still using python2.
I'll switch it around.
> I still am not able to tell if the runtime situation is up due to another
> error (Type str doesn't support the buffer API) which is still under
> investigation.
--
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 | 2016-06-17 10:20:32 | PATCH: Patch to fix issue in trigger function (pgAdmin4) |
Previous Message | Colin Beckingham | 2016-06-17 10:02:15 | pgadmin4 qmake selects python 3 by default? |