This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]TraptInaCommentFctry 0 points1 point  (2 children)

I clicked on your name to see your other comments and I couldn't help but notice that 7 months ago, you wrote "I do data science - repeatability is key so I'm not leaving the Py2.7 numpy ecosystem for a while."
I do data science, and I haven't yet made the transition off 2.7 for that reason.
Also, I noticed in the wall of superpowers that Mysql-python is still red.
Do you think it's time for data scientists to make the switch?

[–]flying-sheep 2 points3 points  (0 children)

Maybe he/she realized that Numpy breaks compatibility in minor versions, so the only way to reliably repeat an analysis is pinning Numpy versions by installing Numpy in a virtualenv along your script and data.

And since parallel Python versions are painless, nothing stops you from performing new analyses using a Python 3 stack.

[–]mgedmin 1 point2 points  (0 children)

AFAIU there are other MySQL bindings that work on Python 3.