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 collinwinter
Recipients alexandre.vassalotti, collinwinter
Date 2009-04-03.17:57:05
SpamBayes Score 3.6284035e-07
Marked as misclassified No
Message-id <1238781429.73.0.706920888395.issue5665@psf.upfronthosting.co.za>
In-reply-to
Content
I've made test_xpickle support Python 2.4 because it uses Python 2.4,
2.5 and 2.6 to check that we haven't broken backwards compatibility with
those versions.

I made AbstractCompatTests use cPickle because that's what I've been
changing :) I can add tests for the pure-Python pickle module if you
want. At that point, though, test_xpickle will be very slow and we'll
want to add a regrtest resource to control how much time test_xpickle
spends running. Does xpickle work for the resource name (ie, regrtest.py
-u xpickle)?

I agree with your other points.
History
Date User Action Args
2009-04-03 17:57:09collinwintersetrecipients: + collinwinter, alexandre.vassalotti
2009-04-03 17:57:09collinwintersetmessageid: <1238781429.73.0.706920888395.issue5665@psf.upfronthosting.co.za>
2009-04-03 17:57:05collinwinterlinkissue5665 messages
2009-04-03 17:57:05collinwintercreate