Skip to content
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

metadata.json missing run_requires #733

Closed
daym opened this issue Jun 17, 2016 · 1 comment
Closed

metadata.json missing run_requires #733

daym opened this issue Jun 17, 2016 · 1 comment

Comments

@daym
Copy link

daym commented Jun 17, 2016

it seems the metadata.json in https://pypi.python.org/packages/c4/59/e48a369168a84c8aef9127c227fc3b9f53bc9c528b24c2cda20487bc2deb/jedi-0.9.0-py2.py3-none-any.whl misses the entry for key "run_requires" which would list the runtime requirements.

Is that on purpose? Does jedi really have no requirements beside Python itself?

I'm trying to package jedi for the GNU Guix distribution and am wondering what the right way to proceed is. I could make run_requires optional or I could ask the jedi maintainers for help in extending their metadata.json . Which do you think is the correct action? Should run_requires be optional?

See https://www.python.org/dev/peps/pep-0426/ for details of the metadata.json format.

The tests seem to need docopt.

@davidhalter
Copy link
Owner

Does jedi really have no requirements beside Python itself?

Yes. The tests have some requirements. Docopt is not really a requirement (since it's just optional), pytest and tox are. But I doubt that they would be part of run_requires?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants