[issue5359] _dbm extension only built using gdbm on linux

Matthias Klose added the comment: > Ok. Just make sure "make clean; make" works. done. the "make clean" was missing before. -- resolution: -> fixed status: open -> closed ___ Python tracker __

[issue5359] _dbm extension only built using gdbm on linux

Benjamin Peterson added the comment: 2009/4/7 Matthias Klose : > > Matthias Klose added the comment: > > I'm removing the db4.6 check instead. This was useful when building the > _bsddb3 extension, where threading tests would fail on these > architectures. It's not necessary for building the _d

[issue5359] _dbm extension only built using gdbm on linux

Matthias Klose added the comment: I'm removing the db4.6 check instead. This was useful when building the _bsddb3 extension, where threading tests would fail on these architectures. It's not necessary for building the _dbm extension. -- ___ Python tr

[issue5359] _dbm extension only built using gdbm on linux

Benjamin Peterson added the comment: This should be reverted on the py3k branch. The changes to setup.py cause the select module to be loaded and that doesn't work when it hasn't be built! Traceback (most recent call last): File "./setup.py", line 1671, in main() File "./setup.py", lin

[issue5359] _dbm extension only built using gdbm on linux

Matthias Klose added the comment: fixed on the 3.0 and 3.1 branches -- assignee: -> doko resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5359] _dbm extension only built using gdbm on linux

New submission from Matthias Klose : in 3.x the _dbm extension can only be built with gdbm as the backend library. gdbm is licensed under the GPL, so some people/projects like Debian may have objections to build _dbm with the gdbm backend. It gets difficult to determine, which code then uses _dbm