#NumPy just started publishing nightly builds for #Python 3.14 (and 3.14t) ! Time for the #scientificPython ecosystem to start testing this year’s edition !

Set PIP_EXTRA_INDEX (or UV_INDEX) to https://pypi.anaconda.org/scientific-python-nightly-wheels/simple/
With #astraluv, you might also need UV_INDEX_STRATEGY=unsafe-best-match to easily combine dependencies from multiple indexes.

Simple Index

🚀 Great news for #python developers! #dependabot now supports #uv #astraluv . Nothing stands between your codebase and almost-instant #dependencymanagement!

https://github.blog/changelog/2025-03-13-dependabot-version-updates-now-support-uv-in-general-availability/

Dependabot version updates now support uv in general availability · GitHub Changelog

Dependabot version updates now support uv in general availability

The GitHub Blog

@hbelmiro Don't tell him how they do it in #nodeJs ;)

But it's nice to see someone notices other tools than #astralUv

#python doubt:

#AstralUV
or
#pyenv + #poetry

? ⁉️❓❔

Update: #astraluv 0.5.9 solves this problem ! This means I can (almost) use uv everywhere in my workflows. The only remaining exceptions are #Python debug builds, pre-releases and versions older than 3.8, all of which I can still get through #pyenv !

Hey everyone thanks so much for all your replies! Wanted to circle wagons since I found a VERY satisfying conclusion!

They JUST added an experimental flag that makes the uv installed python into your current default by adding it to $HOME/.local/bin/python and ensuring that's in PATH. The command is:
uv python install --preview --default

Kudos to the #astraluv folks for all their amazing work!

#python peeps: I switched from pyenv to #astraluv but am confused about PATH management.

If you use uv to manage your python installs, how do you handle adding it to your PATH?

Update: I am now embracing lock files in CI in most packages I control.
I’m very used to CI being a gamble: every time I push with confidence and see CI going red, my first reflex is to suspect something changed in the environment. I'm just coming to terms with the idea that *it doesn't need to be this way*; especially in projects that already a special CI job whose sole purpose is to catch incoming incompatibilities, it makes more sense that *other* jobs just be stable.
#astraluv #Python
@hynek, maybe you’d have some key insight I'm missing here ? It seems you do use lockfiles but are also involved in libraries. Do you use the former when developing the latter ?
#astraluv #Python
The thing with #astraluv is I don't think I understand lock files, and how they’re supposed to be used/maintained. Maybe it's because I mainly develop and maintain #Python libraries and it doesn't make as much sense in that space: I need to be able to test a range of versions of my dependencies (I have little control over my users’ environment), and lockfiles tend to add artificial restrictions to these ranges, to the benefit of (maybe ?) my immediate confort but to the detriment of my users.