Mitchell Hentges added the comment:
That's great, thanks!
--
___
Python tracker
<https://bugs.python.org/issue43749>
___
___
Python-bugs-list mailing list
Mitchell Hentges added the comment:
Hey, can I request a backport of this change? For my use case, 3.9+ would be
great, but going back to 3.7 should be viable? I trust your judgement :)
I'll happily create the PRs for the backport, but it looks like the bug has to
be indicated as &
Mitchell Hentges added the comment:
I'm going to close this here - I currently don't have the cycles to push this
forward. Besides, this issue only occurs in environments that are using both
Python 2 and 3, and as Python 2's EOL date gets further in the past, the
severity
Mitchell Hentges added the comment:
Looking closer into this, it appears that Python 3 will still try to load
non-__pycache__ `.pyc` files. Perhaps I'm missing context, but aren't those
only supposed by to written and read by Python 2?
Location where `pyc` loader is register
New submission from Mitchell Hentges :
Python 3 imports may fail if a Python 2 .pyc file exists without an
accompanying .py file.
-
My project vendors code, and we recently updated "requests" to a drastically
newer version.
As part of this version change, `requests/packages/_
