Dependencies, and upcoming changes to pip

From: Shaheed Haque <shaheedhaque(at)gmail(dot)com>
To: pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: Dependencies, and upcoming changes to pip
Date: 2020-09-29 12:04:33
Message-ID: CAHAc2jehhQxzpc9U-m_oBUO=949jmtS8tGt8MJgbEevw-xkbPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi,

I've long wondered why pgAdmin4 seems to hard pin its dependencies;
specifically these two which do seem rather outdated:

pgadmin4 4.26 requires pytz==2018.9, but you'll have pytz 2020.1 which is
incompatible.
pgadmin4 4.26 requires sqlparse==0.2.4, but you'll have sqlparse 0.3.1
which is incompatible.

So far, I've just ignored this , and as far as I know, I have not
encountered any obvious issues. But, with the upcoming changes to pip's
resolver, I suspect this is going to become a hard error for me as I
believe the new resolver will simply abort the install in such cases:

ERROR: After October 2020 you may experience errors when installing or
updating packages. This is because pip will change the way that it resolves
dependency conflicts.

We recommend you use --use-feature=2020-resolver to test your packages with
the new resolver before it becomes the default.

So, I'd like to request that any unneeded constraints are either removed,
or relaxed, or at least updated to something close to current.

Thanks, Shaheed

P.S. We understand about venvs, but we have a whole bunch of dependencies
beyond pgAdmin and having to set up multiple venvs to isolate everything is
a deployment-time overhead we prefer to avoid.

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Jack Royal-Gordon 2020-09-29 15:30:10 Re: Problem when double-clicking to auto-size column in query window
Previous Message Khushboo Vashi 2020-09-29 05:14:47 Re: Problem when double-clicking to auto-size column in query window