[C++-sig] Unlocking the python interpreter lock when entering Boost.Python

Niall Douglas s_sourceforge at nedprod.com
Sun Sep 28 04:09:22 CEST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was figuring that it would be pretty easy to hack in a guaranteed 
unlock and lock every time Boost.Python went into C++ code. But it 
also occurred to me that this isn't hugely efficient.

I have certain parts of my library where it waits for more data to 
arrive. Thus if my python thread were waiting it could lock out all 
other python code (bad). Would it not be a good idea if one could 
specify a policy to Boost.Python to have it unlock and lock around a 
specific wrap?

Anyway just a suggestion.

Cheers,
Niall





-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBP3ZC08EcvDLFGKbPEQI40wCg7WO842xcsJz+jBg4aXVsbn4saxEAn1j5
pLlglmjs7iiMlf1wrg5Zluur
=Jy+t
-----END PGP SIGNATURE-----




More information about the Cplusplus-sig mailing list