summaryrefslogtreecommitdiffstats
path: root/Lib
Commit message (Collapse)AuthorAgeFilesLines
* Prepare for 2.3.7.v2.3.7Martin v. Löwis2008-03-112-1/+6
|
* Revert r52798, r52803, r52824, r54342, as they don't fixMartin v. Löwis2008-03-025-31/+8
| | | | security issues.
* SF patch #1556895; Typo in encoding name in email package.Barry Warsaw2007-03-132-6/+6
| | | | Patch supplied by Guillaume Rousse.
* [Jython patch #1599050] Avoid crash when os module lacks fstat()Andrew M. Kuchling2006-11-221-1/+3
|
* Jython compatibility fix: if uu.decode() opened its output file, be sure toAndrew M. Kuchling2006-11-201-0/+4
| | | | close it.
* Add extra SHA testsAndrew M. Kuchling2006-11-201-1/+18
|
* updates for 2.3.6 finalAnthony Baxter2006-11-012-1/+6
|
* preparing for 2.3.6c1Anthony Baxter2006-10-232-1/+6
|
* Fix the tests to work with Python 2.1, which email 2.5 must do.Barry Warsaw2006-07-261-4/+4
|
* Back port r50693 and r50754 from the trunk (and 2.4 branch):Barry Warsaw2006-07-253-37/+183
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | decode_rfc2231(): Be more robust against buggy RFC 2231 encodings. Specifically, instead of raising a ValueError when there is a single tick in the parameter, simply return that the entire string unquoted, with None for both the charset and the language. Also, if there are more than 2 ticks in the parameter, interpret the first three parts as the standard RFC 2231 parts, then the rest of the parts as the encoded string. More RFC 2231 improvements for the email 4.0 package. As Mark Sapiro rightly points out there are really two types of continued headers defined in this RFC (i.e. "encoded" parameters with the form "name*0*=" and unencoded parameters with the form "name*0="), but we were were handling them both the same way and that isn't correct. This patch should be much more RFC compliant in that only encoded params are %-decoded and the charset/language information is only extract if there are any encoded params in the segments. If there are no encoded params then the RFC says that there will be no charset/language parts. Note however that this will change the return value for Message.get_param() in some cases. For example, whereas before if you had all unencoded param continuations you would have still gotten a 3-tuple back from this method (with charset and language == None), you will now get just a string. I don't believe this is a backward incompatible change though because the documentation for this method already indicates that either return value is possible and that you must do an isinstance(val, tuple) check to discriminate between the two. (Yeah that API kind of sucks but we can't change /that/ without breaking code.) Test cases, some documentation updates, and a NEWS item accompany this patch. Original fewer-than-3-parts fix by Tokio Kikuchi. Resolves SF bug # 1218081. Also, bump the package version number to 2.5.8 for release.
* Back port from 2.4 branch:Barry Warsaw2006-05-014-0/+18
| | | | | | | | | Patch #1464708 from William McVey: fixed handling of nested comments in mail addresses. E.g. "Foo ((Foo Bar)) <foo@example.com>" Fixes for both rfc822.py and email package.
* Resolve SF bug 1409403: email.Message should supress warning from uu.decode.Barry Warsaw2006-02-094-8/+48
| | | | | | | | However, the patch in that tracker item is elaborated such that the newly included unit test pass on Python 2.1 through 2.5. Note that Python 2.1's uu.decode() does not have a 'quiet' argument, so we have to be sneaky. Will port to email 3.0 (although without the backward compatible sneakiness).
* Patches to address SF bugs 1409538 (Japanese codecs in CODEC_MAP) and 1409455Barry Warsaw2006-02-085-27/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | (.set_payload() gives bad .get_payload() results). Specific changes include: Simplfy the default CODEC_MAP in Charset.py to not include the Japanese and Korean codecs. The names of the codecs are different depending on whether you're using Python 2.4 and 2.5, which include the codecs by default, or earlier Python's which provide the codecs under different names as a third party library. Now, we attempt to discover which (if either) is available and populate the CODEC_MAP as appropriate. Message.set_charset(): When the message does not already have a Content-Transfer-Encoding header, instead of just adding the header, we also encode the body as defined by the assigned Charset. As before, if the body_encoding is callable, we just call that. If not, then we add a call to body_encode() before setting the header. This way, we guarantee that a message's text payload is always encoded properly. Remove the payload encoding code from Generator._handle_text(). With the above patch, this would cause the body to be doubly encoded. Doing this in the Message class is better than only doing it in the Generator. Added some new tests to ensure everything works correctly. Also changed the way the test_email_codecs.py tests get added (using the same lookup code that the CODEC_MAP adjustments use). This resolves both issues for email 2.5/Python 2.3. I will patch forward to email 3.0 for both Python 2.4 and 2.5.
* Resolves SF bug #1423972.Barry Warsaw2006-02-041-2/+4
|
* parsedate_tz(): Return a 1 in the tm_yday field so that the value isBarry Warsaw2006-02-032-5/+13
| | | | | | | | | | 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.
* SF bug #1403349 solution for email 2.5; some MUAs use the 'file' parameterBarry Warsaw2006-01-174-7/+53
| | | | | | | | | | 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. XXX Need to update the documentation.
* For reference, add tests for PCRE fix; the tests aren't run by default ↵Andrew M. Kuchling2005-08-311-0/+18
| | | | because I wanted to minimize upheaval to the 2.3 test suite
* get_filename(), get_content_charset(): It's possible that the charset named inBarry Warsaw2005-04-293-9/+69
| | | | | | | | | | | | | 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.
* damnAnthony Baxter2005-02-081-2/+2
|
* 2.3.5 finalAnthony Baxter2005-02-082-1/+6
|
* sligtly strengthen unit tests for copy.pyAlex Martelli2005-02-071-1/+27
|
* fix bug 1114776Alex Martelli2005-02-062-1/+19
|
* fix XMLFilterBase.resolveEntity() so the caller gets the resultFred Drake2005-02-031-1/+1
| | | | (PyXML bug #1112052)
* Security fix PSF-2005-001 for SimpleXMLRPCServer.py.Guido van Rossum2005-02-031-5/+29
|
* Fix typo in verbose output for RLock when the initial lock acquisition occurs.Brett Cannon2005-01-271-1/+1
| | | | Closes bug #1110998.
* Recompiled after source changes.Thomas Heller2005-01-251-0/+0
|
* 1.0.5, to match the python patchlevelAnthony Baxter2005-01-251-1/+1
|
* copy.py fixed to first lookup __copy__ from the instance being copied,Anthony Baxter2005-01-252-4/+75
| | | | rather than only looking at the type - this was broken in 2.3.
* pre-release bitsAnthony Baxter2005-01-252-4/+4
|
* At least one bug has been fixed in distutils, so increment the last part ofThomas Heller2005-01-201-1/+1
| | | | | the version number. For the distutils version numbering scheme, see http://mail.python.org/pipermail/distutils-sig/2005-January/004368.html
* Fix [ 1103844 ] fix distutils.install.dump_dirs() with negated options.Thomas Heller2005-01-201-2/+7
| | | | Backport from trunk.
* On OpenBSD, terminating IDLE with ctrl-c from the command line caused aKurt B. Kaiser2005-01-192-3/+7
| | | | | | | stuck subprocess MainThread because only the SocketThread was exiting. M NEWS.txt M run.py
* Backport configDialog.py rev 1.60:Kurt B. Kaiser2005-01-192-0/+7
| | | | | | | | | 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. M NEWS.txt M configDialog.py
* Backport EditorWindow rev 1.60 configHelpSourceEdit rev 1.7 15Jul04Kurt B. Kaiser2005-01-193-21/+33
| | | | | | | | | checking sys.platform for substring 'win' was breaking IDLE docs on Mac (darwin). Also, Mac Safari browser requires full file:// URIs. SF 900580. M EditorWindow.py M NEWS.txt M configHelpSourceEdit.py
* Backport rpc.py rev 1.28 dating from 21Jan04Kurt B. Kaiser2005-01-193-9/+15
| | | | | | | | | | | | | | | | | 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. M NEWS.txt M idlever.py M rpc.py
* If an extension can't be loaded, print warning and skip it instead ofKurt B. Kaiser2005-01-172-1/+8
| | | | erroring out.
* Improve error handling when .idlerc can't be created. This is a partialKurt B. Kaiser2005-01-172-2/+6
| | | | backport of configHandler.py, Revision 1.36, 11Jan05.
* Backport of fixes for #887242 and #1097739:Jack Jansen2005-01-111-1/+15
| | | | | | | | | | | | | 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.
* Backport of 1.38:Jack Jansen2005-01-071-135/+136
| | | | Allow relative URLs for included databases and packages.
* Backport of 1.37:Jack Jansen2005-01-031-7/+43
| | | | | | | | | | - 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.
* Backport:Jack Jansen2004-12-312-7/+13
| | | | | | 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.
* Backport of 1.36:Jack Jansen2004-12-281-2/+2
| | | | | | | - 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.
* Use zlib test suite from the trunk (rev. 2.67) on the 2.3 maintenance branchAndrew M. Kuchling2004-12-281-170/+93
|
* Bump idle version.Kurt B. Kaiser2004-12-231-1/+1
|
* The GUI was hanging if the shell window was closed while a raw_input()Kurt B. Kaiser2004-12-232-7/+17
| | | | | | | | was pending. Restored the quit() of the readline() mainloop(). http://mail.python.org/pipermail/idle-dev/2004-December/002307.html M NEWS.txt M PyShell.py
* Recompiled after source file changes.Thomas Heller2004-12-221-0/+0
|
* * closes SF bug/patch 967763Gregory P. Smith2004-12-191-0/+11
| | | | | | | | - 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.
* Backport of fix for bug #1083645; skip test_imp if threading is not available.Brett Cannon2004-12-181-1/+5
|
* Don't have test_mkalias_relative exexute if sys.prefix does not exist.Brett Cannon2004-12-061-0/+2
| | | | Backport of fix for bug #1077302.
* get_boundary(): Fix for SF bug #1060941. RFC 2046 says boundaries may beginBarry Warsaw2004-11-061-1/+2
| | | | -- but not end -- with whitespace.
generated by cgit v0.12 at 2025-12-26 12:30:45 (GMT)