My main use of SQLAlchemy is in the Python incorporated into Autodesk's Maya graphics program, using the standard MySQL-Python driver. Unfortunately for the most recent Maya 2013 version Autodesk has compiled their Python (2.6.4) with Visual Studio 2010 for Windows, instead of the VS2008 used for official python distributions. This can create issues (two different C runtimes) for packages with C bits (like MySQL-Python) compiled with 2008. I'm looking into compiling the driver myself, but I'm also looking at dropping in an alternate driver temporarily.
The pymysql driver is pure python and supposedly a drop-in replacement for MySQL-Python. I was wondering if anyone has had any real-world experience swapping it in, and know of any gotchas? Our usage doesn't require super-duper performance and isn't doing anything horribly exotic. There is one bit that is still importing MySQLdb directly and doing raw SQL stuff instead of SQLA, which is why a temporary drop-in replacement without a lot of side effects would be appealing. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/M4JjMJhYS9MJ. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
