While working with Markdown extensions (c.f. #74), I noticed that mkdocs' setup.py has its dependencies pinned to specific patch versions:
install_requires = [
'Jinja2==2.7.1',
'Markdown==2.3.1',
'PyYAML==3.10',
'watchdog==0.7.0',
'ghp-import==0.4.1'
]
Since these dependencies are slightly out of date (e.g., Jinja2 is at 2.7.3 and Markdown is at 2.4.1), it's hard to use mkdocs on a system with other software. Perhaps it's a shame that Python doesn't have npm-like dependency management, but that's the way it is—you'll get a setuptools when trying to run mkdocs error if any other package upgrades Jinja to a bugfix release.
How would the developers feel about loosening these version requirements? An idiomatic approach is to just use >=.
While working with Markdown extensions (c.f. #74), I noticed that mkdocs' setup.py has its dependencies pinned to specific patch versions:
Since these dependencies are slightly out of date (e.g., Jinja2 is at 2.7.3 and Markdown is at 2.4.1), it's hard to use mkdocs on a system with other software. Perhaps it's a shame that Python doesn't have npm-like dependency management, but that's the way it is—you'll get a setuptools when trying to run mkdocs error if any other package upgrades Jinja to a bugfix release.
How would the developers feel about loosening these version requirements? An idiomatic approach is to just use
>=.