You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this should be Python-specific or VSCode-specific, but the feature applies to any language that supports docstring-like attributes. Rust has ///, and Java has /** that would be similar to Python's module docstrings.
In Python, the function's docstring is displayed when you hover over a function name in an editor window. When you hover over a Python module (for example, something.py) in the Explorer view, you get the full path and a count of the file's issues and git info. Why don't we get the module docstring here as well? While the git and error info are essential, the docstrings could be the most valuable, especially when looking at a library code in a new codebase. File date/time info would be helpful.
The text was updated successfully, but these errors were encountered:
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
I don't know if this should be Python-specific or VSCode-specific, but the feature applies to any language that supports docstring-like attributes. Rust has
///
, and Java has/**
that would be similar to Python's module docstrings.In Python, the function's docstring is displayed when you hover over a function name in an editor window. When you hover over a Python module (for example,
something.py
) in the Explorer view, you get the full path and a count of the file's issues andgit
info. Why don't we get the module docstring here as well? While thegit
and error info are essential, the docstrings could be the most valuable, especially when looking at a library code in a new codebase. File date/time info would be helpful.The text was updated successfully, but these errors were encountered: