dev-lang/python-2.6.3 has a PDEPEND for =dev-lang/python-3*. The Changelog for 2.6.3 has no mention of this, nor is there any reference on this site (bugs). This is a pretty big deal, to me at least, given that python is threaded so heavily through my system. This is tremendously frustrating, to have such a large change with no mention for the reason, at the very least in Changelog. I'm going to attempt a build with the PDEPEND commented out, but having no idea of the reason behind the change leaves me flying blind regarding the impact of removing the PD. And yes, I know, zero-day and all that. Consider this a frustrated user's request to be more attentive to Changelog entries. The sum total of 2.6.3 references in Changelog is: *python-2.6.3 (02 Oct 2009) 02 Oct 2009; Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.org> +python-2.6.3.ebuild: Version bump. Reproducible: Always Steps to Reproduce:
NOTE: This is assuming that >python-3 is masked on your system. The suggested fixes are temporary and should only be used for the quick fix. I'm not going to put up a patch here. Just toss out the workaround until this issue is addressed, or is in fact permanent and it turns out that we actually now do need to install python-3. It looks like the workaround of commenting out the: =dev-lang/python-3*" lines from the ebuilds for each of these files is a workaround, until the ebuilds are fixed: dev-lang/python-2.6.3 dev-python/setuptools-0.6.3-r3 dev-python/sip-4.8.2-r1 NOTE: If you remove or comment the line mentioned above, be sure to add a " to the end of the preceding line. In addition, in the sip ebuild, comment the line: epatch "${FILESDIR}/${P}-python-3.patch"
Having Python 3 installed is one of required steps in transition to Python 3. Python 2 is still used as default version after installation of Python 3. Transition to Python 3 is mandatory for all users of Python. (In reply to comment #1) > In addition, in the sip ebuild, comment the line: > > epatch "${FILESDIR}/${P}-python-3.patch" The change in this patch is compatible with Python 2.
Re: The patch. Mea culpa on that one. Re: The bigger issue: As a user, I have to say that I am tremendously frustrated. I can't seem to find any information regarding the python 3 transition. Is there some place I should be looking for this sort of announcement or discussion that I'm not aware of? The statement that "...Transition to Python 3 is mandatory for all users of Python..." is nerve-wracking, given the lack of any reference to such a discussion or roadmap, any idea of time frame. py3k is a long way from being ready for prime time. Changes that require it are a big surprise, particularly given that the changes seems arbitrary and unnecessary, especially when there's no indication as to the whys of the change. Please, PLEASE offer users _some_ kind of indication of what the heck is going on, einfo, Changelog, bug tracker, heck, even on the python herd wiki. I consider myself a little bit of an advanced user. I do try to go the extra mile before I rant like this. All that said, consider all those users who _don't_ have the time or the experience to go even the extra few yards. Just throw us a bone and let us feel like we're actually a consideration here. Please.
Why not give the users a choice about python3 (as long as its virtually not used anywhere) and use a use flag to select the dependency on python3? Sooner or later everyone will have to install python3 anyway, but till then it's still a long way to go. (I for my part got python3 installed (why not, it just eats a little harddisk space ad if i want to play with it it's there), what bothers is the switching up- and downgrade of packages because of strange (in my understanding) masks of packages.)
(In reply to comment #2) > Having Python 3 installed is one of required steps in transition to Python 3. Then what's the point of the python3 USE flag? When I set -python3, I do NOT want to see ANY python-3* unless I emerge a package that actually needs it. You do a lot of good things for Gentoo and I am grateful for that, but in this case you really might want to reconsider your force-feeding policy.
While I agree that the transition to Python 3 is imminent, I would really appreciate some kind of information on how it is supposed to work. Here are some things I would like to know: - Is Python 3 ever going to be invoked if my default python is 2.6 because the latest version is for Python 3 only? If yes, then why isn't it that those packages depend on Python 3? If not, why do I need Python 3 if it is unused? - Is it at all possible to run the system with Python 3 set as default? If not, how will I know when it is possible? What percentage of packages are "python3-ready"? - Will Python 2 be eventually phased out? PLEASE, provide us with some information, so we at least know what's going on!
QA thoughtlessly decided to break dependencies and cause more problems for users.
Thank you for making this change. As a user, it's a lot more comfortable to receive a heads up from the ebuild than to panic when there are cascades of failures. Anyway, I do appreciate the change. Thank you. (In reply to comment #7) > QA thoughtlessly decided to break dependencies and cause more problems for > users. >
