-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
7 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,11 @@ | |
CHANGES | ||
======= | ||
|
||
v28.0.1 | ||
------- | ||
|
||
* #803: Bump certifi to 2016.9.26. | ||
|
||
v28.0.0 | ||
------- | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
910aa9d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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
andcertifi
, everything with pinned versions). In that list I would like to pincertifi
to the newer version but also specifysetuptools[certifi]
to ensure installation order.Or perhaps the certifi extra is for internal usage only (e.g. tests)?