-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
conda run uses verbosity meant for executable #13639
Comments
Hi @milongo, Thanks for filing this. I've tried to recreate this issue on both macOS and Linux with no luck. Here are the steps I took:
All the above indicates to me that everything is working as it should. Is there something I am not doing that you are? And, is there anything else about your system that would be useful to know to help us figure out why you are seeing this? Unfortunately, until we are able to reliably recreate this on our side, we will be unable to implement fix. |
Hey @travishathaway thanks for the prompt reply. I was working with docker as well and I assumed this would be reproducible outside docker. Now I am thinking I must be doing something wrong, but I'm not sure what it is. With your example, I built a simple dockerfile:
If you do
|
Hi @milongo, I think we have narrowed in on what the problem is:
This will cause conda to spit out debugging information. This is not the expected behavior because these options should be passed to the script and not conda. I still cannot reproduce your original invocation though ( I would recommend that we use this issue to fix the problem that we can both recreate. |
That makes sense to me! I must have made a mistake at first when trying to write the instructions to reproduce my bug. |
Another way this bug can manifest is if you use $ conda run -n myenv pytest -vs tests
usage: conda [-v] [--no-plugins]
conda: error: argument -v/--verbose: ignored explicit argument 's' This used to work (at least as of 23.3.1). It still works fine using This makes |
@kenodegard I think you might know best how this is triggered, I'm guessing because of the preparsing? |
We should implement
This SO answer has some extra details. Maybe we should split on |
@jaimergp beat me to it, yes it's the pre-parser and we need to implement |
Checklist
What happened?
Hi,
I have a python script that accepts a verbosity parameter exactly like
conda run
does, i.e. with-v
or--verbose
, where doing-vv
or-vvv
increases the verbosity level. If I do something likeI get this log at the beginning of my app's execution:
It seems like the
-v
s were somehow added?I'm not sure if this is a bug or not, but it looks like it since I did not mean to set the conda verbosity level to debug mode.
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: