Re: extended_setup.py MIA?
Gerhard Häring <[email protected]>
| Newsgroups | gmane.comp.python.db.pysqlite.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patrick Phalen wrote: > On 6/19/07, *Martin Jenkins* <pysqlite-Vfh7fEhEWOlaa/[email protected] > <mailto:pysqlite-Vfh7fEhEWOlaa/[email protected]>> wrote: > Gerhard's 12:17 announcement said it was in svn, so perhaps it's /only/ > > in svn? > > > I'm not sure what you mean by "12:17 announcement." > > Today's announcement of the release of 2.3.4 says, in CHANGES, to use > that command. > > However, I did go to svn and get exended_setup.py. On running that per > instructions, it complains that ez_setup can't be imported. Apparently, > reading the source on ez_setup.py, it should also be included with > extended_setup.py, in the same directory. > > So, I suspect pysqlite 2.3.4 has been released prematurely? Shit happens. I did the usual QA on the release, unfortunately that did not include compiling using extended_setup.py. That file is there since pysqlite 2.0.6 and was missing from all release tarballs since then. But now it's fixed. Sorry for the trouble. > Nevertheless, I've manually copied both extended_setup.py, ez_setup.py > and the sqlite3.c and sqlite3.h into pysqlite-2.3.4 and run the command. > That yields this error: > > running build_static > [...] > src/connection.h:33:21: sqlite3.h: No such file or directory [...] Maybe it's a gcc-on-FreeBSD issue. You could try removing the include_dirs line from setup.cfg. Did you copy it into the right directory, i. e. alongside setup.py, *not* into src/ ? - -- Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGeFAzdIO4ozGCH14RAkDCAJ4suVY4myAPPdpbsRMpSMdQywDWWwCgqTo3 2kzgKu6/d217QxzABySHo/k= =ommu -----END PGP SIGNATURE-----