Juan Luis
02/23/2023, 3:45 AMkedro
CLI
2. kedro new
creates a new directory
3. cd {newdir} && python -m venv .venv
4. One needs to install Kedro inside the .venv
again
seems like this is not a problem if one uses out-of-tree environments, like conda does. Is there a way around for the other case? Something like:
1. mkdir {newdir} && cd {newdir} && python3 -m venv .venv
2. Install Kedro in the new .venv
3. (From {newdir}
) kedro new --here
Deepyaman Datta
02/23/2023, 4:03 AMkedro new
I think that's like the second workflow you put. Are you saying that doesn't work? Sorry, I didn't quite understand what worked and what didn't in your post. 😅Juan Luis
02/23/2023, 4:12 AMkedro new
, it's a chicken-and-egg problemDeepyaman Datta
02/23/2023, 5:13 AMSebastian Pehle
02/23/2023, 9:06 AMJuan Luis
02/23/2023, 9:07 AMSebastian Pehle
02/23/2023, 9:10 AMdatajoely
02/23/2023, 10:13 AMAntony Milne
02/23/2023, 12:03 PMpipx
would be the answer here I think, but we don’t hear many people ask this, I guess because it’s so common in the DS world to use conda.0.18.1
you should feel free to update kedro to 0.18.5
and there shouldn’t be any problems 🙂Juan Luis
02/24/2023, 8:30 AMpipx
and the one installed inside the .venv
). leaving a comment in the relevant issue