Timothée Mazzucotelli :python:

Open-source developer. Lots of Python, more and more Rust. Working on Zensical (npub1yxz…xvst)!

github: https://github.com/pawamoy
blog: https://pawamoy.github.io/
atmosphere: https://mu.social/profile/pawamoy.fr
matrix: https://matrix.to/#/@pawamoy:matrix.org

Last Notes

2025-09-03 23:14:49 UTC

- reply

thought I did but no, I'm using `humanize` to do the opposite

2025-09-03 11:52:46 UTC

- reply

https://cdn.fosstodon.org/media_attachments/files/115/140/218/661/306/358/original/fc32f2d2f66ae772.png

2025-08-07 16:14:45 UTC

I find it cumbersome to type `help(`, then a symbol name, then `)` and enter to see help for this symbol, in a #Python interpreter.
So I added this to my `~/.pythonrc` file:
```python
import builtins
class _Help:
def __call__(self, o):
return builtins.help(o)
def __truediv__(self, o):
return builtins.help(o)
def __rtruediv__(self, o):
return builtins.help(o)
help = _Help()
```
...which lets me type `name / help` or `help / name` 😄

2025-01-20 15:43:53 UTC

- reply

Yes! I mainly offer Matrix channels for my projects. The big ones sometimes get a Discord server too (well, I only have one big project 😂). Avoiding vendor lock-in is a very important point to me.
Worth noting: my experience with both Matrix and Discord is terrible. I wish chat apps would have "infinite" nesting of threads like HN or Reddit. I prefer no threads over half baked ones. Not sure if just the clients are responsible or the data structures / APIs behind are too.

2024-10-23 14:49:37 UTC

- reply

sure, not arguing about the false promises of semantic versioning. Just wondering what are the impacts for local editable/non-editable installations and upgrades of the project if it doesn't get the standardized .devN and other (less standardized?) +g<commit hash> or +d<date> suffixes when building it at an untagged commit or with uncommitted changes.

2024-10-23 13:18:51 UTC

- reply

thanks!
metametameta seems like a good solution to easily update the static version, thanks for creating it!
I think I like the idea of having the version written in an `__about__.py` module (or other name), that is then picked up by the build backend. The version stays dynamic but doesn't require the Git history.
I wonder though: when building, the version won't be suffixed with .devN.etc. anymore, right? I wonder if it's a good thing or a bad thing.

2024-10-23 12:29:42 UTC

- reply

In CI that means I have to fetch all commits and all tags to satisfy uv. But people forking my projects on GitHub don't get the tags in their fork, so their own CI will fail again (with a confusing message about project name shadowing).
https://github.com/astral-sh/uv/issues/8148
I'm therefore considering switching to static versioning, auto-bumping (somehow) the version in pyproject.toml for each release.

2024-10-23 12:26:57 UTC

- reply

I've been on the dynamic side for a long time. But sometimes it's annoying to be reliant on the Git history being present to build your package with an up-to-date version (instead of a default 0.1.devN.stuff).
I'm notably experiencing an issue with #uv, which will refuse to resolve dependencies when the current project dev-depends on a library that prod-depends back on the project. Without tags, built version is 0.1.stuff, which uv considers incompatible with what the dependency requires.

2024-10-23 12:24:53 UTC

#Python devs, what do you prefer, and why?

2024-09-03 17:33:19 UTC

I just released relative-crossrefs and scoped-crossrefs for the #Python handler of #mkdocstrings 😮 (sponsors only)
https://mkdocstrings.github.io/python/usage/configuration/docstrings/#relative_crossrefs

2024-08-28 09:18:14 UTC

- reply

I think these "build-less" projects mentioned in the issue are what we commonly call "applications". For example, a Django site that is not meant to be built as a package and distributed on PyPI. It's only meant to be deployed somewhere. When you install your deps, you don't want uv to also install the project itself, since it's not supposed to be installable. Simple as that! Just my guess.

2024-08-27 08:26:01 UTC

Seeing a wave of seemingly malicious comments on #GitHub:
> to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/redacted
password: changeme
when you installing, you need to place a check in install to path and select "gcc."
...in random repos, random issues.

2024-08-15 08:52:33 UTC

Help out a FOSS friend: #PDM is getting an endless stream of questions in issues and discussions, and the sole maintainer @npub1c8f…l6r9 is getting burnt out spending his time answering those. If you know PDM and have time to spare, please consider helping with community support and documentation!
(I hope this toot is OK with you Frost, if not, let me know and I'll delete it)
#python #packaging

2024-08-12 21:23:50 UTC

- reply

Well written post, thank you for sharing. I too feel irritated when I discover that some project I'm interested in "still" uses Poetry.
I do wish all the best to Poetry though! It started really well I think (it was a revolution!), but it was crushed under the ecosystem pressure (thousands of issues, hundreds of PRs) and failed to adapt (yet?).

2024-08-08 15:20:41 UTC

Hey #Python friends, could you give me a few examples of Python packages using Numpydoc-style docstrings?