There is additionally a -no-default-packages flag, which can be used to disable such default package installation when you don't need it. If all environments for your user are categorized as "development", then a sensible place to define the default packages would be ~/.condarc. condarc, and Conda can load settings in a nested fashion. Note that there are multiple options for where to store this. The conda env create will respect these and add them to every env you create, so you can still keep a single YAML that describes only the essentials for the production version. The idea would be to define default packages (such as autopep8) in a. One way of managing this without violating environment isolation 1 would be to use Conda's default packages functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |