Python Forum
Not able to set up a virtual environment with venv
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Not able to set up a virtual environment with venv
#8
(Oct-27-2020, 11:08 AM)mohanp06 Wrote: This is what I did but I was getting error, so this post.
Have you build Python: 3.7.4 yourself?
A common mistake is do not include all build tool.
As mention bye bowlofred python3.7-venv.
Try:
apt-get update
apt-get install python3.7-dev python3.7-venv
I use pyenv as i have tutorial about here pyenv Simple Python Version Management.
Look at point .1 there you see all build needed before build yourself or use pyenv to do this.
Reply


Messages In This Thread
RE: Not able to set up a virtual environment with venv - by snippsat - Oct-27-2020, 12:18 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Help with creating folder and "virtual environment" AudunNilsen 1 219 Mar-21-2024, 04:41 AM
Last Post: deanhystad
  my venv is not loading njoki 1 230 Mar-20-2024, 10:41 AM
Last Post: snippsat
  Installing python packages in a virtual environment Led_Zeppelin 1 758 Aug-15-2023, 08:18 PM
Last Post: deanhystad
  Understanding venv; How do I ensure my python script uses the environment every time? Calab 1 2,257 May-10-2023, 02:13 PM
Last Post: Calab
  Problem with virtual environment standenman 2 1,005 Feb-23-2023, 07:09 PM
Last Post: standenman
  Python venv and PIP version issue JanOlvegg 2 1,252 Feb-22-2023, 02:22 AM
Last Post: JanOlvegg
Question Virtual Environment (using VS Code) Ashcora 4 13,649 Feb-15-2023, 07:17 PM
Last Post: snippsat
  Visual Studio Code venv ibm_db error mesi1000 7 2,784 Nov-13-2022, 12:36 AM
Last Post: snippsat
  How do I link the virtual environment of that project to the 3.9.2 version of python? Bryant11 1 1,369 Feb-26-2022, 11:15 AM
Last Post: Larz60+
  Project structure with a virtual environment gdbengo 1 1,429 Jan-26-2022, 03:22 PM
Last Post: snippsat

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020