-
Notifications
You must be signed in to change notification settings - Fork 767
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
False unreachable code #2224
Comments
Thanks for the bug report, but we'll need more context. Could you please provide a minimal, self-contained sample (including any required import statements)? In particular, where are the symbols |
@Rildlanster, as I mentioned to the OP, we'll need more context. Could you provide a self-contained, minimal example in code form? The code within the screen shots you've pasted includes symbols that are defined outside of the sample, and I don't know where these are coming from. |
Hello @erictraut, here is a minimal project I've created:
You will see the unreachable code in the print statement:
|
Thanks for the repro steps. I was able to find and fix the underlying cause. The This will be fixed in the next release of pylance. |
This issue has been fixed in version 2022.1.1, which we've just released. You can find the changelog here: CHANGELOG.md |
Environment data
Expected behaviour
While writing tests for Django, I faced some unreachable code segments (which was okay couple days ago). Upon searching for cause, I saw that, new version of PyLance has come yesterday, so I reverted to previous version, and it worked how it is supposed to be.
Version 2012.12.2
Actual behaviour
Version 2022.1.0
![image](https://user-images.githubusercontent.com/33568903/148529971-5b2b1352-4248-4303-81a3-463f5e96f2e7.png)
Logs
Code Snippet / Additional information
The text was updated successfully, but these errors were encountered: