Skip to content

Using Pydust to Embed a Python Interpreter #342

Description

@hmusgrave

From Python's perspective, there isn't much difference between being embedded in a project with main in another language (like Zig) and the work needed to create a Python library/extension. Pydust has a nice interface for libpython, but a lot of the project seems focused around producing modules for the rest of the Python ecosystem to consume. From a maintainer's perspective (or anyone else with enough context):

  1. How much work is it to cleanly add that functionality to Pydust?
  2. If the workload isn't obscene, do you have any pointers to architecturally "nice" places to try to start making that change?
  3. If somebody adds that feature, do you want it upstreamed to the ziggy-pydust project?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions