deepyaman opened a new issue, #7377: URL: https://github.com/apache/iceberg/issues/7377
### Feature Request / Improvement To follow up on #6620, I am using `pyiceberg` (heavily) for a library that I'm developing. Unfortunately, `pyiceberg` has very restrictive dependencies, and they are in turn determining the bounds for our dependencies (even though I have specified my bounds very loosely). This is problematic, because my users will install my library alongside others in the same environment, so it should be as compatible as possible. Currently, using a newer version of certain dependencies (e.g. say I want to use `s3fs==2023.4.0`) requires updating the bound in the library and creating a new release. This isn't very sustainable, as `pyiceberg` would need to release any time one of its dependencies adds a new version to keep up with the latest and greatest, nor is it proactive. We can mitigate this by using relatively broad ranges, especially on the upper end. There's no real risk to doing this, because consumers can always further restrict/pin dependencies (but they can't loosen restrictive bounds by libraries). There are very valid arguments against capping dependencies (see https://iscinumpy.dev/post/bound-version-constraints/ for a great post on the topic). However, even providing/relaxing the ranges would be a great start! ### Query engine None -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
