[issue5747] knowing the parent command

2014-03-13 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- resolution: - out of date stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5747 ___

[issue5747] knowing the parent command

2010-11-25 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- components: +Distutils2 -Distutils stage: - needs patch versions: +3rd party -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5747 ___

[issue5747] knowing the parent command

2010-07-11 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5747 ___

[issue5747] knowing the parent command

2010-04-08 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5747 ___ ___ Python-bugs-list mailing

[issue5747] knowing the parent command

2009-04-13 Thread Tarek Ziadé
New submission from Tarek Ziadé ziade.ta...@gmail.com: 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