[issue5747] knowing the parent command

Changes by Éric Araujo : -- resolution: -> out of date stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___

[issue5747] knowing the parent command

Changes by Éric Araujo : -- components: +Distutils2 -Distutils stage: -> needs patch versions: +3rd party -Python 3.2 ___ Python tracker ___ _

[issue5747] knowing the parent command

Changes by Mark Lawrence : -- versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue5747] knowing the parent command

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue5747] knowing the parent command

New submission from Tarek Ziadé : Right now there's no way in a command to know that it was launched as a subcommand from another command. For instance every install_* command knows explicitely that it is launched as a subcommand of 'install' and takes back its options in finalize_options() usin