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
install.py: Refactoring #198
Comments
Additionally, install.py should provide a way to obtain the necessary pythonpath information, so that we can do:
|
The current version of install.py does not handle errors in the commands properly. E.g., it is quite common that the compilation failed but install.py thinks everything is ok. The new version should handle this properly. |
Closed
mikand
added a commit
that referenced
this issue
Nov 7, 2015
Each solver has now a dedicated class for installation and all the bindings get copied in a specific folder.
PR #209 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
install.py needs to be refactored, because it is not manageable, if we want to extend to more platforms.
In particular, we should have a main class:
SolverInstaller
that deals with the main flow of installation:Each Solver Installer would be a subclass of the above, in order to provide specific info like:
Additionally, it would be nice if the download function was a bit smarter, and it attempted first to use the mirror and then connect to the original URL in case of failure.
The text was updated successfully, but these errors were encountered: