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
Add configure option to disable Py3k warnings #49612
Comments
The attached patch adds a --with-py3k-warnings option to configure. 2to3 (translate 2to3's source tree five times): Django (render a 150x150 table 100 times): Spitfire (render a 1000x1000 table 100 times): Unpickle (unpickling a list of 8000 dicts 100 times): Build env: gcc 4.3.1 x86_64 on Linux 2.6.18 (Core2 Duo) |
I would like to understand the problem better first. I find it hard to |
s/Leaving/Turning/ in configure.in. It looks like the convention for other --with flags that default to "Trade away speed for Py3k compat warnings" is a bit harsh for a 1.5% |
Jeffrey: updated the patch to address your concerns. Martin: I'm not sure I completely understand it either, though it seems I'm not 100% convinced that something like this should go into CPython, |
Bah, forgot to run autoreconf. Fixed. |
Given the very small benefits, I don't think there's any point in making this a configuration variable. A hardcoded flag would be sufficient, and expert users would be able to recompile their Python (as with the FAST_LOOPS flag). |
I'm with Antoine on this one. Also, instead of removing the flag completely which will cause problems with extensions relying on it, I'd suggest to just disable the PyErr_WarnPy3k(msg, stacklevel) macro and turn it into a no-op if a compile time variable DISABLE_PY3K_WARNINGS (or similar) is defined (which should be undefined per default). |
Since this issue doesn't apply in Python 3 and (as I understand it) the 2.7 branch is only open to bug fixes, can we close this performance issue? |
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: