feat: support `NO_COLOR` and `FORCE_COLOR` env vars (#3979)
## Summary
Closes #3955
Adds explicit support to `NO_COLOR` and `FORCE_COLOR` via
GlobalSettings.
The order, per specs is now `NO_COLOR` > `FORCE_COLOR` > `color`.
This PR is a backup plan pending rust-cli/anstyle#192.
## Test Plan
Tested all cases locally for now; I didn't see existing tests for
GlobalSettings parsing.
57ea55d...
by
Charlie Marsh <email address hidden>
Add a hint for `Requires-Python` (#4021)
## Summary
As requested in the originating PR.
8eea470...
by
Charlie Marsh <email address hidden>
Bias towards local directories for bare editable requirements (#3995)
## Summary
Given `install -e dagster`, we need to assume that the user meant
`install -e ./dagster`, even though `install dagster` should _not_ be
treated as `install ./dagster`. I suspect pip will change this in the
future (since `pip install dagster` does _not_ meant `pip install
./dagster`) but for now it's what users expect.
420333a...
by
Charlie Marsh <email address hidden>
Avoid 'are incompatible' for singular bounded versions (#4003)
## Summary
Not sure if this is worth the complexity, but it does read better.
365ca63...
by
Andrew Gallant <email address hidden>
uv/tests: add new universal tests
This updates to packse 0.3.17. There are a few incidental changes in
places, but the main addition here are the tests for universal
resolutions.
42b584c...
by
Andrew Gallant <email address hidden>
scripts/scenarios: update packse to 0.3.17
7b736fc...
by
Andrew Gallant <email address hidden>
scripts/scenarios: update 'generate.py' to handle universal tests
This commit adds a template and does some light surgery on `generate.py`
to make use of that template. In particular, the universal tests require
using the "workspace"-aware version of `uv`, so we can't use the
existing `uv pip {compile,install}` tests.
459966a...
by
Andrew Gallant <email address hidden>
uv/tests: update packse tests (#4015)
This is just the result of running
./scripts/sync_scenarios.sh
From the root of the `uv` repository.
When I initially ran this, it produced some tests with snapshots that
weren't being updated. It turned out this was because the tests weren't
running, as they were gated behind the `python-patch` feature. In this
commit, we add `python-patch` to our `cargo insta` command, which should
update all relevant snapshots.
There are still some superfluous updates as a result of a spell checker
being run on generated files, but
5c30b39...
by
Andrew Gallant <email address hidden>
uv-resolver: normalize marker expressions (#4017)
This is a quick fix for some flaky tests where the output in the lock
file isn't stable because marker expressions can be combined in a
non-deterministic order.
I believe there is ongoing work to simplify marker expressions which
will help here, but I think some kind of normalization is still
ultimately needed to guarantee consistent output.
