3 ms·
I'm curious, what issues do you run into with python3 incompatibility? Most scientific stuff I've done works in python3. In fact, its now possible to run a ten
by joshuamorton 9y ago
I'm curious, what issues do you run into with python3 incompatibility?
Most scientific stuff I've done works in python3. In fact, its now possible to run a tensorflow/opencv/scipy environment entirely from pip in a virtualenv, though it won't be the fastest. which is amazing. Doing that kind of thing in any other language would require docker.
In general, if you're sticking to python3, the answer will always be "use pip", everything should work with pip, and everything should install as a binary without needing to build source.
Edit:
There's exactly one context where I use python2, and its for a robotics project where some transitive dependencies are python2 only.
- photojosh 9y agoWhy won't it be the fastest? I didn't think there would be any difference between "native" in the system paths and in a virtualenv.
- joshuamorton 9y agoSo, for things like tensorflow, you have to build from source to enable certain optimizations. Wheel's aren't source builds essentially.
- kranner 9y agoI think GP is talking about virtualenv, not pip. Using an optimized build in a virtualenv environment should not be any slower than using it outside the environment, right?
- joshuamorton 9y agoAh yes, that's true as far as I know.