do the latest versions of

meltano

and

singer-sdk

depend on incompatible versions of

click

? i’m trying to add

singer-sdk

to a project that already has meltano and see the error in the snippet

It's very possible, yes. I think we would certainly accept an MR on either to bring these into alignment (assuming their repsective dependencies would allow it). However, we do generally expect those to be installed in separate virtual environments.

The SDK has required click

~=8.0

for a while now (https://gitlab.com/meltano/sdk/-/commit/d7c774e454818b9fc887b86ce0a4a56edd339e35), and @aaronsteers is correct in solving this by them not being in the same venv. But yeah, we could certainly accept an MR to bump Meltano's requirement.

okay maybe i’m just approaching this wrong then. say i’ve forked an SDK built tap to debug an issue and want to install meltano so i can run the tap with meltano, do you recommend i do that in a different venv?

Yeah, I think having meltano in its own venv is always best. Pipx does this automatically (

pipx install meltano

instead of

pip install meltano

). and then if you use Pipx,

meltano

is always on path without having to activate the venv explicitly.

yup, I use either a globally installed meltano (via pipx) or start a

poetry shell

on meltano's master

makes sense, thanks! (realizing now that i’ve done

pipx install meltano

for previous sdk projects without really thinking about the difference)