Closed fanmingyu212 closed 2 years ago
If there is not a reasonable solution to this problem, this can be an "won't fix" issue. This behavior does not matter for our use (it actually simplifies the bat files for us), An user can always do deactivate
in the beginning of the bat file to exit the current conda environment if they need too.
If there is not a reasonable solution to this problem, this can be an "won't fix" issue. This behavior does not matter for our use (it actually simplifies the bat files for us), An user can always do
deactivate
in the beginning of the bat file to exit the current conda environment if they need too.
If this is not a big problem for us, I'd like to push this off a little and work on CLI first. Though I haven't found a way to address this issue, I will come back to this when other parts of the project are done.
This is the correct approach: solve the pressing problems first. I would only spend time on this if it is really relevant to us (at this point). People who are interested can also address.
When we start tray launcher from a conda environment, new scripts also start from this environment right now. However, new scripts should start in the default cmd.