This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author MLModel
Recipients MLModel, georg.brandl
Date 2009-05-18.18:55:08
SpamBayes Score 2.4134646e-05
Marked as misclassified No
Message-id <1242672911.11.0.641137001672.issue6055@psf.upfronthosting.co.za>
In-reply-to
Content
I see that the _sqlite .h and .c files, and the sqlite3/dbapi2.py file,
all use "pysqlite" instead of "sqlite3" internally. Should that be
changed too, or is there just no point? My main concern is that people
relatively new to Python who wouldn't be aware of the long history some
modules have and their migration from external packages into the
distribution (often with a name change) will be confused by mentions of
pysqlite in the documentation.
History
Date User Action Args
2009-05-18 18:55:11MLModelsetrecipients: + MLModel, georg.brandl
2009-05-18 18:55:11MLModelsetmessageid: <1242672911.11.0.641137001672.issue6055@psf.upfronthosting.co.za>
2009-05-18 18:55:09MLModellinkissue6055 messages
2009-05-18 18:55:08MLModelcreate