[issue7463] PyDateTime_IMPORT() causes compiler warnings

[Alexander Belopolsky]

Changes by Alexander Belopolsky belopol...@users.sourceforge.net:


--
status: pending - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7463
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7463] PyDateTime_IMPORT() causes compiler warnings

[Alexander Belopolsky]

Alexander Belopolsky belopol...@users.sourceforge.net 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 this is not a bug, I don't think it is appropriate to change it in 2.x.

--
resolution:  - out of date
stage: needs patch - committed/rejected
status: open - pending

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7463
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7463] PyDateTime_IMPORT() causes compiler warnings

[Alexander Belopolsky]

Changes by Alexander Belopolsky belopol...@users.sourceforge.net:


--
assignee:  - belopolsky
nosy: +belopolsky
stage:  - needs patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7463
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7463] PyDateTime_IMPORT() causes compiler warnings

[Jack Diederich]

Jack Diederich jackd...@gmail.com 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 tried changing it on the 2.x trunk and it compiles 
with no warnings.

+1, any other opinions?

--
nosy: +jackdied

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7463
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7463] PyDateTime_IMPORT() causes compiler warnings

[Murray Cumming]

New submission from Murray Cumming murr...@murrayc.com:

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_Import(datetime, \
datetime_CAPI)

This makes it impossible to build code with warnings as errors, when
using that macro.

--
components: None
messages: 96166
nosy: murrayc
severity: normal
status: open
title: PyDateTime_IMPORT() causes compiler warnings
type: compile error
versions: Python 2.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7463
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com