When calling the register() api to register option...
# generalp
polite-garden-50641
05/20/2020, 5:47 PMWhen calling the register() api to register options:
register("--some-option", type=str, help="bla bla bla.")InvalidKwarg: Invalid registration kwarg required.w
witty-crayon-22786
05/20/2020, 5:50 PMthere isn’t, no.
witty-crayon-22786
05/20/2020, 5:51 PMi think that part of the reason for that is that none of the built in backends or existing plugins have required options, because it can slow down onboarding
witty-crayon-22786
05/20/2020, 5:52 PMif you’ve opted-in to enabling a plugin though, it might be reasonable for it to stop you and ask for required options. cc @happy-kitchen-89482
h
happy-kitchen-89482
05/20/2020, 5:53 PMWhat's the example use-case?
p
polite-garden-50641
05/20/2020, 5:56 PMI have a rule that needs to specify a python version (in order to resolve requirements) the currently, the rule defaults to python 3.6, which means when I run the rule, I thinks I am using 3.6 while in reality I am using 3.8 (I have
interpreter_constraints = ["CPython>=3.8,<4"][python-setup]polite-garden-50641
05/20/2020, 5:57 PMI am thinking about changing the rule to accept PythonSetup instead of declaring its own platform & python version... which is probably the right way to go.
👍 1
w
witty-crayon-22786
05/20/2020, 5:58 PMyea, it should.
witty-crayon-22786
05/20/2020, 5:59 PM@happy-kitchen-89482: sidenote, we don’t support scoped subsystem dependencies in v2, but we probably should
witty-crayon-22786
05/20/2020, 5:59 PMnot sure how many of these use-sites will end up wanting to use that later.
h
happy-kitchen-89482
05/20/2020, 10:29 PMHmm, scoped deps are complicated, are we sure we want that?
happy-kitchen-89482
05/20/2020, 10:30 PMI guess the motivating use case for them still exists
w
witty-crayon-22786
05/20/2020, 10:49 PMyea.