Re: [Zope3-Users] Re: zalchemy - default engine?
Hi, On Tue, Apr 08, 2008 at 11:43:26PM +0200, Martijn Faassen wrote: > Hey,. > > [included: Christian Theune (z3c.sqlalchemy), cc-ed to Andreas Jung > (z3c.sqlalchemy), Laurence Row (collective.lead)] > > On Tue, Apr 8, 2008 at 11:33 PM, Christian Theune <[EMAIL PROTECTED]> wrote: > > On Tue, Apr 08, 2008 at 05:22:31PM -0400, Brandon Craig Rhodes wrote: > [snip] > > > I can't get the new "zalchemy" working even against SQLAlchemy > > > trunk. :-) Might the dependency actually be against an un-merged > > > branch of SQLAlchemy, rather than merely against an unreleased > > > SQLAlchemy trunk? > > > > That's probably right. > > We should really straighten out this situation. I can only use a > branch of collective.lead with a recent sqlalchemy, the z3c.zalchemy > package is evidently broken entirely. I don't know the status of > z3c.sqlalchemy, though I know there's been some activity recently, so > perhaps that Just Works. > > Wouldn't it be possible to factor at least some commonalities into a > base package that all share? And factor out things like container > classes from z3c.sqlalchemy? I know there's been plenty of > cross-fertilization between the packages, but can't we aim for > something better here? Do we really need three? Can't we work > together? > > There must be a reason for this proliferation of integration layers. > People are dissatisfied for whatever reason with one, and create > another. I think it's high time for consolidation. I'm all for this and agree with you. The current situation is because everyone of us had slightly different use cases and the situation they found in the foreign packages wasn't satisfying. Consolidation is a really good idea. Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: zalchemy - default engine?
Hi there, [FYI, before discussion starts here] I've written a new mail with much the same content to zope-dev. Well, it'll appear in a minute. Please take discussion there. Regards, Martijn ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zalchemy - default engine?
I want to claim that "zc.recipe.testrunner" should throw up a traceback when a test hits an "import error", since otherwise it's pretty dratted impossible to tell where the bad import was. When trying to figure out why my application was broken this afternoon (it was because: z3c.zalchemy had been updated to no longer work against any copy of SQLAlchemy I could find), it didn't help that the errors from my test suites were as follows. Trying to run the test suite of my "bottom-level" module, that imports my database tables, gave the result: Running tests at level 1 Test-module import failures: Module: gatech.mage_database.tests.test_docstrings AttributeError: 'module' object has no attribute 'class_state_getter' My next package's test suite, that uses the database tables defined in the first package to create and destroy combinations of objects and model their behavior, gave a quite different error message: Running tests at level 1 Test-module import failures: Module: gatech.iam.tests.test_docstrings Traceback (most recent call last): File "/home/brandon/IamAPI/dev/gatech.iam/src/gatech/iam/__init__.py", line 5, in from .model import ( File "/home/brandon/IamAPI/dev/gatech.iam/src/gatech/iam/model.py", line 15, in from z3c.zalchemy import getSession ImportError: cannot import name getSession Finally, my Grok web application, which presents an XML-RPC interface through which users can manipulate the objects defined in the second package described above, gave this error when I tried to run its test suite: Running tests at level 1 Test-module import failures: Module: iamapi.tests.test_docstrings ImportError: No module named buckets Thank goodness I saw Christian's quick and helpful response to someone here on the mailing list! I would not even have guessed from the above message that z3c.zalchemy was behind every one of those errors. When I downgraded z3c.zalchemy to the previous version, *all three* of the test suites started running again, and succeeded! All three of the above messages, therefore, were each, in some way, trying to complain about the same problem. And yet they look like completely different errors, and only one of them even mentions z3c.zalchemy. I find this somehow depressing, but I'll go eat some dinner and see if that perks me up. (Don't tell ANYONE I said this, but the magic that seems to be involved in the above error messages - the sheer ability of this problem to masquerade as three different problems - reminds me of what I've heard people say about Rails!) -- Brandon Craig Rhodes [EMAIL PROTECTED] http://rhodesmill.org/brandon ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: zalchemy - default engine?
Hey,. [included: Christian Theune (z3c.sqlalchemy), cc-ed to Andreas Jung (z3c.sqlalchemy), Laurence Row (collective.lead)] On Tue, Apr 8, 2008 at 11:33 PM, Christian Theune <[EMAIL PROTECTED]> wrote: > On Tue, Apr 08, 2008 at 05:22:31PM -0400, Brandon Craig Rhodes wrote: [snip] > > I can't get the new "zalchemy" working even against SQLAlchemy > > trunk. :-) Might the dependency actually be against an un-merged > > branch of SQLAlchemy, rather than merely against an unreleased > > SQLAlchemy trunk? > > That's probably right. We should really straighten out this situation. I can only use a branch of collective.lead with a recent sqlalchemy, the z3c.zalchemy package is evidently broken entirely. I don't know the status of z3c.sqlalchemy, though I know there's been some activity recently, so perhaps that Just Works. Wouldn't it be possible to factor at least some commonalities into a base package that all share? And factor out things like container classes from z3c.sqlalchemy? I know there's been plenty of cross-fertilization between the packages, but can't we aim for something better here? Do we really need three? Can't we work together? There must be a reason for this proliferation of integration layers. People are dissatisfied for whatever reason with one, and create another. I think it's high time for consolidation. Regards, Martijn ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: zalchemy - default engine?
On Tue, Apr 08, 2008 at 05:22:31PM -0400, Brandon Craig Rhodes wrote: > Christian Theune <[EMAIL PROTECTED]> writes: > > >> Also : it did not use the latest version of datamanager.py as it > >> gives error trying to get class_state_getter. > > > > That would be the trunk which relies on a (maybe still) unreleased > > version of SQLAlchemy to fix zope.security proxy integration > > problems. > > I can't get the new "zalchemy" working even against SQLAlchemy > trunk. :-) Might the dependency actually be against an un-merged > branch of SQLAlchemy, rather than merely against an unreleased > SQLAlchemy trunk? That's probably right. -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: zalchemy - default engine?
Christian Theune <[EMAIL PROTECTED]> writes: >> Also : it did not use the latest version of datamanager.py as it >> gives error trying to get class_state_getter. > > That would be the trunk which relies on a (maybe still) unreleased > version of SQLAlchemy to fix zope.security proxy integration > problems. I can't get the new "zalchemy" working even against SQLAlchemy trunk. :-) Might the dependency actually be against an un-merged branch of SQLAlchemy, rather than merely against an unreleased SQLAlchemy trunk? I was able to restart my halted development today by asking Subversion specifically for revision -r84044 of z3c.zalchemy rather than HEAD. -- Brandon Craig Rhodes [EMAIL PROTECTED] http://rhodesmill.org/brandon ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
