On Tue, Jul 13, 2010 at 5:13 PM, Leonardo Rochael Almeida
> The latest Zope 2.12.9 release broke the last release of Products.ZMySQLDA.
You are not by any chance interested in taking over maintenance of
ZSQLMethods, are you?
> You'll get the following traceback:
> Traceback (most recent call last):
> File "bin/py", line 107, in <module>
> exec _val
> File "<string>", line 1, in <module>
> line 90, in <module>
> import DA
> line 243, in <module>
> line 77, in __init__
> stat_info = os.stat(path)
> OSError: [Errno 2] No such file or directory:
> The most trivial fix seems fairly obvious: ZMySQLDA should carry its
> own icon, but in any case, Zope 2.12 should not break compatibility in
> the middle of a stable series. I strongly suspect other Zope2 DB
> adapters to suffer from the same problem.
We documented it pretty clearly in the Zope 2.12.0 release notes, that
you can no longer rely on software home or zope home. See for example
The code should have long been changed to import Shared.DC.ZRDB and
then os.path.join(ZRDB.__file__, 'www', 'DBAdapterFolder_icon.gif') or
better yet use its own icon. Both of these would have worked with all
> I'm not sure what the proper fix should be. App.ImageFile.ImageFile
> could grow support for icons outside of software_home, or perhaps the
> spinning-off of Shared.DC.ZRDB should be delayed to the 2.13 series
> only, but in any case the 2.12 branch should be a safe upgrade for
> third party code as much as reasonably possible.
We don't make guarantees on internals. Zope 2 always had a policy of
allowing minor changes and new features to occur in the stable release
series. It's not just pure bugfix releases.
I think in this case the code in Products.ZMySQLDA should be changed
to be compatible with Zope 2.12.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -