DSVWizard.py

[Kevin Altis]

> From: Dave Cole
>
> >>>>> "Cliff" == Cliff Wells <LogiplexSoftware at earthlink.net> writes:
>
> >>  This sounds like a reasonable idea.  I also agree the GUI stuff
> >> will probably not make it into the core.
>
> Cliff> Anyone else?  BTW, where are we planning on hosting this
> Cliff> project?  Under one of the existing projects or somewhere else?
>
> If we are trying to get this into Python shouldn't we use something
> like sourceforge.  Has anyone been through the process of getting code
> into Python before?

Either just use the Python DSV project Cliff already has setup

http://sourceforge.net/projects/python-dsv

or create a new one python-csv

Either way, everyone should have write privs. and a new cvs dir needs to be
created to hold the working code.

Originally, I thought the task of making a standard module was going to be
relatively trivial, but I'm guessing now that there will be enough effort
required in deciding on the API, test cases, a PEP, etc. that it won't be
appropriate to try and make it part of Python 2.3, but will have to wait for
Python 2.4 instead. So, in the meantime, the project will just follow the
lead of other projects prior to being incorporated in the Python core.

Skip has the most experience in this area, do you agree with the assessment
above Skip?

Public discussions can take place on the db-sig and/or c.l.py

ka