pyright/.github/ISSUE_TEMPLATE/bug_report.md

29 lines
1.3 KiB
Markdown
Raw Permalink Normal View History

2019-03-30 19:47:45 +03:00
---
name: Bug report
2023-06-13 01:43:24 +03:00
about: Report incorrect or unintended behaviors
2019-03-30 19:47:45 +03:00
title: ''
2023-06-13 01:43:24 +03:00
labels: bug
2019-03-30 19:47:45 +03:00
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 the behavior you are seeing and the expected behavior along with steps to reproduce it.
2019-03-30 19:47:45 +03:00
2023-06-13 01:43:24 +03:00
**Code or Screenshots**
If possible, provide a minimal, self-contained code sample (surrounded by triple back ticks) to demonstrate the issue. The code should define or import all referenced symbols.
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, a language server in another editor, integrated into Pylance, or the command-line tool? Which version?