[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Ned Deily added the comment: David, right you are. I verified that the current 3.2.3rc2 without gdbm does correctly recognize a shelve from another Python backed with gdbm 1.10: dbm.error: db type is dbm.gnu, but the module is not available Niklas, yes, to build a Python from source on OS X w

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

R. David Murray added the comment: Ned: that shouldn't prevent whichdb from figuring out the type of the db file, though, if I understand correctly. Niklas: that's unexpected, so I suspect something is not right about how you inserted the print. You did say you were a Python newbie...I think

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Niklas Br added the comment: David, print(magic) returns Shelf.__init__(self, dbm.open(filename, flag), protocol, writeback) AttributeError: 'module' object has no attribute 'open' Ned, I tried the dmg first, but then I downloaded the source and built it locally, does this mean that the

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Ned Deily added the comment: Niklas, the Python 2 and 3 binaries for Mac OS X provided by the python.org installers are not built with support for gdbm, nor are the Apple-supplied system Pythons; Apple does not ship gdbm with OS X. So you can't open a shelve file created in another Python th

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

R. David Murray added the comment: Well, that's the correct line. So if that is what is in your /Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/dbm/__init__.py, then there is a problem. If so, please put the line: print(magic) just before that if statement, and let us kno

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Niklas Br added the comment: Found this: # Check for GNU dbm if magic in (0x13579ace, 0x13579acd, 0x13579acf): return "dbm.gnu" I suppose the .dmg pre-packaged installer was insufficient, so I tried to download the source and compile locally, but that didn't help either. Thanks for takin

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

R. David Murray added the comment: Oh, I meant sticking a print statement into the stdlib code. But I really think your problem is that you aren't running the 3.2.3 stdlib code. Try opening up the file /Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/dbm/__init__.py in your f

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Niklas Br added the comment: accidentally a or two word there :) …please have patience… was what I wanted to say -- ___ Python tracker ___

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Niklas Br added the comment: I'm new to python so please , how do I print what? This? >>> shelve -- ___ Python tracker ___ ___ Pyt

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

R. David Murray added the comment: Oh, actually...are you sure you are running 3.2.3 against the 3.2.3 stdlib? It looks like you might be running against the Apple default installed library, but I don't know enough about OSX to be sure. -- ___ Pyt

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

R. David Murray added the comment: It is, yes. Can you do some debugging and see why it is failing? It should be simple enough to add a print to see what magic number Python is seeing. -- nosy: +r.david.murray ___ Python tracker

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Niklas Br added the comment: This fix should be included in RC2, right? Because I can't get it to work. Amarok:roller niklas$ ls data.db roller.py Amarok:roller niklas$ python3-32 Python 3.2.3rc2 (v3.2.3rc2:428f05cb7277, Mar 18 2012, 00:08:43) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Roundup Robot added the comment: New changeset 14cafb8d1480 by Jesus Cea in branch '2.7': Close #13007: whichdb should recognize gdbm 1.9 magic numbers http://hg.python.org/cpython/rev/14cafb8d1480 New changeset 7a41855b6196 by Jesus Cea in branch '3.2': Close #13007: whichdb should recognize g

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Jesús Cea Avión added the comment: I have a question... What about the endianness of the data?. For instance, if an Intel machine (little endian) creates a GDBM file, can it a) be recognized as such in Sparc (big endian)? b) Can be open and used in Sparc? -- _

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

Changes by Jesús Cea Avión : -- assignee: -> jcea nosy: +jcea versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker ___ __

[issue13007] gdbm 1.9 has new magic that whichdb does not recognize

New submission from Marien Zwart : dbm.whichdb (python 3) and whichdb.whichdb (python 2) only check for "magic == 0x13579ace" to recognize gdbm databases. The recently released gdbm 1.9 series adds 0x13579acd (for "32bit") and 0x13579acf (for "64bit") magics (see src/gdbmconst.h in the gdbm-1.