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 pitrou
Recipients asvetlov, christian.heimes, daniel.urban, eltoder, jcea, pitrou, python-dev
Date 2012-12-08.21:00:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355000353.3318.23.camel@localhost.localdomain>
In-reply-to <1355000198.3318.22.camel@localhost.localdomain>
> > In any case, notifying people so they can quickly check their code
> > seems much nicer than having them figure this out the hard way.
> I see it as a double-edged sword: if we start adding a warning for this
> macro, people will expect us to do it for every other macro, which we
> aren't doing right now.

And also, as this issue shows, we may have to change it in a bugfix
release, which means people shouldn't trust the fact that there's no
such warning, anyway.
Date User Action Args
2012-12-08 21:00:37pitrousetrecipients: + pitrou, jcea, christian.heimes, asvetlov, daniel.urban, python-dev, eltoder
2012-12-08 21:00:37pitroulinkissue16602 messages
2012-12-08 21:00:37pitroucreate