Skip to content

Commit

Permalink
certifi-2016.9.26
Browse files Browse the repository at this point in the history
  • Loading branch information
mindw committed Sep 30, 2016
1 parent ae50b56 commit 910aa9d
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 2 deletions.
5 changes: 5 additions & 0 deletions CHANGES.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,11 @@
CHANGES
=======

v28.0.1
-------

* #803: Bump certifi to 2016.9.26.

v28.0.0
-------

Expand Down
4 changes: 2 additions & 2 deletions setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -167,11 +167,11 @@ def pypi_link(pkg_filename):
""").strip().splitlines(),
extras_require={
"ssl:sys_platform=='win32'": "wincertstore==0.2",
"certs": "certifi==2016.8.31",
"certs": "certifi==2016.9.26",
},
dependency_links=[
pypi_link(
'certifi-2016.8.31.tar.gz#md5=2f22d484a36d38d98be74f9eeb2846ec',
'certifi-2016.9.26.tar.gz#md5=baa81e951a29958563689d868ef1064d',
),
pypi_link(
'wincertstore-0.2.zip#md5=ae728f2f007185648d0c7a8679b361e2',
Expand Down

1 comment on commit 910aa9d

@Kentzo
Copy link
Contributor

@Kentzo Kentzo commented on 910aa9d Dec 27, 2017

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 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)?

Please sign in to comment.