Qemu 11 / Python311, lost dependency list

[MG]

While trying to build Qemu 11.0 on a custtom FreeBSD 15.0 system wit X.org, I'm entering a dependency maze of python311-based ports.. Several of these:

py-setuptools-scm
py-pip
py-fur
py-furo
py-accessible-pygments
py-hatch-vcs
py-hatch-fancy-pypi-readme

The ports system somehow doesn't recognize the required dependencies.
The build outputs while trying are too much and not detailed enough.
Is there any method of installing python311 with all of these version-sensitive addition python packages to avoid this dependency hierarchy? While no python user at all, I really wonder why this all have to be separate ports. Can't it keep its own internal needs internal?

 

[kent_dorfman766]

Are you installing python modules using pip? iirc, python likes to manage its own dependencies via their pip utility.

 

[MG]

Are you installing python modules using pip? iirc, python likes to manage its own dependencies via their pip utility.

No, just make and then try to solve problems.
I have it working now for some time. It's part of a full target system that now can boot its own medium again inside qemu 11.
The port make still launches a portconfig options chooser process on the background that goes to 100% single-core and has to be killed manually. I think it's in a return or escape loop and not automated by the make BATCH=1 setting for some reason.

I never used pip. Is it required for something? I'd say the make process just should tell what it wants related to python and make possible differences configurable with port settings. I had build dependency conflicts that shouldn't happen. The portstree can be used for different things that independently need different python additions and don't have to conflict. It feels like python is trying to be a "system layer" or something.