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 yo
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
Jim Li added the comment:
Thanks Eric. That does make sense. The code wasn't really Python 3, it was
migrated from 2.7, which uses some Python 3 syntax.
As a side note, if you run 2to3 on this instead of the previous
`print(response.next_page_token)`
print(response)
Then 2to3 woul
New submission from Jim Li :
I encountered this issue when I was running 2to3 on a package, Python version
3.7.2, CentOS 7.
To reproduce this bug, create a file called test.py and paste the following
code into it
def testSomeRequest(self):
request = {"someRequest"
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
