Skip to content

Specify >= or <= for vcs requirements. #728

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mforbes opened this issue Nov 17, 2012 · 1 comment
Closed

Specify >= or <= for vcs requirements. #728

mforbes opened this issue Nov 17, 2012 · 1 comment
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality

Comments

@mforbes
Copy link

mforbes commented Nov 17, 2012

It would be useful to be able to specify >= or <= requirements for version controlled requirements. For example

hg+http://bitbucket.org/mforbes/pymmf>=633be89a#egg=pymmf

The idea would be that any revision that is a descendant of the specified revision would be acceptable. One could also specify <= to mean any parent would satisfy the requirement (though I don't really have a use-case for this). I suspect that one would always have to specify "=" so that a revision can be found. (If one specified ">", then there is in general no unique way of determining which requirement to pull.)

I took a stab at implementing this, but it looks like vcs requirements do not go through a satisfy check, so I am not sure where I should hook in. Suggestions would be appreciated.

@xavfernandez xavfernandez added the type: enhancement Improvements to functionality label Oct 9, 2015
@dstufft
Copy link
Member

dstufft commented Mar 24, 2017

Closing this, while it may be possible to implement I believe it is a bit of an antipattern and it does not appear that the demand is there to warrant it.

@dstufft dstufft closed this as completed Mar 24, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality
Projects
None yet
Development

No branches or pull requests

3 participants