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 loewis
Recipients carloverre, ghaering, loewis
Date 2008-02-18.17:57:30
SpamBayes Score 0.33974093
Marked as misclassified No
Message-id <1203357452.33.0.327158866951.issue2139@psf.upfronthosting.co.za>
In-reply-to
Content
Such bugs should have been reported here much earlier. Blind upgrading
to the latest version is no option, as the latest version may also
introduce new features, which is unacceptable for a bugfix release.
Specific bugs could have been fixed, but really not now as the release
candidate is already made (unless that release candidate would have
shown serious regressions over 2.5.1, which I understand is not the case
here).

Gerhard, what do you think about backporting some fixes to 2.5.3?
(assuming it really is the case that PySQLite 2.3.2 really is very buggy)
History
Date User Action Args
2008-02-18 17:57:32loewissetspambayes_score: 0.339741 -> 0.33974093
recipients: + loewis, ghaering, carloverre
2008-02-18 17:57:32loewissetspambayes_score: 0.339741 -> 0.339741
messageid: <1203357452.33.0.327158866951.issue2139@psf.upfronthosting.co.za>
2008-02-18 17:57:31loewislinkissue2139 messages
2008-02-18 17:57:30loewiscreate