4 ms·
Not really - we already have __future__ imports, which must be declared at the top of the file before any other modules. I think this could be achieved in a
by chimeracoder 14y ago
Not really - we already have __future__ imports, which must be declared at the top of the file before any other modules.
I think this could be achieved in a simple way in a similar fashion - some sort of a straightforward 'multithreaded' pragma shouldn't be too much of a burden.
- sanxiyn 14y ago__future__ is per-module, so while it is good for syntax changes, I think it is inappropriate for runtime pragmas.