Message341877
| Author | mariocj89 |
|---|---|
| Recipients | cjw296, mariocj89, michael.foord, xtreak |
| Date | 2019-05-08.14:32:27 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1557325947.5.0.963285067358.issue36848@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Agree, for the general case I think it makes sense that this is fixed in pyside. Hijacking __signature__ python-wide sounds like it can cause other issues, if they need such a hack I would suggest finding a way (in pyside) to allow for mock to work. I wonder though if this change in __signature__ will affect in any way any C extension that might not allow setting __signature__ if not set as a lack of __dict__ (I have not managed to find any issue with small examples though). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-05-08 14:32:27 | mariocj89 | set | recipients: + mariocj89, cjw296, michael.foord, xtreak |
| 2019-05-08 14:32:27 | mariocj89 | set | messageid: <1557325947.5.0.963285067358.issue36848@roundup.psfhosted.org> |
| 2019-05-08 14:32:27 | mariocj89 | link | issue36848 messages |
| 2019-05-08 14:32:27 | mariocj89 | create | |