-
Notifications
You must be signed in to change notification settings - Fork 2k
conda create --clone should not allow users to specify a --file
#15073
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
Conversation
CodSpeed Instrumentation Performance ReportMerging #15073 will not alter performanceComparing Summary
|
3af25d6 to
44e11cb
Compare
ryanskeith
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I do have a suggestion on a better error message.
44e11cb to
82df68a
Compare
jezdez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor fixes, so the exception is rendered consistently.
|
To be clear, based on how the exception message is built: Lines 145 to 167 in a9b6ff5
|
Co-authored-by: Jannis Leidel <jannis@leidel.info>
Description
With this change, conda will not allow users to specify extra packages using the
--filearg when cloning an environment. This makes theconda create --clonecommand more consistent in the arguments that are allowed.fixes #15072
Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?