]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
projects / thirdparty / Python / cpython.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f91ad6a) | patch
> Regardless, building a fixed test certificate and checking it in sounds like
authorGuido van Rossum <guido@python.org>
Mon, 27 Aug 2007 17:19:42 +0000 (17:19 +0000)
committerGuido van Rossum <guido@python.org>
Mon, 27 Aug 2007 17:19:42 +0000 (17:19 +0000)
commitba8c5653cc9d2777f8becacad122801a388d6cff
treeafd5db64f49a934526c1f2ceae53a15e88c9663dtree | snapshot
parentf91ad6a5da65cbbf561c6859611b05c5fd83dedccommit | diff
> Regardless, building a fixed test certificate and checking it in sounds like
> the better option.  Then the openssl command in the test code can be turned
> into a comment describing how the test data was pregenerated.

Here's a patch that does that.

Bill
Lib/test/keycert.pem [new file with mode: 0644] blob
Lib/test/test_ssl.py diff | blob | blame | history
Mirror of https://github.com/python/cpython.git