You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created several CLI pythons scripts that utilize click, lets call one test.py. click itself uses --help as a default parameter to get help info. The dotenv CLI also has a --help argument. Running something like:
dotenv -f ../.env run python test.py --help
...results in the --help argument getting used by dotenv, not my script.
Is this intentional, or would this be considered a bug?
Is there a workaround (besides leaving off --help to default to click's help msg)?
The text was updated successfully, but these errors were encountered:
What about dotenv -f ../.env run -- python test.py --help? -- is a common convention to separate options and arguments for the program and click, which we use in python-dotenv, understands that convention.
I've created several CLI pythons scripts that utilize
click
, lets call onetest.py
.click
itself uses--help
as a default parameter to get help info. Thedotenv
CLI also has a--help
argument. Running something like:dotenv -f ../.env run python test.py --help
...results in the
--help
argument getting used bydotenv
, not my script.--help
to default to click's help msg)?The text was updated successfully, but these errors were encountered: