nltk installs but cannot be imported [SOLVED]

[sheepog]

I installed nltk in my virtual environment, but importing does not work. Please advise.

Output:
(venv) mel@Raccoonland:~/Documents/Foreign Countries and Moving Abroad/Portugal/Language/O Organista$ [b]pip install nltk[/b]
Collecting nltk
  Downloading nltk-3.9.1-py3-none-any.whl.metadata (2.9 kB)
Collecting click (from nltk)
  Downloading click-8.2.1-py3-none-any.whl.metadata (2.5 kB)
Collecting joblib (from nltk)
  Using cached joblib-1.5.1-py3-none-any.whl.metadata (5.6 kB)
Collecting regex>=2021.8.3 (from nltk)
  Using cached regex-2024.11.6-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (40 kB)
Collecting tqdm (from nltk)
  Using cached tqdm-4.67.1-py3-none-any.whl.metadata (57 kB)
Downloading nltk-3.9.1-py3-none-any.whl (1.5 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.5/1.5 MB 5.8 MB/s eta 0:00:00
Using cached regex-2024.11.6-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (796 kB)
Downloading click-8.2.1-py3-none-any.whl (102 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 102.2/102.2 kB 10.8 MB/s eta 0:00:00
Using cached joblib-1.5.1-py3-none-any.whl (307 kB)
Using cached tqdm-4.67.1-py3-none-any.whl (78 kB)
Installing collected packages: tqdm, regex, joblib, click, nltk
[b]Successfully installed [/b]click-8.2.1 joblib-1.5.1 [b]nltk-3.9.1[/b] regex-2024.11.6 tqdm-4.67.1
(venv) mel@Raccoonland:~/Documents/Foreign Countries and Moving Abroad/Portugal/Language/O Organista$ ./add_EnglishPortuguese.sh 
Traceback (most recent call last):
  File "/home/mel/Documents/Foreign Countries and Moving Abroad/Portugal/Language/O Organista/./list_sentences.py", line 3, in <module>
    import nltk, sys
ModuleNotFoundError: No module named 'nltk'
Traceback (most recent call last):
  File "/home/mel/Documents/Foreign Countries and Moving Abroad/Portugal/Language/O Organista/./list_sentences.py", line 3, in <module>
    import nltk, sys
ModuleNotFoundError: [b]No module named 'nltk'[/b]

[sheepog]

This was not working because the python file started with

#!/bin/python3

which doesn't work in the virtual environment.

[Plyth]

Thanks for pointing that out, sheepog. I ran into a similar issue before, the shebang line can cause some confusion with virtual environments. Changing it to #!/usr/bin/env python3 usually helps make sure the script uses the Python from the active venv. Glad you got it sorted!

[Larz60+]

I'm pretty sure that if you eliminate the shebang entirely, when using a virtual environment, then the proper python will be used.
Correct me if I am wrong.