| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should be faster.
This means:
(1) "for line in file:" won't work if the xreadlines module can't be
imported.
(2) The body of "for line in file:" shouldn't use the file directly;
the effects (e.g. of file.readline(), file.seek() or even
file.tell()) would be undefined because of the buffering that goes
on in the xreadlines module.
|
| |
|
|
|
|
| |
ought to be faster.
|
|
|
|
| |
instead. Allows this test to finish on Windows again.
|
| |
|
|
|
|
| |
localization of month and day names.
|
|
|
|
|
|
| |
when #ifdef was needed.
This closes (reallu!) SF bug #417418.
|
|
|
|
|
| |
add a list of the mapping methods which are not supported (per Barry's
comments).
|
|
|
|
| |
objects.
|
| |
|
|
|
|
| |
rfc822.Message objects, based on comments from Barry.
|
|
|
|
|
|
| |
for loading modules from the application resource fork stopped working
when sys.path component normalization was implemented. Comparison
of sys.path components is now done by FSSpec in stead of by pathname.
|
|
|
|
|
|
|
| |
ICK ALERT: read the long comment block before run_the_test(). It was
almost impossible to get this to run without instant deadlock, and the
solution here sucks on several counts. If you can dream up a better way,
let me know!
|
| |
|
|
|
|
|
|
|
|
| |
numbers that display nicely after repr(). From much doctest experience
with the same trick, I believe people find examples with simple fractions
easier to understand too: they can usually check the results in their
head, and so feel confident about what they're seeing. Not even I get a
warm feeling from a result that looks like 70330.345024097141 ...
|
|
|
|
| |
prototype, for gcc -Wstrict-prototypes.
|
|
|
|
|
| |
pointers to information about the other mailbox formats; if anyone can
provide the information needed, please let me know!
|
|
|
|
|
| |
test; there is no need to store this in a file if the actual test code
does not produce any output.
|
|
|
|
|
| |
contains a single line of text giving the name of the output file. This
covers all tests that do not actually produce any output in the test code.
|
|
|
|
|
| |
delete ones that can't be imported due to missing symbols or other
causes.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
UTF-16 codec will now interpret and remove a *leading* BOM mark. Sub-
sequent BOM characters are no longer interpreted and removed.
UTF-16-LE and -BE pass through all BOM mark characters.
These changes should get the UTF-16 codec more in line with what
the Unicode FAQ recommends w/r to BOM marks.
|
| |
|
|
|
|
|
| |
for the Maildir mailbox format. This still does not address other mailbox
formats.
|
|
|
|
|
|
|
|
|
| |
basically accept <!...> where the dots can be single- or double-quoted
strings or any other character except >.
Background: I found a real-life example that failed to parse with
the old assumption: http://www.opensource.org/licenses/jabberpl.html
contains a few constructs of the form <![if !supportLists]>...<![endif]>.
|
|
|
|
|
| |
indicate it took an argument. This closes SF patch #402223 by Bastian
Kleineidam.
|
|
|
|
|
|
|
|
|
|
|
| |
indicating whether the entry was extracted from a docstring or not.
write(): If any of the locations of a string appearance came from a
docstring, add a comment such as
#. docstring
before the references (after a suggestion by Martin von Loewis).
|
|
|
|
|
|
| |
first by filename and then by line number. Closes SF patch #425821.
Also, fixes a problem with duplicate entries.
|
|
|
|
|
|
|
|
|
|
| |
floating point numbers in an interactive example.
Added comment to help explain control flow in the example code showing
how to check if a number is prime.
This closes SF bugs 419434 and 424552.
|
| |
|
|
|
|
| |
This closes SF bug #425320.
|
|
|
|
|
| |
Mark Hammond claimed that the iterized filter() forgot to decref the
iterator upon return. He was right!
|
| |
|
|
|
|
|
|
|
| |
but doing so raised EOFError. This makes it work as advertised and
converts to string methods where reasonable.
This closes SF bug #424776.
|
| |
|
| |
|
|
|
|
| |
easier with gcc -Wstrict-function-prototypes.
|
| |
|
|
|
|
| |
have been there in the first place.
|
|
|
|
| |
now appears to work.
|
|
|
|
|
| |
Test for TARGET_API_MAC_OS8 in stead of !TARGET_API_MAC_CARBON where
appropriate.
|
| |
|
|
|
|
| |
the stuff that is only needed on classic-MacOS.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Two exceedingly unlikely errors in dictresize():
1. The loop for finding the new size had an off-by-one error at the
end (could over-index the polys[] vector).
2. The polys[] vector ended with a 0, apparently intended as a sentinel
value but never used as such; i.e., it was never checked, so 0 could
have been used *as* a polynomial.
Neither bug could trigger unless a dict grew to 2**30 slots; since that
would consume at least 12GB of memory just to hold the dict pointers,
I'm betting it's not the cause of the bug Fred's tracking down <wink>.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PyTuple_GetItem() with PyTuple_GET_SIZE() and PyTuple_GET_ITEM().
The code has already done a PyTuple_Check().
|