Yes, I agree yours.
thinking that,
many pgadmin4 is used on windows, or mac,
pgadmin4 for windows installer is including python2.7.
so many users use the python2 environment, with no choice.
if python3 is used on windows distribution (builtin python3), this will
is good choice.
Regards, ioseph.
2018년 02월 06일 13:55에 Murtuza Zabuawala 이(가) 쓴 글:
On Tue, Feb 6, 2018 at 9:21 AM, Ioseph Kim <pgsql...@postgresql.kr
<mailto:pgsql...@postgresql.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
