On Thu, Oct 27, 2016 at 09:10:49PM +0200, Neil Muller
wrote:
> On 23 September 2016 at 00:03, Oleg Broytman wrote:
> > Hi, all!
> >
> > On Thu, Aug 25, 2016 at 11:18:45PM +0200, Oleg Broytman
> > wrote:
> >>Recently tests started to fail both at Travis and Circle, but only
> >> with Postgr
On 23 September 2016 at 00:03, Oleg Broytman wrote:
> Hi, all!
>
> On Thu, Aug 25, 2016 at 11:18:45PM +0200, Oleg Broytman
> wrote:
>>Recently tests started to fail both at Travis and Circle, but only
>> with Postgres. Initially I couldn't reproduce the problem locally but
>> after a dozen o
Hi, all!
On Thu, Aug 25, 2016 at 11:18:45PM +0200, Oleg Broytman wrote:
>Recently tests started to fail both at Travis and Circle, but only
> with Postgres. Initially I couldn't reproduce the problem locally but
> after a dozen of experiments I got it: the problem manifests itself
> only with
On Fri, Aug 26, 2016 at 05:49:00PM +0200, Oleg Broytman wrote:
> On Fri, Aug 26, 2016 at 10:42:04AM -0500, Ian Cordasco
> wrote:
> > tox will install sqlobject first and then run the tests against that
> > installed version (ideally). If you just run py.test directly, it might not
> > be install
Hi!
On Fri, Aug 26, 2016 at 10:42:04AM -0500, Ian Cordasco
wrote:
> On Aug 25, 2016 4:19 PM, "Oleg Broytman" wrote:
>
> > Hi, All!
> >
> >Recently tests started to fail both at Travis and Circle, but only
> > with Postgres. Initially I couldn't reproduce the problem locally but
> > after a
On Aug 25, 2016 4:19 PM, "Oleg Broytman" wrote:
> Hi, All!
>
>Recently tests started to fail both at Travis and Circle, but only
> with Postgres. Initially I couldn't reproduce the problem locally but
> after a dozen of experiments I got it: the problem manifests itself
> only with Python 2.7