3 ms·
I think you misunderstood maple3142 comment: he is only saying that from Python 3.7 onward you could not use "async" as an identifier in your code, as it became
by Xixi 6y ago
I think you misunderstood maple3142 comment: he is only saying that from Python 3.7 onward you could not use "async" as an identifier in your code, as it became a reserved word.
So maybe you were using "async" as a variable name, or as a function name in your code, and suddenly that wouldn't work anymore. It definitely is a backwards-incompatible change, and that has nothing to do with provisional APIs.
Since I have never use "async" as an identifier in my own code, I have no idea if warnings were issued, though probably?
- oefrha 6y agoReserved words are introduced into languages over time. This is how languages evolve and hardly Python-specific. (Example: Rust added async/await keywords relatively recently.) You either stick with an old version or deal with it. gp specifically links to a SO question discussing asyncio.async breakage, which would be considered API breaking except it was specifically provisional.