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 jackdied
Recipients jackdied, murrayc
Date 2010-02-22.21:14:30
SpamBayes Score 0.0011908713
Marked as misclassified No
Message-id <1266873272.66.0.901549661598.issue7463@psf.upfronthosting.co.za>
In-reply-to
Content
changing the definition to (const char *) seems like the right thing to do - a quick grep of the Python source and a search on google codesearch only shows uses with either string literals or string literals cast to (char *) in order to silence a warning.  I tried changing it on the 2.x trunk and it compiles with no warnings.

+1, any other opinions?
History
Date User Action Args
2010-02-22 21:14:32jackdiedsetrecipients: + jackdied, murrayc
2010-02-22 21:14:32jackdiedsetmessageid: <1266873272.66.0.901549661598.issue7463@psf.upfronthosting.co.za>
2010-02-22 21:14:30jackdiedlinkissue7463 messages
2010-02-22 21:14:30jackdiedcreate