| 1 |
On Sat, Jul 25, 2015 at 2:03 PM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> Dnia 2015-07-25, o godz. 13:37:03 |
| 3 |
> Davide Pesavento <pesa@g.o> napisał(a): |
| 4 |
> |
| 5 |
>> On Sat, Jul 25, 2015 at 12:37 PM, Michał Górny <mgorny@g.o> wrote: |
| 6 |
>> > While at it, I also added some 'unsupported' wrappers to ban trying to |
| 7 |
>> > use pythonY (accidental fallback to system python) when pythonX is |
| 8 |
>> > selected via wrapper, and changed the exit code for unsupp-scripts. |
| 9 |
>> |
| 10 |
>> Can you clarify the consequences of this change please? e.g. is it |
| 11 |
>> still possible to call "naked" python2 from src_prepare() of a package |
| 12 |
>> using python-r1.eclass, such as dev-python/sip? |
| 13 |
> |
| 14 |
> If you call python_setup and ensure python2 is selected beforehand, |
| 15 |
> yes. Otherwise, you're doing a QA violation and it never were supported. |
| 16 |
> |
| 17 |
|
| 18 |
Funny. I'm pretty sure you suggested the current implementation |
| 19 |
(directly calling python2) when we first switched to |
| 20 |
python-r1.eclass... |
Archives