Message 108656 - Python tracker

Message108656

Author	r.david.murray
Recipients	LambertDW, eric.araujo, ggenellina, kszawala, r.david.murray, terry.reedy, vstinner
Date	2010-06-26.00:02:55
SpamBayes Score	3.1327854e-05
Marked as misclassified	No
Message-id	<1277510577.1.0.193607876163.issue4640@psf.upfronthosting.co.za>
In-reply-to

Content
I thought the OP might be saying that -debug didn't throw an error in 2.6. test_optparse doesn't seem to have a test for this, so I wrote one. But as far as I can see the correct error (invalid option -e, given that 'd' is defined) is thrown. In 2.5, as well. Rereading the initial post I understand the problem: his 'd' option takes an argument. So 'ebug' becomes the option value, and thus no error is thrown. Which is working as designed (that's how single letter options that take arguments usually work in Unix) So, it is correct that this is not a bug.

Content

I thought the OP might be saying that -debug didn't throw an error in 2.6.  test_optparse doesn't seem to have a test for this, so I wrote one.  But as far as I can see the correct error (invalid option -e, given that 'd' is defined) is thrown.  In 2.5, as well.

Rereading the initial post I understand the problem: his 'd' option takes an argument.  So 'ebug' becomes the option value, and thus no error is thrown.  Which is working as designed (that's how single letter options that take arguments usually work in Unix)

So, it is correct that this is not a bug.

History
Date	User	Action	Args
2010-06-26 00:02:57	r.david.murray	set	recipients: + r.david.murray, terry.reedy, ggenellina, vstinner, LambertDW, eric.araujo, kszawala
2010-06-26 00:02:57	r.david.murray	set	messageid: <1277510577.1.0.193607876163.issue4640@psf.upfronthosting.co.za>
2010-06-26 00:02:55	r.david.murray	link	issue4640 messages
2010-06-26 00:02:55	r.david.murray	create