pyright/.github/ISSUE_TEMPLATE/bug_report.md

37 lines
1.4 KiB
Markdown
Raw Normal View History

2019-03-30 19:47:45 +03:00
---
name: Bug report
about: Create a report to help us improve pyright
2019-03-30 19:47:45 +03:00
title: ''
labels: ''
assignees: ''
---
2020-07-22 04:05:02 +03:00
Note: if you are reporting a wrong signature of a function or a class in the standard library, then the typeshed tracker is better suited for this report: https://github.com/python/typeshed/issues.
If you have a question about typing or a behavior that youre seeing in Pyright (as opposed to a bug report or enhancement request), consider posting to the [Pyright discussion forum](https://github.com/microsoft/pyright/discussions).
2019-03-30 19:47:45 +03:00
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior.
2019-03-30 19:47:45 +03:00
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots or Code**
If applicable, add screenshots or the text of the code (surrounded by triple back ticks) to help explain your problem.
2020-08-03 00:20:07 +03:00
```python
def foo(self) -> str:
return 3
```
2019-03-30 19:47:45 +03:00
If your code relies on symbols that are imported from a third-party library, include the associated import statements and specify which versions of those libraries you have installed.
**VS Code extension or command-line**
Are you running pyright as a VS Code extension or a command-line tool? Which version? You can find the version of the VS Code extension by clicking on the Pyright icon in the extensions panel.
2019-03-30 19:47:45 +03:00
**Additional context**
Add any other context about the problem here.