RGBCube/nu_scripts
1
Fork 0
mirror of https://github.com/RGBCube/nu_scripts synced 2025-08-01 06:37:46 +00:00
Code Issues Activity
nu_scripts/modules/virtual_environments/nu_conda
History
Exact
Elizabeth eedcd10dbb
Fixed sys usage (#916) 
Just as a heads up, I haven't really tested this since a lot of it is
stuff I don't use or know how to set up without some reading up. I have
tested the nu_conda_2 change since I have a python project that I use
that for, and I could look into testing more of it if needed.

I've tried finding (naively using `/sys\W/`) all the usage of the old
plain `sys` calls and replacing them with alternates as appropriate,
which mostly has been to swap a `(sys).host.name` call into a
`$nu.os-info.name` one, since it'll be tad faster and more consistent
across platforms with naming (especially as the value comes from the
[rust stdlib](https://doc.rust-lang.org/std/env/consts/constant.OS.html)
and is very predictable).

Fixes #897
2024-07-24 09:09:31 -05:00
..
nu_conda.nu Fixed sys usage (#916) 2024-07-24 09:09:31 -05:00
README.md resolve several issues in nu_conda and nu_msvs (#872) 2024-06-07 07:36:00 -05:00

README.md

Conda Module for Nushell

A simple module for activating and deactivating Conda environments.

Prerequisites

Installation

Put nu_conda.nu into the module folder of your nushell configuration workspace.

Usage

use nu_conda.nu         # activate module
nu_conda activate py36  # activate a Conda environment, e.g. py36
nu_conda deactivate     # deactivate the activated Conda environment
nu_conda list           # list available environments, same as `$env.CONDA_ENVS`

How It Works

This module re-implements the activation and deactivation functionalities of the conda.nu module while providing a better performance, but not fully replacing it.

This module adds paths of a target Conda environment to PATH/Path while activating the environment, and recover the original PATH/Path while deactivating an environment. Several environment variables are exported:

  • CONDA_BASE_PATH: The original PATH/Path before any activation/deactivation.
  • CONDA_ROOT: Root directory of Conda installation.
  • CONDA_ENVS: Available Conda environments for activation.
  • CONDA_CURR: Current activated Conda environments.

FAQ

Q: How better is the performance?
A: Activating a Conda environment costs ~20ms while conda.nu costs ~1500ms on a PC with Windows 10 Enterprise OS and Intel i7-8700 3.20GHz CPU.

Q: How to show the current Conda environment in the prompt?
A: This module does not automatically change the prompt when a Conda environment is activated, but an environment variable $env.CONDA_CURR is set to the name of the current Conda environment which can be used to customize the prompt.

Q: Does it support Mamba/Micromamba?
A: As Mamba's documentation said, mamba is drop-in replacement for conda, and micromamba seems to be another thing. This module only uses results of conda/mamba info --envs --json. Therefore, I would say Mamba is (partially?) supported but I'm not sure about Micromamba.

Q: How does it choose between Conda and Mamba?
A: This module prefers calling mamba than conda, but it should be very easy to change the preference by modifying the source code.

Q: Completions?
A: PRs are welcomed.