can a whl file aggregate other whl files

Can a whl file aggregate other whl files?

I realize you can create a family of related whl files, and have them reference each other by referencing the dependent modules in install_requires (https://docs.python.org/3/distutils/setupscript.html)

However, what I'm interested in is aggregating some of those dependencies inside the whl file.

I'm building a 'component' based (charting) system in python - different teams can independently develop these 'chart' components and pluging them into the overall system. The independence of these components implies they maybe developed over different lifetimes and have different versions of shared code (common modules).

Thats why I wish to have these modules AGGREGATED inside each individual chart component, rather than referenced (referencing would cause problems if two chart components dependent on differing versions of common components).

So this question is both a whl file packaging question (straight-forward way to combine) and a question about the abilities of pythons module system to support the scenario of aggregating modules so that they dont get registered in the global sys.modules object, but just used inside a given module (chart component in my case).

from can a whl file aggregate other whl files