Skip to content

Why is typing_extensions pinned to 4.3.0? #1479

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

Open
zzzhhh2025 opened this issue May 20, 2025 · 2 comments
Open

Why is typing_extensions pinned to 4.3.0? #1479

zzzhhh2025 opened this issue May 20, 2025 · 2 comments

Comments

@zzzhhh2025
Copy link

sdbuild/packages/python_packages_jammy/requirements.txt requires that the version of typing_extensions be pinned to 4.3.0. This would generate the following error during installation:

Installing collected packages: typing_extensions
  Attempting uninstall: typing_extensions
    Found existing installation: typing_extensions 4.13.2
    Uninstalling typing_extensions-4.13.2:
      Successfully uninstalled typing_extensions-4.13.2
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
exceptiongroup 1.3.0 requires typing-extensions>=4.6.0; python_version < "3.13", but you have typing-extensions 4.3.0 which is incompatible.
Successfully installed typing_extensions-4.3.0

So, is there any special reason to pin typing_extensions to such a low version of 4.3.0, when a higher version of 4.13.2 exists and has been installed in Ubuntu 22.04? If there is no special reason of dependency, can any developer of PYNQ change the requirement from typing_extensions==4.3.0 to typing-extensions>=4.6.0 as indicated by the error message? Thanks.

@mariodruiz
Copy link
Collaborator

Hi @zzzhhh2025,

We verify the pynq environment with a fixed version of the packages. You can try to update the package, but a different version is something we have not verified

@zzzhhh2025
Copy link
Author

Hi @zzzhhh2025,

We verify the pynq environment with a fixed version of the packages. You can try to update the package, but a different version is something we have not verified

First, it is a convention to develop package/library to be backward compatible. So, there is no need to test all versions.

Second, the ultimate purpose of sticking to a fixed version (and verifying based on it) is to avoid a bug. But as I said, typing_extensions==4.3.0 will cause an error in installation, so your response should be trying to fix this error based on my post, but not trying to justify you sticking to a buggy version and asking users to fix by themselves. If you are an Xilinx employee, your attitude to pass the buck is enough to lose your job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants