discussion re supported python versions, switching to uv.

[dougransom]

rom: Roberto Martínez <robertomartinezp@gmail.com>
Sent: February 9, 2025 6:58 AM
To: Doug Ransom <doug@ransom.vip>
Subject: Re: experta

 

I am not familiar with uv yet, but I am very interested in learning it, so go ahead 😁

I also prefer to maintain only a handful of reasonable modern python versions. But if we do that it should be very clearly stated in the README.  Mainly to avoid any confusion about bug fixes being backported.

I am ok with the release number strategy.

In the future I prefer if we stick to github for this kind of conversations. This way it also serves as a loose documentation for the users.

Cheers,

Roberto 

On Sun, Feb 9, 2025, 15:52 Doug Ransom <doug@ransom.vip> wrote:

Roberto,

Are you at all familiar with UV?  I'd like to update the pyproject.toml to use uv as the project tool.  

I'd also like to remove support for python versions < 3.13.  If someone needs an older version support they can install an older version of experta.  Mainly I don't want to be restricted or restrict anyone else from using the newest features of Python (not that I have any bold ideas to do so).

Note in the release number I bumped the release number to a prerelease, the idea that keeps increasing until there is a reason to publish a release.  So we never get confusion with a version number in a dev environment and what is on pypi.

uv - Astraluv. An extremely fast Python package and project manager, written in Rust. Installing Trio's dependencies with a warm cache.. Highlights. 🚀 A single tool to replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.; ⚡️ 10-100x faster than pip.; 🗂️ Provides comprehensive project management, with a universal lockfile. ...docs.astral.sh --

rom: Roberto Martínez <[robertomartinezp@gmail.com](mailto:robertomartinezp@gmail.com)> Sent: February 9, 2025 6:58 AM To: Doug Ransom Subject: Re: experta

I am not familiar with uv yet, but I am very interested in learning it, so go ahead 😁

I also prefer to maintain only a handful of reasonable modern python versions. But if we do that it should be very clearly stated in the README. Mainly to avoid any confusion about bug fixes being backported.

I am ok with the release number strategy.

In the future I prefer if we stick to github for this kind of conversations. This way it also serves as a loose documentation for the users.

Cheers,
Roberto

On Sun, Feb 9, 2025, 15:52 Doug Ransom doug@ransom.vip wrote:
Roberto,

Are you at all familiar with UV? I'd like to update the pyproject.toml to use uv as the project tool.

I'd also like to remove support for python versions < 3.13. If someone needs an older version support they can install an older version of experta. Mainly I don't want to be restricted or restrict anyone else from using the newest features of Python (not that I have any bold ideas to do so).

Note in the release number I bumped the release number to a prerelease, the idea that keeps increasing until there is a reason to publish a release. So we never get confusion with a version number in a dev environment and what is on pypi.

uv - Astral
uv. An extremely fast Python package and project manager, written in Rust. Installing Trio's dependencies with a warm cache.. Highlights. 🚀 A single tool to replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv, and more.; ⚡️ 10-100x faster than pip.; 🗂️ Provides comprehensive project management, with a universal lockfile. ...
docs.astral.sh

[dougransom]

@nilp0inter For versions, do we want to support at least the latest version of PyPy? They are always a few releases behind Cpython?

[nilp0inter]

Sounds reasonable. Always 3.X, of course.