classification
Title: knowing the parent command
Type: enhancement Stage: needs patch
Components: Distutils2 Versions: 3rd party
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: tarek Nosy List: eric.araujo, tarek
Priority: normal Keywords:

Created on 2009-04-13 15:16 by tarek, last changed 2010-11-26 02:13 by eric.araujo.

Messages (1)
msg85950 - (view) Author: Tarek Ziadé (tarek) * (Python committer) Date: 2009-04-13 15:16
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() using set_undefined_options().

For commands that might be used as subcommands of several commands, we
need to pass the name of the parent command to finalize_options() so 
we can call set_undefined_options() without knowing explicitely the name
of the parent command.

This will be done by adding an optional parameter called
'parent_command', to run_command(), then to ensure_finalized() and to
finalized_options().

The first use case of this will be the check command, that will be used
by "register" and "sdist".

This change will be backward compatible with the existing commands and
ths new parameter optional
History
Date User Action Args
2010-11-26 02:13:21eric.araujosetnosy: tarek, eric.araujo
stage: needs patch
components: + Distutils2, - Distutils
versions: + 3rd party, - Python 3.2
2010-07-11 14:34:07BreamoreBoysetversions: + Python 3.2, - Python 3.1, Python 2.7
2010-04-09 00:27:17eric.araujosetnosy: + eric.araujo
2009-04-13 15:16:40tarekcreate