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

Trove Classifier Request: Typing #4348

Closed
tailhook opened this issue Jul 26, 2018 · 13 comments
Closed

Trove Classifier Request: Typing #4348

tailhook opened this issue Jul 26, 2018 · 13 comments

Comments

@tailhook
Copy link

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 include py.typed file as far as I understand.

@ewdurbin
Copy link
Member

ewdurbin commented Jul 26, 2018

highlighting a selection of top contributors from the typing module itself to solicit opinions on this classifier name, though it seems reasonable to me.

@gvanrossum @ilevkivskyi @ambv @vlasovskikh

@gvanrossum
Copy link

  • I'm not sure how we would spread the word that people should add this classifier.
  • I'd name it "Typed" rather than "Typing".

@tailhook
Copy link
Author

I'm not sure how we would spread the word that people should add this classifier.

Looks like this: http://py3readiness.org/ was a great idea, and may be repeated.

I'd name it "Typed" rather than "Typing".

When searching a list I was looking for mypy and typing not sure if I would find Typed. Anyway, may be full name like this would be nice:

  • Typing :: Typed

Another thought, we may want to distinguish type bindings using .pyi and fully typechecked modules. But I'm not sure if it makes sense.

@gvanrossum
Copy link

gvanrossum commented Jul 26, 2018 via email

@asvetlov
Copy link

In aiohttp we have both stubs and inline annotations

@ilevkivskyi
Copy link

FWIW I am equally fine with both Typing and Typed.

@dstufft
Copy link
Member

dstufft commented Aug 12, 2018

Just to clarify, y'all would like: Programming Language :: Python :: Typing :: Typed as your classifier?

@tailhook
Copy link
Author

I expected bare Typing :: Typed.

@asvetlov
Copy link

Programming Language :: Python makes sense for me

@ambv
Copy link

ambv commented Aug 17, 2018

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".

@ethanhs
Copy link

ethanhs commented Jan 6, 2019

I agree with @ambv, I think the bare "Typing::Typed" spelling makes sense.

@ewdurbin
Copy link
Member

Typing :: Typed has been added on pypi.org and test.pypi.org

happy annotating!

@ilevkivskyi
Copy link

Great, thanks!

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

9 participants