> > > pip doesn't necessarily have to "interact with many different versions of > the same build tool during a single invocation" if for example it's > subprocessing the interactions to some "pip-build" tool that handles the > imports and use of the python API. I.e. pips calls some "pip-build" too > (per build), which does the import, not pip itself. >
sorry, there's 2 confusing misspells in my sentence. here it is again: pip doesn't necessarily have to "interact with many different versions of the same build tool during a single invocation" if for example it's sub-processing the interactions to some "pip-build" tool that handles the imports and use of the python API. I.e. pip calls some "pip-build" tool (per build), which does the import, not pip itself.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
