apply-requirement-files broken with recent pip #76
Comments
|
Apparently that API change (nothing less than entire API for pip's requirement class) occurred between versions 8.1.1 and pip 8.1.2. |
gracinet
pushed a commit
to gracinet/anybox.recipe.odoo-1
that referenced
this issue
Aug 23, 2016
gracinet
pushed a commit
to gracinet/anybox.recipe.odoo-1
that referenced
this issue
Aug 23, 2016
gracinet
pushed a commit
to gracinet/anybox.recipe.odoo-1
that referenced
this issue
Aug 23, 2016
... and I checked again that 8.1.2 is the main breaking change here There's another one at 8.1.0 for the egg fragment in requirement
Merged
gracinet
pushed a commit
to gracinet/anybox.recipe.odoo-1
that referenced
this issue
Aug 25, 2016
It's a bit theoretical, but it was easily done
gracinet
pushed a commit
to gracinet/anybox.recipe.odoo-1
that referenced
this issue
Aug 25, 2016
gracinet
added a commit
that referenced
this issue
Aug 29, 2016
Github #76: compatibility with various pip versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the title said,
apply-requirement-file = True(see #45, #43) does not work with most recent version of pip (wich is itself used to read the requirements file).I do have a fix locally, need to wrap it up properly and find the exact pip version introducing the breaking change (and if or why integration tests didn't warn about it)
The text was updated successfully, but these errors were encountered: