Message 62639 - Python tracker

➜

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	vdupras
Recipients	amaury.forgeotdarc, georg.brandl, resolve1, vdupras
Date	2008-02-21.18:45:11
SpamBayes Score	0.097879246
Marked as misclassified	No
Message-id	<1203619513.5.0.0556959353276.issue2127@psf.upfronthosting.co.za>
In-reply-to

Content
Shouldn't we apply this patch directly on pysqlite? Any change made to the sqlite3 module will be overwritten in the next "refresh", right? Anyway, I'm not 100% sure, but it might already be fixed: http://www.initd.org/tracker/pysqlite/changeset/452 So, maybe create a ticket to use the latest version of pysqlite?

Shouldn't we apply this patch directly on pysqlite? Any change made to 
the sqlite3 module will be overwritten in the next "refresh", right? 
Anyway, I'm not 100% sure, but it might already be fixed:

http://www.initd.org/tracker/pysqlite/changeset/452

So, maybe create a ticket to use the latest version of pysqlite?

History
Date	User	Action	Args
2008-02-21 18:45:14	vdupras	set	spambayes_score: 0.0978792 -> 0.097879246 recipients: + vdupras, georg.brandl, amaury.forgeotdarc, resolve1
2008-02-21 18:45:13	vdupras	set	spambayes_score: 0.0978792 -> 0.0978792 messageid: <1203619513.5.0.0556959353276.issue2127@psf.upfronthosting.co.za>
2008-02-21 18:45:12	vdupras	link	issue2127 messages
2008-02-21 18:45:11	vdupras	create