➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2008-03-22 21:29 by benjamin.peterson, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| change_py3kwarning.patch | benjamin.peterson, 2008-03-22 21:29 | |||
| change_py3kwarning2.patch | benjamin.peterson, 2008-04-18 21:23 | |||
| Messages (4) | |||
|---|---|---|---|
| msg64339 - (view) | Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2008-03-22 21:29 | |
This patch removed sys.py3kwarning and adds sys.getpy3kwarn, sys.enablepy3kwarn, and sys.disablepy3kwarn with docs. I also changed the places in the Lib which used sys.py3kwarning. |
|||
| msg64565 - (view) | Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2008-03-26 20:46 | |
Raising priority so this is looked at before we release 2.6. :) |
|||
| msg65625 - (view) | Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2008-04-18 21:23 | |
As suggested by Christian, this patch changes the method names to setpy3kwarn and getpy3kwarn. |
|||
| msg70470 - (view) | Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2008-07-31 02:06 | |
I guess this isn't going anywhere... |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:32 | admin | set | github: 46710 |
| 2008-07-31 02:06:09 | benjamin.peterson | set | status: open -> closed resolution: rejected messages: + msg70470 versions: + Python 2.7, - Python 2.6 |
| 2008-04-18 21:23:19 | benjamin.peterson | set | files:
+ change_py3kwarning2.patch nosy: + christian.heimes messages: + msg65625 |
| 2008-03-26 20:46:00 | benjamin.peterson | set | priority: critical messages: + msg64565 |
| 2008-03-22 21:29:04 | benjamin.peterson | create | |