Pip-tools: pip-compile broken with pip 19.0

[demosdemon]

Describe the issue briefly here.

Environment Versions

1. OS Type
   darwin
2. Python version: $ python -V
   Python 2.7.15
3. pip version: $ pip --version
   pip 19.0 from /Users/brandon/src/images/.venv/lib/python2.7/site-packages/pip (python 2.7)
4. pip-tools version: $ pip-compile --version
   pip-compile, version 3.2.0

Steps to replicate

```sh
$ pip-compile --generate-hashes --upgrade --header --index --annotate --output-file $@ $<
Traceback (most recent call last):
File "/Users/brandon/src/images/.venv/bin/pip-compile", line 10, in
sys.exit(cli())
File "/Users/brandon/src/images/.venv/lib/python2.7/site-packages/click/core.py", line 764, in __call__
return self.main(args, *kwargs)
File "/Users/brandon/src/images/.venv/lib/python2.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/Users/brandon/src/images/.venv/lib/python2.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, *ctx.params)
File "/Users/brandon/src/images/.venv/lib/python2.7/site-packages/click/core.py", line 555, in invoke
return callback(args, **kwargs)
File "/Users/brandon/src/images/.venv/lib/python2.7/site-packages/piptools/scripts/compile.py", line 130, in cli
repository = PyPIRepository(pip_options, session)
File "/Users/brandon/src/images/.venv/lib/python2.7/site-packages/piptools/repositories/pypi.py", line 62, in __init__
process_dependency_links=pip_options.process_dependency_links,
AttributeError: Values instance has no attribute 'process_dependency_links'

[impredicative]

I'm having the same error when running pip-compile under Python 3.6.7, pip-tools==3.2.0, and pip==19.0. The problem doesn't happen with pip==18.1.

[atugushev]

Thanks for the report! It seems --process-dependency-links is not supported since https://github.com/pypa/pip/pull/6060

[NejcZupec]

We have the same issue with Python 2.7.15 and 3.7.1, pip-compile-multi==1.2.1 and pip==19.0.

The issue was fixed with:
pip install -U pip==18

[impredicative]

I don't see a new pypi release out yet for pip-tools, so I don't know why this was closed so soon.

[atugushev]

@impredicative
It is the GitHub's behavior by default. See https://github.blog/2013-05-14-closing-issues-via-pull-requests/.

[impredicative]

Well, so let's reopen it until the issue is actually resolved. Or should users file a new issue? Ridiculous automated actions are no justification for disregarding commonsense.

[vphilippon]

Hello @impredicative,

I'll be making a release to pypi soon, worst case this evening (EST). Quite a busy day today.

Our (my) current approach is to try to make releases a soon as possible once something gets in, which alleviates this "limbo" situation. Although, if you have an idea to track fixed-but-unreleased issues with Github system, I'd be sincerely happy to hear it (maybe as a separate issue for visibility on the discussion).

Cheers!

[vphilippon]

Had a small pipeline issue last night (#716), I'll make a 3.3.1 release ASAP

[vphilippon]

Done: https://pypi.org/project/pip-tools/3.3.1/

Cheers!

[jedie]

Great! It works here, thanks!