- 23 Jul, 2018 6 commits
-
-
jdemeyer authored
-
Matěj Cepl authored
imaplib now allows MOVE command in IMAP4.uid() (RFC 6851: IMAP MOVE Extension) and potentially as a name of supported method of IMAP4 object.
-
Victor Stinner authored
When Python is installed on Windows, python -m test test_tools failed because it tried to run Tools\scripts\2to3.py which requires an argument. Skip this script. On other platforms or on Windows but when run from source code (not installed), the script is called "2to3" instead of "2to.py" and so was already skipped. Modify also the unit test to unload all modules which have been loaded by the test.
-
Victor Stinner authored
Previously, Python was built in 32-bit mode and so issues specific to 64-bit mode like compiler warnings could be missed.
-
Berker Peksag authored
-
Berker Peksag authored
-
- 22 Jul, 2018 3 commits
-
-
Xtreak authored
-
Serhiy Storchaka authored
-
Serhiy Storchaka authored
-
- 21 Jul, 2018 10 commits
-
-
Andrés Delfino authored
-
Serhiy Storchaka authored
-
Bo Bayles authored
-
jdemeyer authored
-
Xtreak authored
-
Serhiy Storchaka authored
-
Victor Stinner authored
* _PyCoreConfig_Read() no longer directly modifies Py_IsolatedFlag and Py_NoSiteFlag global configuration flags. The function now requires two pointers to integer, so these flags can be set later, to avoid side effets in _PyCoreConfig_Read(). * pathconfig_global_init() now leaves Py_IsolatedFlag and Py_NoSiteFlag unchanged. * Fix pathconfig_global_init(): avoid computing the path configuration twice, use _PyCoreConfig_SetPathConfig().
-
Victor Stinner authored
Fix the following warning on Windows: parser\tokenizer.c(1297): warning C4244: 'function': conversion from '__int64' to 'int', possible loss of data.
-
Victor Stinner authored
The test failed on my laptop because the busy loop took 15.9 ms whereas the test expects at least 20 ms. Modify test_process_time() as test_thread_time() has been modified recently: only require 15 ms instead of 20 ms.
-
Victor Stinner authored
Rework _PyCoreConfig_Read() function which *reads* core configuration to not *modify* the path configuration. A new _PyCoreConfig_SetPathConfig() function now recreates the path configuration from the core configuration. This function is now called very late in _Py_InitializeCore(), just before calling initimport(). Changes: * Add _PyCoreConfig.dll_path * Py_SetPath() now fails with a fatal python error on memory allocation failure. * Rename _PyPathConfig_Calculate() to _PyPathConfig_Calculate_impl() * Replace _PyPathConfig_Init() with _PyPathConfig_Calculate(): the function now requires a _PyPathConfig * Add _PyPathConfig_SetGlobal() to set the _Py_path_config global variable. * Add _PyCoreConfig_InitPathConfig(): compute the path configuration * Add _PyCoreConfig_SetPathConfig(): set path configuration from core configuration * Rename wstrlist_append() to _Py_wstrlist_append() * _Py_wstrlist_append() now handles integer overflow.
-
- 20 Jul, 2018 4 commits
-
-
Vinay Sajip authored
-
Aaqa Ishtyaq authored
The parentheses were incorrect.
-
Victor Stinner authored
Py_Main() can again be called after Py_Initialize(), as in Python 3.6. The new configuration is ignored, except of _PyMainInterpreterConfig.argv which is used to update sys.argv.
-
Terry Jan Reedy authored
-
- 19 Jul, 2018 2 commits
-
-
ValeriyaSinevich authored
-
Victor Stinner authored
Increase the timeout: give timeout x 4 instead of timeout x 2 to threads to wait until the Event is set, but reduce the sleep from 500 ms to 250 ms. So the test should be more reliable and faster!
-
- 18 Jul, 2018 3 commits
-
-
Victor Stinner authored
On Windows, sometimes test_signal.test_warn_on_full_buffer() fails to fill the socketpair buffer. In that case, the C signal handler succeed to write into the socket, it doesn't log the expected send error, and so the test fail. On Windows, the test now uses a timeout of 50 ms to fill the socketpair buffer to fix this race condition. Other changes: * Begin with large chunk size to fill the buffer to speed up the test. * Add error messages to assertion errors to more easily identify which assertion failed. * Don't set the read end of the socketpair as non-blocking.
-
Victor Stinner authored
test_signal.test_socket(): On Windows, sometimes even if the C signal handler succeed to write the signal number into the write end of the socketpair, the test fails with a BlockingIOError on the non-blocking read.recv(1) because the read end of the socketpair didn't receive the byte yet. Fix the race condition on Windows by setting the read end as blocking.
-
Serhiy Storchaka authored
-
- 17 Jul, 2018 4 commits
-
-
Raymond Hettinger authored
-
Zackery Spytz authored
-
INADA Naoki authored
-
Raymond Hettinger authored
-
- 16 Jul, 2018 5 commits
-
-
Jon Ribbens authored
-
Antoine Pitrou authored
bpo-32430: Rename Modules/Setup.dist to Modules/Setup Remove the necessity to copy the former manually to the latter when updating the local source tree.
-
Nicolas Noé authored
Replace deprecated inspect.getfullargspec() with inspect.signature().
-
Serhiy Storchaka authored
Check that the size of the varnames tuple is enough at least for all arguments.
-
Benjamin Peterson authored
-
- 14 Jul, 2018 1 commit
-
-
INADA Naoki authored
`_PyUnicode_TransformDecimalAndSpaceToASCII()` missed trailing NUL char. It caused buffer overflow in `_Py_string_to_number_with_underscores()`. This bug is introduced in 9b6c60cb.
-
- 13 Jul, 2018 2 commits
-
-
Jason R. Coombs authored
* Add test capturing failure. * Honor newlines as present in the original file.
-
Andrés Delfino authored
-