[Pyrex] module scope, and threads

[Greg Ewing]

ahalda at cs.mcgill.ca wrote:

> My solution was to create a module level pyrex object to keep at least one
> reference to the object active, for as long as the background thread needs
> the object.

That really should be the responsibility of the
C function that you're passing the object reference
to. Although if the calling module can be sure that
the previous object is no longer needed before
replacing it with a new one, this will work.

--
Greg