Fix docs versioning relating to "v" prefix #2018
Merged
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.
Some more tweaks to our docs versioning and the version switcher. Main issue is a mismatch in how the version is put into a string: whether a "v" prefix is included or not. In the git tag we include a "v" prefix, but in
folium.__version__
we don't have that prefix.In the new situation:
v
prefixgh-pages
will include av
prefixThis change is already live on the
gh-pages
branch, including the manually created docs for v0.18.0.