You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: