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

Are jedi and pygments intended to be *compulsory* dependencies? #10880

Closed
anntzer opened this issue Nov 2, 2017 · 2 comments
Closed

Are jedi and pygments intended to be *compulsory* dependencies? #10880

anntzer opened this issue Nov 2, 2017 · 2 comments

Comments

@anntzer
Copy link
Contributor

anntzer commented Nov 2, 2017

Currently, jedi is listed in install_requires, but there is some code to work around a failure to import jedi (try: import jedi except ImportError: ...)
This causes the Arch Linux maintainers to package IPython without jedi (or, likewise, pygments), as a dependency (https://bugs.archlinux.org/task/56200#comment163092).
Could the IPython devs clarify their intent regarding whether downstream packages should declare jedi and pygments as compulsory dependencies?

@takluyver
Copy link
Member

We're in a transition with respect to Jedi, as @Carreau is experimenting with the completion machinery. Pygments is required for the terminal interface.

I would recommend that downstream packagers should turn all of the install_requires into dependencies (or at least 'recommended' in Debian packaging).

@anntzer
Copy link
Contributor Author

anntzer commented Nov 2, 2017

thanks.

@anntzer anntzer closed this as completed Nov 2, 2017
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