Describe the bug
Splitting off from #1097, this captures just the Python dependency problem. Essentially we need to better handle conflicting requirements. If module-a requires python-module v1.0.0 and module-b requires python-module v2.0.0, we should either be able to separate out the python environments or clearly throw, instead of prioritizing one or the other. Currently we prioritize the first installed version.
The actual failing test is:
[USER|ZPM] Verify SUCCESS```
It has been marked as skipped as part of #1107
## To Reproduce
Remove the AssertSkipped from Test.PM.Integration.ProcessPythonWheel:TestWheelAndReqsPresentOnline and run the test.
## Expected behavior
To be specced out and decided.
Describe the bug
Splitting off from #1097, this captures just the Python dependency problem. Essentially we need to better handle conflicting requirements. If module-a requires python-module v1.0.0 and module-b requires python-module v2.0.0, we should either be able to separate out the python environments or clearly throw, instead of prioritizing one or the other. Currently we prioritize the first installed version.
The actual failing test is: