-
Notifications
You must be signed in to change notification settings - Fork 322
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
Py3k #324
base: master
Are you sure you want to change the base?
Py3k #324
Conversation
Am I missing something? I've tried to install with pip and easy_install under Python 3.3 and the installation fails. If you need further information please let me know and I'll get it across to you. Maybe I should be installing from the repo rather than PyPI? |
Can you let us know what fails? A traceback or something? This pull request hasn't been merged in yet so there is no chance that installing from PyPI will work yet. |
Forget what I've put, I've realised after going through the issues that this was a pull request (!), I'll look at installing the changes you've submitted and let you know how I get on ;) |
Right ok, so this is what I've found thus far: I have to manually install the following packages:
After this, when running lettuce, I'm presented with the following error:
|
hi, this: except Exception, e: must be replaced by: except Exception as e: 2013/11/2 Daniel Ward [email protected]
|
@danielward Also the Py3 porting guide has this to say: Actually to not break Py2 support you should do something like this: try:
unicode = unicode
except NameError:
unicode = str
basestring = (str, bytes) I was working on getting all of lettuces dependancies working on Py3 first, once they get merged I was going to tackle lettuce Py3 support. Unfortunately it has been a month since I did the pull requests... |
I'm not sure if you've looked at it, though Regarding the syntax changes with Unfortunately the lack of activity on |
I tried to port lettuce to Py3k. The biggest problem is that python-mox lib is not suppopred since November, 2012. What about migration to mock? It it in Python Standard Library now |
I endorse mock. Also if you're not keen on six, have a look at python-future. |
I've got a branch that extensively refactors the core of Lettuce (#429), I am taking the time as part of this work to try and makes things as Python3/unicode clean as I possibly can. Once this is done I'm going to attempt porting to Python 3 using python-future as the compatibility layer. |
Hey guys |
It is working with python 3 and django 1.6.2. Maybe we can put all this efforts together |
I'm skeptical that everything will actually work with python3, but all the tests are passing.
It's a start...
Anything that breaks with python3 should result in a new test.