Description of problem:
This broken patch prevents to build fonts packages reported as FTBFS issues.
As per some debugging on python module for fontforge, PyObject still has Py_TPFLAGS_INT_SUBCLASS for the integer object. but after applying this patch, it's checking Py_TPFLAGS_LONG_SUBCLASS for the integer object. then seeing the strange error, "Index must be an integer or a string". even though giving an integer as index.

Version-Release number of selected component (if applicable):
fontforge-20100501-5.fc14.x86_64
python-devel-2.7-8.fc14.1.x86_64

How reproducible:
always

Steps to Reproduce:
1.try to build apanov-heuristica-fonts package say
2.
3.
  
Actual results:
fontforge script fails due to the "Index must be an integer or a string"

Expected results:
should be no errors

Additional info:
gdb logs here:


Breakpoint 2, PyFF_FontIndex (self=<fontforge.font at remote 0xbaec30>, index=
    65) at python.c:14950
14950   static PyObject *PyFF_FontIndex( PyObject *self, PyObject *index ) {
(gdb) p/x index->ob_type->tp_flags
$18 = 0x8e15fb

In intobject.h:

#define PyInt_Check(op) \
                 PyType_FastSubclass((op)->ob_type, Py_TPFLAGS_INT_SUBCLASS)

In longobject.h:

#define PyLong_Check(op) \
                PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_LONG_SUBCLASS)

In object.h:

#define PyType_HasFeature(t,f)  (((t)->tp_flags & (f)) != 0)
#define PyType_FastSubclass(t,f)  PyType_HasFeature(t,f)

#define Py_TPFLAGS_INT_SUBCLASS         (1L<<23)
#define Py_TPFLAGS_LONG_SUBCLASS        (1L<<24)