sfu-db / dataprep

Open-source low code data preparation library in python. Collect, clean and visualization your data in python with a few lines of code.
http://dataprep.ai
MIT License
1.97k stars 201 forks source link

Latest dataprep versions seem to give incompatible requirements to pip-compile #955

Open MaxPowerWasTaken opened 1 year ago

MaxPowerWasTaken commented 1 year ago

Hello, love the dataprep package, thanks for creating it!

I used dataprep in a jupyter notebook, installing via !pip compile dataprep recently and it installed smoothly.

Now I'm tidying up some of that work and am using a venv, but pip-compile keeps crashing and I seem to have isolated dataprep as the cause. A minimal reproducible example below:

Given a test_requirements.in file which contains only a single line of dataprep Running pip-compile test_requirements.in --verbose --output-file test_requirements.txt yields the following error:

Could not find a version that matches executing<0.9.0,>=0.8.3,>=1.2.0 (from varname==0.8.3->dataprep==0.4.5->-r test_requirements.in (line 1))
Tried: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.5.0, 0.5.2, 0.5.3, 0.5.3, 0.5.4, 0.5.4, 0.6.0, 0.6.0, 0.7.0, 0.7.0, 0.8.0, 0.8.0, 0.8.1, 0.8.1, 0.8.2, 0.8.2, 0.8.3, 0.8.3, 0.9.0, 0.9.0, 0.9.1, 0.9.1, 0.10.0, 0.10.0, 1.0.0, 1.0.0, 1.1.0, 1.1.0, 1.1.1, 1.1.1, 1.2.0, 1.2.0
There are incompatible versions in the resolved dependencies:
  executing<0.9.0,>=0.8.3 (from varname==0.8.3->dataprep==0.4.5->-r test_requirements.in (line 1))
  executing>=1.2.0 (from stack-data==0.6.2->ipython==8.8.0->ipywidgets==7.7.2->dataprep==0.4.5->-r test_requirements.in (line 1))

I'm not sure if this is a dataprep problem or a pip-compile problem, or a problem with one of dataprep's dependencies (or some other thing I haven't thought of), but wanted to post here in case it's helpful. I also posted a question on stack overflow at: https://stackoverflow.com/q/75090614/1870832

RADutchie commented 1 year ago

I'm also having the same problem. Any suggestions on a fix or workaround on this? stack_data now requires executing>=1.2.0