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

Kedro forces pip-tools~=6.5 and fails with new pip==23.2.0 & pip-tools==7.0.0 #2807

Closed
FloridaDataGuy opened this issue Jul 17, 2023 · 4 comments

Comments

@FloridaDataGuy
Copy link

Description

Kedro forces pip-tools~=6.5 and fails with new pip==23.2.0 & pip-tools==7.0.0.
As I undestand pip-tools are fixed in dependencies/requriements.txt in Kedro package source.

Context

Trying to use the latest combination of pip==23.2.0 and pip-tools==7.0.0. Can not instantiate virtual environment if there is a requrement kedro==0.18.11.

Steps to Reproduce

  1. enter into requrements.in pip-tools==7.0.0, kedro==0.18.11

  2. install pip==23.2.0

  3. run pip-compile

Expected Result

Receive compiled requirements.txt.

Actual Result

pip-compile fails with the following error:

ERROR: Cannot install kedro[pandas]==0.18.11 and pip-tools==7.0.0 because these package versions have conflicting dependencies.

Your Environment

  • Kedro version used (pip show kedro or kedro -V): 0.18.11
  • Python version used (python -V): 3.10.12
  • Operating system and version: Debian 11 (Bullseye)
@astrojuanlu
Copy link
Member

Thanks for reporting @FloridaDataGuy , we'll have a look at this soon.

@noklam
Copy link
Contributor

noklam commented Jul 31, 2023

@astrojuanlu Anything pip-tools actually break in 7.0.0? Python 3.7 support is dropped from 7.0.0, is it possible to keep test running < 7.0.0 but allow people install with newer version?

@astrojuanlu
Copy link
Member

IIRC this was fixed in #2843, see

"pip-tools>=6.5,<8",

@noklam
Copy link
Contributor

noklam commented Jul 31, 2023

Ah thanks, I thought we only update test requirements. I will close this issue then.

@FloridaDataGuy this should be fixed and will be available in next release (coming this week)

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

No branches or pull requests

3 participants