making python library paths more flexible

Post and comment on recent Inkscape news.
jocaps
Posts: 5
Joined: Sun Mar 14, 2010 5:34 pm

making python library paths more flexible

Postby jocaps » Mon May 23, 2011 1:06 pm

Hi,

I am working in a project where we make extensive python use as well. And we also have python modules, libs and dlls in a folder in our project. But the cool thing is that, if we delete this python folder and supposing we already installed python in your system, then our software is able to use that python. This is good for me because it avoids congestion in my system. Currently there are so many softwares with python dependencies and half of these software fortunately run alone even if you delete their python folders and have already python installed in your system (of course some of them have some extra modules in their python directories so I usually copy them into my main python directory). We don't overwrite the syspath we append to it. Now I tried this on inkscape 4.8 (I was assuming it uses python 2.6.4). But half of the functionalities won't work if you do that (even if I have all the modules in inkscape python copied into my python). Could this not be implemented in inkscape.. or even maybe inkscape asks the users on setup where I have python installed. I almost have a full python installation on half of my softwares that are python dependent and I find that a little... But if the workload for doing this a bit too much then of course this wish is not so serious.

User avatar
tomh
Posts: 218
Joined: Sat Feb 14, 2009 10:14 pm

Re: making python library paths more flexible

Postby tomh » Mon May 23, 2011 7:56 pm

Do you mean that no extensions work at all? or that some do? Also, are any other functions not related to extensions not working,

Just for reference, these are the windows libraries that Inkscape is currently built against: http://bazaar.launchpad.net/~inkscape.d ... readme.txt .


Return to “News, Events & Developments”