-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
Does ccbench still require 2.6 compatibility? #89801
Comments
At the top of Tools/ccbench/ccbench.py is this comment dating from 2010 (probably in the initial version): # This file should be kept compatible with both Python 2.6 and Python >= 3.0. Is there still a need for 2.6 compatibility in what is essentially a test script? There are probably only a few changes necessary to remove 2.x compatibility, but it seems odd to retain them when even the Python library documentation no longer has versionchanged/versionadded directives referencing Python 2.x. |
Lukasz, is 'delete it' the no-brainer it seems to be? |
CCbench was mentioned recently in the discussion about Sam Gross's nogil branch: I'm not convinced that deleting it is a no-brainer. Maybe if it landed somewhere generally useful (pyperformance?). |
By 'it' I meant the comment and 2.6 compatibility you asked about. |
ccbench was removed in #101853 |
Closing since this 2.6 is EOL and ccbench was removed. Thanks for digging up old issues that can be closed! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: