Because PyCall often automatically opts to use an internal Conda installation that uses Anaconda repositories, that can easily lead to an unintentional breach of the ToS if the user is in a large organization. I think PyCall should not make such a choice without informing the user about the possible requirement of a commercial license.
A simple fix would be to disable the Anaconda repository and use Conda-forge instead. That way, the Anaconda ToS would not apply. Personally I find the easiest way to be to use Miniforge instead of Miniconda.
Recently, Anaconda has changed the terms of service of its repository so that a commercial license is required in large organizations:
https://www.anaconda.com/terms-of-service https://www.anaconda.com/blog/anaconda-commercial-edition-faq
Because PyCall often automatically opts to use an internal Conda installation that uses Anaconda repositories, that can easily lead to an unintentional breach of the ToS if the user is in a large organization. I think PyCall should not make such a choice without informing the user about the possible requirement of a commercial license.
A simple fix would be to disable the Anaconda repository and use Conda-forge instead. That way, the Anaconda ToS would not apply. Personally I find the easiest way to be to use Miniforge instead of Miniconda.