search

sphinx-doc / sphinx-autobuild

Watch a Sphinx directory and rebuild the documentation when a change is detected. Also includes a hot-reload web server.
MIT License
527 stars 77 forks source link

Remove requirements.txt parsing from setup.py #2

Closed kmike closed 10 years ago

kmike commented 10 years ago

I think that install_requires with fixed package versions is too strict - it can unintentionally downgrade user packages.

GaretJax commented 10 years ago

We can probably change the pinned versions with minimal version specifiers (>=). I will look into it.

kmike commented 10 years ago

I think that usually requirements.txt and install_requires serve different purposes: requirements.txt lists versions that are guaranteed to work, and install_requires excludes versions that are known not to work. This way setup.py doesn't break valid configurations.

GaretJax commented 10 years ago

@kmike, sorry but going the >= way for the moment. It is always possible to exclude not working versions from requirements.txt if needed in the future.

To obviate to the conflicting dependencies problem I always work with a project specific development virtualenv (project specific dependencies) and a generic management virtualenv (with tools like sphinx, fabric, etc.).

GaretJax commented 10 years ago

Also sorry for taking this long to reply.