You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
Bigjob installs the following packages (from setup.py):
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
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
will result in 'no base in api' if the bigjob api module is picked up -- which is totally confusing...
This is related to #123 .
The text was updated successfully, but these errors were encountered: