-
Notifications
You must be signed in to change notification settings - Fork 22
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
Incompatible with latest version of chardet #3387
Comments
On a related note, the current Lines 26 to 39 in 438628f
With the disclaimer that I fully understand (1) why versioning dependencies can be important (2) "virutalenvs" exist for a reason (3) I might be wishing for something that isn't possible and (4) there are a multitude of different viewpoints on what is "right" in terms of dependency versioning, etc. If at all possible, it would be nice if there was a way to remove restrictions on specific versions for dependencies. I am fully aware that it's easier said than done. Certainly a This particular issue is probably more impactful on rolling distributions like Kali or Arch as compared to Ubuntu or Debian (at least, Debian other than That said, if there's any way to remove "hard" dependencies - that'd be great. Alternatively, using a submodule and/or integrating specific functionality from a specific version of a different module/package might be an option too. Though I recognize and detest the idea of not maximizing code-reuse (i.e. having, essentially, multiple versions of a package installed because the code from one package is incorporated as a sub-part of another.) |
Since commit a98992c polyfile uses a narrower version specifier for the version of
chardet
expected. In the meantime chardet 5.1.0 has been released (and packaged on Arch Linux), which leads to aDistributionNotFound
error sincepkg_resources
is explicitly imported at runtime:This was observed on Arch Linux with the AUR package for polyfile at version 0.5.
Can the version specifier be safely loosened to
chardet>=5.0.0
again?The text was updated successfully, but these errors were encountered: