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 akitada
Recipients akitada, amaury.forgeotdarc, brett.cannon, loewis, rpetrov
Date 2008-11-29.13:28:04
SpamBayes Score 4.564683e-05
Marked as misclassified No
Message-id <1227965286.25.0.0771870251544.issue4370@psf.upfronthosting.co.za>
In-reply-to
Content
Martin,
Thank you for the feedback.

I think we can avoid the problem that would be introduced by the removal
of Py_GCC_ATTRIBUTE by leaving it as is
(probably adding "#warning this macro is deprecated. Please use
Py_GCC_FORMAT_ATTRIBUTE instead").

The patch looks not so complicated to me. It's just a renaming of a
macro. The new name is more explicit.

IMHO, source code should be kept warning-free, as long as the fix is
simple and it does not cost much.

So I think now the question would be whether having explicitly named
macro and warning-free code for old compilers worth the effort of
renaming all Py_GCC_ATTRIBUTE to Py_GCC_FORMAT_ATTRIBUTE.

I would like to leave the decision to the core developers.
History
Date User Action Args
2008-11-29 13:28:06akitadasetrecipients: + akitada, loewis, brett.cannon, amaury.forgeotdarc, rpetrov
2008-11-29 13:28:06akitadasetmessageid: <1227965286.25.0.0771870251544.issue4370@psf.upfronthosting.co.za>
2008-11-29 13:28:05akitadalinkissue4370 messages
2008-11-29 13:28:04akitadacreate