Open prettybits opened 1 year ago
On a related note, the current install_requires
dependencies are (as of the time of posting this comment):
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 >
or >=
is much easier to integrate than a ==
or ~=
.
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 sid
)...
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 a98992c5818129949b11912cbf11b5b4972430c0 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?