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
As far as I understand, Orange3 and the add-ons are on the conda-forge channel which stays free. The Windows installer installs miniconda3 (perhaps the MacOS one as well?).
Would it be possible to use miniforge3 instead in the installer? It is faster and has conda-forge instead of default as default channel. Or keep miniconda3 and remove the default anaconda channel.
If you see other effects of the license change, it would be good to address them.
The text was updated successfully, but these errors were encountered:
Only the Windows version uses conda for now, and all packages come from conda forge. We have been discussing abandoning miniconda in binary packages and just work with straight up packages from pip a while ago. This seems like a good motivating factor.
Discussion summary: big companies seem to start avoiding miniconda. We should probably move. We have to see whether migrating to miniforge is just a question of replacing the executable.
Summary of the changes: https://www.datacamp.com/blog/navigating-anaconda-licensing
As far as I understand, Orange3 and the add-ons are on the conda-forge channel which stays free. The Windows installer installs miniconda3 (perhaps the MacOS one as well?).
Would it be possible to use miniforge3 instead in the installer? It is faster and has
conda-forge
instead ofdefault
as default channel. Or keep miniconda3 and remove thedefault
anaconda channel.If you see other effects of the license change, it would be good to address them.
The text was updated successfully, but these errors were encountered: