FWIW, this is a topic I was planning to bring up at the language summit this year, so for those who are going to be there and want to toss around ideas (mine is nearly developed enough to present, but not quite yet), bring them.
That said, I don’t think relying on relative imports within a package should be at all controversial, but perhaps it needs an official endorsement somehow? PEP 8 is what people read to find these, but I don’t know if it makes sense for the stdlib (maybe it could deal with some of the shadowing issues people run into? If they manage to import the top level module before their own appears ahead of it on sys.path... thinking out loud here). Cheers, Steve Top-posted from my Windows phone From: Barry Warsaw Sent: Thursday, March 22, 2018 12:56 To: Python-Dev Subject: Re: [Python-Dev] Better support for consuming vendored packages On Mar 22, 2018, at 12:33, Oleg Broytman <p...@phdru.name> wrote: > > On Thu, Mar 22, 2018 at 12:30:02PM -0700, Barry Warsaw <ba...@python.org> > wrote: >> Developers are mostly going to use pip, and maybe a requirements.txt, > > +virtual envs to avoid problems with global site-packages. Yep, that was implied but of course it’s better to be explicit. :) > IMO virtualenv for development and frozen app for distribution solve > the problem much better than vendoring. +1 -Barry
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
