/explore
|
You are here |
snarky.ca | ||
| | | | |
jcbsv.net
[AI summary] A post discusses the lack of a standard build backend in Python packaging despite other development tools having clear preferences. |
|
| | | | | ||
| | | | |
adamj.eu
Most projects I work on use Python, good ol' Pip, and pip-tools. Below is a pattern I've used to speed up the GitHub Actions workflow runs on several such projects. On larger projects with many dependencies, it can save tens of seconds per run. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
avilpage.com
How to build and distribute a Python C extension module using wheels |
|
| | | |||