On Sat, Jul 25, 2015 at 2:48 PM, Michał Górny <mgo...@gentoo.org> wrote: > Dnia 2015-07-25, o godz. 14:24:27 > Davide Pesavento <p...@gentoo.org> napisał(a): > >> On Sat, Jul 25, 2015 at 2:03 PM, Michał Górny <mgo...@gentoo.org> wrote: >> > Dnia 2015-07-25, o godz. 13:37:03 >> > Davide Pesavento <p...@gentoo.org> napisał(a): >> > >> >> On Sat, Jul 25, 2015 at 12:37 PM, Michał Górny <mgo...@gentoo.org> wrote: >> >> > While at it, I also added some 'unsupported' wrappers to ban trying to >> >> > use pythonY (accidental fallback to system python) when pythonX is >> >> > selected via wrapper, and changed the exit code for unsupp-scripts. >> >> >> >> Can you clarify the consequences of this change please? e.g. is it >> >> still possible to call "naked" python2 from src_prepare() of a package >> >> using python-r1.eclass, such as dev-python/sip? >> > >> > If you call python_setup and ensure python2 is selected beforehand, >> > yes. Otherwise, you're doing a QA violation and it never were supported. >> > >> >> Funny. I'm pretty sure you suggested the current implementation >> (directly calling python2) when we first switched to >> python-r1.eclass... > > Nope. I'm pretty sure I never suggested or accepted any kind of direct > dev-lang/python dependencies or python[23] calls. >
Seriously, I'm not blaming you (or anybody else), but please just try to be a little less arrogant and self-righteous in your emails. If you don't believe me, look at your #gentoo-python logs around Jan 21, 2013. Also consider that python_setup was only introduced 9 months after the conversion of dev-python/sip. Anyway, I guess I have to fix sip-4.9999 then ;) Thanks, Davide
