-
Notifications
You must be signed in to change notification settings - Fork 769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Statements failed in pylance but passed in mypy again #871
Comments
This is a duplicate of #861. A fix is already in place and will be included in next week's pylance release. |
Sorry I've updated pylance and found that the previous bug in #861 is already fixed, so I thought this may be a new one. |
We haven't published a new version of pylance since that bug was fixed. We typically publish on Wed of each week. We close the associated bug reports just after we publish, so watch for that notification. |
Closing as a duplicate of #861. |
Environment data
Expected behaviour
Actual behaviour
Logs
Code Snippet / Additional information
The text was updated successfully, but these errors were encountered: