-
Notifications
You must be signed in to change notification settings - Fork 8
now with py3, MSSQL #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…t pass at mssql. looks like will have to upgrade whole tree to be py3
…MSSQL. Only works on Py3 for unknown reasons relating to pymssql. Probably should emit warnings on py2.
|
so, tox was wigging out over a comment in MSSQL connector file, and now I'm not sure what it dislikes- it may be the fact that my warning will kill py2 when you try to use the MSSQL connector, and this is by design. |
|
Great that you're working on this! Looking at your code, can I conclude that not only do we get a MSSQL plugin, we also get Python 3 support to boot? That'd be awesome. As a sidenote question: why do you require Python 3.6-dev when testing with Tox? edit: I prefer absolute imports over relative nowadays. This is something my colleague and I did wrong when we originally wrote Cornet. Absolute imports seem to be the least ambiguous option, working for both Python 2 and 3. So instead of: We should do: Thoughts? |
|
@fsiler Are you still working on this? |
|
yes, sorry, still alive- I need to dig deeper into the CI and figure out how to get better and working tests, but happy to fix the imports. |
|
Great job here @fsiler, can you fix the issues? |
I don't know what it is about pymssql- had enough trouble getting it working on py3, and then it wouldn't cooperate on py2. I therefore used 2to3 and it didn't horribly mangle anything. I've also added some documentation and thinking, though it probably could use better documentation. There's much more to do, including proper dependencies, but it's a start.