[Python-Dev] How to help out with PEP 3108 (original) (raw)
Guilherme Polo ggpolo at gmail.com
Mon May 12 04:25:42 CEST 2008
- Previous message: [Python-Dev] How to help out with PEP 3108
- Next message: [Python-Dev] How best to handle the docs for a renamed module?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2008/5/11 Brett Cannon <brett at python.org>:
I have tried to update PEP 3108 (http://www.python.org/dev/peps/pep-3108/) as best as I can to list what needs to be done for each module in order to get it removed if there is some extra step. The ones without comment most likely need no special work and thus I can take care of really quickly myself (have it down to instinct at this point). But anything with special needs I would appreciate the help in dealing with. I have also tried to make the steps necessary to deal with the various modules as clear as possible in the PEP itself.
Although I created issue 2775 to track stuff, it is probably wiser to create individual issues for the modules that require any form of work to deal with. Just make sure that if you do that you make it a dependency in issue 2775 (and if you can, list it in the PEP). I would like to not have to hold up the betas just because of this PEP, but I don't know if I can finish the PEP completely on my own. So help is appreciated. Thanks to anyone who can help (or who already have)! -Brett
Hi Brett,
I've sent a patch regarding the move of Tkinter to the tkinter package. But I'm in doubt about stub modules for this case, I'm not sure if using lib-old is good for Tkinter specifically, since lib-tk is included in sys.path. How should I proceed on this ?
-- -- Guilherme H. Polo Goncalves
- Previous message: [Python-Dev] How to help out with PEP 3108
- Next message: [Python-Dev] How best to handle the docs for a renamed module?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]