Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PyCall & Anaconda terms of service #913

Closed
tverho opened this issue Jul 6, 2021 · 3 comments
Closed

PyCall & Anaconda terms of service #913

tverho opened this issue Jul 6, 2021 · 3 comments

Comments

@tverho
Copy link

tverho commented Jul 6, 2021

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.

@DilumAluthge
Copy link
Contributor

See also:

@stevengj
Copy link
Member

Yes, it would be good to make this the default.

@stevengj
Copy link
Member

stevengj commented Dec 1, 2021

Closed by #207.

@stevengj stevengj closed this as completed Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants