-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin v. Löwis wrote: >>> So what would the specification then read like? >> The 'excel' dialect specified in PEP 305: >> >> http://www.python.org/dev/peps/pep-0305/#id19 > > That works fine for me. > > I notice that the PEP doesn't actually match the API, in particular > wrt. to passing a fieldnames keyword argument. > > Do we need to specify whether there will be a heading line, and if > so, should we require it?
A heading line makes the file self-documenting, and even a bit future-proof (assuming resonable defaults exist for any columns added later). Given that we don't have any legacy code which is generating one without the headings, I would require it. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI9Opj+gerLs4ltQ4RAnibAKC/anBNwT8zId3OSD42uGp+Qgc5qQCgq4MM KKe9oKPqo7W+LfXjyhJdPY4= =9EML -----END PGP SIGNATURE----- _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
