Yicong-Huang commented on PR #4199: URL: https://github.com/apache/texera/pull/4199#issuecomment-4883336541
> > @aicam is this approach the best in a long term? I think fixing the version is a concern > > I think we should set version for all libraries. Just to clarify, pinning a library version in `requirements.txt` is generally not ideal for a source/library project. We usually want to specify a compatible version range instead of forcing one exact version. Pinning with `==` makes sense for a binary release, Docker image, executable package, or any deployment artifact where we need a reproducible runtime environment. But for a library/source project, strict pins can unnecessarily constrain downstream users and create dependency conflicts with other packages. For example, instead of: ```txt foo==1.2.3 ``` we usually prefer something like: ```txt foo>=1.2,<2 ``` This says the project is compatible with a range of versions while still protecting against known breaking changes. We will enforce version lock in LICENSE-binary files for release purposes. -- 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]
