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

Remove support for Python 2.6 #293

Closed
mrbean-bremen opened this issue Aug 20, 2017 · 4 comments · Fixed by #327
Closed

Remove support for Python 2.6 #293

mrbean-bremen opened this issue Aug 20, 2017 · 4 comments · Fixed by #327
Assignees

Comments

@mrbean-bremen
Copy link
Member

With Python 2.6 being at end of life now almost 4 years, we may drop the support IMHO.
Most other packages are also dropping support, so there is not much sense to keep it.
This will also allow to to cleanup the code by removing the Python 2.6 specific workarounds.
I propose to do this for the 3.4 release, alongside with the PEP-8 changes.

@hugovk
Copy link
Member

hugovk commented Oct 16, 2017

Drop it and 3.2 as well. Consider dropping 3.3 at the same time, all are EOL. Dropping 3.2 will help get of the strange Unicode handling it requires.

Reasons for dropping old ones

2.6

3.2

3.3

@mrbean-bremen
Copy link
Member Author

Right, we already dropped testing 3.2 for that reason some time ago, though it shall still work. We have to update the documentation accordingly.
About 3.3 - unlike in 2.6 and 3.2, there are no language features that are missing or getting in the way, so this can wait.

@hugovk
Copy link
Member

hugovk commented Oct 16, 2017

Yeah, ditching 3.3 isn't so pressing at the moment. There's lots to be gained from dropping 2.6!

@mrbean-bremen
Copy link
Member Author

BTW, here 3.2 is already not mentioned.

@mrbean-bremen mrbean-bremen added this to the v3.4 milestone Nov 2, 2017
@mrbean-bremen mrbean-bremen self-assigned this Nov 13, 2017
mrbean-bremen added a commit to mrbean-bremen/pyfakefs that referenced this issue Nov 13, 2017
jmcgeheeiv pushed a commit that referenced this issue Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants