On 12/03/10 13:05, Michał Górny wrote: > The first question that comes into my mind is -- why do we need > to communicate that? I think that USE_PYTHON is a pretty specific > variable which should be used only if specially required (i.e. to keep > multiple Python versions ready for use). > > What needs to be fixed IMO is the default value of that variable. > If you already disabled switching the active Python version by default, > you should also make the Python eclass base its' USE_PYTHON defaults > on the active Python version.
USE_PYTHON hits people when emerging a new 2.x slot. Say they have 2.6 installed and add 2.7 to that. I agree, that its default value may need re-consideration. After that, patches to the python eclass are needed. Depending on how fast we can fix that, communicating status quo before that may still help reduce user frustration. Especially as we have an unmasked 2.7.1 in tree for a few days now. >> - mentioning in 'man make.conf' > > Not related. We don't describe VIDEO_CARDS, LIRC_DEVICES etc. in that > file too. Yes, but that's USE_EXPAND stuff - USE_PYTHON is different, at least at the moment. You may still be right, though. Sebastian
