---
name: Bug Report
about: 'Create a report to help us improve. Use the "Pylance: Report Issue" command
  (via command palette) to fill this out most of this information automatically.'
title: ''
labels: ''
assignees: ''

---

<!--
Read the guidelines for filing an issue first.

https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
-->

## Environment data

<!--
To find your version, open the VS Code extensions panel, then locate Pylance from the list of installed extensions. The version appears next to the name.
-->

-   Pylance version: XXX
-   OS and version: XXX
-   Python version (& distribution if applicable, e.g. Anaconda): XXX

## Code Snippet

<!--
Please provide a minimal, self-contained code snippet that reproduces the issue. If the code snippet uses any libraries, please specify the versions used.

Note: If you think a GIF of what is happening would be helpful, consider tools like https://github.com/vkohaupt/vokoscreenNG, https://www.cockos.com/licecap/, https://github.com/phw/peek or https://www.screentogif.com/ .
-->

```python
XXX
```

## Repro Steps

<!--
If multiple steps are needed to reproduce the issue, please list the steps here. Delete this section if not needed.
-->

1. XXX

## Expected behavior

XXX

## Actual behavior

XXX

## Logs

<!--
Enable trace logging by adding "python.analysis.logLevel": "Trace" to your settings.json configuration file.

Adding this will cause a large amount of info to be printed to the Python output panel. This should not be left long term, as the performance impact of the logging is significant.
-->

```
XXX
```
