Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.

2017-06-13 Thread Ashesh Vashi
On Tue, Jun 13, 2017 at 3:57 PM, Dave Page wrote: > > > On Tue, Jun 13, 2017 at 11:25 AM, Ashesh Vashi < > ashesh.va...@enterprisedb.com> wrote: > >> On Tue, Jun 13, 2017 at 3:52 PM, Ashesh Vashi < >> ashesh.va...@enterprisedb.com> wrote: >> >>> Oops. >>> let me revert it

Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.

2017-06-13 Thread Dave Page
On Tue, Jun 13, 2017 at 11:25 AM, Ashesh Vashi < ashesh.va...@enterprisedb.com> wrote: > On Tue, Jun 13, 2017 at 3:52 PM, Ashesh Vashi < > ashesh.va...@enterprisedb.com> wrote: > >> Oops. >> let me revert it back. >> > 'web/regressions/requirements.txt' needs to change as it is not require > for

Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.

2017-06-13 Thread Ashesh Vashi
On Tue, Jun 13, 2017 at 3:52 PM, Ashesh Vashi wrote: > Oops. > let me revert it back. > 'web/regressions/requirements.txt' needs to change as it is not require for Python >= 3.3. Will do the change. > > -- > > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB

Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.

2017-06-13 Thread Ashesh Vashi
Oops. let me revert it back. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* On Tue, Jun 13, 2017 at 3:50 PM, Dave Page

Re: [pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.

2017-06-13 Thread Dave Page
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 wrote: > Required mock package for python < 3.3. > It was required for the commit: >

[pgadmin-hackers] pgAdmin 4 commit: Required mock package for python < 3.3.

2017-06-13 Thread Ashesh Vashi
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 ---