I built 1.0.7dev from source and can verify that it resolved the issue we
were seeing.
Thanks!
Troy
On Wednesday, July 1, 2015 at 12:20:17 PM UTC-5, Michael Bayer wrote:
>
> resolved in master / rel_1_0
>
>
> On 7/1/15 1:01 PM, Mike Bayer wrote:
>
> after two reports, it is:
> https://bitbu
resolved in master / rel_1_0
On 7/1/15 1:01 PM, Mike Bayer wrote:
after two reports, it is:
https://bitbucket.org/zzzeek/sqlalchemy/issue/3469/comparison-in-persistencepy-can-trip-up-on
On 7/1/15 12:23 PM, Troy Toman wrote:
I am seeing a behavior similar to Issue #3402 but it exists in
SQL
after two reports, it is:
https://bitbucket.org/zzzeek/sqlalchemy/issue/3469/comparison-in-persistencepy-can-trip-up-on
On 7/1/15 12:23 PM, Troy Toman wrote:
I am seeing a behavior similar to Issue #3402 but it exists in
SQLAlchemy 1.0.6 and it involves using geoalchemy2. I have filed an
is
I am seeing a behavior similar to Issue #3402 but it exists in SQLAlchemy
1.0.6 and it involves using geoalchemy2. I have filed an issue there but
since it is behaving differently in sqlalchemy 0.9.3, I wanted to raise it
here as well.
Test program:
import geoalchemy2
from sqlalchemy imp
