-
Notifications
You must be signed in to change notification settings - Fork 77
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
python importing conflicts #224
Comments
Yes, let's just remove our unittest.py, and move the functions to coolfluid.py, preferably as members of a unittest class. I was unaware that we had this, I think this also explains why ipython doesn't start anymore with the dso dir in the PYTHONPATH |
I was also unaware. It seems to be Vivian's good work. We should indeed try to find a solution for this in a more pythonic way, including classes, namespaces etc. |
In the latest commit I renamed the unittest.py file to check.py to solve this temporarily |
OK, good, this might not even need to be so temporary, we just need to come up with a design for the part of our module that will be implemented in python |
After putting the PYTHONPATH to the coolfluid/dso directory,
and in python calling
import numpy
,a conflict appears:
The reason is the file "unittest.py" inside the coolfluid/dso dir, that was added recently. @barche, do you know a way around this?
The text was updated successfully, but these errors were encountered: