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

Certifi again #803

merged 2 commits into from Oct 1, 2016


None yet
3 participants
Copy link

mindw commented Sep 30, 2016

No description provided.

jaraco and others added some commits Sep 27, 2016

@jaraco jaraco merged commit 910aa9d into pypa:master Oct 1, 2016

0 of 2 checks passed

continuous-integration/appveyor/pr AppVeyor build failed
continuous-integration/travis-ci/pr The Travis CI build failed

jaraco added a commit that referenced this pull request Oct 1, 2016

@mindw mindw deleted the mindw:certifi_again branch Oct 5, 2016


This comment has been minimized.

Copy link

Kentzo commented on 910aa9d Dec 27, 2017

@mindw Is there a particular reason for pinning certifi here?

Assuming I have a requirements.txt file for pip where I list setup requirements (version of pip, setuptools and certifi, everything with pinned versions). In that list I would like to pin certifi to the newer version but also specify setuptools[certifi] to ensure installation order.

Or perhaps the certifi extra is for internal usage only (e.g. tests)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.