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

Hardcoded dependency: PyBreeder #46

Closed
kaeff opened this issue Aug 5, 2013 · 3 comments
Closed

Hardcoded dependency: PyBreeder #46

kaeff opened this issue Aug 5, 2013 · 3 comments

Comments

@kaeff
Copy link

kaeff commented Aug 5, 2013

After cloning and setting up the project according to the Readme, attemts to running ./mp fail like so:

➜  Mailpile git:(master) ✗ ./mp -www
Traceback (most recent call last):
  File "./mp", line 3, in <module>
    from mailpile.app import Main
ImportError: No module named mailpile.app

I asumme this happens due to a hardcoded dependency to the PyBreeder project:

$ ls -l scripts/
breeder.py@ -> ../../Beanstalks/PyBreeder/breeder.py

Would it maybe be useful to indirect this dependency using more maintainable mechanisms like e.g. git submodules?

@ei8fdb
Copy link

ei8fdb commented Aug 24, 2013

I had the same issue. However I have not been able to fix this as my python knowledge is not up to speed.

Any assistance?
Thanks,
Bernard

@danx0r
Copy link
Contributor

danx0r commented Aug 24, 2013

The README does explain it (tersely, see line 40) -- you have to set PYTHONPATH in your shell. In bash, do this:

export PYTHONPATH=/home/username/mailpilefolder

obviously replace the string with your appropriate username and path to mailpile.

This can probably be fixed with some Python jimmying, I may look at that.

@danx0r
Copy link
Contributor

danx0r commented Aug 24, 2013

I've fixed this on my fork: danx0r@e8efe5e

You can do a pull and merge this patch until it (hopefully) gets incorporated into the project.

FWIW breeder.py is not the issue, it was a general problem with importing modules from a local path. Not sure why that breeder link is there, it gets created by the makefile but AFAICT is never used (if you do make dev as instructed).

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

4 participants