New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python-typing-extensions fails to build with Python 3.8 #643
Comments
ilevkivskyi
added a commit
that referenced
this issue
Jun 16, 2019
Fixes #643 (Use ignore whitespace option to review this, since it mostly just indents a bunch of stuff.) PR summary: * Update Travis config to run on a bunch of newer Python versions (including 3.8-dev). * Only run `typing` tests on Python 3.6 or older, starting from Python 3.7 development of `typing` moved to CPython repo, where it was significantly reworked. We still run `typing_extension` tests on all versions. * Update `repr()` tests in `typing_extensions` to conditionally expect correct module name. * Add `TypedDict` to `__all__`. * Use `Final`, `Literal`, etc. from `typing` if those are available (as we do for other things). * Rename `@runtime` to `@runtime_checkable` in `typing_extensions` (I think we can keep `@runtime` in `typing_extensions` as an alias for backwards compatibility). Note this only updates Python 3 version of `typing_extensions`. There will be a corresponding update for the Python 2 version of `typing_extensions` as part of #648
JelleZijlstra
pushed a commit
to python/typing_extensions
that referenced
this issue
May 19, 2022
Fixes python/typing#643 (Use ignore whitespace option to review this, since it mostly just indents a bunch of stuff.) PR summary: * Update Travis config to run on a bunch of newer Python versions (including 3.8-dev). * Only run `typing` tests on Python 3.6 or older, starting from Python 3.7 development of `typing` moved to CPython repo, where it was significantly reworked. We still run `typing_extension` tests on all versions. * Update `repr()` tests in `typing_extensions` to conditionally expect correct module name. * Add `TypedDict` to `__all__`. * Use `Final`, `Literal`, etc. from `typing` if those are available (as we do for other things). * Rename `@runtime` to `@runtime_checkable` in `typing_extensions` (I think we can keep `@runtime` in `typing_extensions` as an alias for backwards compatibility). Note this only updates Python 3 version of `typing_extensions`. There will be a corresponding update for the Python 2 version of `typing_extensions` as part of python/typing#648
JelleZijlstra
pushed a commit
to python/typing_extensions
that referenced
this issue
May 19, 2022
Fixes python/typing#643 (Use ignore whitespace option to review this, since it mostly just indents a bunch of stuff.) PR summary: * Update Travis config to run on a bunch of newer Python versions (including 3.8-dev). * Only run `typing` tests on Python 3.6 or older, starting from Python 3.7 development of `typing` moved to CPython repo, where it was significantly reworked. We still run `typing_extension` tests on all versions. * Update `repr()` tests in `typing_extensions` to conditionally expect correct module name. * Add `TypedDict` to `__all__`. * Use `Final`, `Literal`, etc. from `typing` if those are available (as we do for other things). * Rename `@runtime` to `@runtime_checkable` in `typing_extensions` (I think we can keep `@runtime` in `typing_extensions` as an alias for backwards compatibility). Note this only updates Python 3 version of `typing_extensions`. There will be a corresponding update for the Python 2 version of `typing_extensions` as part of python/typing#648
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
python-typing-extensions fails to build with Python 3.8.0b1.
From the build log, it looks like some of the extensions were moved to Python's own typing module, invalidating the tests' expectations:
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.8/fedora-rawhide-x86_64/00927854-python-typing-extensions/
The original issue was submitted here: https://bugzilla.redhat.com/show_bug.cgi?id=1718366
The text was updated successfully, but these errors were encountered: