How a module is being marked as imported?

Hi all, The short version: How CPython marks a module as being fully imported, if it does, so that the same import statement ran from another C thread at the same time does not collide? Or, reversely, does not think the module is not already fully imported? The full version: I'm running

Re: How a module is being marked as imported?

2016 at 11:20:05 AM UTC+1, Jean-Charles Lefebvre wrote: > Hi all, > > The short version: How CPython marks a module as being fully imported, if it > does, so that the same import statement ran from another C thread at the same > time does not collide? Or, reversely, does n

[issue17797] Visual C++ 11.0 reports fileno(stdin) == 0 for non-console program

Jean-Charles Lefebvre added the comment: Well, just in case, I've attached the patch to apply against 3.5.0a2. -- Added file: http://bugs.python.org/file38469/python-3.5.0a2-fdvalidation.patch ___ Python tracker rep...@bugs.python.org http

[issue17797] Visual C++ 11.0 reports fileno(stdin) == 0 for non-console program

Jean-Charles Lefebvre added the comment: Oops, mistyping, #ifdef test would be: #if defined(MS_WINDOWS) defined(HAVE_FSTAT) defined(_MSC_VER) _MSC_VER = 1700 _MSC_VER 1900 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue17797] Visual C++ 11.0 reports fileno(stdin) == 0 for non-console program

Jean-Charles Lefebvre added the comment: Hi all, a small update to confirm this issue with version 3.5.0a2 embedded in a native C++ GUI application, having everything built with VS2013 SP4. Same execution flow as described by Mateusz in msg198689. I've modified Python/pylifecycle.c file