/explore
|
You are here 
|
www.rasulkireev.com | ||
| | | | |
geoff.tuxpup.com
|
|
| | | | | For the first time in quite a while, I caught the urge to publish a package to pypi today. The happy path for publishing a pure python package felt less obvious than I think it should've. Here's what I did. The package in question is published here, and the source code is available on sr.ht. It's the beginning of a youth baseball season. One of the things I do is help our commissioners get all the information our families need to the right places where families will find it. | |
| | | | |
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. | |
| | | | |
vxlabs.com
|
|
| | | | | The new Python package and project manager uv is in fact amazing. I say that, because it's really fast, but more importantly because this single tool does a whole lot, really fast: Installing Python binaries, installing and running packages in self-contained environments like pipx, managing virtual environments. However, I've been avoiding it so far due to one flaw: uv defaults to installing its virtual environment and all dependencies into the .venv sub-directory of your project, almost exactly like the... | |
| | | | |
benrutter.codeberg.page
|
|
| | | [AI summary] A developer from southern England writes about software development and open source projects with a blog post featuring dithered forest imagery. | ||
