On Wed, Oct 5, 2011 at 11:50 AM, ~suv <suv-sf@...58...> wrote:
On 5/10/11 19:49, Nikita Kitaev wrote:
On Mon, Oct 3, 2011 at 2:17 PM, ~suv <suv-sf@...58...> wrote:
Besides python versions the only other feature I worry about is launching an Inkscape subprocess to do some conversions. A simple test would be to draw a rectangle and export the file. Correct behavior is to launch another Inkscape window that converts the rectangle to a path. Incorrect behavior includes failing to run the "inkscape" command.
Launching another instance of Inkscape from the python script in a subprocess does work with the osx-packaged application bundle - other extensions, (e.g. 'Arrange > Restack') use it too, though without gui because they don't need to use verbs.
The Mac OS X Lion problem isn't something I can fix. I'll worry about that system once the bug is resolved.
Leopard is another question. Does the code run if all the "except ExceptionName as e" statements are replaced with "except ExceptionName, e"? If syntax is the only problem I can fix it.
AFAICT it's simply a syntax error in Python 2.5.1 - export and preparing for export works without failure in the osx-packaged Inkscape.app (0.48.2) and Python 2.5.1 after applying the small change as you described (see attached diff). The diff also includes a fix for the vim modeline (else current vim complains when opening the the script).
hth, ~suv
Good to hear! Hopefully that takes care of all the Python 2.5 incompatibilities. Thanks for the patch.
I posted a merge proposal on launchpad. If anyone has feedback on the code I can make changes.
I think something should be done about the "Prepare for Export" menu option. It adds another menu that 99% of people won't need. Any ideas where I can put it? (I could remove it altogether, of course. It's just a convenience, and I don't really know how useful it is.)
~Nikita