From: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
---|---|
To: | Ioseph Kim <pgsql-kr(at)postgresql(dot)kr> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: suggestion: discard python2.x venv |
Date: | 2018-02-06 04:55:46 |
Message-ID: | CAKKotZQn=uYR+_X=ghS6CEv+AbarucFgJd9SGPebw395EuUE9w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Tue, Feb 6, 2018 at 9:21 AM, Ioseph Kim <pgsql-kr(at)postgresql(dot)kr> wrote:
> Hi,
>
> I used pgadmin4 since 2 month.
>
> pgadmin4 is a good application for PostgreSQL. that is true!
>
> but, in multibytes environment, python2 + pgadmin4 is not good choice.
>
>
> if table name or column name is multibytes, export, import is not working,
> because python2 unicode processing is ugly.
>
> and, if server message is multibytes, pgadmin4 does not display that, and
> there are many other problems so.
>
>
> I changed venv to python3, most problems of multibytes have been resolved
> smoothly as expected.
>
>
> we need to narrow its focus.
>
AFAIK we are using Python2.x because many enterprise linux distributions
do not have native support for Python3 in them (from their default repo)
for example CentOS6.x, many versions of Redhat linux etc, Admins have to
download and compile Python3.x manually which adds maintenance of
additional software on their servers (eg manual security updates etc), In
order to support them we are shipping pgAdmin4 with Python2.x, Otherwise
you are correct Python3 will resolve most of the Unicode related issues
which we are currently facing with pgAdmin4.
-- Murtuza
>
>
> Regards Ioseph
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ioseph Kim | 2018-02-06 05:46:12 | Re: suggestion: discard python2.x venv |
Previous Message | Khushboo Vashi | 2018-02-06 04:06:15 | Re: suggestion: discard python2.x venv |