Skip to content
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

Adaptation code structure to Pylince static analyze #3653

Closed
SowingSadness opened this issue Jan 24, 2021 · 4 comments
Closed

Adaptation code structure to Pylince static analyze #3653

SowingSadness opened this issue Jan 24, 2021 · 4 comments

Comments

@SowingSadness
Copy link

I think static analyze is very important for development. I will be happy if Pylance can detecting at least main properties of framework.

https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/
image

@stevepiercy
Copy link
Member

Is this issue already addressed in #2638?

@SowingSadness
Copy link
Author

SowingSadness commented Jan 24, 2021

Is this issue already addressed in #2638?

Both issue have same propose — type hinting. But this one do not require to drop Python 2 because Pylance can detect type as by annotation as by returned value using static analyze value of.
What way developers wish to use i don't know. May will they decide to use annotation way.

@bouillon
Copy link

+10 for this.
Without type-hints pyramid has not future :-D

@mmerickel
Copy link
Member

Hey I'm all for adding type hints but need someone with more experience there to support it than me! We have #2638 and don't support python 2 anymore so I'm closing this issue in favor of that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants