3 ms·

The shebang issue should probably lean on existing Python conventions: from future import nogil It would hot swap interpreters at that point.

• ikari_pl 3y ago
  it could be a nightmare to implement if it's not the first module, and then the first import, to execute
  • pletnes 3y ago
    Not sure about anything nogil related, but future imports already have to be the first executable statement in a file.
    • LtWorf 3y ago
      But what if you already loaded with gil and the 2000th module asks for nogil?
      • sitkack 3y ago
        try: import nogil except ImportError as ie: print(ie) nogil = None if nogil: # gill free code here pass else: # gil requring code here pass
• hsfzxjy 3y ago
  `from __future__ import ` is a specialized statement to indicate flags rather than a runtime statement. https://docs.python.org/3/reference/simple_stmts.html#future-statements https://docs.python.org/3/reference/simple_stmts.html#future...
• kzrdude 3y ago
  """A future statement is a directive to the compiler that a particular module should be compiled using syntax or semantics that will be available in a specified future release of Python where the feature becomes standard.""" future statements are module specific and GIL/no-GIL doesn't fit easily into that model.
  • VagabundoP 3y ago
    In the back of my mind I imagined it being used with this: https://peps.python.org/pep-0397/ https://peps.python.org/pep-0397/ But for all platforms. I should have put that into the comment.