-
Notifications
You must be signed in to change notification settings - Fork 88
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
Port to python 3.5 #50
Comments
It's probably too early to replace all @asyncio/coroutine/yield from pairs with async/await, py3.4 is still too wide-spread and the two schemes are mostly compatible. However, using Python 3.5 does break some tests. |
More over, I don't see python 3.5 coming on debian ( the most interesting link must be https://lists.debian.org/debian-python/2015/06/msg00036.html) Keeping the compatibility from 3.4 to 3.5 looks like pain :( |
Python 3.5 is on Debian experimental and is able to run 3.4 code just fine. |
All tests now pass when using 3.5, at least on my machine. AFAICT there are no plans to remove yield-from style coroutines from Python3. |
then we just need to add python 3.5 to the tox config |
travis config I mean |
On 20.11.2015 09:36, Marco Paolini wrote:
-- Matthias Urlichs |
Imho the first fix should be a port of asyncio.async() to asyncio.ensure_future() ? |
It seems pyrabbit is not python 3.5 compatible :( |
@dzen pyrabbit itself is perfectly 3.5 compatible. httplib2 is not. |
yes, for sure, I didn't go deeper this weekend to know why pyrabbit fails on thoses CONNRESET :) thank you for the patch on httplib2 |
Hello all, We migrated to the git version of pyrabbit. Tests are passing. |
Hello all, |
No, we're still compatible with 3.4. |
Ok, thank you. Do you planning to do this? |
Hi @MaxOvcharov. We still have a lots of python 3.4 running in our production. |
No description provided.
The text was updated successfully, but these errors were encountered: