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

BALL.py should be added to PYTHONPATH automatically #573

Open
cschaerfe opened this issue Dec 11, 2015 · 3 comments
Open

BALL.py should be added to PYTHONPATH automatically #573

cschaerfe opened this issue Dec 11, 2015 · 3 comments

Comments

@cschaerfe
Copy link
Contributor

  1. Cmake does not use contrib sip, but that one that was installed with python (e.g. when using anaconda) -- does it find the contrib sip?

  2. BALL.py is built, but BALLView cannot find BALL module correctly, leading to the following message in BALLView python console:

> No Python support available:
import BALL

These two things are likely connected and thus described here together.

@chahuistle
Copy link
Contributor

Still not sure what's the problem with issue (1), but issue (2) has to do with environment variables (PYTHONPATH) not being properly set.

@tkemmer tkemmer changed the title Wrong SIP used at compilation and BALLView Python support not working BALL.py should be added to PYTHONPATH automatically Mar 16, 2017
@tkemmer tkemmer added enhancement and removed bug labels Mar 16, 2017
@tkemmer tkemmer added this to the BALL 2.0 milestone Mar 16, 2017
@tkemmer
Copy link
Contributor

tkemmer commented Mar 16, 2017

(1) Does not seem to be a problem anymore.

We will consider (2) as a build system feature for BALL 2.0.

@tkemmer
Copy link
Contributor

tkemmer commented Mar 18, 2017

Reopening (1) as separate issue.

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

3 participants