'-e .' resolves to absolute path, breaking compatibility

[rpkilby]

-e . resolves to an absolute path on the local machine, breaking the requirements.txt file for other users since they most likely don't have the package source installed at the same path. Luckily, it's not too difficult to keep up with the output, although it is annoying.

Environment Versions

1. OS Type: macOS
2. Python version: 3.6.0
3. pip version: 10.0.1
4. pip-tools version: 2.0.2

Steps to replicate

1. Add package to requirements.in as -e .[extradep]
2. pip-compile --output-file requirements.txt requirements.in

Expected result

• requirements.txt contains -e .
• requirements.txt contains resolved extra dependencies

Actual result

• requirements.txt contains -e file:///absolute/path/to/package/on/local/machine
• requirements.txt contains resolved extra dependencies

[strichter]

In my case the extra deps are not added to requirements.txt.

[rpkilby]

@strichter - your case might be related to #625.

[regisb]

I observe the same behaviour, even though the local project does not have extra dependencies. This is annoying because it forces us to manually run pip install -e . after every pip-sync.
This issue seems to be related to PR #507.

[mm-matthias]

Duplicate of #204

[atugushev]

Let's track it in #204.