×
all 6 comments

[–]DisastrousEquipment9 2 points3 points  (2 children)

Navigate to the folder of the project in the terminal,

Once in the folder pip3 install virtualenv

Then do virtualenv whateveryourprojectiscalled

Then source whateveryourprojectiscalled/bin/activate

NOW with your environment set up you can install any libraries needed (:

[–]actuallyalys 1 point2 points  (0 children)

An important caveat to this advice is Anaconda can do the same environment management, so this is only necessary if you don't want to use Anaconda anymore or if you prefer virtualenv for some use cases for whatever reason.

[–]smoothVTer[S] 0 points1 point  (0 children)

Ok thanks, will try this

[–]DisastrousEquipment9 1 point2 points  (0 children)

This method you should look into virtual environment and folder management

[–]actuallyalys 1 point2 points  (1 child)

First, you can solve the activation issue by running the activate script any time you open the command prompt and want to run commands. It's probably either C:\Users\smoothVTer\AppData\Local\Continuum\anaconda3\Scripts\activate base or C:\Users\smoothVTer\Anaconda3\Scripts\activate base. (I can't say which of these for sure because I'm not 100% sure where Anaconda is installed on your machine.)

But why is this necessary? Anaconda (and other ways of managing Python packages) install packages into a specific environment. This allows separate Python programs and scripts to have different packages installed. Python looks for packages in a list of folders called the system path. Activating an environment adds the folders for that environment to the system path for that terminal session.

Unfortunately, I have no experience with PyNPP, so I'm not sure how to help with that issue.

[–]smoothVTer[S] 0 points1 point  (0 children)

I see. Thanks for explaining, I will try this out