Alan McKinnon wrote: > Agreed. The elog message strikes me as merely an enthusiastic endorsement of > cool shiny new stuff from an over-zealous maintainer who doesn't quite grasp > how slow traction can be in the real world
While that may be true, and even though he did make a few mistakes in the beginning, arfrever has been doing a tremendous job getting Python "back on track". In particular, he added the possibility to have Python packages install their modules into multiple Python slots, a much needed feature that makes testing software with multiple Python versions much easier. So, going back to the initial question, you could just emerge Python 3.1, enable it in USE_PYTHON in make.conf, but leave 2.6 as a default. From this point, all packages that support 3.1 will be installed for 3.1 as well, and the day you want to switch, you'll just be able to enable it and very few packages will need to be rebuilt. I have 2.4, 2.5, 2.6 and 3.1 in my USE_PYTHON, with 2.6 as default, and it's been working great for a few months now. Or you could just ignore the message. It probably won't make a difference if you don't need multiple Python versions. -- Remy
signature.asc
Description: OpenPGP digital signature
