Conversation
remove unnecessary tests and code update the docs
#:; Remove 🔥 DocStrEnum approach that turned out to not work
#:; Remove 🔥 DocStrEnum approach that turned out to not work#:; Remove 🔥 DocStrEnum approach that turned out to not work
hf-aschloegl
approved these changes
Nov 17, 2021
Collaborator
hf-aschloegl
left a comment
There was a problem hiding this comment.
Ja, schicke Sache 👍
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
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.
The last approaches to have documented enum members (not only classes) on read the docs resulted in a heuristic trial and error development process (see #75).
Now here's the next step to ultimate documentation truth on how to really do it (aka "richtig statt falsch"):
#:prefix as decribed here Python 3.4 enum classes not working (only py34 environment) sphinx-doc/sphinx#3255.tox/docs/tmp/htmlWorks on my machine:
