-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
extras_require in setup.py #5408
Conversation
does this break later upgrading any dependencies the way |
Just checked it - no, if some other package will override dependencies specified in CKAN's |
setup.py
Outdated
('setuptools', 'requirement-setuptools.txt'), ('dev', 'dev-requirements.txt'), | ||
] | ||
for group, filepath in _extras_groups: | ||
with open(filepath, 'r') as f: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this assumes you're running setup.py from the same working directory. better to use the path of the current module to be safe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. I'm usually using pip install -e ...
which implicitly changes directory to the package root before installation, so I didn't notice the problem, even though I've installed it from outside of CKAN's repo.
… actions using pip
Allow installation of requirements without any additional actions using pip(fetch requirements.txt, etc).
For example:
For testing, try to use my fork: