Message 57195 - Python tracker

Message57195

Author	loewis
Recipients	_doublep, drtomc, loewis
Date	2007-11-07.08:55:31
SpamBayes Score	0.40892613
Marked as misclassified	No
Message-id	<1194425732.39.0.745287372085.issue1390@psf.upfronthosting.co.za>
In-reply-to

Content
The standard procedure for an incompatible change would be to add such a parameter to 2.6, and then change the default behavior in 2.7 (or rather 3.1). Of course, people will not notice the change in 2.6, and then be surprised as much about the default change in 2.7, assuming this problem arises in some application (and this issue is proof that the problem does arise in real life - unless drtomc brought up an artificial problem).

Content

The standard procedure for an incompatible change would be to add such a
parameter to 2.6, and then change the default behavior in 2.7 (or rather
3.1). Of course, people will not notice the change in 2.6, and then be
surprised as much about the default change in 2.7, assuming this problem
arises in some application (and this issue is proof that the problem
does arise in real life - unless drtomc brought up an artificial problem).

History
Date	User	Action	Args
2007-11-07 08:55:32	loewis	set	spambayes_score: 0.408926 -> 0.40892613 recipients: + loewis, _doublep, drtomc
2007-11-07 08:55:32	loewis	set	spambayes_score: 0.408926 -> 0.408926 messageid: <1194425732.39.0.745287372085.issue1390@psf.upfronthosting.co.za>
2007-11-07 08:55:32	loewis	link	issue1390 messages
2007-11-07 08:55:32	loewis	create