-
Notifications
You must be signed in to change notification settings - Fork 413
Description
Hello PyAV maintainers,
I've noticed some changes in the PyAV ecosystem that have left me confused about the current state of the project, particularly regarding its relationship with BasswoodAV. I'd greatly appreciate some official clarification on the following points:
Project Status and Ownership
I've observed that PyAV documentation is now hosted at pyav.basswood-io.com, and the installation instructions on PyPI refer to a GitHub repository at https://github.com/basswood-io/PyAV.git. This suggests a transition from the PyAV-Org organization to basswood-io.
- Is BasswoodAV a rebranding of PyAV, a fork, or a continuation of the same project under new management?
- What is the current status of this repository (PyAV-Org/PyAV) compared to the basswood-io/PyAV repository?
Package Naming and Recommendations
There appears to be multiple ways to install what seems to be the same or similar functionality:
- pip install av (older PyPI package)
- pip install pyav (current PyPI package)
- Potentially pip install basswood-av (if this exists)
For users who want to use FFmpeg bindings in Python:
- Which package should we be using going forward?
- Will all packages continue to be maintained, or is there a preferred/recommended option?
Documentation
- Will documentation continue to be available at both the original PyAV domain and the new basswood-io domain?
- Is there a plan to redirect or consolidate documentation to avoid confusion?
Compatibility Considerations
- Are there any breaking changes between PyAV and BasswoodAV that users should be aware of when migrating?
- Will code written for PyAV continue to work with BasswoodAV without modification?
I appreciate any clarification you can provide on these matters. This information would be very helpful for current PyAV users who are trying to understand the best path forward.
Thank you for your time and for maintaining this valuable project.