specifying relative path as source for package

[pypa]

specifying relative path as source for package

[ryneeverett]

I was thinking the main use case would be specifying directories outside the immediate parent of the Pipfile, but within a version controlled tree. This would be nice for managing dependencies when using the mono-repo pattern and maintaining multiple packages in the same repo, as well as single-project repositories that include an example/testing application directory that depends on the main package.

[dstufft]

This seems like a reasonable idea.

Perhaps it should be restricted so that the relative directory cannot be outside of the tree that contains the Pipfile (e.g., you cannot use ..), however I'm not sure if it really matters, if someone has their system laid out in a specific way, it may not make sense to really worry about trying to enforce something like that.

[ryanhiebert]

This is the only blocker that I have for using Pipfile through Pipenv. My deployed application is an installable python package, with my dependencies and a custom entry point declared in setup.py. Currently I have a requirements.in file (for use with pip-tools) that just has the contents -e .. Then the current versions get saved into the requirements.txt. I'd much rather use Pipfile, but I need to be able to install my Python package before that'll work.

It would also be acceptable in my case if it was expected that Pipfile would take over all the dependency management, as long as I can find some way to install my package so that I can get my entry point installed.

[evanj]

Having just spent a bunch of time trying to figure out how to split a single monolithic Python application into a couple different pieces, having relative paths in a Pipfile that reference the parent directory would be very helpful. I think this is exactly what @ryneeverett was pointing out. To be extra clear, as an example, we have a git repository that is approximately:

• somelib/setup.py - A shared library
• app_one/requirements.txt - An application that wants to depend on ../somelib
• app_two/requirements.txt - Another application that wants to depend on ../somelib

It is extremely annoying that pip relative paths are relative to the "current working directory" and not the file. It would be very helpful if Pipfile would fix this.

[kennethreitz]

we support "-e ."

I'll add it to the example

[ryanhiebert]

@kennethreitz : I'm sorry, I'm really having trouble finding the example you're referring to above, or anything about how -e . is supported. I imagine that part of it will be the {editable=true}, but I'm not sure how to specify a path. What am I missing?

[kennethreitz]

{path=".", editable=True}

[ryanhiebert]

Thanks!

[kennethreitz]

I need to update the spec.

[kennethreitz]

Look at Pipenv for most recent examples.

[kennethreitz]

http://docs.pipenv.org/en/latest/

[kennethreitz]

Specifically, the advanced section: http://docs.pipenv.org/en/latest/advanced.html#specifying-package-indexes

[gabrielfalcao]

updated link: https://pipenv.readthedocs.io/en/latest/advanced/#specifying-package-indexes