-
Notifications
You must be signed in to change notification settings - Fork 141
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
More Python Version Support #7
Comments
I see little point in supporting Python 2.6. 2.7 is backwards compatible so anyone should just upgrade. There could be some cases where upgrading is a problem, but that's a problem that will solve itself given some time. So I won't make any serious efforts to support Python 2.6, I will, however, accept pull requests toward it, given they don't spoil Python 2.7 experience. As for Python 3, supporting it will require some interface overhaul to be consistent with new "iterator by default" paradigm. Still I'm planning to add this in some near future. |
Cool. I'll see if I can contribute some Python 2.6 fixes. I do agree with cheers James Mills / prologic E: prologic@shortcircuit.net.au On Thu, Nov 21, 2013 at 1:52 PM, Alexander Schepanovski <
|
I know there's a Python 3.3 Issue already (Issue #1) but I'd like to see support for Python 2.6 as well. I don't think it's unreasonable to support Python 2.6, 2.7, 3.3 and PyPy? I've tested funcy against Python 2.7 and PyPY 2.2 successfully so far.
The text was updated successfully, but these errors were encountered: