[Csv] _csv bug
Andrew McNamara
andrewm at object-craft.com.au
Wed Feb 5 04:54:24 CET 2003
>That sort of thing. (Speaking of which, we should probably all the user to
>specify the hard (embedded) return character.) It's tough enough in C to
>generate really good messages (because it often requires pasting strings
>together on-the-fly to provide the necessary context) that it frequently
>doesn't get done. For example, if I pass None instead of an int for
>parameters with 'i' format characters, all PyArg_PTAK says is "int was
>required". However, there are nine args to the constructor, five of which
>are ints.
I'm not sure this is a good enough reason to move the checks away from the
"coalface" - with a little more work, we can generate friendly messages
from the C level, while at the same time keeping them tightly coupled
to the implementation. I'd certainly agree the PyArg_PTAK validation
is less than useful in our context - but I think it highlights a more
fundemental problem in the way the C code is structured. I'll talk to
Dave tonight and see if we can come up with something better.
--
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/
More information about the Csv
mailing list