|
1 | 1 | # Release Notes
|
2 | 2 |
|
| 3 | +## 2.3.0 |
| 4 | + |
| 5 | +This release introduces `pex3 lock sync` as a higher-level tool that |
| 6 | +can be used to create and maintain a lock as opposed to using a |
| 7 | +combination of `pex3 lock create` and `pex3 lock update`. When there is |
| 8 | +no existing lock file, `pex3 lock sync --lock lock.json ...` is |
| 9 | +equivalent to `pex3 lock create --output lock.json ...`, it creates a |
| 10 | +new lock. On subsequent uses however, |
| 11 | +`pex3 lock sync --lock lock.json ...` updates the lock file minimally to |
| 12 | +meet any changed requirements or other changed lock settings. |
| 13 | + |
| 14 | +This release also fixes `pex --no-build --lock ...` to work with lock |
| 15 | +files also created with `--no-build`. The known case here is a |
| 16 | +`--style universal` lock created with `--no-build` to achieve a |
| 17 | +wheel-only universal lock. |
| 18 | + |
| 19 | +This release includes a fix to clarify the conditions under which |
| 20 | +`--requierements-pex` can be used to combine the third party |
| 21 | +dependencies from a pre-built PEX into a new PEX; namely, that the PEXes |
| 22 | +must use the same value for the `--pre-install-wheels` option. |
| 23 | + |
| 24 | +Finally, this release fixes `pex3 venv` to handle venvs created by |
| 25 | +Virtualenv on systems that distinguish `purelib` and `platlib` |
| 26 | +site-packages directories. Red Hat distributions are a notable example |
| 27 | +of this. |
| 28 | + |
| 29 | +* Implement pex3 lock sync. (#2373) |
| 30 | +* Guard against mismatched `--requirements-pex`. (#2392) |
| 31 | +* Fix `pex --no-build --lock ...`. (#2390) |
| 32 | +* Fix Pex to handle venvs with multiple site-packages dirs. (#2383) |
| 33 | + |
3 | 34 | ## 2.2.2
|
4 | 35 |
|
5 | 36 | This release fixes `pex3 lock create` to handle `.tar.bz2` and `.tgz`
|
|
0 commit comments