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

Question: how to resolve extras_require dependency during setup runtime? #256

Closed
ghost opened this issue Sep 11, 2014 · 1 comment
Closed

Comments

@ghost
Copy link

ghost commented Sep 11, 2014

Originally reported by: marscher (Bitbucket: marscher, GitHub: marscher)


This has been summarised here:

pypa/pip#1993


@ghost
Copy link
Author

ghost commented Sep 11, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


Historically, the way packages have solved this problem is by using the deprecated Feature (#65) feature. However, because it's deprecated, the recommended solution is to use extras for your C extension.

So the way you do that is create a separate distribution package for your C extension module, call it say "jpype.numpy" and have it only implement the C extension. Then define your extras in jpype as so:

extras_require=dict(
  numpy=[
    "numpy>=x.x",
    "jpype.numpy>=x.x",
  ],
)

Then, all of the build implications of jpype.numpy can be specified in the setup.py for that package.

Does that approach solve your issue?

@ghost ghost added major task labels Mar 29, 2016
@ghost ghost closed this as completed Mar 29, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants