Repository navigation
Update Plotly.py version for docs - #4594
Merged
Merged
Conversation
archmoj
reviewed
May 1, 2024
| parmed<=3.4.4; python_version<"3.8" | ||
| dask==2022.2.0 | ||
| polars | ||
| geoparse<=2.0.3 |
Contributor
There was a problem hiding this comment.
Do you know which geoparse version used before?
Contributor
Author
There was a problem hiding this comment.
The last successful build used 2.0.3
gvwilson
approved these changes
May 1, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR updates the docs to use the latest, just released, plotly.py - 5.22
Release step here: https://github.com/plotly/plotly.py/blob/master/release.md#update-documentation-site
Note: Docs build failed for three pages because of an incompatibility between the latest version of geoparse and the library versions we are using in examples.
Pinning it here to the previous version to get the docs for the released merged, and then I can look at updating the requirements for the docs to later versions.