[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: Per Tarek’s pronouncement, closing. -- resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: [Sridhar] >> No, it’s register that uploads metadata. >(was not sent before?) To me, not to the tracker. > Ok, that's interesting. Does p7g.install support packages that do not > register their new releases? > Setuptools/PIP does by scraping the project home page

[issue8927] Handle version incompatibilities in dependencies

Dave Abrahams added the comment: That's quite true. However, I don't think a local index is needed if there's a remote index; you're already looking in a remote index, albeit a less-completeone. And it could be maintained automatically from individual package metadata. Maybe that's out of

[issue8927] Handle version incompatibilities in dependencies

Sridhar Ratnakumar added the comment: Dave, but aptitude contains a local index of all dependency information. Whereas, PyPI's infrastructure and pip/easy_install/p7g.install do not rely on one. Therefore, I think when Tarek said "Trying to do something smarter is very very hard and will prob

[issue8927] Handle version incompatibilities in dependencies

Sridhar Ratnakumar added the comment: On 2011-06-07, at 10:39 AM, Éric Araujo wrote: > Éric Araujo added the comment: > >> Not all packages upload their release sources (thus metadata) to PyPI > No, it’s register that uploads metadata. (was not sent before?) Ok, that's interesting. Does p7g

[issue8927] Handle version incompatibilities in dependencies

Dave Abrahams added the comment: I'm sorry, but it is simply not true that this is not a solved problem. This is a well-understood problem that's solved --- at least as well as anyone could want it to be --- by aptitude (not apt-get) and by http://en.opensuse.org/openSUSE:Libzypp_satsolver

[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: > Not all packages upload their release sources (thus metadata) to PyPI No, it’s register that uploads metadata. > which is why - I believe - PIP is scraping the Simple Index and > home_page urls to get the appropriate sdist for any package. Yes, the screen scrapi

[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: Tarek’s reply on IRC: > I think we should make it dumb: in case of a conflict, it's always > better/simpler to let the user deal with it. A simple "could not > install because you have package X version Y installed'. Trying to do > something smarter is very very

[issue8927] Handle version incompatibilities in dependencies

Sridhar Ratnakumar added the comment: On 2011-06-07, at 9:48 AM, Éric Araujo wrote: > > Éric Araujo added the comment: > >> The only way to fix this is to /not/ install *any* packages prior to >> resolving *all* dependencies > > packaging.install rolls back in case of error, so the system c

[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: > The only way to fix this is to /not/ install *any* packages prior to > resolving *all* dependencies packaging.install rolls back in case of error, so the system can’t be left in a half-installed state. p7g.install is only as smart as p7g.depgraph, however. >

[issue8927] Handle version incompatibilities in dependencies

Sridhar Ratnakumar added the comment: The only way to fix this is to /not/ install *any* packages prior to resolving *all* dependencies ... which means that there needs to be a way to resolve the entire dependency graph for any given package in PyPI. If PyPI provided a mechanism to fetch the

[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: As discussed on the Fellowship ML, ActiveState has implemented an algo for a smart dependency graph: https://github.com/ActiveState/depgraph On the one hand, I think it’s not outside the scope of packaging.depgraph to be a bit smarter about dependencies. On the

[issue8927] Handle version incompatibilities in dependencies

Éric Araujo added the comment: Re: title, I don’t know how to phrase it best. What exactly is the behavior you request? I put “handle” as in “do the right thing”, that is, “don’t install the newest version but the one that satisfies all predicates”. I softened “conflicts” to “incompatibili