You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Excerpts from Windows' mmreg.h (from Windows SDK 10.0.19041.0) relating to RIFF WAVE files
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
But a lot of modern Python code still depends on it. This is a problem because as the years drag on, we will begin to forget the differences. The data for conversions can become lost. It is important to update now while we still remember.
While it'd be nice to just tell everyone to update their modules, transitions are not always simple (I should know). So the only way to resolve Python2 dependencies is to send PRs to projects.
Then maintainers will become free to shed their Python2 support, or at least Python3 code can be completely forked if legacy support becomes a concern, and Python3 code can depend on Python3 code either way, which can be kept up to date and maintained by new developers who have never read a line of Python2 before.
This list focuses on Python modules that continue to support or are directly enmeshed with the Python3 ecosystem in some way. Excellent examples are RPython and Twisted: RPython uses 2.7 Python, but is critical to PyPy, which supports 3.x Pythons