-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 Support #288
Comments
Tests now pass for me and travis for both Python 2 and 3. If other people could test with their projects as well that would be really helpful. |
Yes the tests pass (: but I fear especially some management commands are untested and need some |
Yes, I will try to find some time to and go through as many commands as I can. I'm also thinking that we can either release a beta version or a new version with a big warning that python 3 support is untested. To get feedback from the community and then I will make frequent releases whenever a python 3 related bug is fixed. |
FYI this appears to have broken shell_plus on python 2.x (well, I can reproduce with python 2.6.6 and django 1.4.5 at least). Traceback is here: https://gist.github.com/diox/988867849bdd17fd925f - reverting to an earlier version fixes it. |
I've committed a fix for this in eccf666 Now looking into this I decided to disable the entire pythonrc loading per default. Instead of specifying --no-pythonrc to NOT use it, you must now specify --use-pythonrc. Documentation like; http://docs.python.org/2/library/user.html clearly states its deprecation path and the large amount of problems with it. I must rather prefer we provide extra extensibility points of our own if this functionality is needed by people. |
lets create new tickets for new problems related to Python 3 support |
Let's try to get Python 3 support for Django Extensions
The text was updated successfully, but these errors were encountered: