[issue1512] Removal of stale code in pyconfig.h

2010-05-20 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de 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

2009-03-30 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- stage: - test needed type: - feature request versions: +Python 2.7, Python 3.1 -Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1512

[issue1512] Removal of stale code in pyconfig.h

2007-11-28 Thread Christian Heimes
Changes by Christian Heimes: -- assignee: - loewis nosy: +loewis priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1512 __ ___ Python-bugs-list mailing

[issue1512] Removal of stale code in pyconfig.h

2007-11-28 Thread Joseph Armbruster
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