Fabien <fabien.mauss...@gmail.com>:

> But this was exactly my point! Today in 2015 it's incredibly easy to
> write py2/py3 code for a scientist. The whole SciPy track has done the
> transition. Not an issue anymore either, for me at least (python
> youngster ;-)

I write both Py2 and Py3 code, but I keep the two worlds hermetically
separated from each other.


Marko
-- 
https://mail.python.org/mailman/listinfo/python-list

Reply via email to