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 Charles McEachern
Recipients Charles McEachern, davin
Date 2017-04-07.21:06:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491599216.59.0.724934820559.issue30018@psf.upfronthosting.co.za>
In-reply-to
Content
This caused me several hours of misery yesterday, trying to isolate what was going wrong. 

I am unfortunately not at liberty to share the code I'm working on. The example on GitHub has the general thrust of it: my constructor was always called in a specific way, and didn't expect to be given something that was already processed. 

Interesting to see that this is a product of pickling. That makes me think that "fixing" this corner case would probably be a lot of work.

I suppose I should just work around it by checking right away if the input to my constructor has already been constructed!
History
Date User Action Args
2017-04-07 21:06:56Charles McEachernsetrecipients: + Charles McEachern, davin
2017-04-07 21:06:56Charles McEachernsetmessageid: <1491599216.59.0.724934820559.issue30018@psf.upfronthosting.co.za>
2017-04-07 21:06:56Charles McEachernlinkissue30018 messages
2017-04-07 21:06:56Charles McEacherncreate