Looking at that issue, and suggested fix... I think you're best going with that route. the stock apple Python is usually pretty bad, and it seems to be the compile settings apple selected, not python. apple's version is often VERY out of date and has some weird settings. It's screwed me and colleagues up a lot. I'd strongly suggest you do the following:
1. Install a second, custom python [ you can get one from Python.org in a click-installer https://www.python.org/download/mac ]. You can then update your bash so that your console user will use that python, and not break anything on your mac. 2. reinstall all pyodbc and everything else into that custom python's site-packages. you actually need to do all this stuff whenever you have a version bump (2.7.7 to 2.7.8), but some packages magically work even if you don't. i've found that "shit just works" when you use a python.org interpreter. On Monday, September 8, 2014 7:04:17 PM UTC-4, Horcle wrote: > Unfortunately, dumping SQL Server (in favor of Oracle) may not be an > option, due to management concerns and other factors. Still working on it. > > However, I did manage to get this working with pymssql. Apparently, there > is a bug with pyodbc and 64-bit python (see > https://community.vertica.com/vertica/topics/mac_pyodbc_string_encoding_issue). > > So, short of applying the fix to the cpp file recompiling pyodbc (see > http://www.vertica-forums.com/viewtopic.php?f=35&t=1863&p=6174#p6174), > the easy solution is to use pymssql. I believe the upgrade I did from Lion > to Mavericks allows use of 64-bit python now, so this makes sense. > > Thanks! > -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
