$ ls -latr /usr/lib64/python2.7/site-packages/setuptools total 548 -rw-r--r-- 1 root root 1821 Mar 28 15:55 extension.py -rw-r--r-- 1 root root 35222 Mar 28 15:55 dist.py -rw-r--r-- 1 root root 6370 Mar 28 15:55 depends.py -rw-r--r-- 1 root root 2094 Mar 28 15:55 compat.py -rw-r--r-- 1 root root 6609 Mar 28 15:55 archive_util.py -rw-r--r-- 1 root root 5033 Mar 28 15:55 __init__.py -rw-r--r-- 1 root root 714 Mar 28 15:55 windows_support.py -rw-r--r-- 1 root root 293 Mar 28 15:55 utils.py -rw-r--r-- 1 root root 981 Mar 28 15:55 unicode_utils.py -rw-r--r-- 1 root root 8044 Mar 28 15:55 ssl_support.py -rw-r--r-- 1 root root 2389 Mar 28 15:55 site-patch.py -rw-r--r-- 1 root root 138 Mar 28 15:55 script.tmpl -rw-r--r-- 1 root root 201 Mar 28 15:55 script (dev).tmpl Maybe both *.tmpl files are crap?
What is wrong with it? It seems like a perfectly legal file name to me.
https://bitbucket.org/pypa/setuptools/commits/90d6e15a0f5601f1f086d456bd01c835a9a10d65
Thanks for the commit links, that brought me to https://bitbucket.org/pypa/setuptools/issue/134 That guy is joking.
Oh, you are referring to spaces and parens in filenames. That's certainly nothing broken; you are just misusing your tools. portage supports such filenames without any issue.
Well, while reporting this here I really thought the "script (dev).tmpl" file was installed by mistake. The commit you found explained it is intentionally named in this way and I can only hope it is to be installed under that name. I agree wrapping filenames in shell by quotes is a good practice but there are ton's of proggram which do NOT do the right thing. My point (in the bitbucket issue) is that we should not create such nasty filenames at first. Do Requirements of setuptools say they cannot be installed onto an MS-DOS filesystem? Either way, admittedly not a Gentoo issue. Thanks.
(In reply to Martin Mokrejš from comment #5) > Do Requirements of setuptools say they cannot be installed onto an MS-DOS > filesystem? I just can't resist responding to this bad example. ^_^ Python does not run on DOS. Any modern OS capable of mounting a FAT filesystem also has support for spaces in file names. Anyway, I agree with the upstream dev in that it really does not make sense to change the file name because somebody might run a broken shell command/script. The shell script(s) need fixing, not the python package.
*** Bug 622138 has been marked as a duplicate of this bug. ***
