[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[pygame] Py_BEGIN_ALLOW_THREADS in surface.c

To: pygame-users <pygame-users@xxxxxxxx>
Subject: [pygame] Py_BEGIN_ALLOW_THREADS in surface.c
From: Tom Rothamel <tom@xxxxxxxxxxx>
Date: Thu, 4 Apr 2013 01:33:38 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Thu, 04 Apr 2013 01:42:34 -0400
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

I'm curious - why are Py_BEGIN_ALLOW_THREADS andÂPy_END_ALLOW_THREADS commented out (and otherwise missing) in surface.c? It seems like those would be the most expensive functions, and hence the ones that would benefit most from running in a threaded environment.

They're used in many other parts of pygame.

Follow-Ups:
- Re: [pygame] Py_BEGIN_ALLOW_THREADS in surface.c
  - From: René Dudfield

Prev by Author: Re: [pygame] BUG: reproducible hard hang (i.e. SIGKILL only) in pygame!
Next by thread: Re: [pygame] Py_BEGIN_ALLOW_THREADS in surface.c
Index(es):
- Author
- Thread