[Patches] [ python-Patches-551009 ] Cygwin array patch

[noreply@sourceforge.net]

Patches item #551009, was opened at 2002-05-01 16:25
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=551009&group_id=5470

Category: Modules
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Jason Tishler (jlt63)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cygwin array patch

Initial Comment:
This patch re-enables the clean building of the
array module under Cygwin.

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2002-05-02 22:12

Message:
Logged In: YES 
user_id=21627

Thanks for the patch; this is committed as arraymodule.c 2.71.

----------------------------------------------------------------------

Comment By: Jason Tishler (jlt63)
Date: 2002-05-02 21:43

Message:
Logged In: YES 
user_id=86216

I'm getting errors like the following:

.../arraymodule.c:1700: initializer element is not constant
.../arraymodule.c:1700: (near initialization for `Arraytype.tp_getattro')

So I just used the following to solve this problem:

http://www.python.org/doc/FAQ.html#3.24

Besides, we already have the following in Modules/socketmodule.c:

PySocketSock_Type.tp_getattro = PyObject_GenericGetAttr;
PySocketSock_Type.tp_alloc = PyType_GenericAlloc;
PySocketSock_Type.tp_free = PyObject_Del;

Is the above explanation satisfactory?

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2002-05-02 19:33

Message:
Logged In: YES 
user_id=21627

Can you please explain why this is necessary? It looks like
a bug in cygwin to me.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=551009&group_id=5470