Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

> On Oct 21, 2017, at 10:30 PM, Nick Coghlan wrote: > > However, none of that impacts the question of whether `pip.main()` runs code > in the current process or implicitly runs it in a subprocess - `pip` doesn't > import the modules it installs either way, so it will all look the same as > fa

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On 22 October 2017 at 04:03, xoviat wrote: > Nick: > > That's generally a good idea, but one significant problem that can occur > is that the Python import system will cache certain libraries, people will > run "pip install," and then they will expect such libraries to be > available. I don't eve

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On 21 October 2017 at 19:11, Alex Grönholm wrote: > I need to correct you here: wheel does *NOT* have a public API! Ah, sorry. I hadn't realised that. > It did previously have some documented functions but it was not really well > thought out and we recently decided to remove all traces of API

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On Sat, 21 Oct 2017 at 11:26 Donald Stufft wrote: > > > On Oct 21, 2017, at 2:15 PM, Brett Cannon wrote: > > as long as the module isn't already imported it's fine. > > > Negative imports get cached too don’t they? > Yes, that too. :) (aside: don't reply to technical emails while you're waiting

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

> On Oct 21, 2017, at 2:15 PM, Brett Cannon wrote: > > as long as the module isn't already imported it's fine. Negative imports get cached too don’t they?___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On Sat, 21 Oct 2017 at 11:03 xoviat wrote: > Nick: > > That's generally a good idea, but one significant problem that can occur > is that the Python import system will cache certain libraries, people will > run "pip install," and then they will expect such libraries to be > available. I don't eve

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

Paul Moore kirjoitti 21.10.2017 klo 13:03: On 20 October 2017 at 23:53, Richard Jones wrote: Hiya Paul, There's a bunch of tooling out there using pip's internals to extending pip's functionality. Could you please provide a some reasoning as to why they're all going to be broken at pip 10, and

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

Nick: That's generally a good idea, but one significant problem that can occur is that the Python import system will cache certain libraries, people will run "pip install," and then they will expect such libraries to be available. I don't even know exactly how the caching for the import system wor

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On 21 October 2017 at 12:15, Nick Coghlan wrote: > (Note: this is entirely speculative, and I have no idea how hard it would > be, so please read it as the question it's intended to be) No problem - I don't know myself how hard some of this would be, either ;-) > Do you know if there any key API

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

Thanks for writing that detailed explanation, Paul (and all your other hard work!) Richard On 21 October 2017 at 21:03, Paul Moore wrote: > On 20 October 2017 at 23:53, Richard Jones wrote: > > Hiya Paul, > > > > There's a bunch of tooling out there using pip's internals to extending >

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On 21 October 2017 at 20:03, Paul Moore wrote: > Likely the biggest problems will be for people who call into the pip > resolver and build APIs, as I don't know of any alternatives out > there. But they were *definitely* breaking anyway, as we've made major > changes to that code (and will be mak

Re: [Distutils] pythonhosted.org doc upload no longer works

> On 20 Oct 2017, at 15:52, Nick Coghlan wrote: > > On 20 October 2017 at 22:42, Ronald Oussoren > wrote: > >> On 7 Oct 2017, at 09:12, Giampaolo Rodola' > > wrote: >> >> Any news about this please? This is becoming a problem as my out

Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs

On 20 October 2017 at 23:53, Richard Jones wrote: > Hiya Paul, > > There's a bunch of tooling out there using pip's internals to extending > pip's functionality. Could you please provide a some reasoning as to why > they're all going to be broken at pip 10, and possibly some guidance on how > to g

Re: [Distutils] Entry points: specifying and caching

On 21 October 2017 at 18:04, Wes Turner wrote: > On Saturday, October 21, 2017, Nick Coghlan wrote: >> I'm also going to file an issue on the setuptools issue tracker to make sure Jason is aware of what we're doing, and get his explicit OK with the idea of making the format a PyPA interoperabilit

Re: [Distutils] Entry points: specifying and caching

On Saturday, October 21, 2017, Nick Coghlan wrote: > On 20 October 2017 at 23:42, Donald Stufft > wrote: > >> On Oct 20, 2017, at 9:35 AM, Nick Coghlan > > wrote: >> The interoperability spec is going to state that conflict resolution when >> the same name within a group is declared by multiple

Re: [Distutils] Entry points: specifying and caching

On 21 October 2017 at 05:26, Doug Hellmann wrote: > I would also like to compare the performance of a few approaches > (1 file per sys.path hash using INI, JSON, and sqlite; one file per > entry on sys.path using the same formats) using a significant number > of plugins (~100?) before we decide.

Re: [Distutils] Entry points: specifying and caching

On 20 October 2017 at 23:42, Donald Stufft wrote: > On Oct 20, 2017, at 9:35 AM, Nick Coghlan wrote: > The interoperability spec is going to state that conflict resolution when > the same name within a group is declared by multiple packages is the > responsibility of the group consumer, so docum

Re: [Distutils] Entry points: specifying and caching

On 21 October 2017 at 06:50, Daniel Holth wrote: > I like the idea of lifecycle hooks but I worry about the malware problem; > would there need to be a blacklist / whitelist / disable system? > (ignore-scripts=true is now a recommended part of anyone's npm > configuration) That is why we have avo