v2.0.0

What's Changed

Breaking changes

• venv install can now be used to install individual packages: venv install <package> by @connesy in #37

  To enable this feature, installing from a requirements file now requires the use of the new -r | --requirement flags: venv install -r requirements.txt. Packages installed using venv install <package> are first added to the requirements file before reinstalling the entire environment to ensure reproducibility. To uninstall packages, use the new venv uninstall subcommand, e.g. venv uninstall <package>.

• venv sync has been removed. Use venv install -r <requirements>.lock instead by @connesy in #17

Major changes

• Added venv uninstall subcommand to complement the new functionality of venv install <package> by @connesy in #37

  Running venv uninstall <package> will first remove the package from requirements.txt, then use venv install -r requirements.txt to reinstall the environment without <package>.

  This process ensures that there are no "orphaned dependencies" left in the environment after uninstalling, unlike when using pip uninstall <package>.

• Loosened the file name requirements for requirements files. Requirements files can now be any valid file name with the extension .txt (.lock for lock files) by @connesy in #35

Full Changelog: https://github.com/SallingGroup-AI-and-ML/venv-cli/blob/v2.0.0/CHANGELOG.md