Why is `setuptools` a Kedro dependency? It gets i...
# questions
z
Why is
setuptools
a Kedro dependency? It gets ignored when I piptools compile a
<http://requirements.in|requirements.in>
that contains kedro because setuptools is “considered to be unsafe in a requirements file”
d
it’s to enable the
kedro package
command
and the micro-packaging workflow
z
Is it the same/similar with
pip-tools
?
d
I’m not sure I’m following, one setuptools is a dependency of Kedro as a library. It’s your choice if you include it in your project and respective compiled requirements.
z
Sorry I meant whether
pip-tools
is also a dependency of Kedro for the same reason (to enable kedro package)
d
oh no
that’s for a soon to be deprecated
kedro build-reqs
command
👍 1
in 0.19.x there will just be docs for this
z
Okay thanks. I don’t think there is a clear choice to exclude setuptools when I install kedro though. If I
pip install kedro
, it will always try to install/update setuptools unless the requirement is already satisfied. Would be great to have it separated from the core dependencies and become something like
kedro[package]
. It can be a surprise to have things like
wheel
,
setuptools
or
pip
updated when a package is installed.
d
I think there is a good argument for this, amazingly it’s never been raised
Do you want to raise an issue?
z
Yes I will. Thanks for the discussion 😄
🙌🏼 1
j
hi! @Zirui Xu did you end up opening an issue? otherwise I can do it 😊
z
Thanks for the reminder @Juan Luis. Raised one here https://github.com/kedro-org/kedro/issues/2350
j
Thanks! Duly noted
👍 1