Jonas Camillus Jeppesen

I have no experience with ```go install``` and ```go get```, so I forked the project and changed ```code.google.com/p/gcfg``` to ```gopkg.in/gcfg.v1```, which is where that package is migrated to according to...

Sure, I'll have a look at it one of the coming days. The package needs a new release and have for some time https://github.com/sphinx-contrib/images/issues/33 .

How days turns to weeks ... I've outlined the tasks which needs completion to do a new release, this is obviously on the todo-list since it is required for newer...

@TriangleBear @boryssmejda A PR to fix CI / testing would be very welcome. Since this PR apparently looked good to merge mid 2024 CI / testing has stopped working (I...

Much of the CI work is actually handled in https://github.com/sphinx-contrib/images/pull/41 . But maybe it jumps the gun on newer spinx and python versions or maybe everything will be fine if...

@TriangleBear @j9ac9k I've tested merging #41 followed by merging #39 in this branch https://github.com/sphinx-contrib/images/tree/pr3941 and everything looks good (https://github.com/sphinx-contrib/images/actions/runs/14230225566). Would you test https://test.pypi.org/project/sphinxcontrib-images/0.9.5rc1/ to see if everything is working as...

@j9ac9k Good question, should the commit from this PR be cherry-picked into #41, or should this be rebased on a branch with #41 merged? I think I'm leaning towards cherry-picking...

@j9ac9k If this PR and #41 did not exist, someone looking at the problem today would have done the equivalent of cherry-picking I belive. Iteratively trying to deal with new...

@j9ac9k Thank you for your contribution, it has been incorporated into the project by being cherry picked into #41 : https://github.com/sphinx-contrib/images/commit/8c72db8a978b0c870d3787c99d23634581f4169e

@jack1142 Great idea. I think I'll wait to reach out though, hoping a contributor will invite him-/herself.