| 1 |
On Sat, 11 May 2013 11:51:39 -0400 |
| 2 |
Mike Gilbert <floppym@g.o> wrote: |
| 3 |
|
| 4 |
> On Sat, May 11, 2013 at 5:30 AM, Michał Górny <mgorny@g.o> |
| 5 |
> wrote: |
| 6 |
> > Fixed naming the proper default sub-phase and declaring 'edefault' |
| 7 |
> > in python_prepare_all(). |
| 8 |
> > --- |
| 9 |
> |
| 10 |
> I think I prefer to explicitly name the function I want to call, so I |
| 11 |
> don't really see any great benefit here. I'm not strongly opposed to |
| 12 |
> it, but I don't see myself using it either. |
| 13 |
|
| 14 |
Same here for the reason you mention below. Long term I expect it to be |
| 15 |
more of a hassle than typing a few additional letters now. |
| 16 |
|
| 17 |
> Also, how would this interact with other eclasses which may define a |
| 18 |
> similar "edefault" function? Packages using distutils-r1 don't often |
| 19 |
> utilize other phase-happy eclasses, but I'm sure it will happen |
| 20 |
> eventually. |
| 21 |
> |
Archives