Comment 11 for bug 187290

    As far as I am concerned, this is not a bug, it is an installation issue, which can probably be solved by a user.
    I had the same problem myself when switching from Inkscape 45.1 to 46-devel. The problem was at least partly caused by the switch from python24.dll to python25.dll.
    There are two different ways of tackling this : You can try a clean install where you remove all vestiges of the previous install, remove the \Inkscape\python\ directory, remove the \Inkscape\share\extensions\ directory, make sure python.exe is in the path, make sure there are no old .pyc files left lying around.
    Second method is to install Python 2.5.1 for yourself directly off the net.
    I've tried both methods, afaict they both work.
    I would recommend the second method, for the following reason: In the newer versions of 0.46 the file import procedure has been largely taken over by the uniconv utility, which is really cool, but I think it is extremely unlikely that anyone will get uniconv to run on windows unless they have personally installed it for themselves off the net. (This in turn requires that you first have your own installation of Python as well.) At least that has been my experience so far, it is still a work in progress.
    Anyways, to get to the point, I know that in principle these things are all supposed to be included in the package, but in practice you can simplify life a lot by just installing your own copy. It probably should not be necessary to do this, but on the other hand it is a very small price to pay for the added functionality you are getting, just my 2cts worth.