-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 3 compatibility #16
Comments
Agreed. What is the best way to do this? Do we put |
There is a script called 2to3 that you can run on all the code. It will print out a summary of all the changes you need to make in order for the code to be python 3 compatible. I'll run that and report back. Also, I'll start making the changes on a branch named compat |
If you only have python 3 installed - the pip install notes several modules with invalid syntax. Most often around print rather than print() and also on change in 3 for raising an exception. Here were the warnings: Running setup.py install for quantecon
|
Thanks for this. I will spend some time today starting to make things dually compatible |
happy to help test - but new to python; pandas and Stachurski, Sargent examples pulled me over. But coding ability probably of limited value |
Thanks for the offer. We are almost done making the code compatible for both python 2 and python 3. We definitely appreciate you using the code and for helping point out this issue. We will hopefully close this issue in the next 24 hours, and it would be helpful if you could run through it all again and see if all is in order. |
See #33 for updated issue and PR |
I think we should strive for 100% python 3 compatibility. Guido has officially announced (more than once) that the python 2 branch will only be maintained and that all new language features will only be implemented in python 3. Doing a quick 2to3 pass over the library shows that we will have to make very minor changes to the existing code for it to be python 3 compliant (mostly just swapping out
print
statements for aprint
function call).One of the more exciting features forthcoming in the next python release (3.5) is the new syntax
@
that will mean matrix multiplication. So, instead of writingnp.dot(a, b)
ora.dot(b)
, we can write the much more compacta @ b
.The text was updated successfully, but these errors were encountered: