Message 269322 - Python tracker

Message269322

Author	gvanrossum
Recipients	abarry, ezio.melotti, gvanrossum, r.david.murray, serhiy.storchaka, vstinner, ztane
Date	2016-06-26.22:19:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1466979593.39.0.0983323261364.issue27364@psf.upfronthosting.co.za>
In-reply-to

Content
I am okay with making it a silent warning. Can we do it in two stages though? It doesn't have to be two releases, I just mean two separate commits: (1) fix all places in the stdlib that violate this principle; (2) separately commit the code that causes the silent deprecation (and tests for it). What exactly was the hard crash you got? Do you think it was a bug in your own C code or in existing C code?

Content

I am okay with making it a silent warning.

Can we do it in two stages though? It doesn't have to be two releases, I just mean two separate commits: (1) fix all places in the stdlib that violate this principle; (2) separately commit the code that causes the silent deprecation (and tests for it).

What exactly was the hard crash you got? Do you think it was a bug in your own C code or in existing C code?

History
Date	User	Action	Args
2016-06-26 22:19:53	gvanrossum	set	recipients: + gvanrossum, vstinner, ezio.melotti, r.david.murray, serhiy.storchaka, ztane, abarry
2016-06-26 22:19:53	gvanrossum	set	messageid: <1466979593.39.0.0983323261364.issue27364@psf.upfronthosting.co.za>
2016-06-26 22:19:53	gvanrossum	link	issue27364 messages
2016-06-26 22:19:53	gvanrossum	create