Albert Tugushev

> What about [my comment here](https://github.com/jazzband/pip-tools/pull/1539#issuecomment-1132052061)? @AndydeCleyre the link does not show the comment. Could you quote here?

@AndydeCleyre thanks! That looks like a shoot in the foot 😄 While I understand there are `setup.py` hackers (historically) in the wild, however, we would never satisfy their needs due...

Hello @a666, Thanks for the issue! I believe this should be implemented on [pip](https://github.com/pypa/pip) side. See related issues: - https://github.com/pypa/pip/issues/4995 - https://github.com/pypa/pip/issues/6469 However, there are possible solutions: - using a...

> Did you mean split the `requirements.in` file? Hello @cjerdonek! That's exactly what I mean. Yeah, `--exclude` seems like a good solution.

@cjerdonek, yes, you are right.

Hello @cjerdonek, Could you try out the #1406? Does it resolve the issue?

I'm inclined to think that `pip-compile` should strip all extras in compiled `requirements.txt`. See explanation by @FlorentJeannot in https://github.com/jazzband/pip-tools/pull/1453#discussion_r671595549. Of course this requires some discussion.

what if `my-sub-package` is required by `my-package`, `my-package[extra1]`, and `my-package[extra2]` in sub-dependencies? Then it would be: ``` my-sub-package==1.1.1 # via # -r requirements.txt # my-package # my-package[extra1] # my-package[extra2] ```...

@mmerickel > Ran into this issue as well. If I modify all my `-e src/foo` links to `-e file:src/foo#egg=foo` then the compiled requirements file drops out the same `-e file:src/foo#egg=foo`...

@tisdall you could try `--find-links file:./local_src`. It keeps the relative path.