Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getopt error doesnot display correct error #65693

Closed
priya mannequin opened this issue May 13, 2014 · 2 comments
Closed

getopt error doesnot display correct error #65693

priya mannequin opened this issue May 13, 2014 · 2 comments
Labels
type-bug An unexpected behavior, bug, or error

Comments

@priya
Copy link
Mannequin

priya mannequin commented May 13, 2014

BPO 21494
Nosy @ericvsmith

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2014-05-13.15:01:36.299>
created_at = <Date 2014-05-13.12:41:29.042>
labels = ['type-bug', 'invalid']
title = 'getopt error doesnot display correct error'
updated_at = <Date 2014-05-13.15:01:36.299>
user = 'https://bugs.python.org/priya'

bugs.python.org fields:

activity = <Date 2014-05-13.15:01:36.299>
actor = 'eric.smith'
assignee = 'none'
closed = True
closed_date = <Date 2014-05-13.15:01:36.299>
closer = 'eric.smith'
components = []
creation = <Date 2014-05-13.12:41:29.042>
creator = 'priya'
dependencies = []
files = []
hgrepos = []
issue_num = 21494
keywords = []
message_count = 2.0
messages = ['218447', '218449']
nosy_count = 2.0
nosy_names = ['eric.smith', 'priya']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21494'
versions = ['Python 2.7']

@priya
Copy link
Mannequin Author

priya mannequin commented May 13, 2014

i created command from getopt but it gives error if i give single hyphan in long option
it should check long option not in small option.

eg. hello -foo
-o option is not recognized

hello --foo is working fine.

@priya priya mannequin added the type-feature A feature request or enhancement label May 13, 2014
@ericvsmith
Copy link
Member

That's working as designed. It allows you to say "-fo" if both 'f' and 'o' are short options.

@ericvsmith ericvsmith added invalid type-bug An unexpected behavior, bug, or error and removed type-feature A feature request or enhancement labels May 13, 2014
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

1 participant