Fix libavformat compatiblity break

[B3QL]

FFmpeg/FFmpeg@b7251ae

Close #1714

• I have provided code that clearly demonstrates the bug and that only works correctly when applying this fix
• I have added suitable tests demonstrating a fixed bug or new/changed feature to the test suite in tests/
• I have properly documented new or changed features in the documentation or in the docstrings
• I have properly explained unusual or unexpected code in the comments around it

[mondeja]

Thank you!

[coveralls]

Coverage remained the same at 84.789% when pulling 2464359 on TraseeHQ:bugfix/1714-fix-ffmpeg-infos-parse into 551e265 on Zulko:master.

[B3QL]

@mondeja thanks for the review, I fixed flake8 and rebased with master after #1770

[mondeja]

Great, thank you! 👍

[B3QL]

Thanks for the quick feedback loop! Do you have some ETA for the next release?

[mondeja]

Do you have some ETA for the next release?

No idea, I haven't rights in PyPI for this project so I can't release it. I'm just installing from master or refs using GIT urls.

[B3QL]

No idea, I haven't rights in PyPI for this project so I can't release it. I'm just installing from master or refs using GIT urls.

I'm doing the same ;) but would be nice to have a regular release from time to time. The last official release was 1 year ago (2020-05-07).

@tburrows13 is there an ETA for the next release? Can you also consider granting PyPI access for @mondeja since he is actively maintaining the project?

[tburrows13]

Hello, thanks both for your contributions!

Basically I had a plan for future pre-releases and the v2.0 release (most of which is written in #1089) but a few of the tasks that were blocking the next release never got completed and my life got even more busy! I'm still interested in returning and finishing those tasks - hopefully at the end of June, but it won't be before then.

I do have PyPI access myself but not enough to grant @mondeja access, that would need @Zulko. Or wait a month or so until I can do the next pre-release.

[B3QL]

Basically I had a plan for future pre-releases and the v2.0 release (most of which is written in #1089) but a few of the tasks that were blocking the next release never got completed and my life got even more busy! I'm still interested in returning and finishing those tasks - hopefully at the end of June, but it won't be before then.

Thanks for your contributions so far! It's understandable that the side OSS project is often time-consuming and it's harder to commit more free time over time.

The end of June looks decent, keeping my finger crossed ;) Any clue about the date for the 2.0.0 release? Or what needs to be delivered until it can be shipped? (I saw the road map #1089)

I do have PyPI access myself but not enough to grant @mondeja access, that would need @Zulko. Or wait a month or so until I can do the next pre-release.

Waiting a month or more it's not a problem here. I see it more as a way of reducing the bus factor and enabling people that want to get more involved. The project is very successful - 15,233 repositories use it, 9.2k stars and it would be great to have some regular releases.

@Zulko please consider sharing more power and responsibility with current contributors, thanks!

[tburrows13]

Before v2.0.0, as far as I remember it is the 2 outstanding things from #1089 (comment) and the documentation rework (which I think I nearly finished). The original comment in #1089 had some more things but I don't think that they're as important and I'd be happy to release without them.