[issue11061] Verify command option before parsing config file

Changes by Éric Araujo : -- type: behavior -> performance ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue11061] Verify command option before parsing config file

Changes by Éric Araujo : -- resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ P

[issue11061] Verify command option before parsing config file

Éric Araujo added the comment: Well, the setup.cfg could register a command named “wrong”, so d2 really has to parse all config files before rejecting a command. -- ___ Python tracker

[issue11061] Verify command option before parsing config file

Sebastien Douche added the comment: Oups sorry Eric. I created the report very quickly after a discussion with Tarek. If you type a wrong command like "python -m distutils2:run wrong", disutils2 still parses the setup.cfg. How resolve this? Don't know, maybe a migration to optparse. Anyway,

[issue11061] Verify command option before parsing config file

Éric Araujo added the comment: I’m afraid I don’t understand your report. -- versions: +3rd party ___ Python tracker ___ ___ Python-b

[issue11061] Verify command option before parsing config file

New submission from Sebastien Douche : Distutils2 verify command (like sdist) when he use it. A small optimization is add the verification step at launch. -- assignee: tarek components: Distutils2 messages: 127432 nosy: eric.araujo, sdouche, tarek priority: normal severity: normal statu