-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Does SuSE cPickle 2.7 fix have unintended consequences? #2350
Copy link
Copy link
Closed
Description
@davydden
Sorry I didn't see this before it was committed; but I just looked at #2295. The title implies it affects only Python 2.7, but the code seems to run on all versions of Python. Since the problem was never reported for Python3, I am reluctant to add a patch that will affect Python3.
Ideally, I would like to see the following tests on SuSE 13:
- Try to install Python 2.7 without the patch (we know this doesn't work)
- Try to install Python 2.7 with the patch (we know this does work)
- Try to install Python 3.5 without the patch
- Try to install Python 3.5 with the patch
(Once Python is installed, I would try import pickle for Python3).
Would you be able to please run tests (3) and (4)? This will either:
a) Confirm that the patch is necessary for SuSE 13 on Python3 as well
b) Show that the patch was not necessary but doesn't break anything.
c) Show that the patch actually breaks Python3.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels