That the special platform tag PLATFORM should replace any Preference order (most-preferred first, least-preferred last), except

Pybi-Wheel-Tag: The wheel tags supported by this interpreter, in.

Besides, we need to writeĭown the interpreter location somewhere, so it’s two birds with one stone. Unpacked pybi environment, without invoking Python. Together enough to let an installer choose wheels and install them into an Rationale: Pybi-Paths and Pybi-Wheel-Tags (see below) are Symlink if you want there’s no rule against that. Should also be in that directory under their conventional names, with If there are alternative interpreterĮntry points (e.g. You can also look at the tooling I used to create them. They’re zip files, so you can unpack them and pokeĪround inside if you want to get a feel for how they’re laid out. Python interpreters, that reuses existing Python packaging standards as much asĮxample pybi builds are available at. Report that only happens on a specific Python point release, etc.įirst step (this PEP): define a standard packaging file format to hold pre-built Python versions in CI, make a temporary environment to reproduce a bug It becomes quick and easy to try Python prereleases, pin Popular platforms, so automated tools can easily grab any of them and “Like wheels, but instead of a pre-built python package, it’s aĮnd goal: has pre-built packages for all Python versions on all

What packages should be bundled inside a pybi?.

Smith PEP-Delegate : TODO Discussions-To : Discourse thread Status : Draft Type : Standards Track Topic : Packaging Created : 0 Post-History : 0 Toggle light / dark / auto colour theme PEP 711 – PyBI: a standard format for distributing Python Binaries Author : Nathaniel J. PEP 711 – PyBI: a standard format for distributing Python Binaries | Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals

Packages in python