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 Elizacat
Recipients Elizacat
Date 2014-07-14.00:01:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1405296089.18.0.134297351302.issue21975@psf.upfronthosting.co.za>
In-reply-to
Content
Pickling, unpickling, then using an sqlite3.Row object results in a segfault on at least Python 3.3.5, 3.4.0, and 3.4.1. I have attached a test case and a backtrace below.

I know you're not supposed to pickle sqlite3.Row objects, as the given test case below results in an exception to the effect that sqlite3.Row objects cannot be pickled in Python 2.7. I don't think a segfault is the desired behaviour, however...
History
Date User Action Args
2014-07-14 00:01:29Elizacatsetrecipients: + Elizacat
2014-07-14 00:01:29Elizacatsetmessageid: <1405296089.18.0.134297351302.issue21975@psf.upfronthosting.co.za>
2014-07-14 00:01:29Elizacatlinkissue21975 messages
2014-07-14 00:01:29Elizacatcreate