Barry Warsaw [Fri, 3 Feb 2006 04:41:24 +0000 (04:41 +0000)]
parsedate_tz(): Return a 1 in the tm_yday field so that the value is
acceptable to Python 2.4's time.strftime(). This fix mirrors the behavior in
email 3.0. That field is documented as being "not useable" so it might as
well not be buggy too <wink>.
Add a test for this behavior and update a few tests that were expecting a 0 in
this field. After committing I will run the entire Python 2.3 test suite to
ensure this doesn't break any Python tests.
Barry Warsaw [Tue, 17 Jan 2006 04:34:54 +0000 (04:34 +0000)]
SF bug #1403349 solution for email 2.5; some MUAs use the 'file' parameter
name in the Content-Distribution header, so Message.get_filename() should fall
back to using that. Will port both to email 3.0 and Python 2.5 trunk.
Also, bump the email package version to 2.5.7 for eventual release. Of
course, add a test case too.
Barry Warsaw [Fri, 29 Apr 2005 12:12:02 +0000 (12:12 +0000)]
get_filename(), get_content_charset(): It's possible that the charset named in
an RFC 2231-style header could be bogus or unknown to Python. In that case,
we return the the text part of the parameter undecoded. However, in
get_content_charset(), if that is not ascii, then it is an illegal charset and
so we return failobj.
Test cases and a version bump are included.
Committing this to the Python 2.3 branch because I need to generate an email
2.5.6 release that contains these patches. I will port these fixes to Python
2.4 and 2.5 for email 3.x.
Thomas Heller [Tue, 25 Jan 2005 20:46:48 +0000 (20:46 +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.
(I would be very gratefull if someone proofreads the patch, at least).
Thomas Heller [Thu, 20 Jan 2005 19:28:44 +0000 (19:28 +0000)]
At least one bug has 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
Kurt B. Kaiser [Wed, 19 Jan 2005 05:53:32 +0000 (05:53 +0000)]
Backport configDialog.py rev 1.60:
Saving a Keyset w/o making changes (by using the "Save as New Custom Key Set"
button) caused IDLE to fail on restart (no new keyset was created in
config-keys.cfg). Also true for Theme/highlights. Python Bug 1064535.
Kurt B. Kaiser [Wed, 19 Jan 2005 01:44:06 +0000 (01:44 +0000)]
Backport rpc.py rev 1.28 dating from 21Jan04
rpc.py:SocketIO - Large modules were generating large pickles when downloaded
to the execution server. The return of the OK response from the subprocess
initialization was interfering and causing the sending socket to be not
ready. Add an IO ready test to fix this. Moved the polling IO ready test
into pollpacket().
Fix typo in rpc.py, s/b "pickle.PicklingError" not "pickle.UnpicklingError".
idlever.py should be 1.0.4 to align with NEWS.txt. There was no IDLE release
at 2.3.1 which accounts for the unsync.
If $MACOSX_DEPLOYMENT_TARGET is set, and >= 10.3, during configure we
setup extensions to link with dynamic lookup. We also record the
value in the Makefile, and distutils uses the same value to build extension
modules. If MACOSX_DEPLOYMENT_TARGET is not set it defaults to the
current OSX version.
If we cannot use -undefined dynamic_lookup (such as on 10.2 or earlier)
we link extensions 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.
Jack Jansen [Tue, 4 Jan 2005 16:05:33 +0000 (16:05 +0000)]
Backport of 1.55 and 1.57:
- Added quotes around the destroot arguments, so empty destroot works.
- Run fixapplepython23 script to check whether Apple's Python 2.3 needs
to be patched.
Jack Jansen [Mon, 3 Jan 2005 15:46:30 +0000 (15:46 +0000)]
Backport of 1.37:
- Added an "installer" flavor, which uses the "open" command to install
something (overridable through Install-command entry)
- Hidden status is now determined by flavor == hidden, not by
missing Download-URL. Hidden packages behave like installer packages.
- Made some error messages a bit more understandable.
Because there's new functionality the version has been upped to 0.5.
Jack Jansen [Sun, 2 Jan 2005 23:17:06 +0000 (23:17 +0000)]
Added a band-aid to make this script work with the older 2.3.0
buildtools if no destroot option is given. That makes life for the
additions installer a lot simpler.
Jack Jansen [Fri, 31 Dec 2004 10:44:41 +0000 (10:44 +0000)]
Backport:
Fix for #1091468: DESTROOTed frameworkinstalls fail. Added a --destroot
option to various tools, and do the right thing when we're doing a destroot
install.
Jack Jansen [Tue, 28 Dec 2004 21:53:15 +0000 (21:53 +0000)]
Backport of 1.36:
- getDefaultDatabase wasn't listed in __all__.
- using a different database for non-final releases should only be done
for X.Y.0. Non-final micro releases can use the default database just fine,
as they are required to be backward compatible.
Kurt B. Kaiser [Thu, 23 Dec 2004 04:26:55 +0000 (04:26 +0000)]
The GUI was hanging if the shell window was closed while a raw_input()
was pending. Restored the quit() of the readline() mainloop().
http://mail.python.org/pipermail/idle-dev/2004-December/002307.html
Thomas Heller [Wed, 22 Dec 2004 15:35:20 +0000 (15:35 +0000)]
Backport a patch from Mark Hammond.
Partial fix for [1067732] - "wininst --install-script leaves residual
files on C:\"
'tempnam()' is used rather than 'tmpnam()' - 'tmpnam' creates a temp
file on the root of the current drive, and if this is readonly
explains the 'freopen' errors occasionally reported. 'tempnam' creates
the temp file in the %TEMP% directory.
Gregory P. Smith [Sun, 19 Dec 2004 23:59:51 +0000 (23:59 +0000)]
* closes SF bug/patch 967763
- fixes various memory leaks found by valgrind and a follup closer
code inspection of the bsddb module. (merges r1.32 of _bsddb.c
and an associated test case)
- also merges the one line r1.37 _bsddb.c fix that fixes a leak on
the rare DBEnv creation failed error path.
Gregory P. Smith [Sun, 19 Dec 2004 23:27:48 +0000 (23:27 +0000)]
In 1.17.6.4 part of the patch committed in 1.17.6.3 got reapplied to
the end of a second function whos code was identical enough for patch
not to reject the patch. this reverses that misapplication (only the
DBC_set_range method needed modification, not DBC_set as well). This
problem only exists in the release32-maint branch.
Gregory P. Smith [Sun, 19 Dec 2004 22:39:01 +0000 (22:39 +0000)]
redo this patch on release23-maint rather than release23-branch:
revision 1.17.4.1
date: 2003/11/03 21:37:43; author: greg; state: Exp; lines: +9 -9
* SF patch 835100 - C++ // comments are not allowed. use /* */
Matthias Klose [Wed, 1 Dec 2004 07:36:58 +0000 (07:36 +0000)]
Taken from 2.4/HEAD:
- Bug #875692: Improve signal handling, especially when using threads, by
forcing an early re-execution of PyEval_EvalFrame() "periodic" code when
things_to_do is not cleared by Py_MakePendingCalls().