-
For the target use cases of `makes` (in large orgas / monorepos) it would be extremely useful to provide a doc generator function that generates `mdbook` docs from code comments.
Maybe some of the …
-
Currently for a function like this:
```python
# foo
def bar():
# lol
"""my docstring"""
```
The generated documentation will look like:
```python
("foo", "lol", "my docstring")
```
Th…
-
There are currently no docstrings for a lot of publicly exposed functions in this package. It would be great to add them.
-
BPO | [16731](https://bugs.python.org/issue16731)
--- | :---
Nosy | @loewis, @merwok, @asvetlov, @berkerpeksag, @serhiy-storchaka
Files | [xxdocstrings.diff](https://bugs.python.org/file28367/xxdocstr…
-
### Issue Report Checklist
* [ ] Searched the [issues page](https://github.com/spyder-ide/spyder/issues?q=is%3Aissue) for similar reports
* [ ] Read the relevant sections of the [Spyder Troubl…
-
```
Add more comments and docstrings to the code
```
Original issue reported on code.google.com by `ssbahe...@gmail.com` on 3 May 2011 at 10:37
-
## 🧰 Task
Our layer docstrings are large enough that we probably shouldn't be relying on humans to catch all changes and update them. For example, I just noticed that `layer.coordinates` is still li…
-
-
example.py
`"""
@TODO: Get this to parse.
"""`
This is not parsed.
-
There are no docstrings in synctools (Example issue)