https://bugzilla.novell.com/show_bug.cgi?id=895102 https://bugzilla.novell.com/show_bug.cgi?id=895102#c2 --- Comment #2 from Rolf Krahl <rolf@rotkraut.de> 2014-09-08 10:46:15 UTC --- The problem with "the right way to use it" is the following: most Python packages are installed using setuptools nowadays. If such a package wants to provide a command line tool, the standard way using setuptools is not to write the Python script, but rather to define an entry point into some Python module. setuptools then generates a wrapper script. This wrapper recursively checks that all requirements (as defined in requires.txt in the egg-info) are installed, loads the module and calls the function named in the entry point. The two-liner in the bug report above is nothing then an explicit call to this recursive check that the wrapper scripts also perform. As a consequence, any package that requires matplotlib and installs a command line scripts using setuptools, will break, if python-nose is not installed, just because nose is listed as a requirement of matplotlib. This is certainly not the only way to use matplotlib. But it is the standard way to use it. On the requirement of python-setuptools: Yes, if some package python-foo installs a command line script using setuptools, then this script needs python-setuptools indeed. But this is then a requirement for python-foo, not for python-matplotlib. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.