Message 77699 - Python tracker

➜

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	loewis
Recipients	gpolo, loewis
Date	2008-12-13.00:13:53
SpamBayes Score	0.0034430062
Marked as misclassified	No
Message-id	<4942FE3F.4010601@v.loewis.de>
In-reply-to	<ac2200130812121556t270c3259s1523644abc8bb441@mail.gmail.com>

Content
> Are we talking about the same commit ? 59654 as in your original about > it breaking existing code. Oops, no. I now see that r59654 is fine for backporting. My last message was about r59653, which probably does introduce backward compatibility problems. The other changes seem to introduce new features, so they are out of scope.

> Are we talking about the same commit ? 59654 as in your original about
> it breaking existing code.

Oops, no. I now see that r59654 is fine for backporting. My last message
was about r59653, which probably does introduce backward compatibility
problems.

The other changes seem to introduce new features, so they are out of
scope.

History
Date	User	Action	Args
2008-12-13 00:13:54	loewis	set	recipients: + loewis, gpolo
2008-12-13 00:13:53	loewis	link	issue4342 messages
2008-12-13 00:13:53	loewis	create