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
fixer for sys.exitfunc -> atexit #46609
Comments
sys.exitfunc should raise a Py3K warning when set/used. |
A fixer to use the atexit module is needed. |
Actually, a fixer probably won't work since that would require the |
This is going to be very hard to implement without module descriptors. |
On Thu, Aug 21, 2008 at 6:43 AM, Benjamin Peterson
So for every sys import you are going to add an "import atexit"? That |
On Thu, Aug 21, 2008 at 1:21 PM, Brett Cannon <report@bugs.python.org> wrote:
You're right; it's not going to be perfect, but 2to3 could warn when
|
On Thu, Aug 21, 2008 at 11:45 AM, Benjamin Peterson
OK, I can live with that. |
Here's my 2to3 fixer for the cause. It always changes assignment to |
Since yesterday there is a handy little helper that adds imports to I attached a version that does that. However the import adder is not yet as sophisticated as the one in the |
Here is an attempt to add a Py3K warning when sys.exitfunc is modified. |
I've posted to python-dev asking for a reviewer for this, the thread is at http://mail.python.org/pipermail/python-dev/2010-March/098597.html |
Sean, are you referring to the warning or the 2to3 fixer? |
Committed the 2to3 fixer in r79137. |
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: