list of things that they changed and possible reasons it could break
Seconding this. For ex. "To solve the bug in the transform tool, I also had to touch code shared by the move tool, so please also test that the move tool still works". Ideally, developers would make it a habit to document this in the tickets when they close them so the info could be easily collated.

Two things:

OK, I'm done. Let me know if you put it online so I can give it one last read with the propper formatting.

Should this really go into the 4.2 branch, seeing that it breaks compatibility with Python 2?

Typo in the first sentence: paintaing -> painting

I just tested this and it works. I can see the use of this. What do other people think of this feature? I like how little space the docker takes. Would be neat if the "S" button had a tooltip.

Seeing that this would be importing the attributes from where they are documented to be found, and seeing how we've established that this works on several platforms, I'd like to push this anyway.

It doesn't crash! This is a comparison between normal dogde (left) and logarithmi dogd (right). I have no idea if this is correct. Burn is analogous, in that the logarithmic version turns out very black.

I'm not sure how strict we are with this stuff in the C++ code, but you introduced a couple of trailing whitespaces:

I've already added a flake8 config and instructions to run it, and my plan was to squash the flake8 warnings bit by bit and have a bit of an eye on the code, and bring up any issues worth discussing as I find them, such as right now the line lengths (and keep notes for documenting the stuff). From what I've seen so far from the existing plugins and the ones I've written myself, I don't expect much else that's going to be controversial, or an issue with Krita plugins specifically, regarding PEP8.

Added comments.

You know, I should probably add some comments.

OK, I submitted my developer application.

Btw, it's also possible to provide an additional version of the mock krita module on github. Since pip can install Python packages from directly from github, that would be an easy way for developers of external plugins to write unit tests.

Ooops, I didn't know you need to update a review request with the full patch. Squashed both commits (the original and the typo fix).

Fix typo

I don't have push access. I should probably have mentioned that. ;)