Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2002-July/027098.html below:

[Python-Dev] pre-PEP: The Safe Buffer Interface

• Previous message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Next message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: "Guido van Rossum" <guido@python.org>
> > > ..., but I understand Neil's requirements.
> > > 
> > > Can they be fulfilled by adding some kind of UnlockObject()
> > > call to the 'safe buffer interface', which should mean 'I won't
> > > use the pointer received by getsaferead/writebufferproc any more'?
> > 
> >    Yes, that is exactly what I want.
> 
> I guess I still don't understand Neil's requirements.  What can't be
> done with the existing buffer interface (which requires you to hold
> the GIL while using the pointer)?

Processing in Python :-(.

Thoms

• Previous message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Next message: [Python-Dev] pre-PEP: The Safe Buffer Interface
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4