Richard Kay wrote:
0.3x is a version in transition from .3 to .4. I think its OK, because it
was *after* I changed the name from pyCSV.py to csv.py, but you may want to
download version 0.4 just to be sure. http://purl.net/macquigg/email/python
Have done this. Comparing the version linked from this
page ( 0.3x ) to the .4 version (csv.py) on:
The name csv.py conflicts with the Comma Separated File module present
in Python 2.3 and upwards. This means that a program can't use both
modules unless it artificially places your csv.py in a package directory
so that it doesn't exist on the 'primary' module path:
import csv
When csv.py is in the current working directory, or the package
directory for the currently executing module, it will always shadow the
stdlib's csv.py.
The only way I can see around this is renaming, or creating a dummy
package (and dummy __init__.py), and placing csv.py within that. eg:
import dummy.csv as csv
Might I suggest you create a package called "CLEAR" or "clear", and
distribute csv.py as part of that? It would then natural for a BATV
implementation to live inside that as batv.py. eg:
from clear import csv, batv
from clear.csv import *
etc.
David.
_______________________________________________
ietf-clear mailing list
ietf-clear(_at_)mipassoc(_dot_)org
http://mipassoc.org/mailman/listinfo/ietf-clear