don't use fancy quotes in the conf.py template #87
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
cf. issue abakan-zz#86. (also correct a typo on the same line)
|
Travis CI fails
|
|
Thanks for the patch; I needed it for Sphinx 1.6.5/Python 3.6. Would be great to see this merged and released. |
rayalan
added a commit
to rayalan/ablog-deprecated
that referenced
this pull request
Dec 24, 2017
|
This has now been merged into here. |
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.
This is a three-character patch to partially fix #86 that prevented me from doing
ablog buildright afterablog startunder Windows.I'm still not quite sure what happened (When does Python assume a cp1252 encoding in the first place? If fancy quotes in a comment break the build, why are umlauts in
blog_titleworking?) - but no matter what, I'm confident nobody is going to miss the fancy quotes.