Skip to content

Updated dependencies.rst #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Updated dependencies.rst #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions dependencies.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,12 +63,12 @@ When we publish this to PyPI, calling ``pip install funniest`` or similar will a
Packages Not On PyPI
~~~~~~~~~~~~~~~~~~~~

Sometimes you'll want to use packages that are properly arranged with setuptools, but aren't published to PyPI. In those cases, you can specify a list of one or more ``dependency_links`` URLs where the package can be downloaded, along with some additional hints, and setuptools will find and install the package correctly.
Sometimes you'll want to use packages that are properly arranged with setuptools, but aren't published to PyPI. In those cases, you can directly specify in ``install_requries`` with the syntax ``package_name @ URL`` (checkout PEP 508 for syntax) the URLs where the package can be downloaded, along with some additional hints, and setuptools will find and install the package correctly.

For example, if a library is published on GitHub, you can specify it like::

setup(
...
dependency_links=['http://github.com/user/repo/tarball/master#egg=package-1.0']
install_requires=['repo @ git+http://github.com/user/repo/']
...
)