On 2008-09-10 00:26, [EMAIL PROTECTED] wrote:
> mal> Besides, what's so bad with downloading and installing a package
> mal> from PyPI ?
>
> Nothing, I do it all the time. But my impression is that when an external
> module moves into the core it frequently undergoes some type of name change
> (e.g. pysqlite vs sqlite3 or Optik vs optparse) even if the two versions are
> functionally identical. In this case, my hope is that dbm.sqlite will
> eventually move into the distributed dbm package. If so, it would be nice
> if the move was transparent.
Transparent as in "I don't have to change my code" ?
I actually find it helpful to have the PyPI packages that ended up in
the stdlib use different names, since that opens up the possibility
to use the more current releases from PyPI in an application.
Switching back to the core version usually just takes a one line
change, if at all...
try:
import pysqlite as sqlite
except ImportError:
import sqlite3 as sqlite
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, Sep 10 2008)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
________________________________________________________________________
:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
