this post was submitted on 10 Oct 2025
23 points (100.0% liked)

Python

7565 readers
4 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
23
Release 0.0.1-alpha.22 · astral-sh/ty (github.com)
submitted 1 month ago by lens0021@programming.dev to c/python@programming.dev
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] logging_strict@programming.dev -2 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

My point is to wait for an actual release, a call to action, or an article about the project. Release notes on a dev pre-release is odd.

Not discouraging you from posting. You are very welcome to post here. And btw thanks for responding.

This is the semantic versioning spec, but it'll give you nightmares.

Here are examples with explanation for each versioning component. Much easier on the eyes

gl

[–] fruitcantfly@programming.dev 3 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Astral clearly are using semantic versioning, as should be obvious if you read the spec you linked.

In fact, one of the examples listed in that spec is 1.0.0-alpha.1.

ETA: It should also be noted that ty is a Rust project, and follows the standards for versioning in that language: https://doc.rust-lang.org/cargo/reference/manifest.html#the-version-field

[–] logging_strict@programming.dev 1 points 3 weeks ago

Thanks for the link to Cargo's versioning docs.

In Python, packaging is authoritative. Past that version str thru packaging and it was modified.

Honestly misunderstood, thinking there was 22 alpha releases.

Am still misreading it. The alpha and dev portions are not distinctive enough to be clear. Didn't even see in the Cargo dev portion mentioned.

Obviously publishing dev releases is not allowed, but in git dev commits are a thing.