On 16/01/2013 18:01, Tres Seaver wrote:
from ZDOB.DB import DB # This one can even be ambiguous now
FTR, I don't like this style. Somewhat a matter of taste.
Sure. I don't like using APIs via long, multi-dotted paths.
What Tres said ;-)
- - Nose gives us easy access to Ned Batchelder's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/15/2013 06:11 AM, Jim Fulton wrote:
On Mon, Jan 14, 2013 at 1:32 PM, Tres Seaver tsea...@palladion.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
While working on preparation for a Py3k port, I've stumbled across
a fundamental
On Mon, Jan 14, 2013 at 1:32 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While working on preparation for a Py3k port, I've stumbled across a
fundamental issue with how ZODB structures its API. Do we intend that
client code do the following::
On Mon, Jan 14, 2013 at 7:20 PM, Tres Seaver tsea...@palladion.com wrote:
...
I'm tempted to rename the 'DB.py' module 'db.py', and jam in a BBB entry
in sys.modules for 'ZODB.DB'; likewise, I am tempted to rename the
'FileStorage.py' package 'filestorage', its same-named module
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While working on preparation for a Py3k port, I've stumbled across a
fundamental issue with how ZODB structures its API. Do we intend that
client code do the following::
from ZDOB import DB, FileStorage
db = DB(FileStorage('/path/to/Data.fs'))
On Mon, Jan 14, 2013 at 01:32:07PM -0500, Tres Seaver wrote:
While working on preparation for a Py3k port, I've stumbled across a
fundamental issue with how ZODB structures its API. Do we intend that
client code do the following::
from ZDOB import DB, FileStorage
db =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/14/2013 03:33 PM, Marius Gedminas wrote:
Can you demonstrate the ambiguity? As I've shown before, I was
unable to find it, at least with Python 2.x.
On the filesystem:
$ find src/ZODB/FileStorage/ -name *.py
src/ZODB/FileStorage/fspack.py
