-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decide how the --force-non-host
flag should evolve
#3982
Comments
I personally think this should be a natural closing step to #3635. Once implicit installations are removed, there should be fewer places that require We should not remove the flag completely though:
... so I recommend changing the flag to only suppress the warnings, and these warnings can of course be inaccurate, as suggested by their current wording. |
Makes sense. |
force_non_host
flag should evolve--force-non-host
flag should evolve
Originally posted by @rbtcollins in #3980 (comment) |
After https://discord.com/channels/442252698964721669/463480252723888159/1284703690204385290 and other similar issues showing a common confusion between Now I'm more convinced that we should go with the original plan with |
Sounds sensible to me... |
Originally posted by @rami3l in #3980 (comment)
The text was updated successfully, but these errors were encountered: