-
Notifications
You must be signed in to change notification settings - Fork 955
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
Trove Classifier Request: Typing #4348
Comments
highlighting a selection of top contributors from the typing module itself to solicit opinions on this classifier name, though it seems reasonable to me. |
|
Looks like this: http://py3readiness.org/ was a great idea, and may be repeated.
When searching a list I was looking for
Another thought, we may want to distinguish type bindings using |
"Typing :: Typed" is fine.
Distinguishing between the two approaches seems overkill, and in fact it's
totally fine to use a mixture (or use .pyi files to cover extension modules
but inline annotations for the rest).
|
In aiohttp we have both stubs and inline annotations |
FWIW I am equally fine with both |
Just to clarify, y'all would like: |
I expected bare |
|
There's no precedent in specifying features of the language used in a project by classifiers under "Programming Language :: Python". I think what we're after here is closer to what "Framework ::" is doing. Thus, I would like to see a bare "Typing :: Typed". |
I agree with @ambv, I think the bare "Typing::Typed" spelling makes sense. |
happy annotating! |
Great, thanks! |
Request to add a new Trove classifier.
The name of the classifier you would like to add
Something like this:
Programming Language :: Python :: Typing
But I'm sure this isn't perfect name, so I'm open to bikeshedding.
Why do you want to add this classifier?
This should show, that source code either covered by type annotations, or has a
.pyi
files that accompany sources. Also package should includepy.typed
file as far as I understand.The text was updated successfully, but these errors were encountered: