Movatterモバイル変換

[Python-Dev] Exception Reorg PEP revised yet again

• Previous message:[Python-Dev] Exception Reorg PEP revised yet again
• Next message:[Python-Dev] Exception Reorg PEP revised yet again
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

[Brett]> I can compromise to this if others prefer this alternative.  Anybody> else have an opinion?We're not opinion shopping -- we're looking for analysis.  Py3.0 is notsupposed to just a Python variant -- it is supposed to be better.  It isnot about making compromises -- it is about only making changes that areclear improvements.  First, do no harm.It is an abuse of the PEP process to toss up one random idea afteranother with whimsical justifications, zero research, zero analysis ofthe implications, no respect for existing code, no recognition that thecurrent design is somewhat successful, and contravention of basic designprinciples (Zen of Python).The only thing worse is wasting everyone's time by sticking to theproposals like glue when others take the time to think it through andoffer sound reasons why the proposal is not a good idea.[Aahz]> Googling for "windowserror python" produces 800 hits.  So yes, it does> seem to be widely used.  I'm -0 on renaming; +1 on leaving thingsas-is.Well said.  Squirreling WindowsError away in another namespace harmsexisting code, reduces clarity, and offers no offsetting gains.  It issimply crummy design to take a multi-module, multi-application exceptionand push it down into a module namespace.+0 on renaming; +1 on leaving as-is.Raymond

• Previous message:[Python-Dev] Exception Reorg PEP revised yet again
• Next message:[Python-Dev] Exception Reorg PEP revised yet again
• Messages sorted by:[ date ][ thread ][ subject ][ author ]