-
Notifications
You must be signed in to change notification settings - Fork 48
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
Please allow Textual version installed to roll forwards and not be pinned to 0.43
#94
Comments
This stems from a period when Textual was going through quite a few breaking changes, and needing to remember to reevaluate Frogmouth in the light of those changes wasn't a priority (and was far more extra effort than bumping the pin on occasion). I suspect we're more or less at a point where we can relax this. |
Also relax things a little now that Textual has calmed down somewhat in terms of breaking changes. (see #94).
From the next release it'll now be going out with just a lower-bound for Textual. |
See #98 and Textualize/textual#4360 for more context. For the moment this commit will undo the change made in respect to the request made in #94, but we'll have to remember to unpin again as soon as the Textual issue is resolved.
Just to update that I've reverted this change, for the moment, but will go back to this approach again soon. See #99 for context. |
Current behaviour
Textual is pinned with a poetry caret requirement in
pyproject.toml
:The latest version of which is https://pypi.org/project/textual/0.43.2/ released 29th November 2023.
This is annoying / jarring because:
rich
https://github.com/Textualize/textual/blob/main/pyproject.toml#L45Expected behaviour
Soften the requirement on Textual so clients / users can get the latest version of Textual when they install Frogmouth - maybe something like:
Or
The text was updated successfully, but these errors were encountered: