Alright, thanks! I would try to submit the PR. But it does look like a transitional package to me. How do we generally handle such upstream changes anyway?
On Monday, June 1, 2015 at 9:06:20 AM UTC+5:30, Michael Bayer wrote: > > > > On 5/31/15 8:58 PM, Fayaz Yusuf Khan wrote: > > On Sunday 31 May 2015 11:06:32 AM Mike Bayer wrote: > >> pysqlcipher is right here: > >> > >> > http://docs.sqlalchemy.org/en/rel_1_0/dialects/sqlite.html#module-sqlalchemy > >> .dialects.sqlite.pysqlcipher > >> > >> SQLAlchemy supports Python 2K and Python 3K in place though the above > >> dialect has probably not been tested on Py3K. > > pysqlcipher does not support Py3K. > > https://github.com/leapcode/pysqlcipher/issues/3 > > It's a known issue. > > you can send in "pysqlcipher3" to create_engine() using the "dbapi" > argument: > > import pysqlcipher3 > e = create_engine("sqlite+pysqlcipher:///file.db", dbapi=pysqlcipher3) > > feel free to submit a PR that returns this DBAPI from the "dbapi" method > under py3k: > > > > https://bitbucket.org/zzzeek/sqlalchemy/src/0766c80b9c02fdbad3203835ab850ad690f4c03b/lib/sqlalchemy/dialects/sqlite/pysqlcipher.py?at=master#cl-82 > > > > > > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
