One thing we'd need to consider is that some more or less basic Inkscape functionality currently relies on Python extensions, e.g. - Several templates - Help links although I already wondered if this was even really necessary - I assume there are better solutions available to open a link from GTK - Export/Import extensions They are not strictly Inkscape core but a lot of users are not aware they might be running an extension to export to their favorite format.
Second important questions is if this would only affect packaging or if we really want to split out the extension code from the Inkscape source repository into a more or less self sufficient sub-project. In the latter case I fear that the bundled extensions - which are in a pretty desolate state even now - might bit-rot even faster (less users, less developers having the repo on their radar, less obvious affiliation with the core program). If we could achieve to make the extensions into a "community project" (that is a lot more user driven, allowing easy contributions and additions of new extensions with well-organized categorization and documentation) that could also improve upon the status-quo but as a start this would require a "core team" of people who would be willing to do the necessary maintenance (not sure we have that right now...). -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
