On Fri, February 19, 2021 09:10, Dave Page wrote:
> Hi
>
>
> A couple of possibilities spring to mind:
>
> 1) Python hasn't noticed the update, and is using the older bytecode. Try
> searching for and removing any __pycache__ directories under
>
Hi
On Fri, Feb 19, 2021 at 2:05 PM James B. Byrne
wrote:
>
>
> On Fri, February 19, 2021 04:33, Dave Page wrote:
> > Hi
> >
> > On Thu, Feb 18, 2021 at 7:34 PM James B. Byrne
> > wrote:
> >
> >> When starting pgadmin4 in a python venv I get a warning that I am
> starting
> >> version 4.27 and
On Fri, February 19, 2021 04:33, Dave Page wrote:
> Hi
>
> On Thu, Feb 18, 2021 at 7:34 PM James B. Byrne
> wrote:
>
>> When starting pgadmin4 in a python venv I get a warning that I am starting
>> version 4.27 and that 4.30 is available.
>>
>> However, I have updated that venv to 4.30:
>>
. .
Hi
On Thu, Feb 18, 2021 at 7:34 PM James B. Byrne
wrote:
> When starting pgadmin4 in a python venv I get a warning that I am starting
> version 4.27 and that 4.30 is available.
>
> However, I have updated that venv to 4.30:
>
> [root@vhost01 ~ (master)]# source
>
When starting pgadmin4 in a python venv I get a warning that I am starting
version 4.27 and that 4.30 is available.
However, I have updated that venv to 4.30:
[root@vhost01 ~ (master)]# source /opt/python_venv/3.7/pgadmin4/bin/activate
(pgadmin4) [root@vhost01 ~ (master)]# pip install
