[issue1512] Removal of stale code in pyconfig.h

Martin v. Löwis added the comment: I think there is harm in removing this block; it would cause PY_LONG_LONG not to be defined anymore. Closing as invalid. -- resolution: -> invalid status: open -> closed ___ Python tracker

[issue1512] Removal of stale code in pyconfig.h

Changes by Daniel Diniz : -- stage: -> test needed type: -> feature request versions: +Python 2.7, Python 3.1 -Python 3.0 ___ Python tracker ___

[issue1512] Removal of stale code in pyconfig.h

Changes by Christian Heimes: -- assignee: -> loewis nosy: +loewis priority: -> low __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mail

[issue1512] Removal of stale code in pyconfig.h

New submission from Joseph Armbruster: Question: Is there any harm in removing this block from pyconfig.h? #ifndef PY_LONG_LONG # define PY_LONG_LONG __int64 # define PY_LLONG_MAX _I64_MAX # define PY_LLONG_MIN _I64_MIN # define PY_ULLONG_MAX _UI64_MAX #endif pyconfig.h