3 ms·
So development on the author’s Molecular Modeling Toolkit will stop, I see that. But it sounds like these older packages can still be used, it’s just that scien
by Myrmornis 8y ago
So development on the author’s Molecular Modeling Toolkit will stop, I see that. But it sounds like these older packages can still be used, it’s just that scientists can’t blindly run everything on the same python installation. But with pyenv/virtualenv, or dockerized versions of python2, it should be perfectly possible to keep using them for a very long time. For the same reason, the author’s comment that scientific python scripts tend not to be usable after 5 or more years seems not entirely accurate.
However, it wom’t be possible to use them together in the same project with modern python3 code. So that’s bad. I wonder whether one option is to create a dockerized version of the library runnng against python2 and the write a serialization/deserialization layer allowing the old API to be implemented in python3?
- Myrmornis 8y agoI asked the author; he says that there would be too much serialization/deserialization overhead. https://twitter.com/khinsen/status/996046318773657600 https://twitter.com/khinsen/status/996046318773657600