(please keep Guilherme CCed)

On Saturday 23 January 2010 11:54:57, Benjamin MAISONNAS wrote:
> Well, even after reinstall python-wicd (just in case), here is what I get :
> 
> [..]
>
> I tried to check exactly which module is imported by python, see :
> st...@localhost:~$ python -c "import wicd.wpath; print wicd.wpath"
> <module 'wicd.wpath' from
>  '/usr/lib/python2.5/site-packages/wicd/wpath.pyc'>

Oh, here's the culprit.

$ LANG=C ls -d /usr/*/python*.*/*-packages/wicd*
ls: cannot access /usr/*/python*.*/*-packages/wicd*: No such file or directory
$

> [..]
> So, it seems that the wrong module (an older version maybe) is
> imported, my python setup may be wrong or something. I didn't mess
> with it in the past though.

I suspect this has something to do with python-support.
What version do you have?
What happens if you purge python-wicd, and then reinstall it?

Also, see:

$ dpkg -c ../../build-area/wicd_1.6.2.2-4_all.deb |grep python
drwxr-xr-x root/root         0 2010-01-23 11:28 ./usr/share/python-support/
-rw-r--r-- root/root       879 2010-01-23 11:28 ./usr/share/python-
support/wicd.private
$

i.e. there's no pythonX.Y/*-packages in the 1.6.2.2-4 package, thus I don't 
think it's some old file staying around.

Kindly,
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|----
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to