➜

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 bkabrda
Recipients benjamin.peterson, bkabrda, eryksun, twouters, uosiu
Date 2016-01-18.17:11:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453137069.2.0.831872701576.issue25731@psf.upfronthosting.co.za>
In-reply-to
Content 
Hi, I'm maintainer of flexmock [1] and some users of my library have started hitting this bug [2] - when one tries to mock __new__ and then revert this mock at the end of testcase to the original one (either by deleting the mock __new__ or replacing mock __new__ by the old one), then one gets "TypeError: object() takes no parameters".

I think that solution proposed by Eryk is correct, but I don't have that much insight into Python internals to confirm that 100 %. I would appreciate this getting fixed. Thanks!

[1] https://github.com/bkabrda/flexmock
[2] https://github.com/bkabrda/flexmock/issues/13
History
Date User Action Args
2016-01-18 17:11:09bkabrdasetrecipients: + bkabrda, twouters, benjamin.peterson, eryksun, uosiu
2016-01-18 17:11:09bkabrdasetmessageid: <1453137069.2.0.831872701576.issue25731@psf.upfronthosting.co.za>
2016-01-18 17:11:09bkabrdalinkissue25731 messages
2016-01-18 17:11:08bkabrdacreate