| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixed (re: SF bug #555035). Include a unittest.
|
|
|
|
| |
closes patch #536278.
|
|
|
|
|
|
|
|
|
| |
A MemoryError is now raised when the list cannot be created.
There is a test, but as the comment says, it really only
works for 32 bit systems. I don't know how to improve
the test for other systems (ie, 64 bit or systems
where the data size != addressable size,
e.g. 64 bit data, but 48 bit addressable memory)
|
| |
|
|
|
|
|
|
| |
the AddressList.addresslist attribute directly.
Also, add a test case for the email.Utils.getaddresses() interface.
|
| |
|
|
|
|
|
| |
non-callable objects is always None. This makes for less confusing
output and fixes the problem reported in SF patch #550290.
|
|
|
|
|
|
|
|
| |
instead of calling the getaddrlist() method, since the latter doesn't
work with multiple calls (it will return the empty list for the second
and subsequent calls).
Closes SF bug #555035. Include a unittest.
|
| |
|
|
|
|
|
|
| |
of the PyUNIT version of the same file. This helps people understand that
this version is the same as the version from the independent PyUNIT
release (confusion was indicated on the PyUNIT mailing list).
|
| |
|
|
|
|
| |
This is a strange test.
|
|
|
|
| |
I'm getting better at vi!
|
|
|
|
|
|
| |
works better (at all!) in --disable-unicode builds.
Bugfix candidate, probably.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and explicit maxlinelen arguments to the Header constructor.
|
|
|
|
|
|
|
|
|
|
|
|
| |
email package's Parser to handle the three common line endings.
Certain protocols such as IMAP define CRLF line endings and it doesn't
make sense for the client app to have to normalize the line endings
before handing it message off to the Parser.
_parsebody(): Be more flexible in the matching of line endings for
finding the MIME separators. Accept any of \r, \n and \r\n. Note
that we do /not/ change the line endings in the payloads, we just
accept any of those three around MIME boundaries.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
single byte character sets. Also fixed a semantic problem with the
constructor's default arguments. Specifically,
__init__(): Change the maxlinelen argument default to None instead of
MAXLINELEN. The semantics should have been (and now are) that if
maxlinelen is given it is always honored. If it isn't given, but
header_name is given, then the maximum line length is calculated. If
neither are given then the default 76 characters is used.
_split(): If the character set is a single byte character set then we
can split the line at the maxlinelen because we know that encoding the
header won't increase its length. If the charset isn't a single byte
charset then we use the quicker divide-and-conquer line splitting
algorithm as before.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the email package. The former is now just a shell project that
has some extra files for packaging for independent use (e.g. setup.py
and README).
Added a compatibility layer so that the same API can be used in Python
2.1 and 2.2/2.3 with the major differences shuffled off into helper
modules (_compat21.py and _compat22.py).
Also bumped the package version number to 2.0.3 for some fixes to be
checked in momentarily.
|
| |
|
|
|
|
|
|
|
| |
[ 555382 ] test_array v.s. --disable-unicode
+ MvL's suggestions. Just the 32 failing tests in --disable-unicode builds
now...
|
|
|
|
| |
Closes patch 556161.
|
| |
|
| |
|
|
|
|
| |
Raymond Hettinger, beware! This caused the Unix install to fail!
|
| |
|
| |
|
|
|
|
|
|
| |
Scot Stevenson. Could be a bug fix candidate, but probably doesn't
matter much unless a certain blue-nosed cat suddenly becomes corporeal
and starts emailing some stmp.py (sic) fronted mailer.
|
| |
|
|
|
|
|
|
|
|
| |
returned a proxy for __class__ whose __bases__ was also a proxy. The
merge_class_dict() helper for dir() assumed incorrectly that __bases__
would always be a tuple and used the in-line tuple API on the proxy.
I will backport this to 2.2 as well.
|
| |
|
|
|
|
| |
following IAC. Bugfix candidate if anyone cares.
|
| |
|
|
|
|
| |
Closes patch 552452 and feature request 426539.
|
|
|
|
|
| |
NOT a bugfix candidate: this is a fix to an optimization introduced
in 2.3.
|
|
|
|
|
|
| |
test if 'callable' has not been supplied is to test for None instead of
False. The previous correction to 'if callable()' was wrong because an unusable
callback would be ignored rather than raising an exception.
|
| |
|
| |
|
|
|
|
| |
candidate.
|
|
|
|
|
|
|
|
|
|
|
| |
and the .seed() and .whseed() methods failed to reset it. In other
words, setting the seed didn't completely determine the sequence of
results produced by random.gauss(). It does now. Programs repeatedly
mixing calls to a seed method with calls to gauss() may see different
results now.
Bugfix candidate (random.gauss() has always been broken in this way),
despite that it may change results.
|
|
|
|
|
| |
"What's New in Python 2.2" documented that these would be removed in
Python 2.3.
|
| |
|
|
|
|
| |
See SF bug #551285.
|