python-mock tests fail with python3.4
Bug #1283742 reported by
Matthias Klose
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mock (Debian) |
Fix Released
|
Unknown
|
|||
python-mock (Ubuntu) |
Fix Released
|
High
|
Barry Warsaw | ||
Trusty |
Fix Released
|
High
|
Barry Warsaw |
Bug Description
python-mock tests fail with python3.4, see
https:/
tags: | added: python3.4 |
Changed in python-mock (Debian): | |
status: | Unknown → New |
tags: | added: patch |
Changed in python-mock (Ubuntu Trusty): | |
assignee: | nobody → Barry Warsaw (barry) |
status: | Confirmed → Fix Committed |
Changed in python-mock (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Ah yes, I know the reason for that. It's due to the new signature changes in Python 3.4 - some builtin objects are now introspectable with inspect. getfullargspec but don't have the full range of "normal" attributes. The fix is just to catch the AttributeError around copying them. FWIW mock is *included* in Python 3.4 as unittest.mock, so nothing using Python 3.4 should be using the python-mock package!