k
k
The chronology of actions taken on this PR and OP not showing interest in improving their submission is fascinating, in any case. Guess I wasn't too far off with what...
@bzczb Thanks for the submission – I don't have time to review its actual contents, but saw it didn't pass the formatting checks. Could you update the formatting?
Please always code format any code snippets you include in your issues to make it easier for others to parse them. You can either type the formatting out yourself –...
Code blocks require 3 backticks at the start of the block and 3 at the end, just FYI.
Please always include code samples in the form of code-formatted text, not screenshots. Images of code are very bad practice, see e.g. other platforms like StackOverflow and similar, where this...
Please always include your specs like we ask for in our issue templates – MoviePy version, platform used etc. – to help pinpoint what causes your problem, thanks.
The first sentence in the linked PR says (emphasis mine): > When using **recent** Pillow, a deprecation warning occurs Is MoviePy currently using this particular version of Pillow? Or is...
I just found PR #2072 which links to a commit (not a PR) which looks like it's solving a similar – or potentially the same – issue, though the other...
Ok, found it, was apparently already merged: #2003 – is your fix another fix on top of that one?
Please always include your specs like we ask for in our issue templates – MoviePy version, platform used etc. – and code-format code samples to improve readability, thanks.