-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perhaps we should ditch the alpha thing and go back to 0.* releases #2245
Comments
Yeah... I'll admit I didn't quite think through the result of having the alpha releases semi-hidden from people, especially now that 0.20.0 is wildly out of date. I originally suggested alpha releases thinking that 0.20.0 would be a "semi-stable" version that people could still use, since with our current push every release is a major breaking change... but I agree that the alphas seem to instead just be causing even more confusion (and really, nobody should be using 0.20.0 anymore). In hindsight breaking changes aren't really a huge issue if one just specifies a fixed version in their dependencies; we just let people know that Hy is not yet stable, ye be warned. |
Why? |
It's missing the many improvements to Hy that have happened since, particularly, support for newer versions of Python. |
It's also significantly less simple to use now that much of the useful functionality has been moved to libraries. Honestly, I have Hy 0.20 code serving hundreds of people daily out there, and I'm not about to learn an increasingly different language also called "Hy". My brain can't hack that. That's the risk one gets as an early adopter I guess. I was hoping the plan to have a version 1.0 that was like Python 3 and left 0.20 alone was workable. (There are paper cuts; if you have a stable 0.35 version it's harder to steer people to the 0.20 docs). Anyway, I can't think of a way of making my opinions and vested interests matter. Godspeed. |
Using
That's still the plan. Hy 0.20.0 isn't going anywhere. It's just not recommended. We're not the programming police. |
There was a survey at some point of the most-often pinned versions of Hy. I feel like because of the alpha 1.0 plan there's a big cut-off at 0.20. Can we have some kind of "What's new since 0.xx" thing? It would ease migration pain if the need to update existing code becomes overwhelming. |
Yeah, that's one reason the alpha thing was a mistake.
|
It's confusing to have two version lines. And no matter how much we beg and plead for people to say
pip install --pre
, some people are going to do it without the--pre
because it's the obvious thing to do, which doesn't work (e.g., vlasovskikh/funcparserlib#65 (comment)) and will continue to break worse over time (particularly because of changes between major versions of Python). There is no reason to suggest that people should be installing 0.20.0.The text was updated successfully, but these errors were encountered: