Can a Pixi project environment inherit from the a global environment?

[Six6stRINgs]

Hello, thanks for your great work of pixi. I'm a Miniconda user who's recently become interested in Pixi and am exploring its capabilities.
And, I'm a student study the deep learning. Many project were run on my own computer, so I may care for the project disk space it is using.

I have a question about environment management that stems from my experience with Conda.
With Miniconda, I often faced a dilemma:

• Single, large environment: Using a single Conda environment for multiple projects leads to a bloated and potentially conflicting environment.
• Many small, isolated environments: Creating completely isolated environments for each project consumes a significant amount of disk space, especially when many projects share common dependencies. (torch cuda consumes too much disk space!)

Pixi emphasizes project-center environments with fast speed. So, my question is: Is it possible in Pixi to create a new project environment that inherits from an existing, global Pixi environment?
This is very similar to Make virtualenv inherit specific packages from your global site-packages.

Here is a situation:
Project A and B both need python interpreter and torch cuda with the same version and necessary dependencies. But A needs pytorch_lighting to build the whole project while B needs PyQt5 to create an UI. I want to create a global env named torch-base contains basic env of torch and have each project env share the base packages from the torch-base environment. The project env will only need to install the additional packages and dependencies(pytorch_lighting and PyQt5 in this case). In this circumstances, I can save the disk space and also create some neat environments.
The torch-base is frozen, so while I can add a new package in the project env, it would only install to the project path unless I run some global install cmd.

Plus, It is possible to creat a tree-structured inheritance relationship? Like: global env Ea is a basic torch env (root of the tree), global env Eb is inherited from Ea with additional package like transformers. Eb can be inherited to other project env(leaf of the tree) which will mainly foucs on NLP. On the other hand, global env Ec is inherited from Ea with some packages like PyQt5, so project needs UI can inherit from it. Every package as well as its dependencies use disk only one time.

       Ea (root - PyTorch)
      /  \
     /    \
    Eb     Ec  (intermediate - specialized)
   /  \   /  \
  NLP  ... UI  ... (leaves - project-specific)

I'm not certain my idea is completely thought out, but I'm very curious about it!
Thanks in advance for any insights or guidance you provide!

[HernandoR]

It's a great idea, though I would probably not to use it since inheritance generally brings redundant unexpected behaviour. Disk space is usually cheaper than your time to avoid potential conflict and unexpected behaviour.