Perhaps, but why make such broad suggestions if the example is pretty clear? At least have the decency to write in your reply that your suggestion is violating the given example. Give the readers a hint that you actually thought about the question and answer and that you didn't just try to get a answer - any anwer - just to say something.

I don't know why anyone whould write a new module, and I don't know what that has to do with the answer. But now we are getting something like:

• Poster: "How do I do X"? Here's an example.
• Reply: Use Y!
• Me: Y doesn't solve X, here look, it does Z.
• You: Yeah, but perhaps the poster wanted to do Z.

I'd think this forum would quickly become useless if all threads go this way.

If you have a solution that doesn't solve the problem, but solves a different one, say so. Don't suggest it solves the problem. That only wastes a lot of time of people.

(As for wanting options to take multiple arguments, without having to repeat the option, I think that's reasonable. I've wanted that in the past as well. The fact that there's a module to parse options in a different way doesn't invalidate the wish to do it otherwise. This is Perl remember, not Python).

Abigail