Skip to content
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

Drop python3.4 support #1513

Closed
fafhrd91 opened this issue Dec 27, 2016 · 9 comments
Closed

Drop python3.4 support #1513

fafhrd91 opened this issue Dec 27, 2016 · 9 comments

Comments

@fafhrd91
Copy link
Member

i think it is time

@AraHaan
Copy link
Contributor

AraHaan commented Dec 27, 2016

Yeah 3.4 has a coroutine bug which was fixed since 3.5 and 3.6 is actually better. However 3.4 users who use aiohttp on debian systems don't even have a final version of 3.5 so that is an issue their last version is 3.4 for now unless they can build from source.

@asvetlov
Copy link
Member

It's very tempting decision but I'm thinking about python 3.5 support in major linux distributions.
Say, Debian includes Python 3.4 only in the latest Debian Jessie.

@AraHaan
Copy link
Contributor

AraHaan commented Dec 28, 2016

Yeah, which is sad that means they would have to manually compile 3.6 but it is good thing not hard to do.

Other than that if they can make install I think they would be fine with building 3.6 from source.

@asvetlov
Copy link
Member

No, it's not an option.

IIRC Blind sudo make install on Debian effectively breaks OS down to non-bootable state :)

@fafhrd91
Copy link
Member Author

@asvetlov do you know when debian is planing to upgrade?

latest ubuntu lts already uses python3.5, i guess redhead should too.

@mwfrojdman
Copy link
Contributor

Debian Stretch ought to be released in the second half of 2017 if progress is as before. Seems it will include only 3.5, not 3.6 as freeze is around now.

@Rapptz
Copy link

Rapptz commented Dec 31, 2016

I haven't dropped 3.4 support in my libraries for similar reasons. Not every distro comes with it and truthfully if there's a compatibility layer then the effort of supporting 3.4 and 3.5+ is not too steep.

@asvetlov
Copy link
Member

asvetlov commented Jan 1, 2017

Let's wait for a while

@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants