Raw.anonymize() docstring is irritating
See original GitHub issueWhen viewing the docs of Raw.anonymize()
, I’m confronted with a warning:
If info is part of an object like raw.info, you should directly use the method raw.anonymize() to ensure that all parts of the data are anonymized and stay synchronized (e.g., raw.annotations).
which is irritating because, well, I am reading up on Raw.anonymize
already. Also see screenshot below.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Documenting a Python function with a docstring that is both ...
However, as I say in my question, I don't agree that the raw version of option 2 is very readable. I know it's...
Read more >Don't write documentation in Markdown | Hacker News
Keeping docs and code as close together as possible. Certainly same repo. But for instance one of pythons greatest feature is docstrings. Which ......
Read more >reStructuredText Markup Specification - Docutils - SourceForge
The simplest solution when backslashes appear in Python docstrings is to use raw docstrings: r"""This is a raw docstring. Backslashes (\) are not...
Read more >Raw docstring not ignored when computing similarities #2829
Raw docstrings are not ignored with the ignore-docstring=yes in the similarities checker. I think it should be ignored because raw ...
Read more >Python Docstrings (With Examples) - Programiz
Python docstrings are the string literals that appear right after the definition of a function, method, class, or module. Let's take an example....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
date of service can refer to the date at which the MEG system was checked by MEGIN. It’s typically once a year.
I would consider a rephrasing then. Date of acquisition ?