Skip to main content

How to Integrate Anaconda Prompt and Jupyter Notebook with CMDER

I personally find CMDER a fantastic tool and do believe its the best windows console emulator out there. I prefer make use of its capability to run multiple commands side by side with split panes and tabs, which helps multitasking and productivity. For those of you who aren't aware, CMDER is a user-friendly console emulator for Windows that offers numerous features, including a sleek and intuitive GUI, making it easy for users, including beginners, to interact with the command line.

 In this blog, I'll guide you through the steps to set up CMDER to work similar to Anaconda Prompt, a popular environment for Python development.



 A Step-by-Step Guide to Anaconda Prompt Integration in CMDER

 

  •  Step 1: Navigate to Anaconda Prompt

Before we begin, ensure you have Anaconda installed on your system. Open the Anaconda Prompt to find the location of the 'conda' executable.




  • Step 2: Locate the 'conda' Executable

In the Anaconda Prompt, enter the following command:

where conda 

This command will display the location to the 'conda' executable.




  • Step 3: Add 'conda' to the "PATH" Environment Variable

Copy the path of the 'conda' executable and add it to the "PATH" environment variable. This step allows CMDER to access the 'conda' command globally.


Note: you shouldn't include the actual .bat or .files in the path, so in my case the paths to be added were :


    • D:\Tools\up-ml\Library\bin\
    • D:\Tools\up-ml\Scripts\
    • D:\Tools\up-ml\condabin\

  • Step 4: Initialize CMDER with Conda

Start CMDER and enter the following command:

conda init cmd.exe

This command initializes CMDER with Conda integration, enabling you to use CMDER just like Anaconda Prompt.

  • Step 5: Restart CMDER

CMDER might ask you to restart the console after running the initialization command. Close CMDER and open it again to apply the changes.

  • Step 6: CMDER as Your Anaconda Prompt Alternative

Congratulations! You are all set. Now, you can use CMDER just like you would use Anaconda Prompt. You have the flexibility of the familiar Anaconda environment while enjoying the additional features and user-friendly interface CMDER provides.

  • Step 7: Open Jupyter Notebook

To open Jupyter Notebook in CMDER, simply type the same command as you would in Anaconda Prompt:

jupyter notebook

CMDER will seamlessly launch Jupyter Notebook, allowing you to start coding and exploring data instantly.


Conclusion:

CMDER's integration with Anaconda Prompt opens up a world of possibilities for Python developers. Its user-friendly interface and productivity-enhancing features make it an indispensable tool in your coding arsenal. By following these simple steps, you can harness the full power of CMDER while experiencing the ease of Anaconda Prompt for your Python development projects. Give it a try, and witness the remarkable difference CMDER can make in your Python workflow

Comments

Popular posts from this blog

FTP C# Error : “The remote server returned an error: (530) Not logged in ."

  Recently working on a FTP solution using C# , i encountered an error  “ The  remote server returned an error: (530) Not logged in.” The code i used was following: FtpWebRequest request = (FtpWebRequest)WebRequest.Create( ftp://xxxxxx/file.txt ); request.Method = WebRequestMethods.Ftp.UploadFile request.Credentials = new NetworkCredential(usernameVariable, passwordVariable); What was more bewildering was if i modified the code to following, the solution was working fine. But this for obvious reasons is not an option as the username cannot be hardcoded //works but implausible to use in realtime solutions request.Credentials = new NetworkCredential("dmn/#gsgs", password);  Some googling revealed that special charcters create issues in the NetworkCredential Object. Hence some playing around worked for me, and it works irrespective of wether i do a FTPWebRequest or WebRequest. Solution: Instantiate NetworkCredential object with three paramters (username, password, domain) and m

Llamhub SnowflakeReader: A Loader to query and chat Snowflake Data in your LLM Applications

  Snowflake Loader for LLM Recently my second contribution to Llamaindex "SnowflakeReader" was merged to Lllamahub repository. This loader connects to Snowflake (using SQLAlchemy under the hood). The user specifies a query and extracts Document objects corresponding to the results. This loader is designed to be used as a way to load data into  LlamaIndex  and/or subsequently used as a Tool in a  LangChain  Agent.  Usage Option 1: Pass your own SQLAlchemy Engine object of the database connection Here's an example usage of the SnowflakeReader. from llama_index import download_loader SnowflakeReader = download_loader ( 'SnowflakeReader' ) reader = SnowflakeReader ( engine = your_sqlalchemy_engine , ) query = "SELECT * FROM your_table" documents = reader . load_data ( query = query ) Option 2: Pass the required parameters to esstablish Snowflake connection Here's an example usage of the SnowflakeReader. from llama_index import down

BLAS: Basic Linear Algebra Subprograms | Navigating Through BLAS on Your Windows Machine

Basic Linear Algebra Subprograms (BLAS), a term I encountered w hile working with the LLAMA (LLM model from Meta) on my windows machine seems to directly affect the performance of the model's inference. Most probably you (like me) already have BLAS capabilities on your windows machine and may be missing on the chance to leverage its capabilities. Lets understand the steps to ensure you are aware of BLAS and its implementation on your machine. Introduction: Basic Linear Algebra Subprograms (BLAS) is the standard that outlines a collection of fundamental routines designed to execute prevalent linear algebra operations, including vector addition, scalar multiplication, dot products, linear combinations, and matrix multiplication. Universally recognized as the standard foundational routines for linear algebra libraries, BLAS routines offer bindings for both C, through the "CBLAS interface," and Fortran, known as the "BLAS interface." While the BLAS specification is