- 03 Jun, 2002 2 commits
-
-
Walter Dörwald authored
x in string.whitespace => x.isspace() type(x) in types.StringTypes => isinstance(x, basestring) isinstance(x, types.StringTypes) => isinstance(x, basestring) type(x) is types.StringType => isinstance(x, str) type(x) == types.StringType => isinstance(x, str) string.split(x, ...) => x.split(...) string.join(x, y) => y.join(x) string.zfill(x, ...) => x.zfill(...) string.count(x, ...) => x.count(...) hasattr(types, "UnicodeType") => try: unicode except NameError: type(x) != types.TupleTuple => not isinstance(x, tuple) isinstance(x, types.TupleType) => isinstance(x, tuple) type(x) is types.IntType => isinstance(x, int) Do not mention the string module in the rlcompleter docstring. This partially applies SF patch http://www.python.org/sf/562373 (with basestring instead of string). (It excludes the changes to unittest.py and does not change the os.stat stuff.)
-
Walter Dörwald authored
string.split(foo, bar) must be foo.split(bar) instead of bar.split(foo).
-
- 02 Jun, 2002 15 commits
-
-
Tim Peters authored
-f/--fromfile <filename> option. This runs all and only the tests named in the file, in the order given (although -x may weed that list, and -r may shuffle it). Lines starting with '#' are ignored. This goes a long way toward helping to automate the binary-search-like procedure I keep reinventing by hand when a test fails due to interaction among tests (no failure in isolation, and some unknown number of predecessor tests need to run first -- now you can stick all the test names in a file, and comment/uncomment blocks of lines until finding a minimal set of predecessors).
-
Barry Warsaw authored
parent is now a multipart with one element, the sub-message object).
-
Barry Warsaw authored
Also, adjust to the new message/rfc822 tree layout.
-
Barry Warsaw authored
compatibility module.
-
Barry Warsaw authored
-
Barry Warsaw authored
as_string(): Use Generator.flatten() for better performance.
-
Barry Warsaw authored
Use MIMENonMultipart as the base class so that you can't attach() to these non-multipart message types.
-
Barry Warsaw authored
__call__() can be 2-3x slower than the equivalent normal method. _handle_message(): The structure of message/rfc822 message has changed. Now parent's payload is a list of length 1, and the zeroth element is the Message sub-object. Adjust the printing of such message trees to reflect this change.
-
Barry Warsaw authored
-
Raymond Hettinger authored
-
Neal Norwitz authored
-
Michael W. Hudson authored
There's some wierdness here, but the test ran before and not after, so I'm just hacking the change out. Someone more motivated than me can work out what's really happening. Raymond: *PLEASE* run the test suite before checking things like this in!
-
Martin v. Löwis authored
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
- 01 Jun, 2002 15 commits
-
-
Martin v. Löwis authored
compiler. Fixes #559429. 2.2 bugfix candidate.
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Barry Warsaw authored
-
Barry Warsaw authored
subclasses. MIMENonMultipart: Base class for non-multipart/* content type subclass specializations, e.g. image/gif. This class overrides attach() which raises an exception, since it makes no sense to attach a subpart to e.g. an image/gif message. MIMEMultipart: Base class for multipart/* content type subclass specializations, e.g. multipart/mixed. Does little more than provide a useful constructor.
-
Barry Warsaw authored
better code reuse. _split() Use _floordiv().
-
Barry Warsaw authored
-
Tim Peters authored
debug build. Repaired that, and rewrote other parts to reduce long-winded casting.
-
Barry Warsaw authored
Python 2.1 compatibility.
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
- 31 May, 2002 8 commits
-
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Neal Norwitz authored
-
Raymond Hettinger authored
-
Guido van Rossum authored
If a rexec instance allows writing in the current directory (a common thing to do), there's a way to execute bogus bytecode. Fix this by not allowing imports from .pyc files (in a way that allows a site to configure things so that .pyc files *are* allowed, if writing is not allowed). I'll apply this to 2.2 and 2.1 too.
-
Guido van Rossum authored
-
Neal Norwitz authored
-
Neal Norwitz authored
-