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 serhiy.storchaka
Recipients python-dev, serhiy.storchaka, skrah
Date 2015-12-25.20:10:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1451074204.85.0.531009214344.issue25923@psf.upfronthosting.co.za>
In-reply-to
Content
get_native_fmtstr() returns a pointer to C string literal. It is constant by its nature, and I thought it would be more clear to cast it explicitly if needed. It would be better (in particular for compatibility with C++) to make Py_buffer.format to be const char*, since it is borrowed reference to constant string, and often is initialized with string literal, but this is backward incompatible change of public API. I'm planning to open separate issue for backward-incompatible (controlled with a macro) constantness changing.
History
Date User Action Args
2015-12-25 20:10:04serhiy.storchakasetrecipients: + serhiy.storchaka, skrah, python-dev
2015-12-25 20:10:04serhiy.storchakasetmessageid: <1451074204.85.0.531009214344.issue25923@psf.upfronthosting.co.za>
2015-12-25 20:10:04serhiy.storchakalinkissue25923 messages
2015-12-25 20:10:04serhiy.storchakacreate