At 03:04 PM 10/26/2006 -0600, Jeremy Kloth wrote: >On Thursday 26 October 2006 2:41 pm, Phillip J. Eby wrote: > > At 01:58 PM 10/26/2006 -0600, Jeremy Kloth wrote: > > >The consumer of those fields is actually the PackageManager class: > > > > > >http://cvs.4suite.org/viewcvs/4Suite/Ft/Lib/DistExt/PackageManager.py?view > > >=markup > > > > Yeah, I'm still not getting what it *does* with this information. What's > > it *for*? > >Since there is no current way to get the requires/provides/obsoletes from >PyPI >RPC, they are used to determine the sub-package installation order and to >verify that the requirements are installed if not already provided by another >sub-package.
What's a sub-package? >PackageManager doesn't do any downloading as it is pointless until those >fields become available through RPC. Okay, I thought you said this was a tool that did something useful with the PEP 314 data. So I'm confused now. This sub-package thing, if I'm getting the gist correctly, only works with stuff you're actually *bundling*, so what difference does PyPI make? _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
