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

Python

7580 readers
16 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
jnovinger@programming.dev
erlingur@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 -1 points 1 month ago* (last edited 1 month ago) (9 children)

Really don't understand why post about a dev pre-release? It's confusing, what is the goal trying to achieve with this post?

And why not using semantic versioning?

>>> from packaging.version import Version
>>> v = Version("0.0.1-alpha.22")
>>> str(v)
'0.0.1a22'
>>>

0.0.1alpha22 or 0.0.1a22 although that looks alot like pre-release dev level fixes. In which case, 0.0.1a0-dev22

There is no project ever that had 22 alpha releases. That's nuts. Your alpha testers must be really overworked.

Fire the six year old in charge versioning decisions ;-)

Your welcome. Your future user base can thank me later for putting a stop to that atrocity posing as versioning

epoch is used to transition from random nonsense versioning to semantic versioning.

There is no shame/stigma for admitting a mistake and correcting it. Eventhough that epoch will now stick around with the project forever.

[–] lens0021@programming.dev 3 points 1 month ago* (last edited 1 month ago) (8 children)

I posted because I was happy to see some software in growing up. If you are not comfortable, I will not post this kind again.

[–] logging_strict@programming.dev -2 points 1 month ago* (last edited 1 month ago) (2 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 1 month ago* (last edited 1 month 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 1 month 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.

load more comments (5 replies)
load more comments (5 replies)