Skip to content

Conversation

@stonebig
Copy link
Contributor

@stonebig stonebig commented May 7, 2016

No description provided.

@takluyver
Copy link
Member

I've said this so many times I feel like a broken record, but I don't think we should use the specific Python 3.x classifiers, because it's presumed to work with new Python 3.x releases, and we'll only forget to update them. I'd rather just use the general 'Python 3' classifier.

@stonebig
Copy link
Contributor Author

stonebig commented May 7, 2016

recent packages have the full list of Python 3.x classifiers, so you may define the rule for the whole Jupyter thing. and some packages may request the asyncio thing, 3.4+ only

@stonebig
Copy link
Contributor Author

stonebig commented May 7, 2016

you are right that everything that is Python 3.3.+ only can be marked "Python 3" only, as Python3.2 is out of maintenance since February 2016:
https://www.python.org/dev/peps/pep-0392/#lifespan

all maintained Python3 are 3.3+ now,
@minrk minrk added this to the 5.0 milestone May 7, 2016
@minrk minrk changed the title python3.5 official support simplify Python 3 classifiers May 7, 2016
@minrk
Copy link
Member

minrk commented May 7, 2016

👍 to 2.7, 3

@minrk minrk merged commit 5d72ff2 into ipython:master May 7, 2016
@takluyver
Copy link
Member

Thanks @stonebig

@minrk minrk modified the milestones: 5.0, 4.4 Aug 8, 2016
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.

3 participants