Skip to content

Update mypy development status to Alpha #3753

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

Merged
merged 1 commit into from
Jul 21, 2017
Merged

Conversation

JukkaL
Copy link
Collaborator

@JukkaL JukkaL commented Jul 21, 2017

No description provided.

@gvanrossum gvanrossum merged commit 2589b1b into master Jul 21, 2017
@gvanrossum gvanrossum deleted the readme-dev-status branch July 21, 2017 17:45
@gvanrossum
Copy link
Member

Honestly that's a pretty conservative use of Alpha (I think of it as close to Beta myself) but I guess we're not promising strict backwards compatibility so this is not unreasonable. When do you expect to declare it Beta? I suppose it should come out of Beta when we release version 1.0. Maybe 0.600 or 0.700 should be Beta?

@emmatyping
Copy link
Member

It makes more sense to me to make it beta when we feel it is at that level, not by an arbitrary deadline. But I think that is probably going to be close to 0.600/0.700 in my experiences at least.

@JukkaL
Copy link
Collaborator Author

JukkaL commented Jul 21, 2017

For beta we should at least have well documented distinction between experimental and non-experimental features, and probably some degree of backward compatibility guarantees for non-experimental features.

@ilevkivskyi
Copy link
Member

Looking at the current mypy roadmap I would draw the line for Beta after protocols (this is just a coincidence :-), plus I would move the support for ORM/Django sooner.

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

Successfully merging this pull request may close these issues.

4 participants