Well so first i edited the file setup.cfg as suggested from Arthur,
the package seems installed correctly, but "setup.py build" returned
to me this output:

/usr/bin/ld: for architecture ppc
/usr/bin/ld: warning /usr/local/lib/libsqlite3.dylib cputype (7,
architecture i386) does not match cputype (18) for specified -arch
flag: ppc (file not loaded)

Why pysqlite builds as power pc architeture?

Anyway i tried the pysqlite test and no errorrs:

""
from pysqlite2 import test

In [4]: test.test()
.............................................................................................................................................................................
----------------------------------------------------------------------
Ran 173 tests in 0.220s

OK
""

Also SQLAlchemy don't show errors anymore.
So i'm fine?

Thanks all for the great help!


On 7 Mag, 17:16, mike bayer <[EMAIL PROTECTED]> wrote:
> just a heads up about a few things regarding this:
>
> the errors that SQLite fixes in version 3.3.13 was probably introduced
> in sqlite 3.3.9, and its this ticket:
>
> http://www.sqlite.org/cvstrac/tktview?tn=2211
>
> to see how well your sqlite version works, run the unit tests.  they
> pass 100% with sqlite 3.3.13 .
>
> to know immediately what version of sqlite your pysqlite is bound to:
>
> using pysqlite2:
>
> >>> from pysqlite2 import dbapi2 as dbapi
> >>> dbapi.sqlite_version
>
> '3.3.13'
>
> using py2.5's builtin sqlite:
>
> >>> import sqlite3
> >>> sqlite3.sqlite_version
>
> '3.3.5'
>
> note that SQLAlchemy imports sqlite like this (i.e. importing an
> external pysqlite2 first, then the sqlite3 built in):
>
>         try:
>             from pysqlite2 import dbapi2 as sqlite
>         except ImportError, e:
>             try:
>                 from sqlite3 import dbapi2 as sqlite #try the 2.5+
> stdlib name.
>             except ImportError:
>                 try:
>                     sqlite = __import__('sqlite') # skip ourselves
>                 except ImportError:
>                     raise e
>
> this behavior can be overridden by passing in a sqlite module directly
> to create_engine:
>
> create_engine('sqlite://', module=sqlite3)


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to