- 20 Jan, 2016 3 commits
-
-
Berker Peksag authored
Initial patch by Carlo Beccarini.
-
Donald Stufft authored
-
Donald Stufft authored
-
- 19 Jan, 2016 7 commits
-
-
Serhiy Storchaka authored
-
Serhiy Storchaka authored
-
Victor Stinner authored
Issue #11816: Fix bytecode_helper to handle correctly errors. Don't use unassigned variables.
-
Benjamin Peterson authored
Debugging by Eryk Sun.
-
Senthil Kumaran authored
Patch contributed by Ryder Lewis.
-
Martin Panter authored
The previous test relied on a remote server, which currently seems to be shutting the connection down once TLS has been set up, causing an EOFError. Now the test is implemented using a minimal NNTP server running in a background thread.
-
Berker Peksag authored
Some dependencies of pip import threading module unconditionally so we need to skip the test to make buildbots happy.
-
- 18 Jan, 2016 4 commits
-
-
Serhiy Storchaka authored
-
Serhiy Storchaka authored
in old Python 3 versions (3.4.3 and lower).
-
Serhiy Storchaka authored
-
Senthil Kumaran authored
Issue26017 - Suggest enclosing command args in double quotes when using characters which get interpreted by shell.
-
- 17 Jan, 2016 2 commits
-
-
Terry Jan Reedy authored
Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'.
-
Senthil Kumaran authored
-
- 16 Jan, 2016 10 commits
-
-
Steve Dower authored
-
Steve Dower authored
-
Steve Dower authored
-
Steve Dower authored
-
Steve Dower authored
-
Senthil Kumaran authored
Issue26035 - Correct the argument names used in the docs of the traceback module. Make it consistent with module args. Patch contributed by Upendra Kumar.
-
Martin Panter authored
Otherwise, GDB seems to affect the terminal's foreground process group, interfering with test_ioctl, which does not expect the foreground process to change during the test. This change also solves the problem of the tests being stopped in the shell if test_gdb is run twice in parallel.
-
Martin Panter authored
-
Gregory P. Smith authored
"certificate verify failed " and "CERTIFICATE_VERIFY_FAILED " as some SSL libraries use different text than OpenSSL.
-
Gregory P. Smith authored
"certificate verify failed " and "CERTIFICATE_VERIFY_FAILED " as some SSL libraries use different text than OpenSSL.
-
- 15 Jan, 2016 7 commits
-
-
Brett Cannon authored
Previously zipimport mistakenly limited namespace support to only the top-level of the zipfile when it should have supported an arbitrary depth. Thanks to Phil Connel for the bug report and initial patch and Mike Romberg for the final patch.
-
Brett Cannon authored
Permission was validated prior to adding these markings.
-
Brett Cannon authored
While no copyright violation occurred, the license which 'Numerical Recipes' operates under is not amenable to Python, so to prevent confusion it's easier to simply remove its mention.
-
Martin Panter authored
-
Martin Panter authored
-
Martin Panter authored
-
Martin Panter authored
-
- 14 Jan, 2016 7 commits
-
-
Martin Panter authored
Removed SSL_ERROR_SYSCALL checking from ssl_io_loop() so that the loop can terminate when unwrap() raises that error.
-
Martin Panter authored
-
doko@ubuntu.com authored
-
Martin Panter authored
-
Martin Panter authored
-
Martin Panter authored
-
Martin Panter authored
This is instead of svn.python.org, whose certificate recently expired, and whose new certificate uses a different root certificate. The certificate used at the pythontest server was modifed to set the "basic constraints" CA flag. This flag seems to be required for test_get_ca_certs_ capath() to work (in Python 3.4+). Added the new self-signed certificate to capath with the following commands: cp Lib/test/{selfsigned_pythontestdotnet.pem,capath/} c_rehash -v Lib/test/capath/ c_rehash -v -old Lib/test/capath/ # Note the generated file names cp Lib/test/capath/{selfsigned_pythontestdotnet.pem,0e4015b9.0} mv Lib/test/capath/{selfsigned_pythontestdotnet.pem,ce7b8643.0} The new server responds with "No route to host" when connecting to port 444.
-