lens0021@programming.dev to Python@programming.dev · 11 days agoRelease 0.0.1-alpha.22 · astral-sh/tygithub.comexternal-linkmessage-square13fedilinkarrow-up120arrow-down10
arrow-up120arrow-down1external-linkRelease 0.0.1-alpha.22 · astral-sh/tygithub.comlens0021@programming.dev to Python@programming.dev · 11 days agomessage-square13fedilink
minus-squarelogging_strict@programming.devlinkfedilinkarrow-up1arrow-down3·edit-211 days agoMy 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
minus-squarefruitcantfly@programming.devlinkfedilinkarrow-up3·edit-210 days agoAstral 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
minus-squarelogging_strict@programming.devlinkfedilinkarrow-up1·8 days agoThanks 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.
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
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
tyis a Rust project, and follows the standards for versioning in that language: https://doc.rust-lang.org/cargo/reference/manifest.html#the-version-fieldThanks for the link to Cargo’s versioning docs.
In Python,
packagingis authoritative. Past that version str thrupackagingand 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.