Re:Creating Python Virtual Environments with Conda: Why and How
by jawilson2 on Wednesday December 11, 2019 @08:35AM
(#21762165)
Do you mean the condarc file? You can do `export CONDARC=./project_condarc`
Re:Creating Python Virtual Environments with Conda: Why and How
by mulmen on Wednesday December 11, 2019 @05:47PM
(#21767617)
No I mean in the config file example the PREFIX is set to a static path including a user directory. This means if anyone checks out the config file and tries to run it the path will not exist. Is there an override somewhere that provides the desired prefix at a user level? Something like ~/.condarc or /etc/condarc?
Ideally I would set the prefix for Conda for myself only once (~/.condarc?) and the source controlled config file would then extend that config.
I would expect the conda config file in a project to say nothing at all about the prefix unless it is relative to an existing prefix I set elsewhere.
This way I don't have to manipulate my environment and edit config files every time I run conda.
I should probably just RTFM.
It seems less valuable if the prefix is hard coded to the specific user. To a lesser extent even specifying the name may be too limiting.