R. David Murray [Wed, 29 Apr 2009 13:17:37 +0000 (13:17 +0000)]
Fix issue 2245. aifc now skips any chunk type it doesn't actually
process instead of throwing errors for anything not in an explicit
skip list. This is per this spec: http://www.cnpbagwell.com/aiff-c.txt.
Spec reference and test sound file provided by Santiago Peresón, fix
based on patch by Hiroaki Kawai.
R. David Murray [Tue, 28 Apr 2009 16:08:18 +0000 (16:08 +0000)]
Various small fixups to the multiprocessing docs, mostly fixing and
enabling doctests that Sphinx can run, and fixing and disabling tests that
Sphinx can't run. I hand checked every test not now marked as a doctest,
and all except the two that have open bug reports against them now work,
at least on Linux/trunk. (I did not look at the last example at all since
there was already an open bug). I did not read the whole document with
an editor's eye, but I did fix a few things I noticed while working on
the tests.
Antoine Pitrou [Mon, 27 Apr 2009 21:53:26 +0000 (21:53 +0000)]
Issue #1734234: Massively speedup `unicodedata.normalize()` when the
string is already in normalized form, by performing a quick check beforehand.
Original patch by Rauli Ruohonen.
Antoine Pitrou [Mon, 27 Apr 2009 20:50:20 +0000 (20:50 +0000)]
Issue #5853: calling a function of the mimetypes module from several threads
at once could hit the recursion limit if the mimetypes database hadn't been
initialized before.
R. David Murray [Mon, 27 Apr 2009 17:22:36 +0000 (17:22 +0000)]
Make sys.xxx variable references into links, note that print_last only
works when an exception gets to the interactive prompt, and update the
examples after testing. The last one is now a valid Sphinx doctest,
but of the preceding two one can't be made a doctest and the other one
I'm postponing to 3.x because sphinx handles doctests as Unicode strings
and that makes the 2.x output confusing.
Georg Brandl [Mon, 27 Apr 2009 15:29:09 +0000 (15:29 +0000)]
Demote warnings to notices where appropriate, following the goal that as few "red box" warnings
should clutter the docs as possible. Part 1: stuff that gets merged to Py3k.
Issue #4129: More documentation pointers about int -> Py_ssize_t.
Also fix up the documentation for PyObject_GC_Resize(). It seems that since
it first got documented, the documentation was actually for
_PyObject_GC_Resize().
Issue #4129: Belatedly document which C API functions had their argument(s) or
return type changed from int or int * to Py_ssize_t or Py_ssize_t * as this
might cause problems on 64-bit platforms.
Walter Dörwald [Sat, 25 Apr 2009 12:15:07 +0000 (12:15 +0000)]
Issue #5837: Certain sequences of calls to set() and unset() for
support.EnvironmentVarGuard objects restored the environment variables
incorrectly on __exit__.
Fix this by recording the initial value of each environment variable on the
first access in set() or unset().
Mark Dickinson [Fri, 24 Apr 2009 16:34:14 +0000 (16:34 +0000)]
Issue #5593: Use more robust test for double-rounding in test_fsum.
While we're at it, use new unittest.skipUnless decorator to
implement skipping for that test.
Mark Dickinson [Fri, 24 Apr 2009 12:46:53 +0000 (12:46 +0000)]
Issue #5816:
- simplify parsing and printing of complex numbers
- make complex(repr(z)) round-tripping work for complex
numbers involving nans, infs, or negative zeros
- don't accept some of the stranger complex strings
that were previously allowed---e.g., complex('1..1j')
Eric Smith [Wed, 22 Apr 2009 13:29:05 +0000 (13:29 +0000)]
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.