[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Thomas Grainger added the comment: Yep that's the fix I went for in the end https://github.com/twisted/twisted/pull/1628/files#diff-8110fe13865c1f305bb999e82cd7514b2e7269f41087bd7ef39c3d6de508R105 -- ___ Python tracker

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Steve Dower added the comment: > do you know what the correct usage of importlib.util.spec_from_file_location > is to match importlib.import_module ? Maybe I'm misreading your example, but isn't the correct usage here to pass an absolute location= argument? Or are you suggesting that

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Thomas Grainger added the comment: hello, just chiming in to let you know that this broke CI on twisted: https://github.com/twisted/twisted/pull/1628/ (As above for Chalice, I think this didn't actually break the framework itself, just the tests for the framework. ) do you know what the

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Łukasz Langa added the comment: New changeset 378211f7789c4edf7385ff619fa74d6615bef242 by Steve Dower in branch '3.8': bpo-44070: No longer eagerly makes import filenames absolute, except for extension modules (GH-26025) (#26028)

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Steve Dower added the comment: New changeset b4884083aed9bfec22c4da0e0223ad6a04a4bef2 by Steve Dower in branch '3.9': bpo-44070: Clarify NEWS message to specify the version when the behaviour was introduced (GH-26029)

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Change by Steve Dower : -- pull_requests: +24679 pull_request: https://github.com/python/cpython/pull/26029 ___ Python tracker ___

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Change by Steve Dower : -- pull_requests: +24678 pull_request: https://github.com/python/cpython/pull/26028 ___ Python tracker ___

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Steve Dower added the comment: New changeset 23822e2c654e950bcfa563e27b99bcb46187ac8b by Steve Dower in branch '3.9': bpo-44070: No longer eagerly makes import filenames absolute, except for extension modules (GH-26025)

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Change by Steve Dower : -- keywords: +patch pull_requests: +24675 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26025 ___ Python tracker ___

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44070] __file__ is now fully qualified in 3.8 and 3.9

Steve Dower added the comment: Yeah, you're probably right. That effect was not noticed when implementing it. We should update the fix in 3.9 and 3.8 to limit it to .pyd's on Windows to protect against the security risks, but leave other import types loaded with relative paths. I think