delta/python-packages/sqlalchemy.git, branch pr/231 github.com: zzzeek/sqlalchemy.git - properly handle negative indexes in RowProxy.__getitem__() 2016-01-28T08:04:40+00:00 Lele Gaifax lele@metapensiero.it 2016-01-28T08:04:40+00:00 f84ef1f83cc64a5ea3a910b8d1bdf00b05e9ceab 






- experimental - try out a very open ended design for the factors, assume
2016-01-27T22:39:48+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-27T22:39:48+00:00

086ad9ce6413e73f93506523d4eb8e23710443dc

many more combinations of factors are possible and basically make them
more akin to command options at the tox level.





many more combinations of factors are possible and basically make them
more akin to command options at the tox level.







- reinstate "dont set up integer index in keymap if we're on cexts",
2016-01-27T19:49:40+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-27T19:49:40+00:00

516a442f233d90eb7b8bb844e2dea7865bb21f66

and this time also fix the cext itself to properly handle int vs. long
on py2k





and this time also fix the cext itself to properly handle int vs. long
on py2k







- restore the use of PYTHONNOUSERSITE that was removed
2016-01-27T19:23:33+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-27T19:23:33+00:00

49dfeda6d7578aeae9ec954945cda38ee5aae6a9

in df3f125bd84fc7ec5d45592c5774daf3a39d9bc9, this flag is
explicitly checked within conftest.py and we need to continue to use
it, otherwise a tox build inside of .tox that isn't usedevelop
is ignored, including C extensions
- rework the whole system of running with coverage, so that
with coverage, we *are* using usedevelop, but also make sure
we rm the .so files for nocext, make sure we --cov-append, etc.





in df3f125bd84fc7ec5d45592c5774daf3a39d9bc9, this flag is
explicitly checked within conftest.py and we need to continue to use
it, otherwise a tox build inside of .tox that isn't usedevelop
is ignored, including C extensions
- rework the whole system of running with coverage, so that
with coverage, we *are* using usedevelop, but also make sure
we rm the .so files for nocext, make sure we --cov-append, etc.







Revert "- dont set up integer index in keymap if we're on cexts"
2016-01-27T17:41:01+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-27T17:41:01+00:00

8aa95fa2cd0e15b77af3e5976436adc6ed6123b9

This reverts commit de0d144a395c31eb74084177df95a4858b830f88.

Apparently the test suite is not using the cextensions correctly at the moment.





This reverts commit de0d144a395c31eb74084177df95a4858b830f88.

Apparently the test suite is not using the cextensions correctly at the moment.







- dont set up integer index in keymap if we're on cexts
2016-01-27T16:35:43+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-27T16:35:43+00:00

de0d144a395c31eb74084177df95a4858b830f88












fix %x string format to compatible with Python 3.5
2016-01-27T08:21:59+00:00

Ruilin Huang
cxghrl@gmail.com

2016-01-27T08:21:59+00:00

4b9f6f407ceedde247982501a6ae406242c80b4a












fix %x string format to compatible with Python 3.5
2016-01-27T08:10:06+00:00

xghrl
cxghrl@gmail.com

2016-01-27T08:10:06+00:00

324e532d6081d9b9ea90bf3945cecfc792264f8d












- unfortunately we need to match within join where col.key does not match
2016-01-26T22:28:40+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-26T22:28:40+00:00

5742e321b261c0c1303835b80418cd3cdc1b5643

what's given so we need to use a set() here.  contains_column is not within
any performance paths





what's given so we need to use a set() here.  contains_column is not within
any performance paths







- rework ColumnCollection to no longer persist "all_col_set"; we don't
2016-01-26T21:41:26+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-26T21:41:26+00:00

8163de4cc9e01460d3476b9fb3ed14a5b3e70bae

need this collection except in the extend/update uses where we
create it ad-hoc.  simplifies pickling.  Compatibility with 1.0
should be OK as ColumnColleciton uses __getstate__ in any case
and the __setstate__ contract hasn't changed.
- Fixed bug in :class:`.Table` metadata construct which appeared
around the 0.9 series where adding columns to a :class:`.Table`
that was unpickled would fail to correctly establish the
:class:`.Column` within the 'c' collection, leading to issues in
areas such as ORM configuration.   This could impact use cases such
as ``extend_existing`` and others.  fixes #3632





need this collection except in the extend/update uses where we
create it ad-hoc.  simplifies pickling.  Compatibility with 1.0
should be OK as ColumnColleciton uses __getstate__ in any case
and the __setstate__ contract hasn't changed.
- Fixed bug in :class:`.Table` metadata construct which appeared
around the 0.9 series where adding columns to a :class:`.Table`
that was unpickled would fail to correctly establish the
:class:`.Column` within the 'c' collection, leading to issues in
areas such as ORM configuration.   This could impact use cases such
as ``extend_existing`` and others.  fixes #3632