Skip to content
This repository has been archived by the owner on Mar 6, 2023. It is now read-only.

Rethinking Jupyter Interactive Documentation | Quansight Labs #301

Open
utterances-bot opened this issue Jan 26, 2022 · 1 comment
Open

Rethinking Jupyter Interactive Documentation | Quansight Labs #301

utterances-bot opened this issue Jan 26, 2022 · 1 comment
Labels
utterances Label that needs to be named "utterances" for the Utterances commenting system

Comments

@utterances-bot
Copy link

Rethinking Jupyter Interactive Documentation | Quansight Labs

https://labs.quansight.org/blog/2021/05/rethinking-jupyter-documentation/
@MarcSkovMadsen utterances
Copy link

I'm thinking about this too. Right now I'm trying to make HoloViz Panel docstrings work better in VS Code as that is my working environment. At the same time I want to improve things for Jupyter users.

VS Code can interpret some Markdown/ ReST. See holoviz/panel#3131 (comment)

It would be so nice if it was easy to write useful and powerful docstrings that would just work across VS Code, PyCharm, Jupyter and Sphinx.

@MarcSkovMadsen MarcSkovMadsen mentioned this issue Jan 26, 2022
Closed
@trallard trallard added the utterances Label that needs to be named "utterances" for the Utterances commenting system label May 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
utterances Label that needs to be named "utterances" for the Utterances commenting system
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@trallard @utterances-bot @MarcSkovMadsen