413315 – games-util/nml-0.2.3 doesn't compile: missing setuptools

Bug 413315 - games-util/nml-0.2.3 doesn't compile: missing setuptools

Summary: games-util/nml-0.2.3 doesn't compile: missing setuptools

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Games (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Games

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-04-24 00:34 UTC by Mark Wagner
Modified:	2012-05-15 14:51 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mark Wagner 2012-04-24 00:34:44 UTC

I've got Python 2.7 and Python 3.2 installed with Python 3.2 as the default; this is the standard situation for new installs of Gentoo.  Attempting to emerge nml-0.2.3 gives the following output:

>>> Compiling source in /var/tmp/portage/games-util/nml-0.2.3/work/nml-0.2.3 ...
python2.7 setup.py build
Traceback (most recent call last):
  File "setup.py", line 5, in <module>
    from setuptools import setup
ImportError: No module named setuptools

This happens because dev-python/setuptools only installs the setuptools module for Python 3.2.

Reproducible: Always

Comment 1 Tomáš Chvátal (RETIRED) gentoo-dev

2012-04-24 07:09:45 UTC

And I should do what with yet again completely broken python.

Afaik also python should still default to 2.x.

Comment 2 Arfrever Frehtes Taifersar Arahesis 2012-04-24 16:21:49 UTC

Bug reporter forgot to run python-updater.

Comment 3 Mark Wagner 2012-05-01 20:12:49 UTC

(In reply to comment #2)
> Bug reporter forgot to run python-updater.

That fixed it.

It sounds like the Python ebuild needs to be changed.  Right now, the ebuild only tells you to run python-updater if you've *upgraded* Python, and I didn't -- I installed Python 2.7 when I already had 3.2 installed.  The ebuild should tell you to run python-updater any time you've installed a new slot version of Python.

Comment 4 Kacper Kowalik (Xarthisius) (RETIRED) gentoo-dev

2012-05-15 14:51:28 UTC

(In reply to comment #3)
> (In reply to comment #2)
> > Bug reporter forgot to run python-updater.
> 
> That fixed it.

Not a bug then :)

> It sounds like the Python ebuild needs to be changed.  Right now, the ebuild
> only tells you to run python-updater if you've *upgraded* Python, and I
> didn't -- I installed Python 2.7 when I already had 3.2 installed.  The
> ebuild should tell you to run python-updater any time you've installed a new
> slot version of Python.

This is slightly beyond the scope of this bug. However, with the changes that are currently being implemented that ought to get better over time.