Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 778
    • Issues 778
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 211
    • Merge requests 211
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #17913
Closed
Open
Created May 28, 2020 by Ben Boeckel@ben.boeckelOwner

Investigate HPy API proposal

The HPy API was presented recently at the Python Language Summit (LWN article and PSF article). This is proposed as a way to make Python extensions with compiled code that are agnostic to the Python interpreter in use. If true, this would mean we'd be able to compile once and work with CPython 3.X (once support lands), CPython 3.X+1, and PyPy all at once (if I'm reading it right).

It also adds a ctx parameter (similar to Lua's L argument) which would mean we could keep different subsystems using separate Python interpreters (finally!).

This is mostly meant as an awareness/tracking/planning issue; HPy is not yet complete and there are no plans to port VTK to it, but it can't hurt to think about it.

Cc: @utkarsh.ayachit @dgobbi @brad.king

Assignee
Assign to
Time tracking