Explore >> Select a destination
|
You are here 
|
themythicalengineer.com | ||
| | | | |
daniel-m.github.io
|
|
| | | | | Generalist Developer, an enthusiastic physicist that spends most of its days telling computers how to do stuff | |
| | | | |
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. | |
| | | | |
www.softdevtube.com
|
|
| | | | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | |
| | | | |
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. | ||
