- 25 Nov, 2009 4 commits
-
-
Benjamin Peterson authored
svn+ssh://pythondev@svn.python.org/sandbox/trunk/2to3/lib2to3 ........ r76160 | benjamin.peterson | 2009-11-08 18:53:48 -0600 (Sun, 08 Nov 2009) | 1 line undeprecate the -p option; it's useful for converting python3 sources ........ r76161 | benjamin.peterson | 2009-11-08 19:05:37 -0600 (Sun, 08 Nov 2009) | 1 line simplify condition ........ r76250 | benjamin.peterson | 2009-11-13 16:56:48 -0600 (Fri, 13 Nov 2009) | 1 line fix handling of a utf-8 bom #7313 ........ r76252 | benjamin.peterson | 2009-11-13 16:58:36 -0600 (Fri, 13 Nov 2009) | 1 line remove pdb turd ........ r76447 | benjamin.peterson | 2009-11-22 18:17:40 -0600 (Sun, 22 Nov 2009) | 1 line #7375 fix nested transformations in fix_urllib ........ r76506 | benjamin.peterson | 2009-11-24 18:34:31 -0600 (Tue, 24 Nov 2009) | 1 line use generator expressions in any() ........
-
Vinay Sajip authored
-
Vinay Sajip authored
-
Vinay Sajip authored
Issue #6615: logging: Used weak references in internal handler list. Thanks to flox (Florent Xicluna) for the patch.
-
- 24 Nov, 2009 7 commits
-
-
Mark Dickinson authored
(Should silence some compiler warnings.)
-
Alexandre Vassalotti authored
The reference to copyreg was a unnoticed leftover from the compatibility support for the grand renaming of the standard library in Python 3. The compatibility support was reverted in r63493, but not completely as this patch shows. Based on a patch by Amaury Forgeot d'Arc.
-
Vinay Sajip authored
-
Mark Dickinson authored
-
Mark Dickinson authored
-
Jesse Noller authored
-
Mark Dickinson authored
-
- 23 Nov, 2009 7 commits
-
-
Mark Dickinson authored
%f-style formatting, which used to occur at high precision. Float formatting should now be consistent between 2.7 and 3.1.
-
Georg Brandl authored
-
Mark Dickinson authored
first step towards removing the %f -> %g switch (see issues 7117, 5859).
-
Senthil Kumaran authored
characters.
-
Mark Dickinson authored
-
Mark Dickinson authored
-
Lars Gustäbel authored
closes the internal file object in case of an error (issue #7341).
-
- 22 Nov, 2009 1 commit
-
-
Lars Gustäbel authored
(Note that an empty archive is not the same as an empty file. An empty archive contains no members and is correctly terminated with an EOF block full of zeros. An empty file contains no data at all.) The problem was that although tarfile was able to create empty archives, it failed to open them raising a ReadError. On the other hand, tarfile opened empty files without error in most read modes and presented them as empty archives. (However, some modes still raised errors: "r|gz" raised ReadError, but "r:gz" worked, "r:bz2" even raised EOFError.) In order to get a more fine-grained control over the various internal error conditions I now split up the HeaderError exception into a number of meaningful sub-exceptions. This makes it easier in the TarFile.next() method to react to the different conditions in the correct way. The visible change in its behaviour now is that tarfile will open empty archives correctly and raise ReadError consistently for empty files.
-
- 21 Nov, 2009 3 commits
-
-
Jesse Noller authored
-
Jesse Noller authored
-
Jesse Noller authored
issue5738: The distribution example was confusing, and out of date. It's too large to include inline in the docs as well. It belongs in an addons module outside the stdlib. Removing.
-
- 20 Nov, 2009 7 commits
-
-
Mark Dickinson authored
properly, and use this to skip test_multiprocessing on platforms where sem_open raises a signal. This should fix some FreeBSD buildbot failures for test_multiprocessing.
-
Mark Dickinson authored
-
R. David Murray authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
- 19 Nov, 2009 9 commits
-
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
- Fix #7362: give a good error message for parenthesized arguments with defaults. - Add a py3k warning for any parenthesized arguments since those are not allowed in Py3. This warning is not given in tuple unpacking, since that incurs the tuple unpacking warning.
-
Mark Dickinson authored
-
Ronald Oussoren authored
(Issue 7179)
-
Ronald Oussoren authored
On MacOSX 10.6 the CoreFoundation framework must be initialized on the main thread, the constructor function in that framework will cause an SIGABRT when it is called on any other thread. Because a number of extension link (indirectly) to CoreFoundation and the Python core itself didn't the interpreter crashed when importing some extensions, such as _locale, on a secondary thread. This fix ensures that Python is linked to CoreFoundation on OSX, which results in the CoreFoundation constructor being called when Python is loaded. This does not require code changes.
-
Tarek Ziadé authored
-
Benjamin Peterson authored
-
Raymond Hettinger authored
-
- 18 Nov, 2009 2 commits
-
-
Raymond Hettinger authored
-
Lars Gustäbel authored
constructor in case of an error.
-