Repository navigation
Pylance cannot identify dynamic azure methods #8143
Replies: 4 comments
|
Hi Tidux (@tidux), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime. Similar Issues (FYI only, not solutions) The following issues may or may not be related to your report. They are provided for reference only, as they may describe similar symptoms, affect the same feature, or address related concerns, but may not be the same issue.
The team will respond to your issue shortly. Please note this is a trial feature and may not be fully accurate. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or was incorrect, please give it a 👎. Your feedback helps us improve! |
|
This issue is due to PyLance's static type checking struggling to resolve methods dynamically generated by the Azure SDK at runtime (e.g., list_for_subscription()). |
|
Repro workspace for investigation: https://github.com/heejaechang/pylance-repro/tree/main/pylance-issues/7449 |
|
Going to transfer this to discussions for up votes. Basically the request is to support dynamic azure methods. This might be possible, but likely not if we can't reproduce how azure generates the methods. |
Uh oh!
There was an error while loading. Please reload this page.
Environment data
Code Snippet
Repro Steps
list_for_subscriptionand marks my code as having a "problem."This shows the definition as expected, meaning that VSCode and PyLance are identifying the method, but it is also being identified as an attribute which does not exist.
Expected behavior
No squiggly highlights or "your code has a problem" warning for perfectly valid code.
Actual behavior
see above
All reactions