Jarek Potiuk

> All of this feedback is incredibly useful and will directly assist me in creating the workspaces feature! Happy to help if you are open to it :).

@DavidVujic -> It does look promising, it's a bit difficult to wrap your head around bases/components (especially that the `base` is not realy a term I've seen used outside of...

Just to take off the pressure a bit. I figured out how to get rid of the `--user` flag (still have a problem to fix) https://github.com/apache/airflow/pull/37796 - I attempted it...

> @potiuk - At the very least I can add `--system-site-packages`, that's really easy. I'm somewhat undecided on `--user`... Gonna sleep on it. Yep. That would be a good start...

Yes. In Airflow we have something called `PythonVirtualenvOperator`. Airflow has operators (4000+ of them 😱 ) that can do tasks related to some "stuff" to do - some of them...

Under the hood, the operator does: ``` def _generate_virtualenv_cmd(tmp_dir: str, python_bin: str, system_site_packages: bool) -> list[str]: cmd = [sys.executable, "-m", "virtualenv", tmp_dir] if system_site_packages: cmd.append("--system-site-packages") if python_bin is not None:...

The way how it works now (just built and tested a new image): With system-site packages: ```bash airflow@a249d829a411:/opt/airflow$ python -m virtualenv --system-site-packages ~/.aaaa created virtual environment CPython3.10.13.final.0-64 in 422ms creator...

> @potiuk -- I'm trying to make a decision on whether to support --user. Do you have any references you could share for these side effects in pip? 🙏 The...

> It's worth keeping in mind throughout this discussion that we _will_ be building new workflows on top of the fundamental tooling we've built for pip-compatibility. If we can avoid...

> This should ideally just work, Yep. My proposal is that it will just install things in `.local` (or equivalent on other systems) venv created and used automatically by `uv`...