Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

60%
+1 −0
Q&A Why does `venv` seem to be missing or broken? Isn't it part of the standard library?

venv is indeed part of the standard library. However, some Linux distros modify Python to exclude some parts for various reasons, and venv might be among them. On Debian-based Linux distros you ...

posted 6mo ago by Karl Knechtel‭

Answer
#1: Initial revision by user avatar Karl Knechtel‭ · 2024-06-18T10:34:28Z (6 months ago)
`venv` is indeed part of the standard library. However, some Linux distros modify Python to exclude some parts for various reasons, and `venv` might be among them.

<section class="notice is-success">

On Debian-based Linux distros you can generally install `venv` for the system Python with something like `apt install python3.x-venv` (replace `x` with the minor version number for your system Python). **This is generally safe and recommended for development**. Of course, this approach limits you to environments that use the same *version* of Python.
</section>

Alternatively, you could install (or just build) a separate copy of the same version (or whichever other version you need) of Python yourself, keeping it in a location that won't interfere with the system, and use its `venv` to create virtual environments. This is at least as risky/error-prone, and completely unnecessary for most users. Or you can use an environment management tool such as [`pyenv`](https://github.com/pyenv/pyenv), if that doesn't seem like overkill.