Brett Cannon [Thu, 15 Nov 2012 21:10:16 +0000 (16:10 -0500)]
Remove the Vim syntax files.
They had become extremely stale (the script to generate the file was
Python 2 compatible!). Plus the community took the work and made
improvements that are available on www.vim.org.
If you want to update Vim's runtime files to the latest available,
follow the instructions at http://www.vim.org/runtime.php .
Victor Stinner [Mon, 12 Nov 2012 22:04:02 +0000 (23:04 +0100)]
Issue #16416: OS data are now always encoded/decoded to/from
UTF-8/surrogateescape, instead of the locale encoding (which may be ASCII if no
locale environment variable is set), to avoid inconsistencies with
os.fsencode() and os.fsdecode() functions which are already using
UTF-8/surrogateescape.
Gregory P. Smith [Sun, 11 Nov 2012 09:41:49 +0000 (01:41 -0800)]
Fixes issue #16140: The subprocess module no longer double closes its
child subprocess.PIPE parent file descriptors on child error prior to
exec().
This would lead to race conditions in multithreaded programs where
another thread opened a file reusing the fd which was then closed out
from beneath it by the errant second close.
Gregory P. Smith [Sun, 11 Nov 2012 09:38:18 +0000 (01:38 -0800)]
Fixes issue #16140: The subprocess module no longer double closes its
child subprocess.PIPE parent file descriptors on child error prior to
exec().
This would lead to race conditions in multithreaded programs where
another thread opened a file reusing the fd which was then closed out
from beneath it by the errant second close.
Gregory P. Smith [Sun, 11 Nov 2012 09:37:02 +0000 (01:37 -0800)]
Fixes issue #16140: The subprocess module no longer double closes its
child subprocess.PIPE parent file descriptors on child error prior to
exec().
This would lead to race conditions in multithreaded programs where
another thread opened a file reusing the fd which was then closed out
from beneath it by the errant second close.
Gregory P. Smith [Sun, 11 Nov 2012 08:08:45 +0000 (00:08 -0800)]
Remove the subprocess "bad exception data" warning (formerly a print!)
all together and just include the repr of the data in the exception
itself instead of the useless string "Unknown".
This code path is unlikely to even be possible to take given the
nature of the pipe it gets subprocess data from.
Gregory P. Smith [Sun, 11 Nov 2012 08:04:52 +0000 (00:04 -0800)]
Remove the subprocess "bad exception data" warning (formerly a print!)
all together and just include the repr of the data in the exception
itself instead of the useless string "Unknown".
This code path is unlikely to even be possible to take given the
nature of the pipe it gets subprocess data from.
Gregory P. Smith [Sun, 11 Nov 2012 08:04:13 +0000 (00:04 -0800)]
Remove the subprocess "bad exception data" warning (formerly a print!)
all together and just include the repr of the data in the exception
itself instead of the useless string "Unknown".
This code path is unlikely to even be possible to take given the
nature of the pipe it gets subprocess data from.
Gregory P. Smith [Sun, 11 Nov 2012 07:35:15 +0000 (23:35 -0800)]
Rename a local variable for readability and change a "this can't
happen" print() call into a RuntimeWarning as it should've been in the
first place. Because nothing should ever cause unexpected stdout output.
Gregory P. Smith [Sun, 11 Nov 2012 07:33:56 +0000 (23:33 -0800)]
Rename a local variable for readability and change a "this can't
happen" print() call into a RuntimeWarning as it should've been in the
first place. Because nothing should ever cause unexpected stdout output.
Gregory P. Smith [Sun, 11 Nov 2012 07:33:17 +0000 (23:33 -0800)]
Rename a local variable for readability and change a "this can't
happen" print() call into a RuntimeWarning as it should've been in the
first place. Because nothing should ever cause unexpected stdout output.