* Add blacklist handling for skipping requirements in pex resolver #457 * Better error handling for missing setuptools. * Mock PATH for problematic interpreter selection test in CI (#474) * Add manylinux wheel support and fix a few bugs along the way (#316) Special thanks to Dan Blanchard for seeding the initial PR for Manylinux support and wheel resolution improvements.
#Appcloner 1.4.7 full
This release includes full Manylinux support, improvements to wheel resolution (including first class platform/abi tag targeting) and a handful of other improvements and bugfixes. egg resolution for platform specific eggs. egg dists that inadvertently went out in 1.4.1. This release repairs a tag matching regression for. * Broaden abi selection for non-specified abi types. * Repair environmental marker platform setting. * Add resource / source bundling to pex cli (#507)Īnother bugfix release for the 1.4.x series. This release adds support for including sources and resources directly in a produced pex - without the need to use pants. * Invoke test runner at a more granular level for pypy shard. * Introduce a controlled env for pex testing. * Fix `PythonInterpreter` caching and ergonomics. * Validate entry point at build time (#521) * Fix installers to be insensitive to extras iteration order. This release adds support for validating pex entrypoints at build time in addition to several bugfixes. * Preserve perms of files copied to pex chroots. * Expand the range of supported setuptools. * Support `-` when running as an interpreter. * Support -c for plat spec dists in multiplat pexes. * Cleanup bootstrap dependencies before handoff. * Fix for super() usage on "old style class" ZipFile (#546) This release opens up setuptools support for more modern versions that support breaking changes in * Fixup `PEX.demote_bootstrap`: fully unimport. This is a hotfix release for a regression in setuptools compatibility introduced by #542.
To contribute, follow these instructions: If you don't have tox, you can generate a pex of tox: $ pex requests flask 'psutil>2,`_ for test and development automation. Launch an interpreter with ``requests``, ``flask`` and ``psutil`` in the environment: Possible and is more in-line with what pex does philosophically.
The advantage to this approach is that it keeps your Python environment as empty as This builds a pex binary in ``dist/pex`` that can be copied onto your ``$PATH``. You can also build pex in a git clone using tox: Pex is licensed under the Apache2 license. Still unsure about what pex does or how it works? Watch this quick lightning Pex files can be built using the ``pex`` tool. Include multiple platform-specific Python distributions, meaning that a single pex file Pex is an expansion upon the ideas outlined inĪnd makes the deployment of Python applications as simple as ``cp``.
pex (Python EXecutable) files which areĮxecutable Python environments in the spirit of `virtualenvs `_.
0 kommentar(er)
