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.20:58:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355000198.3318.22.camel@localhost.localdomain>
In-reply-to <>
> > People should simply avoid doing this kind of thing, as it's
> > knowingly fragile, and trivial to avoid anyway.
> Is this documented in the C API guide, or somewhere else?

I don't think so, but it's common C wisdom that you shouldn't pass
arguments which have side effects to a macro, except if you are sure the
macro allows it.

> 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.
Date User Action Args
2012-12-08 20:58:03pitrousetrecipients: + pitrou, jcea, christian.heimes, asvetlov, daniel.urban, python-dev, eltoder
2012-12-08 20:58:03pitroulinkissue16602 messages
2012-12-08 20:58:03pitroucreate