This item, from the TODO list, has been bugging me for a while:
>* Reader and universal newlines don't interact well, reader doesn't
> honour Dialect's lineterminator setting. All outstanding bug id's
> (789519, 944890, 967934 and 1072404) are related to this - it's
> a difficult problem and f
>> Andrew explains that in the CSV module, escape characters are not
>> properly removed.
>>
>> Magnus writes:
>>> IMO this is the *only* reasonable behaviour. I don't understand why
>>> the escape character should be left in; this is one of the reason why
>>> UNIX-style colon-separated values don'
> Instead, I would suggest that even a very limited initial
> implementation of StructReader() like object suggested by Raymond
would
> be more useful...
I have a draft patch also.
Let's work out improvements off-list (perhaps on ASPN).
Feel free to email me directly.
Raymond
__
>I'd love to see a 'split' and a 'join' function in the csv module to
>just convert between string and list without having to bother about
>files.
>
>Something like
>
>csv.split(aStr [, dialect='excel'[, fmtparam]]) -> list object
>
>and
>
>csv.join(aList, e[, dialect='excel'[, fmtparam]]) -> str
Okay. I've created a bug report 1098990: codec readline() splits lines
apart
Btw, I've set it to group Python 2.5, is that correct?
Or should bugs that relate to the current CVS trunk have no group?
Thx
Irmen.
___
Python-Dev mailing list
Python-Dev@pytho
> (a) A higher-level API can and should be constructed which acts like a
> (binary) stream but has additional methods for reading and writing
> values using struct format codes (or, preferably, somewhat
> higher-level type names, as suggested). Instances of this API should
> be constructable from a
Simon Percivall wrote:
It looks like the readline method broke at revision 1.36 of codecs.py,
when it was modified, yes.
Okay. I've created a bug report 1098990: codec readline() splits lines apart
--Irmen
___
Python-Dev mailing list
Python-Dev@python.org
