@Pedroski55 you should make a your own Thread.
As the topic is kind of similar i don't move Thread for now.
What you doing is confusing,you make folder
Do you make this folder with mkdir or with venv?
When you use
I would do it like this,i always end
Or navigate to where you have
no matter what folder you are in it will use Python from this environment(that has Pillow installed).
Example:
As the topic is kind of similar i don't move Thread for now.
What you doing is confusing,you make folder
/home/pedro/images
Do you make this folder with mkdir or with venv?
When you use
venv
its making a new folder.I would do it like this,i always end
_env
so know that folder is used for virtual environment.# Make G:\div_code λ python -m venv image_env # cd in G:\div_code λ cd image_env\ # Activate # Linux <source /bin/activate> G:\div_code\image_env λ G:\div_code\image_env\Scripts\activate # install Pillow (image_env) G:\div_code\image_env λ pip install pillow Collecting pillow Downloading Pillow-9.2.0-cp310-cp310-win_amd64.whl (3.3 MB) ---------------------------------------- 3.3/3.3 MB 6.2 MB/s eta 0:00:00 Installing collected packages: pillow Successfully installed pillow-9.2.0 (image_env) G:\div_code\image_envAt this point can make
images
folder in image_env
folder.Or navigate to where you have
images
as long as (image_env)
is activate,no matter what folder you are in it will use Python from this environment(that has Pillow installed).
Example:
(image_env) C:\Users\Tom λ cd C:\foo\images # In different folder as activate (image_env) will use python executable from this environment (image_env) C:\foo\images # Test what python interpreter used,see it point to image_env λ python -c "import sys; print(sys.executable)" G:\div_code\image_env\Scripts\python.exe