Re: pgAdmin v3.1 candidate builds and source...

Re: Khushboo Vashi 2018-07-02 <CAFOhELc2oFoN_ic3a6oW6nt-9W3=ADgczfZxdE9VjHcj1emL_Q@mail.gmail.com>
> > I could finally build the packages now. (There were some issues with
> > the python3.7 update happening in Debian at the same time, which broke
> > a few bits, but I managed to work around.)
> >
> > One user raised the same issue that pgAdmin is not working with python
> 3.7. He found that the issue is with psycopg2 (Ref:
> https://github.com/psycopg/psycopg2/issues/714) as async and await are now
> keywords and we are using async in pgAdmin 4.
>
> So, I am curious to know how you have fixed this issue?

Hi Khushboo,

I simply postponed building the pgadmin4 packages for sid until the
problem is fixed.

pgadmin4 |      3.0-2.pgdg+1 |             sid-pgdg | amd64, i386, ppc64el, source
pgadmin4 |   3.1-1.pgdg100+1 |          buster-pgdg | amd64, i386, ppc64el, source
pgadmin4 |    3.1-1.pgdg90+1 |         stretch-pgdg | amd64, i386, ppc64el, source
pgadmin4 | 3.1-1.pgdg18.04+1 |          bionic-pgdg | amd64, i386, ppc64el, source
pgadmin4 | 3.1-1.pgdg16.04+1 |          xenial-pgdg | amd64, i386, ppc64el, source

The fix from
https://github.com/psycopg/psycopg2/issues/714#issuecomment-401570055
looks promising, I'll probably apply that to psycopg2 in sid unless
someone else is faster.

Christoph