python-build-standalone
semver
python-build-standalone | semver | |
---|---|---|
11 | 721 | |
1,544 | 7,026 | |
- | 1.4% | |
9.1 | 0.6 | |
8 days ago | 7 days ago | |
Python | ||
BSD 3-clause "New" or "Revised" 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.
python-build-standalone
-
Mise is a polyglot tool version manager
It also replaces "just" as a task manager for me which is very pleasant.
The fact that the python plugin uses precompiled Python binaries by default instead of building them from source remove common issues I had with the asdf's python plugin at work with missing dependencies.
Just so you know, I encountered two little quirks that needed a fix:
- [Backspace Key Doesn't work in Python REPL](https://github.com/indygreg/python-build-standalone/blob/mai...)
-
Pyenv – lets you easily switch between multiple versions of Python
These builds are an alternative: https://github.com/indygreg/python-build-standalone
Those are what Rye and hatch use.
Drawbacks: late availability of patch versions, various quirks from how they are built (missing readline, missing some build info that self-compiled C python modules might need.)
-
Show HN: Pywebview 5
Bundling Python isn't too bad if you find the right tools for it.
I really like https://github.com/indygreg/python-build-standalone and https://github.com/indygreg/PyOxidizer
A bundled, built standalone Python can be 16 to 32MB (including the full standard library, which you can strip down to just the bits you use to save size). Not tiny, but probably not worth switching programming languages over.
-
ModuleNotFoundError, but it's there
I'm trying to build a "portable" Python package based on those available from https://github.com/indygreg/python-build-standalone/releases.
-
Briefcase: Convert a Python project into a standalone native application
I'm a huge fan of https://github.com/indygreg/python-build-standalone which provides Python builds that CAN be moved around and work independently of any other Python installation.
I used that for my own Python+Electron app, which I wrote about here: https://til.simonwillison.net/electron/python-inside-electro...
-
alternative to poetry/pip/pipenv/pyenv/venv/virtualenv/pdm/hatch/…
I used to build my own Pythons that are the same everywhere, now I use indygreg's Python builds. Rye will automatically download and manage Python builds from there. No compiling, no divergence.
-
As if there weren't enough packaging tools already: mitsuhiko/rye: an experimental alternative to poetry/pip/pipenv/venv/virtualenv/pdm/hatch/…
One interesting tidbit is that it completely ignores your system Python installations, and instead uses precompiled installations of Python by indygreg from PyOxidizer. This means you don't have to deal with installing Python. It just auto downloads the right builds.
-
How to install any version of Python on Northeastern's Linux server
wget https://github.com/indygreg/python-build-standalone/releases/download/20220630/cpython-3.10.5+20220630-x86_64_v3-unknown-linux-gnu-install_only.tar.gz -O - | tar -xz && mv python PortablePython
-
Switching from pyenv, rbenv, goenv and nvm to asdf – yujinyuz
The lack of Ruby support instantly rings an alarm for me because CPython (on POSIX) also is not relocatable, but is listed as support. Turns pit Hermit is actually using a third-party build script[1] instead of the official one. While the python-build-standalone project is quite awesome and indeed is useful for a lot of things, it has enough quirks I would recommend against any generic package distributor to advertise as Python for general use. This in turn makes me lose most confidence on Hermit, unfortunately.
Be careful if you’re also interested in Hermit. These kinds of things bit you up way down the road when you least expect them to.
[1] https://github.com/indygreg/python-build-standalone
-
How to make sure a python program runs on a computer that might not have internet connection to download the external libraries used?
If you really want to be sure, you can download an install_only standalone Python build from https://github.com/indygreg/python-build-standalone/releases and install the libraries with the included pip. Then just tar it again to archive it, and use the included python to run your project. The downloaded wheel you get with pip wheel may depend on the Python version so you just save the wheels you must make sure the Python point version is exactly the same.
semver
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
-
Neovim v0.9.5 Released
I believe neovim follows semantic versioning. https://semver.org/
-
Semver 2.0.0 Released
Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.
https://github.com/semver/semver/releases
-
First purchase advice
All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)
-
fkYAML v0.3.0: Support non-string-scalar nodes as mapping keys
If you're using semver, read the spec it's not overly long or hard to understand.
-
Immich will have breaking changes (again) in the next release
Semantic versioning actually has a clear rule about this:
What are some alternatives?
iron.nvim - Interactive Repl Over Neovim
react-native - A framework for building native applications using React
pyenv - Simple Python version management
semantic-release - :package::rocket: Fully automated version management and package publishing
eclectica - ☀️ Cool and eclectic version manager for any language
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
Visual Studio Code - Visual Studio Code
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
evcxr
helmfile - Deploy Kubernetes Helm Charts
vscode-jupyter - VS Code Jupyter extension
Poetry - Python packaging and dependency management made easy