RetroSearch Browse

Wed Nov 21 09:54:19 EST 2018 · https://mail.python.org/pipermail/python-dev/2018-November/155800.html

On Wed, Nov 21, 2018, at 06:53, Matěj Cepl wrote:
> On 2018-11-19, 11:59 GMT, Stefan Krah wrote:
> > In practice people desperately *have* to use whatever is 
> > there, including functions with underscores that are not even 
> > officially in the C-API.
> 
> Yes, there are some functions which evaporated and I have never 
> heard a reason why and how I am supposed to overcome their 
> removal. E.g., when porting M2Crypto to Python3 I had to 
> reimplement my own (bad) version of `FILE* 
> PyFile_AsFile(PyObject *pyfile)` function 
> (https://is.gd/tgQGDw). I think it is obvious why it is 
> necessary for C bindings, and I have never found a way how to 
> get the underlying FILE handle from the Python File object 
> properly.   

In Python 3, there is no underlying FILE* because the io module is implemented using fds directly rather than C stdio.

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

Showing content from https://mail.python.org/pipermail/python-dev/2018-November/155800.html below:

Experiment an opt-in new C API for Python? (leave current API unchanged)]