4 ms·
Not meaning to apologize for Python here, but you have significantly more ability to segregate “editions” when you statically compile code. All the more reason
by 0cf8612b2e1e 2y ago
Not meaning to apologize for Python here, but you have significantly more ability to segregate “editions” when you statically compile code.
All the more reason to take a breakage very seriously. This is even worse than the walrus operator. At least I can ignore that. This breaks working code for some notion of purity.
- roblabla 2y agoCode compilation doesn't really have much to do with it. Python already has a somewhat similar ability - opting into certain language features of python on a file-by-file basis - using __future__[0]. It'd be pretty easy to add something like Rust editions by looking for a special statement in the file. And to make it more convenient, put it in the __init__.py and have it be transitive to the module. [0]: https://docs.python.org/3/library/__future__.html https://docs.python.org/3/library/__future__.html