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

Added Required Python Version #152

Merged
merged 4 commits into from Oct 27, 2021
Merged

Added Required Python Version #152

merged 4 commits into from Oct 27, 2021

Conversation

Nirzak
Copy link
Contributor

@Nirzak Nirzak commented Apr 21, 2021

Added python_requires to specify the required python version for the library.

Added python_requires to specify the required python version for the library.
@sigmavirus24
Copy link
Member

I believe this library supports Python 3.5+ not 3.3+

@Nirzak
Copy link
Contributor Author

Nirzak commented Apr 21, 2021

I believe this library supports Python 3.5+ not 3.3+

Ok updated it. There are classifiers for python 3.3 and 3.4 that's why I thought it would be 3.3+

@Nirzak
Copy link
Contributor Author

Nirzak commented Apr 21, 2021

Should I also remove the classifiers for python 3.3 and 3.4?

@jdufresne
Copy link
Contributor

Should I also remove the classifiers for python 3.3 and 3.4?

IMO, yes. The classifiers and python_requires should be compatible with one another.

Copy link

@iceman201 iceman201 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'Programming Language :: Python :: 3.3',
        'Programming Language :: Python :: 3.4',

would be good to remove

setup.py Show resolved Hide resolved
@@ -48,15 +48,14 @@
include_package_data=True,
zip_safe=False,
license='MPL-2.0',
python_requires=">=3.5",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be preferable to introduce this in declarative config. i.e.:

# setup.cfg
[options]
python_requires = >=3.5

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to do setup-py-upgrade in another pr I think?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, perhaps. My preference is to introduce changes in the preferred location rather than to cling to old conventions, but I also see the value in keeping it all consistent and to move everything at once.

@jaraco
Copy link

jaraco commented Oct 18, 2021

This PR fixes #174.

@alex alex merged commit 1c8485c into certifi:master Oct 27, 2021
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.

None yet

8 participants