[issue7463] PyDateTime_IMPORT() causes compiler warnings

2010-06-11 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue7463] PyDateTime_IMPORT() causes compiler warnings

2010-06-06 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: PyCObject is deprecated in 2.7 and removed in 3.x. PyCapsule_Import() should be used instead of PyCObject_Import() and it already has correct signature: Include/pycapsule.h:PyAPI_FUNC(void *) PyCapsule_Import(const char *name, int no_block); Since thi

[issue7463] PyDateTime_IMPORT() causes compiler warnings

2010-06-05 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- assignee: -> belopolsky nosy: +belopolsky stage: -> needs patch ___ Python tracker ___ ___ Pytho

[issue7463] PyDateTime_IMPORT() causes compiler warnings

2010-02-22 Thread Jack Diederich
Jack Diederich added the comment: 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

[issue7463] PyDateTime_IMPORT() causes compiler warnings

2009-12-09 Thread Murray Cumming
New submission from Murray Cumming : At least in Python 2.5 and 2.6 (I haven't checked newer versions), the PyDateTime_IMPORT() macro passes string literals to a function that takes non-const char* parameters: #define PyDateTime_IMPORT \ PyDateTimeAPI = (PyDateTime_CAPI*) PyCObject_Impo