On 01/26/2014 04:29 AM, Jakub Wilk wrote: > * Thomas Goirand <z...@debian.org>, 2014-01-26, 03:50: >> - No file shipped into /usr/lib/python2.x/dist-packages (well, 2.7 for >> Sid, and 2.x if you consider an eventual backport). Now, I'm saying: >> "sorry what?" like on your 1st mail. This breaks the package for >> everybody (and not "only my case"). > > It has always worked for me. Now what?
Now, try this: zigo@host # sudo dpkg -i python-concurrent.futures_2.1.6-1_all.deb (Reading database ... 108371 files and directories currently installed.) Preparing to unpack python-concurrent.futures_2.1.6-1_all.deb ... Unpacking python-concurrent.futures (2.1.6-1) over (2.1.6-1) ... Setting up python-concurrent.futures (2.1.6-1) ... Processing triggers for python-support (1.0.15) ... zigo@host # python Python 2.7.6 (default, Jan 11 2014, 14:34:26) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import futures Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named futures I'm however confused how "import concurrent" works, even if there's nothing in /usr/lib/python2.7/dist-packages in this package. How come? Thomas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e4243c.2000...@debian.org