maxiconda-envs

In this repository we maintain and release the maxiconda environments. The overview of the environments and their contents can be found in the maxiconda-envs.xlsx file.

Solving the specifications is done daily with GitHub Actions. New sollutions are commited directly to the recipes directory. Releases are made once so often, which will upload them to the anaconda.org/Semi-ATE channel.

This anaconda.org/Semi-ATE channel is included when installing with the maxiconda installers.

Usage

Installing the maxiconda meta package

(base) me@mybox:~$ conda create -n some_env maxiconda

or alternatively

(base) me@mybox:~$ mamba create -n some_env maxiconda

The above will create an environment with the name (-n) some_env and install the maxiconda meta package in it.

Installing the _spyder_ meta package

(base) me@mybox:~$ conda create -n _spyder_ _spyder_

or alternatively

(base) me@mybox:~$ mamba create -n _spyder_ _spyder_

The above will create a spyder application environment called _spyder_ and installs the _spyder_ metapackage in it.

NOTE: Environments starting with an underscore ('_') are considered to be application environments (as opposed to development environments). As Spyder is an application it is good practice to install it in an environment starting with an underscore.

Whe Semi-ATE channel is not configured

In case you don't have the Semi-ATE channel available (for example you installed with miniforge) you can do this :

(base) me@mybox:~$ conda create -n some_env maxiconda -c Semi-ATE

or alternatively first add the channel like so :

(base) me@mybox:~$ conda config --set channel_priority strict
(base) me@mybox:~$ conda config --append channels Semi-ATE
(base) me@mybox:~$ conda create -n some_env maxiconda