summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Release bump for Python 3.5.0a3.v3.5.0a3Larry Hastings2015-03-294-5/+5
|
* Regenerated pydoc topics and minor doc fixes for 3.5.0a3.Larry Hastings2015-03-293-8/+18
|
* Issue #14260: The groupindex attribute of regular expression pattern objectSerhiy Storchaka2015-03-295-5/+31
| | | | now is non-modifiable mapping.
* #2211: properly document the Morsel behavior changes.R David Murray2015-03-294-12/+55
| | | | | | | Also deprecate the undocumented set argument instead of removing it already in 3.5. Initial patch by Demian Brecht.
* merge 3.4 (#23801)Benjamin Peterson2015-03-293-2/+29
|\
| * Closes #23801 - Ignore entire preamble to multipart in cgi.FieldStorageDonald Stufft2015-03-293-2/+29
| |
* | Merge: #23792: Ignore KeyboardInterrupt when the pydoc pager is active.R David Murray2015-03-292-3/+14
|\ \ | |/
| * #23792: Ignore KeyboardInterrupt when the pydoc pager is active.R David Murray2015-03-292-3/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, if you hit ctl-c while the pager was active, the python that launched the subprocess for the pager would see the KeyboardInterrupt in the __exit__ method of the subprocess context manager where it was waiting for the subprocess to complete, ending the wait. This would leave the pager running, while the interactive interpreter, after handling the exception by printing it, would go back to trying to post a prompt...but the pager would generally have the terminal in raw mode, and in any case would be still trying to read from stdin. On some systems, even exiting python at that point would not restore the terminal mode. The problem with raw mode could also happen if ctl-C was hit when pydoc was called from the shell command line and the pager was active. Instead, we now wait on the subprocess in a loop, ignoring KeyboardInterrupt just like the pager does, until the pager actually exits. (Note: this was a regression relative to python2...in python2 the pager is called via system, and system does not return until the pager exits.)
* | Added explicit tests for issue #23803.Serhiy Storchaka2015-03-291-0/+2
|\ \ | |/
| * Issue #23803: Fixed str.partition() and str.rpartition() when a separatorSerhiy Storchaka2015-03-293-5/+10
| | | | | | | | is wider then partitioned string.
* | Removed unintentional trailing spaces in text files.Serhiy Storchaka2015-03-2915-66/+66
| |
* | Make some tests more frienly to MemoryError.Serhiy Storchaka2015-03-286-16/+42
|\ \ | |/ | | | | Free memory, unlock hanging threads.
| * Make some tests more frienly to MemoryError.Serhiy Storchaka2015-03-286-16/+43
| | | | | | | | Free memory, unlock hanging threads.
* | Issue #22117: Fix _PyTime_GetMonotonicClock() andVictor Stinner2015-03-281-12/+20
| | | | | | | | | | _PyTime_GetSystemClockWithInfo() to not raise an exception and return 0 on error (it should never occur)
* | Issue #22117: Add the new _PyTime_ROUND_FLOOR rounding method for the datetimeVictor Stinner2015-03-285-56/+43
| | | | | | | | | | module. time.clock_settime() now uses this rounding method instead of _PyTime_ROUND_DOWN to handle correctly dates before 1970.
* | Issue #22117: Use the _PyTime_t API for time.clock_settime()Victor Stinner2015-03-283-27/+5
| | | | | | | | Remove also the now unused _PyTime_AddDouble() function.
* | Issue #22117: Use the new _PyTime_t API in the select moduleVictor Stinner2015-03-283-41/+22
| |
* | Issue #22117: The thread module uses the new _PyTime_t timestamp APIVictor Stinner2015-03-283-219/+76
| | | | | | | | | | | | | | | | | | Add also a new _PyTime_AsMicroseconds() function. threading.TIMEOUT_MAX is now be smaller: only 292 years instead of 292,271 years on 64-bit system for example. Sorry, your threads will hang a *little bit* shorter. Call me if you want to ensure that your locks wait longer, I can share some tricks with you.
* | Issue #22117: Fix ssl to use _PyTime_t API on sock_timeoutVictor Stinner2015-03-281-11/+14
| | | | | | | | I didn't notice that the ssl module uses private attributes of socket objects.
* | Issue #22117: remove _PyTime_INTERVAL() macroVictor Stinner2015-03-281-10/+0
| |
* | Issue #22117: The socket module uses _PyTime_t timestamp for timeoutsVictor Stinner2015-03-282-91/+124
| |
* | Issue #22117: Write unit tests for _PyTime_AsTimeval()Victor Stinner2015-03-285-15/+103
| | | | | | | | | | | | | | * _PyTime_AsTimeval() now ensures that tv_usec is always positive * _PyTime_AsTimespec() now ensures that tv_nsec is always positive * _PyTime_AsTimeval() now returns an integer on overflow instead of raising an exception
* | Issue #23618, #22117: refactor socketmodule.cVictor Stinner2015-03-271-83/+113
| | | | | | | | | | Move Py_BEGIN_ALLOW_THREADS/Py_END_ALLOW_THREADS inside internal_select_ex() to prepare a switch to the _PyTime_t type and retry syscall on EINTR.
* | Issue #22117: The signal modules uses the new _PyTime_t APIVictor Stinner2015-03-275-15/+88
| | | | | | | | | | * Add _PyTime_AsTimespec() * Add unit tests for _PyTime_AsTimespec()
* | Issue #22117: The gc module now uses _PyTime_t timestampVictor Stinner2015-03-271-6/+6
| |
* | Issue #22117: time.time() now uses the new _PyTime_t APIVictor Stinner2015-03-273-12/+133
| | | | | | | | * Add _PyTime_GetSystemClockWithInfo()
* | Issue #22117: time.monotonic() now uses the new _PyTime_t APIVictor Stinner2015-03-275-15/+121
| | | | | | | | | | | | * Add _PyTime_FromNanoseconds() * Add _PyTime_AsSecondsDouble() * Add unit tests for _PyTime_AsSecondsDouble()
* | format .. note properlyBenjamin Peterson2015-03-271-3/+5
| |
* | Remove a dead test for a never-launched APIBrett Cannon2015-03-271-9/+0
| |
* | MergeBrett Cannon2015-03-275-86/+211
|\ \
| * | Issue #22117: Fix rounding in _PyTime_FromSecondsObject()Victor Stinner2015-03-275-86/+211
| | | | | | | | | | | | | | | | | | * Rename _PyTime_FromObject() to _PyTime_FromSecondsObject() * Add _PyTime_AsNanosecondsObject() and _testcapi.pytime_fromsecondsobject() * Add unit tests
* | | Fix module deprecation warnings to have a useful stacklevelBrett Cannon2015-03-272-2/+2
|/ /
* | Issue #22117: Fix test_gdb for the new time.sleep()Victor Stinner2015-03-271-6/+8
| | | | | | | | | | | | | | Use time.gmtime() instead of time.sleep(), because time.sleep() is no more declared with METH_VARARGS but with METH_O. time.gmtime() is still declared with METH_VARARGS and so it is called with PyCFunction_Call() which is the target of the test_gdb unit test.
* | Merge 3.4 (test.support)Victor Stinner2015-03-271-1/+1
|\ \ | |/
| * Issue #23445: Fix test.support.python_is_optimized() for CFLAGS=-OgVictor Stinner2015-03-271-1/+1
| | | | | | | | -Og does not optimize the C code, it's just "fast debugging".
* | Merge 3.4 (asyncio)Victor Stinner2015-03-272-1/+6
|\ \ | |/
| * asyncio: Fix _SelectorTransport.__repr__() if the event loop is closedVictor Stinner2015-03-272-1/+6
| |
* | Issue #23715: Fix test_sigtimedwait() of test_eintrVictor Stinner2015-03-271-1/+1
| | | | | | | | | | sigtimedwait([], timeout) fails with OSError(EINVAL) on OpenIndiana, wait for a signal which will never be received instead.
* | Issue #23451, #22117: Python 3.5 now requires Windows Vista or newer, soVictor Stinner2015-03-271-47/+2
| | | | | | | | GetTickCount64() is now always available.
* | Issue #22117: Add a new Python timestamp format _PyTime_t to pytime.hVictor Stinner2015-03-273-22/+361
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In practice, _PyTime_t is a number of nanoseconds. Its C type is a 64-bit signed number. It's integer value is in the range [-2^63; 2^63-1]. In seconds, the range is around [-292 years; +292 years]. In term of Epoch timestamp (1970-01-01), it can store a date between 1677-09-21 and 2262-04-11. The API has a resolution of 1 nanosecond and use integer number. With a resolution on 1 nanosecond, 64-bit IEEE 754 floating point numbers loose precision after 194 days. It's not the case with this API. The drawback is overflow for values outside [-2^63; 2^63-1], but these values are unlikely for most Python modules, except of the datetime module. New functions: - _PyTime_GetMonotonicClock() - _PyTime_FromObject() - _PyTime_AsMilliseconds() - _PyTime_AsTimeval() This change uses these new functions in time.sleep() to avoid rounding issues. The new API will be extended step by step, and the old API will be removed step by step. Currently, some code is duplicated just to be able to move incrementally, instead of pushing a large change at once.
* | Issue #23648: Document the PEP 475 in the "Porting to Python 3.5" section andVictor Stinner2015-03-263-0/+33
| | | | | | | | add a version changed note in modified functions.
* | _PyUnicodeWriter_WriteStr() now checks that the input string is consistentVictor Stinner2015-03-261-0/+1
| | | | | | | | | | | | | | in debug mode to detect bugs earlier. _PyUnicodeWriter_Finish() doesn't check if the read only string is consistent, whereas it does check consistency for strings built by itself.
* | Issue #23775: pprint() of OrderedDict now outputs the same representationSerhiy Storchaka2015-03-263-24/+40
| | | | | | | | as repr().
* | Issue #23776: Removed asserts from pprint.PrettyPrinter constructor.Serhiy Storchaka2015-03-262-7/+23
| |
* | Issue #23765: Removed IsBadStringPtr calls in ctypesSteve Dower2015-03-262-8/+6
| |
* | Issue #22364: Improved some re error messages using regex for hints.Serhiy Storchaka2015-03-256-196/+300
| |
* | Check that failed writerow() doesn't produce change a file.Serhiy Storchaka2015-03-251-14/+16
|\ \ | |/
| * Check that failed writerow() doesn't produce change a file.Serhiy Storchaka2015-03-251-14/+16
| |
* | Issue #23742: ntpath.expandvars() no longer loses unbalanced single quotes.Serhiy Storchaka2015-03-253-1/+4
|\ \ | |/
| * Issue #23742: ntpath.expandvars() no longer loses unbalanced single quotes.Serhiy Storchaka2015-03-253-1/+4
| |
generated by cgit v0.12 at 2025-03-21 19:56:48 (GMT)