Explore >> Select a destination
|
You are here 
|
www.simplygeek.co.uk | ||
| | | | |
janakiev.com
|
|
| | | | | Python's built-in venv module makes it easy to create virtual environments for your Python projects. Virtual environments are isolated spaces where your Python packages and their dependencies live. This means that each project can have its own dependencies, regardless of what other projects are doing. | |
| | | | |
www.mackorone.com
|
|
| | | | | ||
| | | | |
128bit.io
|
|
| | | | | Over the past couple months, I've been working on fine tuning my Python skills, part of this has been taking tutorials online along with building some applications. One of the things I've been wanting to document, mostly for myself, is setting up a new environment for developing with Python. I'm using macOS Sierra right now, it seems that most operating systems still comes with version 2.x of Python. It's always a good idea to be able to control the version of Python you are using. | |
| | | | |
vickiboykis.com
|
|
| | | When I'm working with Jupyter notebooks, I often want to work with them from within a virtual environment. The general best practice is that you should always use either virtual environments or Docker containers for working with Python, for reasons outlined in this post, or you're gonna have a bad time. I know I have. The workflow is a little long, so I thought I'd document it for future me here. | ||
