Tim Peters [Fri, 11 Mar 2005 17:20:43 +0000 (17:20 +0000)]
Bug #1160802: Can't build Zope on Windows w/ 2.4.1c1.
MSVCCompiler.initialize(): set self.initialized to True, as suggested
by AMK. Else we keep growing the PATH endlessly, with each new C
extension built, until putenv() complains.
This doesn't appear to be an issue on the HEAD (MSVCCompiler initializes
itself via __init__() on the HEAD).
Also added a "2.4.1c2" section to NEWS. Not meant to imply that Anthony
will do a 2.4.1c2 release, just needed to a place to put the news about the
MSVCCompiler bugfix.
Fred Drake [Thu, 10 Mar 2005 04:59:14 +0000 (04:59 +0000)]
- fix generated Texinfo markup for \deprecated
- add support for additional markup: \leq, \textbar, \textit
- add a comment about the non-support for the Euro character
Greg Ward [Mon, 7 Mar 2005 01:32:03 +0000 (01:32 +0000)]
SF #818006: add useful read-only attributes to oss_audio_device object:
'closed', 'name', and 'mode' (as recommended by
http://python.org/doc/current/lib/bltin-file-objects.html).
Fred Drake [Thu, 3 Mar 2005 17:24:20 +0000 (17:24 +0000)]
minor edits:
- function names marked with \function should include parentheses
- "standard error" instead of "stderr" for text
- a boolean parameter takes true or false values, not just True or False
Ka-Ping Yee [Sat, 19 Feb 2005 22:57:37 +0000 (22:57 +0000)]
Use getdoc(object) instead of object.__doc__ to fix indentation problems.
Thanks to Robert Dick <dickrp@ece.northwestern.edu> for reporting this bug
and submitting a patch.
Adjust doc(object) to display useful documentation for plain values (e.g.
help([]) now shows the methods on the list instead of just printing "[]").
(This change has been tested interactively, by generating docs for the
standard library, and by running the module documentation webserver.)
[ 1124295 ] Function's __name__ no longer accessible in restricted mode
which I introduced with a bit of mindless copy-paste when making
__name__ writable. You can't assign to __name__ in restricted mode,
which I'm going to pretend was intentional :)
Thomas Heller [Thu, 3 Feb 2005 20:37:04 +0000 (20:37 +0000)]
Running a bdist_wininst installer, built with Python 2.3, installing
for Python 2.4 caused a segfault when post_install_script was used.
The reason was that the file handle passed to PyRun_SimpleFile() was
created with MSVCRT.DLL, but Python 2.4 uses MSVCR71.DLL.
So, I replaced PyRun_SimpleFile() with PyRun_SimpleString(). The
segfault is gone, but the output of the postinstall script doesn't
show up, because still freopen() from MSVCRT is used.
Thomas Heller [Thu, 20 Jan 2005 19:25:24 +0000 (19:25 +0000)]
Some bugs have been fixed in distutils, so increment the last part of
the version number. For the distutils version numbering scheme, see
http://mail.python.org/pipermail/distutils-sig/2005-January/004368.html
Backport for bug #839496: always read files in binary mode. Opening files in
text mode may cause newline translations, making the actual size of the content
transmitted *less* than the content-length.
Backport patch #712317: In URLs such as http://www.example.com?query=spam,
treat '?' as a delimiter. Previously, the 'network location' (<authority> in
RFC 2396) would become 'www.example.com?query=spam', while RFC 2396 does not
allow a '?' in <authority>. See bug #548176 for further discussion.
Backport patch #1095362: replace hardcoded test for POST/GET with call to
get_method, removing some duplication and gaining some flexibility in the
process.
* In the documentation for createDocument(), it is now stated that the Python
DOM API allows implementations to forego creation of the document element
child node, if no namespace and local name arguments are given. (This
possibility is left open and unaddressed in the W3C spec).
* Addition by me: use 'name' rather than 'attname', for consistency with the
DOM specification and the Python DOM API implementation.
Jack Jansen [Fri, 7 Jan 2005 13:17:33 +0000 (13:17 +0000)]
Backport of Patch #1097739 by Bob Ippolito:
MacOSX: if we cannot use -undefined dynamic_lookup (such as on 10.2 or earlier)
we link extension directly against the dynamic library in the framework in
stead of against the framework. This will fix building extensions for 2.3
after 2.4 has been installed too.