Skip to content

Remove unused/deprecated AVConv_ classes #18666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Remove unused/deprecated AVConv_ classes #18666

wants to merge 2 commits into from

Conversation

Tranquilled
Copy link
Contributor

PR Summary

Removes AVConvBase et al. and a related method in FFMpegBase that refers to a deprecated Ubuntu release. The deprecation warnings (which raise errors during tests) say that these classes will be removed by version 3.5, and they don't seem to be used by any other code in this version.

PR Checklist

  • Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (run flake8 on changed files to check).
  • New features are documented, with examples if plot related.
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • Conforms to Matplotlib style conventions (install flake8-docstrings and pydocstyle<4 and run flake8 --docstring-convention=all).
  • New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

@QuLogic
Copy link
Member

QuLogic commented Oct 5, 2020

3.4 is not out yet, so unfortunately, this cannot be done until then.

Copy link
Member

@QuLogic QuLogic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things deprecated in 3.3 cannot be removed until 3.5.

@Tranquilled
Copy link
Contributor Author

Things deprecated in 3.3 cannot be removed until 3.5.

That's fair. Can I just leave the branch here until then? I notice that the circleCI tests are failing, anyway.

@QuLogic
Copy link
Member

QuLogic commented Oct 5, 2020

Sure, but you would need to fix the doc build before it is eventually merged.

@QuLogic
Copy link
Member

QuLogic commented Oct 6, 2020

Also, removals should get an API note.

@jklymak jklymak marked this pull request as draft October 6, 2020 00:41
@jklymak
Copy link
Member

jklymak commented Oct 6, 2020

I'm not clear how we resurface this whenever 3.5 comes out....

@dopplershift
Copy link
Contributor

By milestoning for 3.5?

@dopplershift dopplershift added this to the v3.5.0 milestone Oct 6, 2020
@jklymak
Copy link
Member

jklymak commented Oct 6, 2020

Fair - I wasn't sure what our milestone guidelines were.

@QuLogic
Copy link
Member

QuLogic commented Apr 6, 2021

This can go in now, but it needs an API note.

@QuLogic
Copy link
Member

QuLogic commented Jul 6, 2021

Thanks for the PR, but this was complete in #20465.

@QuLogic QuLogic closed this Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants