| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
advertised in the docs.
|
|
|
|
|
| |
that given the inputs in these tests Excel does indeed produce the output
these tests expect. Document that for future confused folks.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove various dependencies on dictionary order in the standard library
tests, and one (clearly an oversight, potentially critical) in the
standard library itself - base64.py.
Remaining open issues:
* test_extcall is an output test, messy to make robust
* tarfile.py has a potential bug here, but I'm not familiar
enough with this code. Filed in as SF bug #1496501.
* urllib2.HTTPPasswordMgr() returns a random result if there is more
than one matching root path. I'm asking python-dev for
clarification...
|
|
|
|
|
|
|
|
| |
returning 'a' as the delimiter. It now returns '|', but not because I
understood better what the code was supposed to do. Would someone that
understands the idea behind _guess_delimiter() (see its doc string) look to
see if my fallback choice is better than before or if it's just serendipity
that I picked the proper delimiter?
|
|
|
|
|
|
| |
last field was empty it would strip the delimiter and incorrectly guess that
"" was the delimiter. Reported in c.l.py by Laurent Laporte. Will
backport.
|
| |
|
| |
|
|
|
|
|
| |
user error messages (otherwise difficult to do without instrumenting
the source).
|
|
|
|
| |
to floats.
|
| |
|
|
|
|
|
|
|
|
| |
PyNumber_Check, rather than trying to convert to a float. Reimplemented
writer - now raises exceptions when it sees a quotechar but neither
doublequote or escapechar are set. Doublequote results are now more
consistent (eg, single quote should generate """", rather than "",
which is ambiguous).
|
|
|
|
| |
gets).
|
| |
|
|
|
|
|
|
|
| |
when this limit is reached. Limit defaults to 128k, and is changed
by module set_field_limit() method. Previously, an unmatched quote
character could result in the entire file being read into the field
buffer, potentially exhausting virtual memory.
|
|
|
|
| |
dialect type (which has a better idea of what is and isn't valid).
|
|
|
|
|
|
| |
was done because we were previously performing validation of the dialect
from python, but this is now down within the C module. Also, the method
we were using to detect classes did not work with new-style classes.
|
|
|
|
|
| |
record objects of internal dialect type, rather than instances of
python objects.
|
|
|
|
| |
left in stream).
|
| |
|
|
|
|
|
| |
implementation features better error reporting, and better compliance
with the PEP.
|
| |
|
|
|
|
| |
Goal is to work in the direction of universal newline support.
|
|
|
|
|
|
|
|
|
| |
is None, the next row read is used as the fieldnames. In the common case,
this means the programmer doesn't need to know the fieldnames ahead of time.
The first row of the file will be used. In the uncommon case, this means
the programmer can set the reader's fieldnames attribute to None at any time
and have the next row read as the next set of fieldnames, so a csv file can
contain several "sections", each with different fieldnames.
|
|
|
|
| |
will backport.
|
| |
|
|
|
|
|
| |
* Add optional delimiters arg to Sniffer.sniff() which restricts the set of
candidate field delimiters.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
and test_support.run_classtests() into run_unittest()
and use it wherever possible.
Also don't use "from test.test_support import ...", but
"from test import test_support" in a few spots.
From SF patch #662807.
|
| |
|
| |
|
| |
|
|
|
|
| |
fail in a non-debug build. Only print this in verbose test mode.
|
|
|