Getting around with Anaconda License violation while using Conda or Miniconda

If you are a Conda or Miniconda user you might have noticed that installing Anaconda packages via the default channel https://repo.anaconda.com/pkgs/ now requires a commercial license if you are an enterprise . If you are using it for individual purposes or are a startup, you are still able to use it without violating any license.

So for eg. if you normally installed conda and miniconda using the installers or any package manager and do a 

conda install <package>

it by default uses a default package repo channel https://repo.anaconda.com/pkgs/ to download that python package and install it. So you might be violating the licence by using this repo URL as your default channel. 

To confirm whether you are violating the license one can issue  conda config --show default_channels

 
 
It can be seen that default repo is set to use https://repo.anaconda.com/pkgs/  channel URLs. 

To get around this violation there are multiple options. I will list 2 of them here.
 

Option#1 :

The first one is to use opensource and free to use channels like conda-forge as default channel for your conda or Miniconda installation. The conda-forge  is a Community-based Software Distribution Built on the conda Package Format and Ecosystem. (Zenodo. http://doi.org/10.5281/zenodo.4774216)
 
Do use conda-forge as default channel,  perform the follwing steps.

  1. Add conda-forge to your existing conda or miniconda installation, using
    •  conda config --add channels conda-forge
  2. Once done verify the channels again using conda config --show channels . It should print following.
    • channels:
        - conda-forge
        - defaults
  3. Once verified, remove the defaults channel using conda config --remove channels defaults . Once removed issue conda config --show channels to verify that only conda-forge is present as the only channel. You should see output like.
    • channels:
        - conda-forge
 That is it, you are done with getting around this violation.

To verify this setup install a conda package and see the channel being used to download the package. If it looks like below, it is all good.

 
 

Option#2 :

 As a second option, one can use Miniforge. Miniforge is an effort to provide Miniconda-like installers, with the added feature that conda-forge is the default channel. 
Miniforge does this for you by default, but if you still love using conda or miniconda, fee free to set the default channel yourself using Option#1. 


Comments

Post a Comment

Popular posts from this blog

Developing Garmin SmartWatch Apps with ConnectIQ Platform-Part 3

Image
In this third and last part of this tutorial we shall see how to pass the meeting information from the Android app to the SmartWatch app/widget that we developed in part 2 of this tutorial. This part of the tutorial requires some prior knowledge on Android development. If you are in need of a quick android tutorial then you can find it  here . ConnectIQ platform comes with following pre-built mobile SDKs. Android BLE - (actually connects Android app to Smartwatch Apps over BLE) iOS BLE - (connects an iOS mobile app to Smartwatch App over BLE) Android ADB - ( used to simulate BLE connection over ADB) These SDK's  are set of libraries  required to communicate over BLE or to simulate a BLE like connection over ADB (the Android debug bridge). In this part of the tutorial we will look at that Android ADB SDK so that we can simulate the BLE like connection using the emulator in our development environment. You can select and download the Android ADB SDK from the ...
Read more

Developing Garmin SmartWatch Apps with ConnectIQ Platform-Part 1

Image
Recently I was involved in developing apps for Gramin Wearables . Being new to the wearables world I found it relatively easier to develop apps for Garmin Wearables then what I had thought earlier. Hence I would like to share my experience via this blog series. I will take you through the step by step process of developing a simple watch widget that synchronizes with an Android phone's Google Calendar to send out meeting alerts and reminders on your Garmin Watch. Apps for Garmin Wearables are developed using the Garmin ConnectIQ SDK   and are programmed using  Monkey C language  . You are already familiar with Monkey C if you are familiar with languages like Java or Objective C. Introduction to  Monkey C language   highlights the basic difference between other languages and Monkey C. Its a short and precise tutorial, I would suggest to give a quick read in case you are planning to develop apps for Garmin. The Problem Statement Lets say you own an And...
Read more

Web Service Security and Native Mobile App User Authentication

Image
In this article I am going to throw some light around web service security,  user Authentication  for native mobile applications and how both the topics are connected. Me along with my cool team members at Zycus were working on the same off lately. The idea is to highlight the fact that it is ideal to implement web service security by being agnostic to the type of web service clients (like mobile apps) but these decisions may impact the mobile app user authentication process. If you are working on a mobile application that requires user authentication and fetching data from a server side application then it is highly likely that you are exposing certain functionality of your server side application via web services that can be accessed over the web by your mobile application. While developing such applications you will usually encounter following challenges.  How to secure the web service endpoints?  How to authenticate users from the mobile app in secure way...
Read more