Georg Brandl ge...@python.org added the comment:
Yes, Sphinx is still 2.x, although we could switch to a Python 3 version since
now all necessary dependencies are ported.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
New submission from Serhiy Storchaka storch...@gmail.com:
I was very surprised to find in Python source code files that are not
compatible with Python3. It turns out that this is not an exception, such files
very much (see scanner script in attachment). Surely for many years no one had
Serhiy Storchaka storch...@gmail.com added the comment:
See also issues 14490, 14491, and 14492.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14497
___
Changes by Serhiy Storchaka storch...@gmail.com:
Added file: http://bugs.python.org/file25125/invalid.txt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14497
___
R. David Murray rdmur...@bitdance.com added the comment:
Some of these at least are intentional. There are test files (especially in
2to3!) that use python2 syntax, and test files that have specially crated
syntax errors in them. Sphinx at one point was using Python2, I'm not sure if
it has
Ned Deily n...@acm.org added the comment:
There was some related work on this in the earlier Demo clean up issue
(Issue7962) and the still open make altnstall shebang line cleanup
(Issue10318).
But I'm confused. From the list of files you show in invalid.txt appear to be
from a Python 2
R. David Murray rdmur...@bitdance.com added the comment:
Here's a run of your script against Python3.3
I see nothing on this list that is a problem (after the recent fixes in
Tools/scripts). The Doc stuff can be ignored, that's a Python2 based toolchain
checked out by the Doc 'make' file.
Serhiy Storchaka storch...@gmail.com added the comment:
Indeed, somehow I have in the source tree were many Python2 files. After `rm -r
*` and `hg revert -a ` number of invalid files decreased to a reasonable limit.
Sorry for the false alarm.
--
