So are we going for a "primarily isolation" approach then where builds are only isolated on the first level, but subsequent levels share the same build environment?
2017-08-22 10:23 GMT-05:00 Jim Fulton <j...@jimfulton.info>: > I didn't mention (nor do I recall anyone mentioning) venvs. > > Jim > > > On Tue, Aug 22, 2017 at 11:15 AM, Matt Joyce <m...@nycresistor.com> wrote: > >> venvs within venvs... terrifying concept. >> >> On Tue, Aug 22, 2017 at 11:02 AM, Jim Fulton <j...@jimfulton.info> wrote: >> >>> >>> >>> On Tue, Aug 22, 2017 at 9:23 AM, Daniel Holth <dho...@gmail.com> wrote: >>> >>>> Isn't this a special case of needing . on sys.path when building a >>>> package? Then the same version of setuptools that is being packaged builds >>>> itself. >>>> >>> No. The issue for us it wasn't setuptools itself, but it's dependencies >>> and those dependencies conflicted with dependencies of of packages we were >>> installing *and* those packages importing these dependences (indirectly) in >>> their setup scripts. Setup scripts that import the thing they're about to >>> install, generally to get the version :(, is something I'd love to see go >>> away. >>> >>> Jim >>> >>> -- >>> Jim Fulton >>> http://jimfulton.info >>> >>> _______________________________________________ >>> Distutils-SIG maillist - Distutils-SIG@python.org >>> https://mail.python.org/mailman/listinfo/distutils-sig >>> >>> >> > > > -- > Jim Fulton > http://jimfulton.info > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
