Release 0.0.1-alpha.22 · astral-sh/ty

a year ago by lens0021 to c/python

Release Notes Released on 2025-10-10. Bug fixes Enforce that typing_extensions must come from a stdlib search path. This fixes a panic that could occur with a confusing backtrace if the extra-path...

dallen 5 points a year ago

Really looking forward to running type checks with pre-commit. Mypy is just too slow with most code bases.

save

path: 0 19864355, hotness: undefined, score: 5, children: 1

Doccool 1 point a year ago

Same honestly. Mypy is sooo slow... Very excited for the emerging landscape with both Ty and Pyrefly

save

path: 0 19864355 19876033, hotness: undefined, score: 1, children: 0

1984 2 points a year ago

Ive tried ty in neovim and it runs circles around basedpyright. You can feel its instant. You should try it.

save

path: 0 19882243, hotness: undefined, score: 2, children: 0

logging_strict -1 points a year ago

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.

save

path: 0 19874960, hotness: undefined, score: -1, children: 9

lens0021 3 points a year ago

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.

save

path: 0 19874960 19875161, hotness: undefined, score: 3, children: 8

1984 1 point a year ago

Or you just do what you want. He is not the internet police.

save

path: 0 19874960 19875161 19882253, hotness: undefined, score: 1, children: 1

logging_strict 1 point a year ago

Until @fruitcantfly set me straight, couldn't read and understand the version str and was unaware Rust followed a different pattern than Python.

save

path: 0 19874960 19875161 19882253 19923739, hotness: undefined, score: 1, children: 0

Doccool 1 point a year ago

I recommend you ignore this guys takes, he's posted a lot of wild and controversial takes on other topics and honestly it's not like we have too much posts in this community anyway. Post if you like, up- and downvotes are meant to give and indication of what people think. Not a single person. Conversation is good even if it's on a alpha release!

save

path: 0 19874960 19875161 19876021, hotness: undefined, score: 1, children: 2

lens0021 3 points a year ago

Thank you for your kind words! Meanwhile, thanks to logging_strict, I discovered that GA and Beta milestones are set on the https://github.com/astral-sh/ty/milestones page, and the Beta milestone is 69% complete. Looking forward to ty's GA.

save

path: 0 19874960 19875161 19876021 19876158, hotness: undefined, score: 3, children: 1

logging_strict 1 point a year ago

Never even viewed Milestones before. Thanks @lens0021 for pointing them out. Link to Milestone found on both Issues and PR sections.

Don't know why been ignoring it, maybe something like,

"Milestones ewww scary. Might be dangerous better not click on it"

save

path: 0 19874960 19875161 19876021 19876158 19923412, hotness: undefined, score: 1, children: 0

logging_strict -2 points a year ago

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

save

path: 0 19874960 19875161 19875314, hotness: undefined, score: -2, children: 2

fruitcantfly 3 points a year ago

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/...

save

path: 0 19874960 19875161 19875314 19883256, hotness: undefined, score: 3, children: 1

logging_strict 1 point a year 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.

save

path: 0 19874960 19875161 19875314 19883256 19923674, hotness: undefined, score: 1, children: 0

📅 Events

🐍 Python project:

💓 Python Community:

✨ Python Ecosystem:

🌌 Fediverse

Communities

Projects

Feeds

📅 Events

🐍 Python project:

💓 Python Community:

✨ Python Ecosystem:

🌌 Fediverse

Communities

Projects

Feeds