Contrary to setuptools-0.6.30 the first revision tries to pull in Python3.2 which I've masked here. I do have Python2.7 and Python3.3 installed here but have masked Python-3.{1,2}. I have setuptools-0.6.30 installed here with this configuration. But I cannot emerge setuptools-0.6.30-r1 since it wants to pull in Python3.2. The line PYTHON_COMPAT=( python{2_5,2_6,2_7,3_1,3_2,3_3} pypy{1_8,1_9} jython2_5 ) suggests it would install for Python3.3 What am I missing? Thanks, Helmut.
You should set PYTHON_TARGETS="python2_7" in make.conf. The default value for this is PYTHON_TARGETS="python2_7 python3_2", as set in your profile. We probably should have posted the relevant news item before converting such a well-used package. Sorry for the confusion.
(In reply to comment #1) > You should set PYTHON_TARGETS="python2_7" in make.conf. > > The default value for this is PYTHON_TARGETS="python2_7 python3_2", as set > in your profile. > > We probably should have posted the relevant news item before converting such > a well-used package. Sorry for the confusion. Please elaborate. I do want Python3.3. And setuptools are installed for Python3.3 with the non -r1 version. There are quite same packages which fail to install because they are not compatible with Python3.3 but unfortunately they don't even install the Python2.7 files. I'll generate a bug for each of them. So, should I try PYTHON_TARGETS="python2_7 python3_3" here? Many thanks, Helmut.
Ah, sorry, I missed that bit. To use python3.3, you'll first need to unmask the python_targets_python3_3 use flag: mkdir -p /etc/portage/profile echo "-python_targets_python3_3" >> /etc/portage/profile/use.mask Then set PYTHON_TARGETS="python2_7 python3_3" in make.conf.
Also, you may find the user guide useful [1]. If it doesn't explain it clear enough, please tell me and I'll do my best to improve it. [1]:http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml
(In reply to comment #4) > Also, you may find the user guide useful [1]. If it doesn't explain it clear > enough, please tell me and I'll do my best to improve it. > > [1]:http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml (In reply to comment #3) > Ah, sorry, I missed that bit. > > To use python3.3, you'll first need to unmask the python_targets_python3_3 > use flag: > > mkdir -p /etc/portage/profile > echo "-python_targets_python3_3" >> /etc/portage/profile/use.mask > > Then set PYTHON_TARGETS="python2_7 python3_3" in make.conf. Hi Mike, the packages dev-python/docutils dev-python/pandas dev-python/pygobject dev-python/shiboken dev-python/pyside dev-python/pyside-tools dev-python/pyfits sci-libs/scipy don't like Python3.3 and therefore don't even install the files for Python2.7 Do I have to toggle between two version of make.conf, one with python3_3 in PYTHON_TARGETS and one without? --- The following packages are especially annoying since they make emerge hang when executing python3.3 setup.py build -b build-3.3 hangs with These are dev-python/pyenchant dev-python/pyudev dev-python/requests Shall I create a bug report for each of them? Thanks, Helmut.
(In reply to comment #5) > the packages > dev-python/docutils > dev-python/pandas > dev-python/pygobject > dev-python/shiboken > dev-python/pyside > dev-python/pyside-tools > dev-python/pyfits > sci-libs/scipy > > don't like Python3.3 and therefore don't even install the files for Python2.7 > > Do I have to toggle between two version of make.conf, one with > python3_3 in PYTHON_TARGETS and one without? > They are restricted to versions 3.2 and below. We are waiting for upstream to release versions which are compatible with python3.3. Also, these packages are still using the old python eclass, which does not utilize PYTHON_TARGETS. You would have to eselect python3.2 to install them. eselect python set --python3 python3.2 If you want to test python3.3, I still suggest setting your system python3 interpreter to python3.2 (see above). You can then set the undocumented USE_PYTHON variable to force packages to be installed for 3.3 as well. The following settings in make.conf would be optimal: # python-r1.eclass PYTHON_TARGETS="python2_7 python3_2 python3_3" # python.eclass (legacy code) USE_PYTHON="2.7 3.2 3.3" > --- > > The following packages are especially annoying since they make emerge hang > when executing > python3.3 setup.py build -b build-3.3 hangs with > > These are > dev-python/pyenchant > dev-python/pyudev > dev-python/requests > > There are already bug reports for these 3 packages.
I think there's nothing more we can do here.
