Our install pattern + the fact that all the popula...
# meltano-plugin-development
f
Our install pattern + the fact that all the popular (at least Airflow/Superset) have unique requirement for click/structlog versions is - annoying.
..because we're also trying to use structlog and click in the sdk 😢
I do have a set of version constraints that makes airflow 2.3.3 + the sdk and superset 2.0 +the sdk play nice together - but I bet extension devs wrapping older python packages are gonna run into issues.
Optionally, having your extension + the thing you're wrapping in two different venv's might be handy
w
Yeah, separating stuff into different venvs would be great. Would make it easy for us to keep up with the latest and greatest (e.g. security patches, Python 3.11, etc.) while not harming support for less actively maintained packages.
f
i think we actually had a issue similar to this - so this could be a dupe, but Gitlab search is being wonky and Github didn't pop up the issue I was thinking off.
w
@aaronsteers I believe you mentioned this when we originally discussed Python 3.10 support, but I didn't see an issue for it in our DMs. Do you know if there was one?
a
Yeah, I do think we have an issue out there regarding different plugins sharing a venv - but that was for use cases of sqlfluff and dbt, where they both could be separate plugins and wanting to use the same venv. This almost seems like a use case for a single plugin to have multiple venvs (?)
f
yep, thats exactly what it is. I pop'd #6600 just incase yesterday. I trolled through a lot of the issues but pip and venv show up a lot in searches 😁
spent a solid 30 minutes going "crap how did i break this" thinking it was a weird dep conflict , but no its a superset 2.0 bug.