Skip to content

Bump pex from 1.6.11 to 2.1.26#216

Closed
dependabot-preview[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pex-2.1.26
Closed

Bump pex from 1.6.11 to 2.1.26#216
dependabot-preview[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pex-2.1.26

Conversation

@dependabot-preview

@dependabot-preview dependabot-preview Bot commented Jan 22, 2021

Copy link
Copy Markdown
Contributor

Bumps pex from 1.6.11 to 2.1.26.

Release notes

Sourced from pex's releases.

pex 2.1.26

2.1.26

This is a hotfix release that fixes requirement parsing when there is a local file in the CWD with the same name as the project name of a remote requirement to be resolved.

  • Requirement parsing handles local non-dist files. (#1190)

pex 2.1.25

2.1.25

This release brings support for a --venv execution mode to complement --unzip and standard unadorned PEX zip file execution modes. The --venv execution mode will first install the PEX file into a virtual environment under ${PEX_ROOT}/venvs and then re-execute itself from there. This mode of execution allows you to ship your PEXed application as a single zipfile that automatically installs itself in a venv and runs from there to eliminate all PEX startup overhead on subsequent runs and work like a "normal" application.

There is also support for a new resolution mode when building PEX files that allows you to use the results of a previous resolve by specifying it as a -pex-repository to resolve from. If you have many applications sharing a requirements.txt / constraints.txt this can drastically speed up resolves.

  • Improve PEX repository error for local projects. (#1184)
  • Use symlinks to add dists in the Pex CLI. (#1185)
  • Suppress pip debug warning. (#1183)
  • Support resolving from a PEX file repository. (#1182)
  • PEXEnvironment for a DistributionTarget. (#1178)
  • Fix plumbing of 2020-resolver to Pip. (#1180)
  • Platform can report supported_tags. (#1177)
  • Record original requirements in PEX-INFO. (#1171)
  • Tighten requirements parsing. (#1170)
  • Type BuildAndInstallRequest. (#1169)
  • Type AtomicDirectory. (#1168)
  • Type SpawnedJob. (#1167)
  • Refresh and type OrderedSet. (#1166)
  • PEXEnvironment recursive runtime resolve. (#1165)
  • Add support for -r / --constraints URL to the CLI. (#1163)
  • Surface Pip dependency conflict information. (#1162)
  • Add support for parsing extras and specifiers. (#1161)
  • Support project_name_and_version metadata. (#1160)
  • docs: fix simple typo, orignal -> original (#1156)
  • Support a --venv mode similar to --unzip mode. (#1153)
  • Remove redundant dep edge label info. (#1152)
  • Remove our reliance on packaging's LegacyVersion. (#1151)
  • Implement PEX_INTERPRETER special mode support. (#1149)

... (truncated)

Changelog

Sourced from pex's changelog.

2.1.26

This is a hotfix release that fixes requirement parsing when there is a local file in the CWD with the same name as the project name of a remote requirement to be resolved.

2.1.25

This release brings support for a --venv execution mode to complement --unzip and standard unadorned PEX zip file execution modes. The --venv execution mode will first install the PEX file into a virtual environment under ${PEX_ROOT}/venvs and then re-execute itself from there. This mode of execution allows you to ship your PEXed application as a single zipfile that automatically installs itself in a venv and runs from there to eliminate all PEX startup overhead on subsequent runs and work like a "normal" application.

There is also support for a new resolution mode when building PEX files that allows you to use the results of a previous resolve by specifying it as a -pex-repository to resolve from. If you have many applications sharing a requirements.txt / constraints.txt this can drastically speed up resolves.

2.1.24

This release upgrades Pip to 20.3.3 + a patch to fix Pex resolves using the pip-legacy-resolver and --constraints. The Pex package is also fixed to install for Python 3.9.1+.

2.1.23

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview
Bump pex from 1.6.11 to 2.1.26
8fe035c 
Bumps [pex](https://github.com/pantsbuild/pex) from 1.6.11 to 2.1.26.
- [Release notes](https://github.com/pantsbuild/pex/releases)
- [Changelog](https://github.com/pantsbuild/pex/blob/master/CHANGES.rst)
- [Commits](pex-tool/pex@v1.6.11...v2.1.26)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview Bot added the dependencies Pull requests that update a dependency file label Jan 22, 2021
@dependabot-preview dependabot-preview Bot mentioned this pull request Jan 22, 2021
Closed
@dependabot-preview

dependabot-preview Bot commented Jan 22, 2021

Copy link
Copy Markdown
Contributor Author

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

@dependabot-preview

dependabot-preview Bot commented Jan 25, 2021

Copy link
Copy Markdown
Contributor Author

Superseded by #218.

@dependabot-preview dependabot-preview Bot deleted the dependabot/pip/pex-2.1.26 branch January 25, 2021 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants