Re: Can someone here shed some light on this ctypes/sqlite3 failure?
Gerhard Häring <[email protected]>
| Newsgroups | gmane.comp.python.db.pysqlite.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [email protected] wrote: > [...] > The workaround is (hopefully) to guarantee that the sqlite3 module is > imported before you begin mucking around with any of Apple's libraries which > depend on CoreData. This is a link I looked at yesterday: https://develop.participatoryculture.org/trac/democracy/browser/trunk/tv/platform/osx/Miro.py?rev=4717 """ # Import the pysqlite module as soon as possible to avoid (very) weird # errors ("library routine called out of sequence") probably due to a # conflict between the standard OS X sqlite lib and our own most recent # one. from pysqlite2 import dbapi2 """ They seem to have the same problem. > For an application writer this may be feasible. For > Python I think we need to find a library to load in test_ctypes which > doesn't depend on CoreData. (I imagine Thomas picked GLUT because it is > widely available across platforms.) Or just change the order of tests and make sure the sqlite3 test is run before the ctypes test. Probably best to put it at the start of the list of test suites. - -- Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGhsyHdIO4ozGCH14RAqu3AJ9gB6kunYbt1U3KKGEw2OfDz+ZvdACeNM0C zdX+cJRgxIUdpp6mljx0BBk= =Zcxk -----END PGP SIGNATURE-----