➜

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 serhiy.storchaka
Recipients alexandre.vassalotti, barry, benjamin.peterson, dangyogi, serhiy.storchaka
Date 2017-08-01.06:41:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501569713.8.0.883041878135.issue29902@psf.upfronthosting.co.za>
In-reply-to
Content 
Thank you Benjamin for your review!

But I have a design question. Is DeprecationWarning a correct warning type? DeprecationWarning is used when some feature less or more works in the current version, but will be removed in future releases. But pickling memoryview and staticmethod don't work and never worked correctly. A warning here is a sign that the code can not work as expected. Wouldn't RuntimeWarning be more appropriate warning type?
History
Date User Action Args
2017-08-01 06:41:53serhiy.storchakasetrecipients: + serhiy.storchaka, barry, alexandre.vassalotti, dangyogi, benjamin.peterson
2017-08-01 06:41:53serhiy.storchakasetmessageid: <1501569713.8.0.883041878135.issue29902@psf.upfronthosting.co.za>
2017-08-01 06:41:53serhiy.storchakalinkissue29902 messages
2017-08-01 06:41:53serhiy.storchakacreate