pex
pants
pex | pants | |
---|---|---|
9 | 35 | |
2,457 | 3,098 | |
0.4% | 0.8% | |
8.9 | 9.8 | |
3 days ago | 6 days ago | |
Python | Python | |
Apache License 2.0 | Apache License 2.0 |
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.
pex
-
Our Plan for Python 3.13
We get (very) close to cross-environment reproducible builds for Python with https://github.com/pantsbuild/pex (via Pants). For instance, we build Linux x86-64 artifacts that run on AWS Lambda, and can build them natively on ARM macOS.
This is not raw requirements.txt, but isn’t too far off: Pants/PEX can consume one to produce a hash-pinned lock file.
-
Is it possible pickle a function with its dependencies?
You should look into pex, or it’s parent build system pants. A PEX (Python EXecutable) file can package up all your code including dependencies and run on another machine of similar OS with just an available compatible interpreter.
- Pex: Python EXecutable
-
security risks in python libs
For well-supported libraries, pip-audit might do the trick. Where I've worked, we have used a central build system with library version enforcement. The build system produces a deployable archive, like PEX or similar. Rock-solid tests and sandbox validation environments provide good paths for version upgrades. Restricting libraries to a small set, making sure those repos remain actively developed, performing audits and centralizing builds has helped organizations I've worked in keep on top of potential security issues.
- My latest blogpost, python packaging has moved forward, but we're still missing a crucial part - what do you think?
- PyBake: Create single file standalone Python scripts with builtin frozen file system
- I am frustrated with packaging python, please educate me.
-
A function decorator that rewrites the bytecode to enable goto in Python
Don't know if I agree about the goto thing, but there are actually a number of options now for delivering varying degrees of self-contained Python executable.
When I evaluated the landscape a few years ago, I settled on PEX [1] as the solution that happened to fit my use-case the best— it uses a system-provided Python + stdlib, but otherwise brings everything (including compiled modules) with it in a self-extracting executable. Other popular options include pyinstaller and cx_freeze, which have different tradeoffs as far as size, speed, convenience, etc.
[1]: https://github.com/pantsbuild/pex
-
Mypyc: Compile type-annotated Python to C
Somewhat related, I had a devil of a time a little bit ago trying to ship a small Python app as a fully standalone environment runnable on "any Linux" (but for practical purposes, Ubuntu 16.04, 18.04, and 20.04). It turns out that if you don't want to use pip, and you don't want to build separate bundles for different OSes and Python versions, it can be surprisingly tricky to get this right. Just bundling the whole interpreter doesn't work either because it's tied to a particular stdlib which is then linked to specific versions of a bunch of system dependencies, so if you go that route, you basically end up taking an entire rootfs/container with you.
After evaluating a number of different solutions, I ended up being quite happy with pex: https://github.com/pantsbuild/pex
It basically bundles up the wheels for whatever your workspace needs, and then ships them in an archive with a bootstrap script that can recreate that environment on your target. But critically, it natively supports the idea of targeting multiple OS and Python versions, you just explicitly tell it which ones to include, eg:
--platform=manylinux2014_x86_64-cp-38-cp38 # 16.04
pants
-
The xz attack shell script
> C/C++'s header system with conditional inclusion
Wouldn't it be more accurate to say something like "older build systems"? I don't think any of the things you listed are "modern". Which isn't a criticism of their legacy! They have been very useful for a long time, and that's to be applauded. But they have huge problems, which is a big part of why newer systems have been created.
FWIW, I have been using pants[0] (v2) for a little under a year. We chose it after also evaluating it and bazel (but not nix, for better or worse). I think it's really really great! Also painful in some ways (as is inevitably the case with any software). And of course it's nearly impossible to entirely stomp out "genrules" use cases. But it's much easier to get much closer to true hermeticity, and I'm a big fan of that.
0: https://www.pantsbuild.org/
-
Monorepo + Microservices + Dependency Managment + Build system HELL
Does pants/bazel can help me?
- Pants 2: The ergonomic build system
-
Go Dependency management in large company projects - How do you do it?
Hyper-large tech companies managing hyper-large monorepos using Bazel (google), buck (Facebook), please (thought machine), pants (Twitter, Foursquare & Square) enjoy them but also have a lot of resources devoted to running and maintaining it.
-
Reason to use other Build Tool than Make?
Yeah there's definitely some alternatives out there. Pants is another one that has a lot of traction.
-
Is it possible pickle a function with its dependencies?
You should look into pex, or it’s parent build system pants. A PEX (Python EXecutable) file can package up all your code including dependencies and run on another machine of similar OS with just an available compatible interpreter.
-
Sanity check of my decision for "Iterative AI" (DVC, MLEM, CML) pipeline over Azure ML
We don't have the CD yet, but I think what I put in place counts as simple CI (even if incomplete)? Every push & PR trigger an azure pipeline, which runs pants. This install the dependencies from the lockfile, run some linters, uses DVC to pull the data necessary for tests, and run unit tests (mypy check is deactivated until I solve a weird error). Basically the same script runs on laptops cross-platform (one of us uses Max, one Ubuntu with GPU, one Ubuntu with CPU, the scripts runs on every platform). The only difference with CI is the installation of Pants and the gestion of Cache (needs to be downloaded in CI so it takes ~3min in CI versus 20 seconds on my laptop).
- Pants 2: fast, scalable, user-friendly build system for codebases of all sizes
-
Maintain a Clean Architecture in Python with Dependency Rules
This has also been recently integrated in pants.
https://github.com/pantsbuild/pants/issues/13393
- Blazing fast CI with MicroVMs
What are some alternatives?
mypyc - Compile type annotated Python to fast C extensions
Bazel - a fast, scalable, multi-language and extensible build system
setup.py - 📦 A Human's Ultimate Guide to setup.py.
megalinter - 🦙 MegaLinter analyzes 50 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally.
python-goto - A function decorator, that rewrites the bytecode, to enable goto in Python
please - High-performance extensible build system for reproducible multi-language builds.
pyBake - Create single file standalone Python scripts with builtin frozen file system
pyflow - An installation and dependency system for Python
plusplus - Enables increment operators in Python using a bytecode hack
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
typed_python - An llvm-based framework for generating and calling into high-performance native code from Python.
Buck - A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.