pantsbuild / pants / 9397
0%
main: 93%

LAST BUILD BRANCH: multiplatform_pex_with_uv
DEFAULT BRANCH: main
Ran
Jobs 7
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
9397

push

travis-ci

benjyw 
Reimplement list options to support appending.

[To releasers: See end of this message for things to call out in release notes]

To append a single value to a list-valued option, just "set" the option
to that value, as with action='append'.

`./pants --foo=1 --foo=2`

To append several values, add a plus sign in front of the value:

`./pants --foo=+[1,2]`

To replace the existing value, just set to a list:

`./pants --foo=[1,2]`

Note that this syntax works with config and env values as well.  This
means that you can append to the value specified in, say, pants.ini,
but also override it entirely, if you need to.

This endows list_option with the only useful feature of action='append', which
will therefore soon be deprecated.  In fact, action='append' is now implemented
as a list_option under the covers, so replacing all uses of it should be
straightforward.

In order to support lists of values other than strings, this change
introduces a member_type registration arg, which is only valid when
type=list_option.

This change was more complex than you'd think, as it required refactoring
Parser._compute_value. That method is now clearer and better documented
than before.

Some behavior has changed slightly. E.g., previously we validated
values even if they weren't used (e.g., the config, when it was overridden
by a cmd-line flag). Now we only validate the actual final value. But
these changes are either positive or neutral, in terms of their impact,
and they make the code more straightforward.

Release notes should also call out the following:

- This commit tightens up some aspects of option type conversion. There may be options
  in plugins that were relying on broken behavior (such as when using a string where an
  int was expected), and that will now (correctly) break.
- This commit deprecates the `PANTS_DEFAULT_*` env vars in favor of `PANTS_GLOBAL_*`.

Testing Done:
CI passes: https://travis-ci.org/pantsbuild/pants/builds/114384803

Reviewed at https://rbcommons.com/s/twitter/r/3541/
Jobs
ID Job ID Ran Files Coverage
1 9397.1 (CI_FLAGS="-cjlpn 'Various pants self checks'") 0
Travis Job 9397.1
4 9397.4 (CI_FLAGS="-fkmsrcjlpa 'Python contrib tests'") 0
Travis Job 9397.4
5 9397.5 (CI_FLAGS="-fkmsrjlpn -i 0/6 'Python integration tests for pants - shard 1'") 0
Travis Job 9397.5
6 9397.6 (CI_FLAGS="-fkmsrjlpn -i 1/6 'Python integration tests for pants - shard 2'") 0
Travis Job 9397.6
7 9397.7 (CI_FLAGS="-fkmsrjlpn -i 2/6 'Python integration tests for pants - shard 3'") 0
Travis Job 9397.7
8 9397.8 (CI_FLAGS="-fkmsrjlpn -i 3/6 'Python integration tests for pants - shard 4'") 0
Travis Job 9397.8
10 9397.10 (CI_FLAGS="-fkmsrjlpn -i 5/6 'Python integration tests for pants - shard 6'") 0
Travis Job 9397.10
Source Files on build 9397
Detailed source file information is not available for this build.