zope.sqlalchemy+py3 test failures.
In case anyone is interested, I've made a stab at porting zope.sqlalchemy to Python 3 at http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several tests still fail. I could use some help fixing them. To run the test suite: - Create a Python 3.2 virtualenv. - Install nose into the virtualenv. - Check out the "chrism-py3" transaction branch from svn://svn.zope.org/repos/main/transaction/branches/chrism-py3 - Install the "chrism-py3" transaction checkout into the virtualenv, e.g. $env32/bin/python setup.py develop. - Install this package into the virtualenv eg. run $env32/bin/python setup develop. - Run $env32/bin/python setup.py nosetests. Currently 2 tests fail: [chrism@thinko zope.sqlalchemy]$ env32/bin/python setup.py test running test running egg_info writing requirements to src/zope.sqlalchemy.egg-info/requires.txt writing src/zope.sqlalchemy.egg-info/PKG-INFO writing namespace_packages to src/zope.sqlalchemy.egg-info/namespace_packages.txt writing top-level names to src/zope.sqlalchemy.egg-info/top_level.txt writing dependency_links to src/zope.sqlalchemy.egg-info/dependency_links.txt writing manifest file 'src/zope.sqlalchemy.egg-info/SOURCES.txt' running build_ext testTwoEngines (zope.sqlalchemy.tests.MultipleEngineTests) ... ok testRetry (zope.sqlalchemy.tests.RetryTests) ... ERROR testRetryThread (zope.sqlalchemy.tests.RetryTests) ... ERROR testAbortAfterCommit (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testAbortBeforeCommit (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testBulkDelete (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testBulkUpdate (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testCommit (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testCommitWithSavepoint (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testMarkUnknownSession (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testRelations (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testRollbackAttributes (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testSavepoint (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testSimplePopulation (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testThread (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testTransactionJoining (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testTwoPhase (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok ====================================================================== ERROR: testRetry (zope.sqlalchemy.tests.RetryTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1633, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/default.py", line 327, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: no such table: test_users The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/tests.py", line 513, in setUp self.tm1.commit() File "/home/chrism/projects/transaction/transaction/_manager.py", line 89, in commit return self.get().commit() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 342, in commit reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 333, in commit self._commitResources() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 473, in _commitResources reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 445, in _commitResources rm.tpc_begin(self) File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/datamanager.py", line 87, in tpc_begin self.session.flush() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1493, in flush self._flush(objects) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1562, in _flush flush_context.execute() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 327, in execute rec.execute(self) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 471, in execute uow File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/mapper.py", line 2147, in _save_obj execute(statement, multiparams) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1399, in execute params) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1532, in _execute_clauseelement compiled_sql, distilled_params File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1640, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1777, in _handle_dbapi_exception from e sqlalchemy.exc.OperationalError: (OperationalError) no such table: test_users 'INSERT INTO test_users (id, firstname, lastname) VALUES (?, ?, ?)' (1, 'udo', 'juergens') ====================================================================== ERROR: testRetryThread (zope.sqlalchemy.tests.RetryTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1633, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/default.py", line 327, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: no such table: test_users The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/tests.py", line 513, in setUp self.tm1.commit() File "/home/chrism/projects/transaction/transaction/_manager.py", line 89, in commit return self.get().commit() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 342, in commit reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 333, in commit self._commitResources() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 473, in _commitResources reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 445, in _commitResources rm.tpc_begin(self) File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/datamanager.py", line 87, in tpc_begin self.session.flush() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1493, in flush self._flush(objects) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1562, in _flush flush_context.execute() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 327, in execute rec.execute(self) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 471, in execute uow File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/mapper.py", line 2147, in _save_obj execute(statement, multiparams) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1399, in execute params) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1532, in _execute_clauseelement compiled_sql, distilled_params File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1640, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1777, in _handle_dbapi_exception from e sqlalchemy.exc.OperationalError: (OperationalError) no such table: test_users 'INSERT INTO test_users (id, firstname, lastname) VALUES (?, ?, ?)' (1, 'udo', 'juergens') ---------------------------------------------------------------------- Ran 17 tests in 0.152s FAILED (errors=2) This appears to be some sort of Py3+SQLite thing, beacuse if I run the tests using Postgres isntead of SQLALchemy (after "env32/bin/easy_install py-postgresql", and then running the tests using 'TEST_DSN="postgresql+pypostgresql://localhost:5432/testing" env32/bin/python setup.py nosetests' against Postgres 8.4.8 after a "createdb testing"), I get different failures: ====================================================================== FAIL: testRetryThread (zope.sqlalchemy.tests.RetryTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/tests.py", line 564, in testRetryThread self.assertTrue(retryable, "Error should be retryable") AssertionError: None is not true : Error should be retryable -------------------- >> begin captured logging << -------------------- txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: commit <zope.sqlalchemy.datamanager.SessionDataManager object at 0x2dd6ed0> txn.140333906949888: DEBUG: commit txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: commit <zope.sqlalchemy.datamanager.SessionDataManager object at 0x2dda9d0> txn.140333906949888: DEBUG: commit txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: abort txn.140333906949888: DEBUG: abort --------------------- >> end captured logging << --------------------- ---------------------------------------------------------------------- Ran 18 tests in 5.099s FAILED (failures=1)
On 27/09/2011 02:47, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting zope.sqlalchemy to Python 3 at http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several tests still fail. I could use some help fixing them.
Have you tried running the tests by building the buildout instead? (that's making a huge assumption that zc.buildout and zope.testing work on Py3, which I guess isn't the case...) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Tue, 2011-09-27 at 06:43 +0100, Chris Withers wrote:
On 27/09/2011 02:47, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting zope.sqlalchemy to Python 3 at http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several tests still fail. I could use some help fixing them.
Have you tried running the tests by building the buildout instead? (that's making a huge assumption that zc.buildout and zope.testing work on Py3, which I guess isn't the case...)
I'm not sure how to do it under Python 3, and I may be sufficiently unmotivated to figure it out without some help. ;-) The tests indeed pass on python 2 using bin/test though, so if I could get the testrunner running the tests under Py3, they would also at this point. - C
On Mon, 2011-09-26 at 21:47 -0400, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting zope.sqlalchemy to Python 3 at http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several tests still fail. I could use some help fixing them.
To run the test suite:
- Create a Python 3.2 virtualenv.
- Install nose into the virtualenv.
- Check out the "chrism-py3" transaction branch from svn://svn.zope.org/repos/main/transaction/branches/chrism-py3
- Install the "chrism-py3" transaction checkout into the virtualenv, e.g. $env32/bin/python setup.py develop.
- Install this package into the virtualenv eg. run $env32/bin/python setup develop.
- Run $env32/bin/python setup.py nosetests.
Currently 2 tests fail:
Mike Merickel solved this... This is because the setuptools (and nose) testrunners do not respect the ``test_suite`` stanza at the bottom of ``tests.py``; these shouldn't be getting run unless the DSN has postgres in it, and they are getting run regardless (under sqlite). That brings up how to cope with running test suites that depend on zope.testrunner features in a cross-platform way. Currently the bootstrap script in this package wont run under Py3. - C
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/27/2011 02:01 AM, Chris McDonough wrote:
On Mon, 2011-09-26 at 21:47 -0400, Chris McDonough wrote:
In case anyone is interested, I've made a stab at porting zope.sqlalchemy to Python 3 at http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several tests still fail. I could use some help fixing them.
To run the test suite:
- Create a Python 3.2 virtualenv.
- Install nose into the virtualenv.
- Check out the "chrism-py3" transaction branch from svn://svn.zope.org/repos/main/transaction/branches/chrism-py3
- Install the "chrism-py3" transaction checkout into the virtualenv, e.g. $env32/bin/python setup.py develop.
- Install this package into the virtualenv eg. run $env32/bin/python setup develop.
- Run $env32/bin/python setup.py nosetests.
Currently 2 tests fail:
Mike Merickel solved this...
This is because the setuptools (and nose) testrunners do not respect the ``test_suite`` stanza at the bottom of ``tests.py``; these shouldn't be getting run unless the DSN has postgres in it, and they are getting run regardless (under sqlite).
That brings up how to cope with running test suites that depend on zope.testrunner features in a cross-platform way. Currently the bootstrap script in this package wont run under Py3.
This bootstrap is from Jim's '2' branch of zc.buildout: http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484... It is designed to work with Py3k. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6B/IYACgkQ+gerLs4ltQ6XOwCeNuYNhjXbasb5Qfr729Howd5N 6sAAoIpnbXpvLMP340cyt3PghRjrah34 =933g -----END PGP SIGNATURE-----
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484...
It is designed to work with Py3k.
I've replaced the bootstrap.py in the chrism-py3 branch of both the transaction package and the zope.sqlalchemy packages with that one, and everything looks good! I think we can probably merge both of these branches to their respective trunks and make releases. I have the necessary powers to do it for transaction; I'll try to track down elro to see if he's willing to do it for zope.sqlalchemy. - C
On 29 September 2011 10:33, Chris McDonough <chrism@plope.com> wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484...
It is designed to work with Py3k.
I've replaced the bootstrap.py in the chrism-py3 branch of both the transaction package and the zope.sqlalchemy packages with that one, and everything looks good!
I think we can probably merge both of these branches to their respective trunks and make releases. I have the necessary powers to do it for transaction; I'll try to track down elro to see if he's willing to do it for zope.sqlalchemy.
I've added chrism as an owner. Before we make a final release I'd like to revisit the savepoint release branches of transaction / zope.sqlalchemy. I'll bring this up in another mail. Laurence
On 29/09/2011 15:22, Laurence Rowe wrote:
On 29 September 2011 10:33, Chris McDonough<chrism@plope.com> wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484...
It is designed to work with Py3k.
I've replaced the bootstrap.py in the chrism-py3 branch of both the transaction package and the zope.sqlalchemy packages with that one, and everything looks good!
I think we can probably merge both of these branches to their respective trunks and make releases. I have the necessary powers to do it for transaction; I'll try to track down elro to see if he's willing to do it for zope.sqlalchemy.
I've added chrism as an owner. Before we make a final release I'd like to revisit the savepoint release branches of transaction / zope.sqlalchemy. I'll bring this up in another mail.
It'd also be great if we could get support for SA 0.7+'s new events system... cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On 29 September 2011 16:51, Chris Withers <chris@simplistix.co.uk> wrote:
It'd also be great if we could get support for SA 0.7+'s new events system...
I'm not convinced this will give any benefit. Currently we just require:
Session = scoped_session(sessionmaker(bind=engine, ... extension=ZopeTransactionExtension()))
Instead we would require something like:
Session = scoped_session(sessionmaker(bind=engine)) ext = ZopeTransactionExtension() event.listen(Session, "after_attach", ext.after_attach) event.listen(Session, "after_begin", ext.after_begin) event.listen(Session, "after_flush", ext.after_flush) event.listen(Session, "after_bulk_update", ext.after_bulk_update) event.listen(Session, "after_bulk_delete", ext.after_bulk_delete) event.listen(Session, "before_commit", ext.before_commit)
Though this could become:
Session = scoped_session(sessionmaker(bind=engine)) ZopeTransactionExtension(Session)
I'm just not sure that it's worthwhile. Laurence
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
On 29 September 2011 10:33, Chris McDonough <chrism@plope.com> wrote:
On Tue, 2011-09-27 at 12:40 -0400, Tres Seaver wrote:
This bootstrap is from Jim's '2' branch of zc.buildout:
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484...
It is designed to work with Py3k.
I've replaced the bootstrap.py in the chrism-py3 branch of both the transaction package and the zope.sqlalchemy packages with that one, and everything looks good!
I think we can probably merge both of these branches to their respective trunks and make releases. I have the necessary powers to do it for transaction; I'll try to track down elro to see if he's willing to do it for zope.sqlalchemy.
I've added chrism as an owner. Before we make a final release I'd like to revisit the savepoint release branches of transaction / zope.sqlalchemy. I'll bring this up in another mail.
Sorry I haven't merged the transaction stuff to trunk yet. While doing a review, I realize that one downside to doing this merge is that it will kill Python 2.4 and 2.5 compatibility. I think this is a reasonable thing, given that Python 2.5 will no longer get any maintenance as of today or so, and Python 2.4 hasn't gotten any for a long time, and folks who need a 2.4/2.5 compat version can always use an older version. That said, before I go ahead and do this merge, is there anyone who believes we should continue to support 2.4 and 2.5 in the transaction package? If so, for how long? - C
On Sat, 2011-10-01 at 03:28 -0400, Chris McDonough wrote:
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
I've added chrism as an owner. Before we make a final release I'd like to revisit the savepoint release branches of transaction / zope.sqlalchemy. I'll bring this up in another mail.
Sorry I haven't merged the transaction stuff to trunk yet.
While doing a review, I realize that one downside to doing this merge is that it will kill Python 2.4 and 2.5 compatibility. I think this is a reasonable thing, given that Python 2.5 will no longer get any maintenance as of today or so, and Python 2.4 hasn't gotten any for a long time, and folks who need a 2.4/2.5 compat version can always use an older version.
That said, before I go ahead and do this merge, is there anyone who believes we should continue to support 2.4 and 2.5 in the transaction package? If so, for how long?
Nobody responded to this, so I've merged the chrism-py3 branch into the trunk. Any word on the savepoint release branch featureset before I make a release? - C
On Wed, 2011-10-12 at 06:07 -0400, Chris McDonough wrote:
On Sat, 2011-10-01 at 03:28 -0400, Chris McDonough wrote:
On Thu, 2011-09-29 at 15:22 +0100, Laurence Rowe wrote:
I've added chrism as an owner. Before we make a final release I'd like to revisit the savepoint release branches of transaction / zope.sqlalchemy. I'll bring this up in another mail.
Sorry I haven't merged the transaction stuff to trunk yet.
While doing a review, I realize that one downside to doing this merge is that it will kill Python 2.4 and 2.5 compatibility. I think this is a reasonable thing, given that Python 2.5 will no longer get any maintenance as of today or so, and Python 2.4 hasn't gotten any for a long time, and folks who need a 2.4/2.5 compat version can always use an older version.
That said, before I go ahead and do this merge, is there anyone who believes we should continue to support 2.4 and 2.5 in the transaction package? If so, for how long?
Nobody responded to this, so I've merged the chrism-py3 branch into the trunk.
Any word on the savepoint release branch featureset before I make a release?
I'm going to make a new major release of the transaction package tomorrow (without the savepoint release features, and bw incompat with 2.4 and 2.5), unless I hear otherwise. - C
On Sun, 2011-12-04 at 22:12 -0500, Chris McDonough wrote:
I'm going to make a new major release of the transaction package tomorrow (without the savepoint release features, and bw incompat with 2.4 and 2.5), unless I hear otherwise.
transaction 1.2.0 released with Py3 compat (and removing Py2.4 and Py2.5) compatibility. Tested against the ztk trunk tests under Python 2.6. - C
Tomorrow, I plan to: - Merge the chrism-py3 branch of zope.sqlalchemy into its trunk. (http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/) to get Python 3 compatibility. - Once the compat branch is merged, I'll make a 0.7 release of zope.sqlalchemy. Any dissent? - C
On Mon, Dec 05, 2011 at 04:21:51PM -0500, Chris McDonough wrote:
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk. (http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/) to get Python 3 compatibility.
- Once the compat branch is merged, I'll make a 0.7 release of zope.sqlalchemy.
Any dissent?
None from me! This all looks like great work. -- Brian Sutherland
On Mon, 2011-12-05 at 16:21 -0500, Chris McDonough wrote:
Tomorrow, I plan to:
- Merge the chrism-py3 branch of zope.sqlalchemy into its trunk. (http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/) to get Python 3 compatibility.
- Once the compat branch is merged, I'll make a 0.7 release of zope.sqlalchemy.
Any dissent?
I've merged the chrism-py3 branch to trunk and I've made a 0.7 release from the resulting trunk to PyPI. - C
participants (5)
-
Brian Sutherland -
Chris McDonough -
Chris Withers -
Laurence Rowe -
Tres Seaver