Automatically search for docstrings #5
Closed
Conversation
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
|
I don't think it's a good idea. "Explicit is better than implicit". For me passing Although, I must admit, I thought that what you did is impossible without a macro-system. Seeing this, I probably should reconsider how I obtain docstrings in another project (https://github.com/halst/pep257). If you have more ideas, we can discuss them. I'm working now on a pattern-matching (https://github.com/halst/docopt/blob/pattern-matching/docopt.py), which should allow to match usage (like |
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 makes the doc argument optional, and adds a little magic to search for the docstring. Makes the simple case simpler, and doesn't complicate the existing use case.