Explore >> Select a destination
|
You are here 
|
jeroenjanssens.com | ||
| | | | |
www.ethanrosenthal.com
|
|
| | | | | I make Python packages for everything. Big projects obviously get a package, but so does every tiny analysis. Spinning up a quick jupyter notebook to check something out? Build a package first. Oh yeah, and every package gets its own virtual environment. Let's back up a little bit so that I can tell you why I do this. After that, I'll show you how I do this. Notably, my workflow is set up to make it simple to stay consistent. | |
| | | | |
nickcharlton.net
|
|
| | | | | I recently completed a project for an assignment which had a mess of dependencies. It depends upon libgit2 and pygit2, both of which are a complete pain to get working. After it blew up in my face for the third time, I realised I was being silly and should go back to using Vagrant, and along with it, the configuration management tool, Chef. | |
| | | | |
stribny.name
|
|
| | | | | ||
| | | | |
pythonspeed.com
|
|
| | | How to activate a Python virtualenv in a Dockerfile without repeating yourself-plus, you'll learn what activating a virtualenv actually does. | ||
