Issue Management

We appreciate all the time people take reporting new ideas or bug reports to help us continue improving Pylance! We wish we were able to thoroughly investigate all issues and leave all feature requests open indefinitely, but unfortunately, we have limited resources and it’s hard to organize and prioritize our work if we have a large number of issues open in our repository.

To help us stay more organized, we close issues that we are unlikely able to fix/address in the near future for various reasons, such as:

• The bug or feature request is only relevant in a niche scenario that we believe will not have wide range impact;
• We believe the cost of implementing the fix or feature outweighs its value to our users;
• The issue is not reproducible, or lacks sufficient detail for us to be able to investigate it effectively;
• The issue is only relevant to outdated versions of Python (i.e. not in the Active Python Releases list).

We understand having an issue closed can be frustrating, but please don’t take personal offense if it happens to one of your issues. If you think closing your issue is a mistake, ping us providing more information on your use case (or even gather more up-votes as we take that into consideration when prioritizing issues), and we can reconsider.

We love hearing your ideas and feedback, please don’t be discouraged from filing issues! We just want to make sure we’re maximizing our impact by staying organized and focused on improving the product for you and the entire Python community 💖