-
Notifications
You must be signed in to change notification settings - Fork 17
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
Provide support for python 3 #120
Comments
Hi Joannah, and thanks! Ideally the gpkit codebase should provide neutral
support (I've been trying to do that, except for some of the
visualizations), but the largest obstacle is our interfacing with solvers;
our method for using mosek's c bindings relies on ctypesgen, and cvxopt
doesn't seem to be planning a python 3 version. Concretizing neutral
support in gpkit first, and then working on solver interfaces (using
mosek_cli in the meantime) seems like a potentially fruitful path forwards.
The SPaircraft codebase should be very easy to switch to neutral support
once gpkit has; I bet print statements are the only non-forwards-compatible
element.
…On Sun, Dec 10, 2017 at 2:54 AM, Joannah Nanjekye ***@***.***> wrote:
One of the installation requirements
<http://spaircraft.readthedocs.io/en/latest/Installation.html> of this
tool is python 2.7 but the python community is planning to stop support for
python 2 in 2020 around time for pycon, that is roughly 2 years from now.
We should therefore think of providing support for the recommended version
of python which is python 3. A great decision to make is either to port to
python 3 or to provide neutral support (both python 2 and 3) using
libraries like six <https://pythonhosted.org/six/>.
If we agree on what should be done i.e port or neutral support, I will be
happy to work on this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#120>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ABagGCrbOgKoXEOYTbBRmv7bZxeVJoVPks5s-447gaJpZM4Q8aP5>
.
|
I see similar efforts here If the owners of cvxopt are not considering python 3 support because even if we provided compatibility on our end we wont achieve our full objectives if one of our dependencies will never support python 3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of the installation requirements of this tool is python 2.7 but the python community is planning to stop support for python 2 in 2020 around time for pycon, that is roughly 2 years from now.
We should therefore think of providing support for the recommended version of python which is python 3. A great decision to make is either to port to python 3 or to provide neutral support (both python 2 and 3) using libraries like six.
If we agree on what should be done i.e port or neutral support, I will be happy to work on this.
The text was updated successfully, but these errors were encountered: