On Fri, Oct 25, 2019 at 11:35:08AM +0000, Cristián Maureira-Fredes wrote: > Could it be possible to evaluate a migration in your case? > there are many tools also that can help you moving forward to use > Python 3, maybe something like that could speed up things? [2] > > [2] 2to3 executable in Python 3 versions.
The usual way projects take nowadays is to first switch to a polyglot (2 + 3) codebase using libraries like "six", then remove the compatibility layer when they're ready to drop Python 2 support. That way, it's easier to do things incrementally rather than all in one go. Some more useful resources, FWIW: https://portingguide.readthedocs.io/ ("It mainly targets projects with large, conservative codebases.") http://python3porting.com/ https://docs.python.org/3/howto/pyporting.html Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ PySide mailing list PySide@qt-project.org https://lists.qt-project.org/listinfo/pyside
