-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package request: python3-typst #47044
Comments
What is this good for? How is import typst
typst.compile(in, output=out) any different than import subprocess
subprocess.run(["typst", "compile", in, out]) ? |
i would assume typst-as-a-library has a more flexible of an api than shelling out, not to mention probably being faster the package in question is pyo3 bindings not just a library that runs shell commands |
All it seems to have is a Template is easy if you want to try it:
I'm honestly not sure its worth shipping, but I don't mind making a PR if you think it's worthwhile. Note that the whole of typst (and dependencies) seem to be vendored in, so the pkg will be roughly the same size as |
It's worst in every way. It only exposes a single |
I was more referring to the native rust library for typst, which is a lot more flexible than these bindings, it seems. |
This is what I noticed while trying (without success) to write the template myself. I asked for this package thinking that maybe there is a way to make |
Flexible or not, if it's not exposed, it's useless. Worse, the current state of Rust ecosystem, everything is static-linked, which brings more burden in maintaining.
Wait until Rust can have stable ABI, which means never. :-p |
Package name
python3-typst
Package homepage
https://github.com/messense/typst-py
Description
Python binding to typst.
Does the requested package meet the package requirements?
System, Compiled
Is the requested package released?
Yes
The text was updated successfully, but these errors were encountered: