Skip to content

Drop support for Inkscape < 1 - #31660

Draft
QuLogic wants to merge 3 commits into
matplotlib:mainfrom
QuLogic:min-inkscape
Draft

Drop support for Inkscape < 1#31660
QuLogic wants to merge 3 commits into
matplotlib:mainfrom
QuLogic:min-inkscape

Conversation

@QuLogic

@QuLogic QuLogic commented May 12, 2026

Copy link
Copy Markdown
Member

PR summary

This version was released in 2020, which should be sufficiently long enough to have reached development machines.

AI Disclosure

None

PR checklist

Comment on lines -174 to -178
# Old versions of Inkscape (e.g. 0.48.3.1) seem to sometimes
# deadlock when stderr is redirected to a pipe, so we redirect it
# to a temporary file instead. This is not necessary anymore as of
# Inkscape 0.92.1.
stderr = TemporaryFile()

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, it appears that this comment may be incorrect. It works for me locally with 1.4.3, and on older Ubuntu 22.04 with 1.1.2, but times out with Ubuntu 24.04 that has 1.2.2

@tacaswell

Copy link
Copy Markdown
Member

appveyor failure looks like a hang halfway through, restarted that job.

@QuLogic

QuLogic commented May 13, 2026

Copy link
Copy Markdown
Member Author

Hmm, I'll have to test if the AppVeyor hang is a code change, or because of the new Inkscape.

@QuLogic
QuLogic marked this pull request as draft May 15, 2026 19:12
@QuLogic

QuLogic commented Jul 29, 2026

Copy link
Copy Markdown
Member Author

Comparing the builds logs against a working one, the new Inkscape seems to make tests 10-15% slower up until we get a little under 30% of the way through. Then reaching up to 40%, it's 23% slower, and then it skyrockets to barely reaching 42% tests before AppVeyor kills it.
Figure_1
I've initially thought it might be stuck on one process with other tests running, until each one hits an SVG test getting stuck, and all of them end up getting stuck eventually. But AppVeyor is running on 1 process only.

I will try out some older versions.

@QuLogic

QuLogic commented Jul 31, 2026

Copy link
Copy Markdown
Member Author

So even 1.0.2 times out, though it's not nearly as slow. I'll try one more time with the same version we were using before, but from Chocolately and see how that goes for comparison.

It is stuck on 0.91, which is 11 years old.
This version was released in 2020, which should be sufficiently long
enough to have reached development machines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants