|
You are here |
tomaugspurger.net | ||
| | | | |
stribny.name
|
|
| | | | | ||
| | | | |
bylr.info
|
|
| | | | | Often, technical documentations include lists or other snippets of text that are strongly related to some of the projects code. vpypes documentation is no exception to this. For instance, the Built-in symbols section lists the units available to expressions: These units are related to the following piece of code: # vpype/utils.py UNITS = { "px": 1.0, "in": 96.0, "inch": 96.0, "ft": 12.0 * 96.0, "yd": 36.0 * 96.0, "mi": 1760.0 * 36. | |
| | | | |
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. | |
| | | | |
stribny.name
|
|
| | | [AI summary] This article provides a modern Python project template using Poetry for dependency management, along with tools for testing, code formatting, static analysis, and version control. | ||