pgAdmin 4 commit: Revert changes to support Python 3.10. Too many thing

Revert changes to support Python 3.10. Too many things broke, needs more thought :-( Branch -- master Details --- https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=d7f5e13cdde7ee7c60c5f21de1f4586000d7be6b Modified Files -- requirements.txt | 6 +- 1 file cha

pgAdmin 4 commit: Only include the dnspython library for Python 3.10.

Only include the dnspython library for Python 3.10. Branch -- master Details --- https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=33aeacd8d1b39d8f7ead17ec5dfca8dd1e74a0ee Modified Files -- requirements.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-

pgAdmin 4 commit: Fix dependencies to work with Python 3.10.

Fix dependencies to work with Python 3.10. Patch by me, legwork by Aditya. Branch -- master Details --- https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=f3bf0680665419386e353412fa0c82c1152326db Modified Files -- requirements.txt | 6 +- 1 file changed, 5 in

Re: Issue tracking

Hi Sorry, I missed that update. The tracker is part of the PostgreSQL project infrastructure, and thus the pgAdmin project has no control over the requirement to login to see tickets. We are considering a move to Github issues, but that's a huge and complex task. On Wed, Nov 3, 2021 at 9:20 AM

Issue tracking

Greetings, After starting to use pgAdmin a couple years ago and struggling to track one of its issues, I figured out that its issue tracker was not publicly visible (an account is required to display tickets). I reported that meta-issue in report #5042. The ticket's Status field was later set