[issue14599] Windows test_import failure thanks to ImportError.path

Brett Cannon added the comment: MAXPATHLEN no longer shows up in Python/import.c. -- dependencies: +Clear C code under PyImport_ExecCodeModuleObject() resolution: -> fixed status: open -> closed ___ Python tracker

[issue14599] Windows test_import failure thanks to ImportError.path

Roundup Robot added the comment: New changeset 9e164b404983 by Brett Cannon in branch 'default': Issues #15169, #14599: Make PyImport_ExecCodeModuleWithPathnames() use http://hg.python.org/cpython/rev/9e164b404983 -- ___ Python tracker

[issue14599] Windows test_import failure thanks to ImportError.path

Brett Cannon added the comment: Thanks for the info, Roumen. It looks like there is a single use of MAXPATHLEN still in import.c which I hope to eliminate, so hopefully that will rectify this problem. -- ___ Python tracker

[issue14599] Windows test_import failure thanks to ImportError.path

Roumen Petrov added the comment: The issue is related to MAXPATHLEN limit and how is implemented . One part of request are already closed , another part wait . Some people port patches other wrote that would not use very long path. I'm in the second group. This buildbot use path with length 5

[issue14599] Windows test_import failure thanks to ImportError.path

Brett Cannon added the comment: It's not a problem, Stefan. I just happened to have already added the importlib.invalidate_caches() call to test_reprlib so I know that isn't the issue. -- ___ Python tracker

[issue14599] Windows test_import failure thanks to ImportError.path

Stefan Krah added the comment: Brett, I reopened this because you said earlier that the test_reprlib failure is due to a race condition where an invalidate_caches() call is needed. You're quite right of course that the new occurrence could be caused by something unrelated. I can't reproduce the

[issue14599] Windows test_import failure thanks to ImportError.path

Brett Cannon added the comment: Roumen, what issue is that? Do you have an issue # you can share? -- ___ Python tracker ___ ___ Pytho

[issue14599] Windows test_import failure thanks to ImportError.path

Roumen Petrov added the comment: There is one long standing issue with length of the build path ... -- nosy: +rpetrov ___ Python tracker ___

[issue14599] Windows test_import failure thanks to ImportError.path

Brett Cannon added the comment: If you look at line 127 in importlib/_bootstrap.py you will see that it is an os.open() call to open the bytecode file for exclusive writing. I'm willing to bet the buildbot didn't have the directory writable or something and that triggered the issue. Regardles

[issue14599] Windows test_import failure thanks to ImportError.path

Stefan Krah added the comment: I think the issue mentioned in eae7cc54d28b just occurred again: http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/6807/steps/test/logs/stdio == ERROR: test_module (test.tes

[issue14599] Windows test_import failure thanks to ImportError.path

Changes by Brett Cannon : -- assignee: -> brett.cannon resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python

[issue14599] Windows test_import failure thanks to ImportError.path

Roundup Robot added the comment: New changeset 56aa4cda11a8 by Brett Cannon in branch 'default': Issue #14599: Support ImportError.path on AIX and HPUX when loading http://hg.python.org/cpython/rev/56aa4cda11a8 -- ___ Python tracker

[issue14599] Windows test_import failure thanks to ImportError.path

Roundup Robot added the comment: New changeset 573010778eed by Brett Cannon in branch 'default': Issue #14599: Generalize a test for ImportError.path and add support http://hg.python.org/cpython/rev/573010778eed -- ___ Python tracker

[issue14599] Windows test_import failure thanks to ImportError.path

Changes by Brett Cannon : -- title: Windows test_import failure -> Windows test_import failure thanks to ImportError.path ___ Python tracker ___