[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Géry added the comment: @barry You gave 2 reasons for changing __spec__.origin and __file__ for namespace packages. Your 1st reason: > I don't particularly like that its origin is "namespace". That's an odd > special case that's unhelpful to test against (what if you import a >

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Change by Barry A. Warsaw : -- pull_requests: +5761 ___ Python tracker ___ ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Barry A. Warsaw added the comment: On Mar 5, 2018, at 10:33, Ned Batchelder wrote: > As is usual for me, I am here because some coverage.py code broke due to this > change. A diff between b1 and b2 found me the code change (thanks for the >

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Ned Batchelder added the comment: As is usual for me, I am here because some coverage.py code broke due to this change. A diff between b1 and b2 found me the code change (thanks for the comment, btw!), but a What's New doesn't seem out of place. --

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Barry A. Warsaw added the comment: I guess it depends on whether you think this is a new feature or a bug fix. Or, OTOH, since we had to revert for 3.6, maybe it makes sense either way since some code will be affected. -- ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Ned Batchelder added the comment: Should this get an entry in the What's New? -- nosy: +nedbat ___ Python tracker ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Ned Deily added the comment: Note that this change was originally also backported to 3.6 in PR 5504 but, due to third-party package regressions discovered in pre-release testing, the 3.6 change was reverted in PR 5591 prior to release of 3.6.5rc1. -- nosy: +ned.deily

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Change by Barry A. Warsaw : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Change by Barry A. Warsaw : -- keywords: +patch pull_requests: +5312 stage: -> patch review ___ Python tracker ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Barry A. Warsaw added the comment: 3.5 is in security fix only mode, and this is not a security issue. -- versions: -Python 3.5 ___ Python tracker

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Change by Barry A. Warsaw : -- assignee: -> barry versions: +Python 3.8 ___ Python tracker ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

Change by Eric V. Smith : -- nosy: +eric.smith ___ Python tracker ___ ___

[issue32305] Namespace packages have inconsistent __file__ and __spec__.origin

New submission from Barry A. Warsaw : Along the lines of Issue32303 there's another inconsistency in namespace package metadata. Let's say I have a namespace package: >>> importlib_resources.tests.data03.namespace The package has no __file__ attribute, and it has a