Elena Mironova
05/09/2023, 3:43 PMkedro pull micropkg
and sdist here. Would anyone know how to best deal with the multiple egg.info error in the screenshot?
Context: with kedro==0.18.3
on a mac I used python -m build --sdist path/to/package
to create tar.gz inside our Git repo (i know alternative is available to create sdist through kedro micropkg package
, but i can't do it from inside a kedro project). I see the archive, but when doing kedro pull micropkg
(from kedro project root), the following error comes up. This may or may not be related to the existing issue .Juan Luis
05/09/2023, 3:49 PMfind . -name "*.egg-info
and tell us what you see? I see you're erasing the name of the wheel for confidentiality purposes. maybe if you can't share it, at least it will give you an indication of what's happening.egg-info
directory corresponding to the micropipeline you're trying to pull, and another one corresponding to something else. but could be another issueElena Mironova
05/09/2023, 3:55 PM.tar
), it only provides one entry for the .egg-info
directory of the pipelineJuan Luis
05/09/2023, 4:32 PMkedro micropkg pull pipeline-name.tar.gz --verbose
, right? in principle, Kedro is checking that the file exists:
https://github.com/kedro-org/kedro/blob/ae2022840147d0c46a985fb3061beac452b2ab59/kedro/framework/cli/micropkg.py#L320
so, I think when you specify a full filename ending in .tar.gz
, it has to be the path of an actual file on disk. otherwise, it tries to pip download
it, most likely it doesn't find it, and so the errors appears. could you make sure that your pipeline-name.tar.gz
exists?Elena Mironova
05/10/2023, 8:22 AMJuan Luis
05/10/2023, 9:12 AMls pipeline-name.tar.gz
, and provided there are no leftover .egg-info
directories, does kedro micropkg pull pipeline-name.tar.gz --verbose
fail? if so, more debugging will be needed, and maybe we could setup a meeting to discuss that live