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
Consider relaxing the upper bounds on some requirements #2485
Labels
enhancement
New feature or request
Milestone
Comments
Thanks a lot for these suggestions, @sscherfke! Let me share my thoughts:
Would you like to create a pull request relaxing the mentioned (and maybe more) dependencies? 🙂 |
Thanks for the quick reply :-) I’ll open a PR in the next few days. |
sscherfke
added a commit
to sscherfke/nicegui
that referenced
this issue
Feb 3, 2024
- The "^" specifier is often too restrictive for 0.* versions so I would not recommend to use it in these cases: https://python-poetry.org/docs/dependency-specification/ - Markdown2: The issue from 2.4.11 was fixed in 2.4.12: - zauberzeug#2154 - trentm/python-markdown2#546 - https://github.com/trentm/python-markdown2/blob/master/CHANGES.md#python-markdown2-2412 - Watchfiles: Doesn't look like v1 will introduce breaking changes: samuelcolvin/watchfiles#186 - python-multipart: "^0.06" is "==0.0.6" which is too strict and at this stage, any release can potentially add breaking changes - aiofiles: Uses CalVer and 24.0.0 is as likely to introduce breaking changes as 23.2.0. - httpx: It does not look like 1.0.0 will introduce breaking changes (if you already fixed any deprecation warnings). Testing against the 1.0.0beata0 is advisable, though. encode/httpx#3069 - ifaddr: Development is rather slow, package looks quite stable. I don't think that a 0.3.0 will add breaking changes and a 1.0 is not in sight. - pytest-asyncio: Restriction to >=0.19,<0.20 seems unwanted and updates are needed for recent pytest versions - pytest: Has there been a reason to not support pytest7? pytest8 currently breaks some plugins, but this should be fixed soon. Fixes: zauberzeug#2485
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Many requirements of nicegui have upper bounds. I understand the principal need for this, but upper bounds can make repackaging harder or using nicegui in larger environments tricky.
For example, setuptools is pinned to <50, but Nicegui works just fine with recent versions. Aiofiles is pinned to < 24.0.0 but this makes not sense with cal-ver, because the first release of this year is not necessarily more likely to introduce breaking changes than the last release of 23.*.
And, out of curiosity, why did you re-add aiohttp as requirement? It seems nowhere to be used. The links to the "dependabot issues" in the corresponding commit don't work.
The text was updated successfully, but these errors were encountered: