Explore >> Select a destination
|
You are here 
|
janakiev.com | ||
| | | | |
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.rasulkireev.com
|
|
| | | | | If you are using a virtual environment, you might have ome issues with Jupyter Notebook. In this post we go through proper Jupyter Setup with venv. | |
| | | | |
jaketae.github.io
|
|
| | | | | As a novice who just started learning Python just three months ago, I was clueless about what virtual environments were. All I knew was that Anaconda was purportedly a good way to download and use Python, in particular because it came with many scientific packages pre-installed. I faintly remember reading somewhere that Anaconda came with conda, a package manager, but I didn't really dig much into it because I was busy learning the Python language to begin with. I wasn't interested in the complicated details-I just wanted to learn how to use this language to start building and graphing and calculating. | |
| | | | |
dbanuggets.com
|
|
| | | Thanks to Kevin Chant for inviting us to write this month's T-SQL Tuesday. This month is special, as Kevin mentioned due to the Festive Tech Calendar, which I have been speaking about for a couple of years now. Every day of the December month, a new recording or a blog post will be released for... | ||
