On Thu, Nov 28, 2019 at 10:02 AM Brett Cannon <br...@python.org> wrote:
> But there is other things that might break your code between releases, > such as bug fixes, language changes that become the default, etc. Are > deprecations the biggest pain point in transitioning to a new Python > version for people, or is it just part of a greater culmination of changes? > I just started the 3.7 -> 3.8 migration on our codebase yesterday, so this is fresh in my mind (about 500k LOC with 72 external packages plus four home-built extension modules, three of which use SWIG wrapping). My biggest pain point is making the external extension modules work due to API changes; deprecations are only a minor issue, although that's probably because we turn all warnings on during development and clean things up as soon as they appear (if there are any win32.pywintypes devs listening, fix that use of the old imp module at line 2). Things I fixed quickly include some int vs float warnings in our GUI code, replacing the call to create a new CodeType object with a code.replace, and repair some SyntaxWarnings where "is" had crept into places where "==" should have been used. So, all good improvements to the code and I've spent far longer thus far on other aspects of the porting. I would be on the side of "sooner is better", with three releases of deprecated, we-really-mean-it and gone.
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/MAPZHRVXLWLOOEP2US3P6UUNFN6JWPKS/ Code of Conduct: http://python.org/psf/codeofconduct/
