[gentoo-python] Re: [PATCH] Do not call the dummy no-op default phases.

[Mike Gilbert]

On Tue, Jan 8, 2013 at 3:36 PM, Michał Górny <mgorny@g.o> wrote:
> This just causes a severe amount of unnecessary output.
> ---
>  gx86/eclass/distutils-r1.eclass | 6 ------
>  1 file changed, 6 deletions(-)
>
> diff --git a/gx86/eclass/distutils-r1.eclass b/gx86/eclass/distutils-r1.eclass
> index f52ffbd..fd3e856 100644
> --- a/gx86/eclass/distutils-r1.eclass
> +++ b/gx86/eclass/distutils-r1.eclass
> @@ -454,8 +454,6 @@ distutils-r1_src_prepare() {
>         _distutils-r1_multijob_init
>         if declare -f python_prepare >/dev/null; then
>                 python_foreach_impl distutils-r1_run_phase python_prepare
> -       else
> -               python_foreach_impl distutils-r1_run_phase distutils-r1_python_prepare
>         fi
>         multijob_finish
>  }
> @@ -464,8 +462,6 @@ distutils-r1_src_configure() {
>         _distutils-r1_multijob_init
>         if declare -f python_configure >/dev/null; then
>                 python_foreach_impl distutils-r1_run_phase python_configure
> -       else
> -               python_foreach_impl distutils-r1_run_phase distutils-r1_python_configure
>         fi
>         multijob_finish
>
> @@ -496,8 +492,6 @@ distutils-r1_src_test() {
>         _distutils-r1_multijob_init
>         if declare -f python_test >/dev/null; then
>                 python_foreach_impl distutils-r1_run_phase python_test
> -       else
> -               python_foreach_impl distutils-r1_run_phase distutils-r1_python_test
>         fi
>         multijob_finish
>
> --
> 1.8.1
>

Makes sense.