v0.4.2

What's Changed

• Fixes slim update and allows for version selection by @Nortamo in #32
• Features by @Nortamo in #33

• Automatically determine host os for base container
• Warn when group setting fails, and don't stop the installation
• Activate venv when forcing conda to be active
• Keep venv active for environments created from wrapped containers

Logic for venv activation:

• An existing conda-containerize installation is used to create a venv.
• If no variables are set, the venv will be active (not by explicit activation but by the virtue of being called -> equivalent by python standard ) in the container but the conda environment will not be in PATH.
• Setting CW_FORCE_CONDA_ACTIVATE will first activate the conda environment and then the virtual env on startup
  (This was done to reduce the complexity of manually shuffling around the PATH entries)
• The use case where you would want for both the venv and conda to be in PATH but for the conda environment not to be active is not considered or supported.

Full Changelog: v0.4.0...v0.4.2