Loosen requirements to use lower bound pins instead of exact match

PelicanPlatform / pelicanfs

An fsspec implementation that uses the pelican client

https://pelicanplatform.org/

Apache License 2.0

1 stars 4 forks source link

Loosen requirements to use lower bound pins instead of exact match #56

Closed duncanmmacleod closed 4 months ago

duncanmmacleod commented 5 months ago

The current runtime requirements are pinned using exact match operators for everything:

https://github.com/PelicanPlatform/pelicanfs/blob/7bb7b4fc11451bdb18bf52a4995ba1ad9615dec2/setup.py#L37-L46

This will make this package hard to integrate into larger software environments. Is it reasonable to replace the == exact match operators with ~=X.Y version constraints?

duncanmmacleod commented 5 months ago

For example, aiohttp==3.9.4 is (for an unknown reason) not available from conda-forge, so this project cannot be packaged for that distribution right now.

turetske commented 4 months ago

Done!