[IronPython] Additional modules to ship with IronPython 2.7.1?

[Vernon Cole]

Dear Group:
  On another thread, Jeff Hardy and "Slide" have commented that they have
important standard library modules (unicodedata and csv, respectively) which
will not be ready for IronPython 2.7 but should be targeted for 2.7.1.  Jeff
also says he may also have sqlite3 ready for prime time by then.   [Well
done, guys!]

   I would like to start a discussion about adding modules to the IronPython
distribution which are not in the C-Python standard library. The idea would
be to include more batteries.  (FePy started out to do that, but has not
been seriously updated since IronPython 2.0 came out with a real, genuine
Windows installer.)  Good idea, or Bad?

  I see that adodbapi is still getting about 300 downloads a month, and I
presume that most of them are for IronPython, since it's already included in
pywin32 for CPython users. FePy is getting around 50 downloads a month,
which I guess is mostly  to get the dbapi modules. The FePy modules are
lighter in weight than adodbapi, and use genuine .NET system calls, but are
not completely PEP 249 compliant.  Adodbapi is compliant, but uses COM to
read the database, so will not run on linux/mono. Should db api and/or other
modules be considered for inclusion?
--
Vernon Cole
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20110209/8f8b5fc7/attachment.html>