GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Heap allocate type structs in native extension modules?

[Python-Dev] Heap allocate type structs in native extension modules?

Benjamin Peterson benjamin at python.org
Fri Dec 29 02:00:47 EST 2017

  • Previous message (by thread): [Python-Dev] Heap allocate type structs in native extension modules?
  • Next message (by thread): [Python-Dev] Heap allocate type structs in native extension modules?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Dec 28, 2017, at 03:29, Erik Bray wrote:
> On Tue, Dec 26, 2017 at 3:00 PM, Benjamin Peterson <benjamin at python.org> wrote:
> > I imagine Cython already takes care of this?
> 
> This appears to have a distinct purpose, albeit not unrelated to
> Cython.  The OP's program would generate boilerplate C code for
> extension types the rest of which would perhaps be implemented by hand
> in C.  Cython does this as well to an extent, but the generated code
> contains quite a bit of Cython-specific cruft and is not really meant
> to be edited by hand or read by humans in most cases.

It still seems the OP is likely to reinvent a lot of Cython. One option is to write a bunch of "pure" .c and then only have the Python bindings in Cython.

> 
> Anyways I don't think this answers the OP's question.

I think this belongs on python-list anyway.

  • Previous message (by thread): [Python-Dev] Heap allocate type structs in native extension modules?
  • Next message (by thread): [Python-Dev] Heap allocate type structs in native extension modules?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.