Skip to content
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

[0.14.17] Loosen requirements with bounds #278

Merged
merged 1 commit into from
Jun 8, 2024

Conversation

malcolmgreaves
Copy link
Contributor

@malcolmgreaves malcolmgreaves commented Jun 4, 2024

Loosens the requirements by establishing the current == as lower bounds (>=) and uses the next major version update as an upper bound (<).

Bumps patch version to 0.4.17 too.

@malcolmgreaves
Copy link
Contributor Author

malcolmgreaves commented Jun 4, 2024

Hello! 👋

This PR enables downstream users to have greater compatibility with TDC's dependencies. Currently, it is difficult to use TDC as a dependency since its dependencies are pinned to specific versions. This PR allows for more flexibility by enabling any non breaking change version of a dependency to be used. This PR is motivated by a dependency version conflict that I'm encountering in my own project.

Since RDKit doesn't use Semantic Versioning 2.0, I manually looked through the release notes to determine that version 2024.3.1 is the first release after 2023.9.5 that introduces breaking changes.

@malcolmgreaves malcolmgreaves force-pushed the mg/loosen_requirements branch 2 times, most recently from 07f3b9a to f660be0 Compare June 4, 2024 19:01
@malcolmgreaves malcolmgreaves changed the title Loosen requirements with bounds [0.14.17] Loosen requirements with bounds Jun 4, 2024
@malcolmgreaves
Copy link
Contributor Author

@amva13 Not sure if you'd like me to include the version bump in this PR or not. Happy to make any changes :)

Loosens the requirements by establishing the current `==` as lower bounds (`>=`) and uses the next major version update as an upper bound (`<`).

Bumps patch version to 0.4.17
@malcolmgreaves malcolmgreaves force-pushed the mg/loosen_requirements branch from f660be0 to c4d6795 Compare June 4, 2024 19:11
@amva13 amva13 self-assigned this Jun 7, 2024
@amva13 amva13 self-requested a review June 7, 2024 17:17
@amva13
Copy link
Member

amva13 commented Jun 7, 2024

@malcolmgreaves, sorry for the delay. will review it in the next few days. TDC is submitting a paper.

Skimming it looks reasonable

@malcolmgreaves
Copy link
Contributor Author

malcolmgreaves commented Jun 8, 2024 via email

@amva13 amva13 merged commit 42bab5e into mims-harvard:main Jun 8, 2024
3 checks passed
@amva13
Copy link
Member

amva13 commented Jun 8, 2024

hi @malcolmgreaves this is merged and new version released. Let me know if you still face any issues!

https://pypi.org/project/PyTDC/0.4.17/

@malcolmgreaves
Copy link
Contributor Author

Thank you very much! 👏 I'll try it out today!

@ghost
Copy link

ghost commented Aug 17, 2024

As a corollary to this MR, would bit be possible to completely relax the version requirement for pandas? I don't think anything in this repo requires pandas>=2.1.4 right?

Pandas has had rapid growth recently and our production containers aren't keeping up... we're living in pandas==1.5.3 (sadly on the cusp of 2.0.0) right now and depend on PyTDC.

Testing on my side with --no-deps to unblock, just an observation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants