Please don't lock package requirements to specific versions

[uSpike]

setup.py reads requirements.txt to populate install_requires. The issue is that typically requirements.txt requirements are locked to specific versions for reproducibility of developer environments. This is not ideal for install_requires since these specific version dependencies will reduce the entire environment of someone who installs this package.

For example, once anyio 3.2 comes out, I have to wait for this project to update requirement.txt before I can use it in my project.

The solution is to update setup.py to be less specific about version numbers:

install_requires=["anyio>=3,<4", "aiofile>=3,<4"]

[alexdelorenzo]

Thanks for the tip, sorry for holding your project back!

This was addressed in 02ec017 and a988aa1, and I'll comment again when the changes are pushed to PyPI.

[alexdelorenzo]

This issue was addressed in aiopath==0.5.11 for Python 3.9 and below, and in aiopath==0.6.9 for Python 3.10 and above.

You can upgrade aiopath like so:

python3 -m pip install --upgrade aiopath

[alexdelorenzo]

I'm going to close this issue. Feel free to comment again if there's still an issue.