BinaryBuilder.jl
py2many
BinaryBuilder.jl | py2many | |
---|---|---|
5 | 29 | |
379 | 599 | |
1.1% | 2.5% | |
6.5 | 8.1 | |
8 days ago | about 1 month ago | |
Julia | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
BinaryBuilder.jl
-
Is Julia suitable today as a scripting language?
There are some efforts and the startup times are getting better with every release and there's BinaryBuilder.jl.
-
Because cross-compiling binaries for Windows is easier than building natively
There is the Julia package https://github.com/JuliaPackaging/BinaryBuilder.jl which creates an environment that fakes being another, but with the correct compilers and SDKs . It's used to build all the binary dependencies
-
Discussion Thread
https://binarybuilder.org/. You can do it manually obviously, but this is easier.
-
PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
> The main pain point is probably the lack of standard, multi-environment packaging solutions for natively compiled code.
Are you talking about something like BinaryBuilder.jl[1], which provides native binaries as julia-callable wrappers?
--
[1] https://binarybuilder.org
-
What to do about GPU packages on PyPI?
Julia did that for binary dependencies for a few years, with adapters for several linux platforms, homebrew, and for cross-compiled RPMs for Windows. It worked, to a degree -- less well on Windows -- but the combinatorial complexity led to many hiccups and significant maintenance effort. Each Julia package had to account for the peculiarities of each dependency across a range of dependency versions and packaging practices (linkage policies, bundling policies, naming variations, distro versions) -- and this is easier in Julia than in (C)Python because shared libraries are accessed via locally-JIT'd FFI, so there is no need to eg compile extensions for 4 different CPython ABIs (Julia also has syntactic macros which can be helpful here).
To provide a better experience for both package authors and users, as well as reducing the maintenance burden, the community has developed and migrated to a unified system called BinaryBuilder (https://binarybuilder.org) over the past 2-3 years. BinaryBuilder allows targeting all supported platforms with a single build script and also "audits" build products for common compatibility and linkage snafus (similar to some of the conda-build tooling and auditwheel). There was a nice talk at AlpineConf recently (https://alpinelinux.org/conf/) covering some of this history and detailing BinaryBuilder, although I'm not sure how to link into the video.
All that to say: it can work to an extent, but it has been tried various times before. The fact that conda and manylinux don't use system packages was not borne out of inexperience, either. The idea of "make binaries a distro packager's problem" sounds like a simplifying step, but that doesn't necessarily work out.
py2many
-
Transpiler, a Meaningless Word
> Another problem is that there are hundreds of built-in library functions that need to be compiled from Python from C
An approach I've advocated as one of the main authors of py2many is that all of the python builtin functions be written in a subset of python[1] and then compiled into native code. This has the benefit of avoiding GIL, problems with C-API among other things.
Do checkout the examples here[2] which work out of the box for many of the 8-9 supported backends.
[1] https://github.com/py2many/py2many/blob/main/doc/langspec.md
-
py2many VS kithon - a user suggested alternative
2 projects | 17 Jun 2023
-
Why I'm still using Python
https://github.com/py2many/py2many/blob/main/doc/langspec.md
Reimplement a large enough, commonly used subset of python stdlib using this dialect and we may be in the business of writing cross platform apps (perhaps start with android and Ubuntu/Gnome)
-
Codon: A high-performance Python compiler
For py2many, there is an informal specification here:
https://github.com/py2many/py2many/blob/main/doc/langspec.md
Would be great if all the authors of "python-like" languages get together and come up with a couple of specs.
I say a couple, because there are ones that support the python runtime (such as cython) and the ones which don't (like py2many).
-
A Python-compatible statically typed language erg-lang/erg
It'd not fully solve your issue, but have you ever seen https://github.com/py2many/py2many ?
-
Omyyyy/pycom: A Python compiler, down to native code, using C++
Cython doesn't consume python3 type hints and needs special type hints of its own. But it's certainly more mature than other players in the field.
What we need is a rpython suitable for app programming and a stdlib written in that dialect.
https://github.com/py2many/py2many/blob/main/doc/langspec.md
- I made a Python compiler, that can compile Python source down to fast, standalone executables.
- PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
-
Show HN: prometeo – a Python-to-C transpiler for high-performance computing
No intermediate AST. To understand the various stages of transpilation and separation of language specific and independent rewriters, this file is a good starting point:
https://github.com/adsharma/py2many/blob/main/py2many/cli.py...
-
Implicit Overflow Considered Harmful (and how to fix it)
Link to the test that's relevant for this discussion:
https://github.com/adsharma/py2many/blob/main/tests/cases/in...
This is an explicit deviation from python's bigint, which doesn't map very well to systemsey languages. The next logical step is to build on this to have dependent and refinement types.
Work in progress here:
https://github.com/adsharma/Typpete
What are some alternatives?
functorch - functorch is JAX-like composable function transforms for PyTorch.
pybind11 - Seamless operability between C++11 and Python
Yggdrasil - Collection of builder repositories for BinaryBuilder.jl
PyO3 - Rust bindings for the Python interpreter
HTTP.jl - HTTP for Julia
PythonNet - Python for .NET is a package that gives Python programmers nearly seamless integration with the .NET Common Language Runtime (CLR) and provides a powerful application scripting tool for .NET developers.
dh-virtualenv - Python virtualenvs in Debian packages
PyCall.jl - Package to call Python functions from the Julia language
RDKit - The official sources for the RDKit library
julia - The Julia Programming Language
StarWarsArrays.jl - Arrays indexed as the order of Star Wars movies
rust-numpy - PyO3-based Rust bindings of the NumPy C-API