> With the release of Python 3.6, it became clear that Pylama was in need of maintenance updates. Python 3.6 warned that async was about to become a reserved keyword in Python 3.7.
I can imagine there must be lot of code bases with async as variable name. For example:
I can imagine there must be lot of code bases with async as variable name. For example:
This is an error in Python 3.7. But this used to run just fine without any warning or issues until Python 3.5.So now any code that uses async as a variable name would break. So is Python 3.7 considered a breaking change that is not backward compatible?