##// END OF EJS Templates
manifest: delay import of `typing.ByteString` for py 3.14 support (issue6940)...
manifest: delay import of `typing.ByteString` for py 3.14 support (issue6940) Since Python 2.7 and 3.5, `typing.ByteString` was defined as an alias for `bytes | bytearray | memoryview`, and `bytes` was also accepted as a shorthand for this, so we have `bytes` sprinkled all over the codebase. But then PEP-688 reversed all of that by deprecating `typing.ByteString` and its successor `collections.abc.ByteString` in Python 3.12 (as well as the `bytes` shorthand)[1], and removing it completely in Python 3.14. That leaves us with a couple of problems, namely defining something useful that spans py3.8-py3.13 and keeps pytype happy, and finding all of the instances where `bytes` doesn't really mean `bytes`. The current successor to all of this is `collections.abc.Buffer` in Python 3.12 (or `typing_extensions.Buffer` in previous versions). However, the current CI does type checking using Python 3.11 (so the former is not avaiable), and pytype has issues with importing `typing_extensions.Buffer`[2]. The good news is we don't need to deal with this mess immediately, since the type annotation evaluation is delayed to the type checking phase, and we're making no effort at supporting it in all supported versions of Python. So by delaying the import of this particular symbol, we can still use it for type checking purposes, but can start assessing Python 3.14 problems without doing a lot of extra work. Putting this on stable will allow people interested in 3.14 to work on it 4-5 extra months earlier (and apparently there's some interest). [1] https://peps.python.org/pep-0688/#no-special-meaning-for-bytes [2] https://github.com/google/pytype/issues/1772

File last commit:

r50501:4092db99 stable
r53224:0851d94b stable
Show More
requirements-windows.txt.in
23 lines | 507 B | text/plain | TextLexer
/ contrib / packaging / requirements-windows.txt.in
Jason R. Coombs
packaging: refresh dependency hashes (issue6750)...
r50501 # Declare Windows-specific requirements for generating
# the compiled (frozen) set of requirements in
# ./requirements-windows-py3.txt.
# If run on Windows, it may be necessary to run dos2unix
# on the output file to replace any CRLF newlines with LF.
Gregory Szorc
contrib: split Windows requirements into multiple files...
r46344 docutils
Gregory Szorc
packaging: remove requirements constraints to support Python 2...
r49704 dulwich
pyoxidized: install fuzzywuzzy too...
r48654
# Needed by the release note tooling
fuzzywuzzy
Gregory Szorc
contrib: split Windows requirements into multiple files...
r46344 keyring
Gregory Szorc
packaging: remove requirements constraints to support Python 2...
r49704 pygit2
Gregory Szorc
contrib: split Windows requirements into multiple files...
r46344 pygments
windows: add pytest-vcr to the dependencies...
r48657
# Needed by the phabricator tests
pytest-vcr
Gregory Szorc
contrib: split Windows requirements into multiple files...
r46344 # Need to list explicitly so dependency gets pulled in when
# not running on Windows.
pywin32-ctypes
Matt Harbison
packaging: include `windows-curses` on Windows...
r47036 windows-curses