Allow most recent versions of dependencies to be used in documentation builds #332
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This flag was added for documentation builds to prevent a SunPyDeprecationWarning from happening.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #330, we were getting
SunPyDeprecationWarnings when using the most recent version of SunPy in documentation builds (see #327). To temporarily alleviate this, I added an--exclude-newerflag that is invoked byuvwhen installing packages for the doc builds. This flag prevents dependency resolutions from including packages that were added after a particular date in the environment.This PR removes the
--exclude-newerflag, which will allow the most recent versions of dependencies to be used in the Python environments for documentation builds. The deprecation warning is still happening, so this PR is mostly a placeholder so that we don't forget about it later on. This PR should only be merged when the documentation build is passing.