-
Notifications
You must be signed in to change notification settings - Fork 17
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
Python via Codon compiler #14
Comments
Other options include https://github.com/cython/cython and https://github.com/Nuitka/Nuitka |
I think that runs into the issue of what is "the canonical way" to AOT compile Python (there isn't one as far as I'm aware). Choosing one arbitrarily then opens the question whether we can use TinyGo for Go, etc. I've been thinking whether to introduce a "language+compiler" sub-scoreboard where the other ones could show up. There would still be just the main "language" category as it exists right now, but there would also be a B-sides "language+compiler" scoreboard for tcc/clang/gcc/... for C, all the different kinds of AOT compiled Python, etc. As things are right now, the existing scope is how much I can maintain - I'd need a bit more automation set up to be able to handle the language+compiler combination. At minimum, I'd need to have an automated way to check that the generated executables work on a clean install of Windows (no missing DLLs, and prints Hello World) and tiny things like #13. I'd like to get to it at some point. |
https://github.com/exaloop/codon
I've remembered about this project, that claims to compile Python to machine code using LLVM.
But I'm not 100% sure it fits into the rules, will Python be accepted if compiled with Codon or not ?
The text was updated successfully, but these errors were encountered: