homepage

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 michael.foord
Recipients Vlastimil.Zíma, davin, michael.foord, peter.otten, r.david.murray, serhiy.storchaka
Date 2017年01月11日.09:15:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484126142.27.0.966521922221.issue20804@psf.upfronthosting.co.za>
In-reply-to
Content
So my thinking has evolved slightly on it. If it's *possible* for sentinels to be copied and pickled and preserve identity then I'm happy for it. I think the right semantics for copying a sentinel is that you get the original object back. If you pickle a sentinel and then unpickle back *into the same process* you should get the same object back. 
David worried that this confuses the semantics of pickling/copying because it isn't generally the case - so I'm open to further discussion on it, but if Serhiy has fixed the "problem" here I'm happy for it to go in.
History
Date User Action Args
2017年01月11日 09:15:42michael.foordsetrecipients: + michael.foord, peter.otten, r.david.murray, serhiy.storchaka, Vlastimil.Zíma, davin
2017年01月11日 09:15:42michael.foordsetmessageid: <1484126142.27.0.966521922221.issue20804@psf.upfronthosting.co.za>
2017年01月11日 09:15:42michael.foordlinkissue20804 messages
2017年01月11日 09:15:42michael.foordcreate

AltStyle によって変換されたページ (->オリジナル) /