/explore
|
You are here 
|
nikgrozev.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. | |
| | | | |
janakiev.com
|
|
| | | | | One of the crucial tasks when working with data is to load data properly. The common way the data is formated is CSV, which comes in different flavors and varying difficulties to parse. This article shows three common approaches in Python. | |
| | | | |
utf9k.net
|
|
| | | | | A step by step walkthrough on how I cleaned up some data as part of a side project | |
| | | | |
ljvmiranda.micro.blog
|
|
| | | I'm now a uv convert. I haven't really updated my Python tooling and workflow for the past two years. In fact, I've been using the same workflow ever since I started working: python -m venv venv source /venv/bin/activate # While in venv pip install -r requirements.txt But there's a lot of limitations in this workflow. For example, I'm limited by the Python version installed in my machine or it's hard to just install ad-hoc dependencies for my one-off scripts. | ||
