Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package forpython < 3.3. - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package forpython < 3.3.
Date
Msg-id CA+OCxow9iExbaTH88PeDm7_cjtoMMXMMb8Hy4D4g=da4W1Kt6g@mail.gmail.com
Whole thread Raw
In response to [pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Responses Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package forpython < 3.3.  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
List pgadmin-hackers
Is mock required at runtime, or just for tests? It's already in
web/regressions/requirements.txt

On Tue, Jun 13, 2017 at 11:13 AM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Required mock package for python < 3.3.
> It was required for the commit:
> 1208206bc0eca2d135469258e8a209b983e668be
>
> Also, do not fetch the scenario-name, when it is not avaiable (but - use
> default vaule as the stringified test-case itself).
>
> Branch
> ------
> master
>
> Details
> -------
> https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=903389d7b76046141c92a720e9e515cc4bb46274
>
> Modified Files
> --------------
> requirements.txt           | 3 ++-
> web/regression/runtests.py | 8 +++++---
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers



--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgadmin-hackers by date:

Previous
From: pgAdmin 4 Jenkins
Date:
Subject: [pgadmin-hackers] Build failed in Jenkins: pgadmin4-master-python36 #166
Next
From: pgAdmin 4 Jenkins
Date:
Subject: [pgadmin-hackers] Build failed in Jenkins: pgadmin4-master-python34 #160