[issue9563] optparse: bad exception handling when giving no value to an option requiring one

R. David Murray added the comment: Thanks for the confirmation. -- resolution: -> out of date stage: unit test needed -> committed/rejected status: open -> closed ___ Python tracker ___

[issue9563] optparse: bad exception handling when giving no value to an option requiring one

Gwendal LE BIHAN added the comment: I confirm. Fixed in Python 2.7. I didn't have Python 2.7 installed since it's not in the Ubuntu repository yet. -- ___ Python tracker ___

[issue9563] optparse: bad exception handling when giving no value to an option requiring one

R. David Murray added the comment: 2.6 no longer receives bug fixes now that 2.7 is out. Is this still a problem in 2.7? (My testing indicates that it isn't.) -- nosy: +r.david.murray stage: -> unit test needed ___ Python tracker

[issue9563] optparse: bad exception handling when giving no value to an option requiring one

Changes by Gwendal LE BIHAN : -- title: bad exception handling when giving no value to an option requiring one -> optparse: bad exception handling when giving no value to an option requiring one ___ Python tracker