Pin the Sphinx version in setup.py #23
Milestone
Comments
riley-harper
added a commit
that referenced
this issue
Dec 6, 2022
This pins production dependencies to a minor version instead of a patch version. These dependencies can now silently be upgraded from 1.1.0 -> 1.1.3, for example. Upgrades that increment the minor or major version will still require manual changes. These packages are all fairly stable, and so we don't expect these bug fix patches to affect hlink's behavior significantly. This has the side effect of upgrading Spark to 3.3.1 and completing #61. Development dependencies are pinned on a more ad-hoc basis. Some like black and pre-commit can be pinned quite loosely. Others like Sphinx and pytest we would like to keep more strictly pinned. This commit also completes #23 by pinning Sphinx.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Generating the documentation with different versions of Sphinx can cause lots of changes to the html pages. Let's pin the version of Sphinx that's installed with hlink to reduce the number of issues with developers generating the documentation with differing versions of Sphinx. It looks like the most recent Sphinx version is 5.1.1.
The text was updated successfully, but these errors were encountered: