Melon Mouse

> I actually found https://github.com/marketplace/actions/test-reporter to solve this issue. It doesn't natively support the XML results that Unity outputs yet, but that's apparently in the works, and a [workaround](https://github.com/dorny/test-reporter/issues/98#issuecomment-867106931) was...

For me, skipped/inconclusive tests were simply counted as passed. As a very ugly hacky workaround, I added the following to my yml right after the `Transform NUnit3 to JUnit` step:...

Potentially, https://github.com/ImageMagick/ImageMagick/issues/3599 is related.

I was unable to reproduce this bug when using ImageMagick 7.1.0-37 Q16-HDRI x86_64 b65d0d9af:20220605 `magick in.png out.gif`.

Ah thanks for the clarification! I guess I read over those because "The save/load method supports the following options:" looks to me to be a part of the header above/below...

How about the following? I think the thing you propose is already a big win for readability of the docs, but maybe this is a bit neater. ``` The :py:meth:`~PIL.Image.Image.save`...

Suppose a user wants to set an exif tag, I presume they would want to set the data using a human readable tag name.

> > A nicer solution would be to switch to an enum with the right values, but this is the quick win. > > Could you expand on this? Using...

To elaborate a bit more. **Currently** ```python exif_data = Image.Exif() exif_data[0x123456] = '2020:01:01 00:00:00' image.save(filename, exif=exif_data.tobytes()) ``` People have to manage how to keep it readable themselves. Their options include...

Whenever adding anything to an API, it is important to think about a potential future cost of deprecating it again. Deprecation of the old approach would be costly indeed. It...