Closed GoogleCodeExporter closed 9 years ago
I'd second this. I tried using the instructions attached to issue 178 to get
it working with SQLAlchemy, Python 3.2, and Windows 7 Professional, and there
are problems. I'd like to be certain things work on the ODBC driver side
before I go pestering the SQLAlchemy folks about this.
There is currently no Python library that (a) can access MSSQL (b) in python
3.2 (c) and work with SQLAlchemy (d) on Windows. ceODBC compiles, connects,
and runs, but doesn't integrate with SQLAlchemy. The SQLAlchemy folks don't
want to add yet another MSSQL-capable ODBC library to the MSSQL dialects for
SQLAlchemy, so they'd prefer that one of the existing libraries gains Python
3.2 support. I understand this is not the problem of the developer of pyodbc,
but it points to a need.
pymssql is in a similar state right now--working towards a 2.0 branch that
should be Python 3.2 capable, but nothihg publicly accessible works right now.
I did try pulling down the v31 branch and the associated fixes branch, but
couldn't get either one to compile alone without the patches in issue 178.
I'd be willing to assist in testing/debugging to move this along.
Original comment by kozmik...@gmail.com
on 30 Jun 2011 at 8:09
Please try the "py3" beta releases...
Original comment by mkleehammer
on 13 Sep 2011 at 11:17
Original comment by mkleehammer
on 27 Dec 2011 at 1:02
Original issue reported on code.google.com by
JoeSalm...@hotmail.com
on 3 Mar 2011 at 12:50