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 vstinner
Recipients larry, skrah, vstinner
Date 2013-12-16.08:50:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYOFwK_eU+SbhDcQo8sxOtBGqOrgTHPhokKNwbBas-GwQ@mail.gmail.com>
In-reply-to <1387127886.64.0.968380167158.issue19976@psf.upfronthosting.co.za>
Content
> The Visual Studio pragma disables for the rest of the file, which is undesirable.  Maybe we could turn it on and off inline, but it's not clear to me that that would have the desired effect of turning off the warning for explicitly that parameter declaration.

Oh, I didn't know that it is file-wide. There are
__pragma(warning(push)) and __pragma(warning(pop)) commands to disable
a pragma. I don't know it is can be used using Py_UNUSED(name) macro
(is it possible to "pop" the pragma before the function body?).

If a compiler does not provide a syntax to disable the warning just in
one function, the warning should be disabled for the compilation of
the whole project.
History
Date User Action Args
2013-12-16 08:50:34vstinnersetrecipients: + vstinner, larry, skrah
2013-12-16 08:50:34vstinnerlinkissue19976 messages
2013-12-16 08:50:34vstinnercreate