Thank you for the explanation, Bryce and Mattia! But until 2020, this
should be solved, as far as I understand, regardless of this? We've only
got 2 hackfests until then... time flies.

I found that these depend on python scripts, but there may be more, hope
others will fill in the blanks (I've also got no clue of how easy or
hard it's to port these):

- several python export and import routines (that use extensions, e.g.
save as optimized SVG via scour (how's scour doing with Python3,
@Eduard?), dxf. What about uniconvertor? Does it have a python3
version?... We don't include it, but it needs to work with the rest...
:-/ Or I think there was talk about dropping it...?

- the customizable templates (those with dots in the 'New from Template'
dialog).

- everything aside from Tutorials in the Help menu (probably very quick
to port, if anything needs to be done at all)

- couldn't find what 'prepare_file_save_as.py' is currently used for,
weirdly - but I think it was needed for export to dxf...

- there seem to be several i18n-generation scripts in various
subdirectories of the /share/... directory tree - guess they are used to
internationalize the svg files (filters, markers,...) there

- several packaging scripts, for win and some Cmake scripts

- (extension tests)

- dpi switcher extension (not needed when opening files, intended for
switching manually later)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to