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

bigjob package naming #153

Open
andre-merzky opened this issue Oct 17, 2013 · 1 comment
Open

bigjob package naming #153

andre-merzky opened this issue Oct 17, 2013 · 1 comment

Comments

@andre-merzky
Copy link
Member

Bigjob installs the following packages (from setup.py):

      packages=['bigjob', 'bigjob_dynamic', 'coordination', 'pilot', 'bigjob.job_plugin', 'pilot.api','pilot.api.compute', 'pilot.api.data', 'pilot.coordination', 
                'pilot.filemanagement', 'pilot.impl', 'pilot.scheduler', 'examples', 'api', 'bootstrap', 'cli']

That basically implies that whenever I install bigjob, I will get naming conflicts on pilot.py, example.py, cli.py, api.py, bootstrap etc which I happen to have in my own tree. Like

import pilot

will not be able to distinguish between the bigjob package and my sinon/pilot.py. I would very much appreciate it if bigjob packages could be moved into the bigjob namespace...

Mostly python does the right thing - but if not this screws up badly. Like

from api import base 

will result in 'no base in api' if the bigjob api module is picked up -- which is totally confusing...

This is related to #123 .

@andre-merzky
Copy link
Member Author

I would love to get a reaction on this ticket...

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

1 participant