[issue37422] Documentation on the change of __path__ in Python 3

Change by Irit Katriel : -- resolution: -> not a bug stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Pytho

[issue37422] Documentation on the change of __path__ in Python 3

Irit Katriel added the comment: >From the discussion is seems like there is nothing that needs to be added to >the docs. I will close this in a while if nobody objects. -- nosy: +iritkatriel status: open -> pending ___ Python tracker

[issue37422] Documentation on the change of __path__ in Python 3

Change by Terry J. Reedy : -- versions: +Python 3.8, Python 3.9 -Python 3.5, Python 3.6 ___ Python tracker ___ ___ Python-bugs-list

[issue37422] Documentation on the change of __path__ in Python 3

Jim Li added the comment: Ah, that started to make sense. To be honest I didn't really pay much attention to the _namespace's documentation, I only looked at that of __path__ and somehow expected it to mention that certain namespace won't be a type anymore. I will re-read your comments and

[issue37422] Documentation on the change of __path__ in Python 3

Eric V. Smith added the comment: And I see you're not asking for changed behavior, just documentation. But I think it is documented that this is how namespace packages work. -- ___ Python tracker __

[issue37422] Documentation on the change of __path__ in Python 3

Eric V. Smith added the comment: It's a _NamespacePath in 3.7 because there's no __init__.py in the top-level "google" directory, and that makes it a namespace package. I'm not exactly sure why it works in 2.7, frankly. Looking some more: it's because they're playing tricks in a .pth file.

[issue37422] Documentation on the change of __path__ in Python 3

Change by Karthikeyan Singaravelan : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue37422] Documentation on the change of __path__ in Python 3

Jim Li added the comment: Hi Eric, Sorry for the late reply. I think I did not accurately describe the issue at all. As a minimal example, set up two virtual environments, one from 2.7.x, one from 3.7.2. When you are in the virtual environment, do - pip install protobuf==3.3.0 - python (to

[issue37422] Documentation on the change of __path__ in Python 3

Eric V. Smith added the comment: Can you provide a short runnable example that used to work and now does not? And please show any error messages you're seeing. -- nosy: +eric.smith ___ Python tracker __

[issue37422] Documentation on the change of __path__ in Python 3

New submission from Jim Li : In Python 2, `__path__` used to be a list, so all of the operations available to list are available, e.g., `insert`; you can also do indexing; e.g., `__path__[0]`. However, I believe that starting from Python 3, it seems to be a , and a lot of operations that wor