-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
π Release VidGear Stable v0.3.2
#379
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- π Raised `python_requires` to `>=3.8`. Thereby python `3.7` and any before legacy are no longer supported. - π₯ Removed `3.7` legacy from Programming Language metadata. - π©Ή Readded latest patch to `uvicorn`, `starlette`, `mss`, `pyzmq` dependencies. Docs: - π Updated minimum python to version `3.8` while installing vidgear. - π¨ Updated API-specific dependencies. - βοΈ Fixed hyperlinks.
- β¨ Added python 3.11 legacy support for MacOS environments. - π₯ Deprecated python 3.7 legacy support.
- β¨ Added python 3.11 legacy support for Windows OS environments. - π₯ Deprecated python 3.7 legacy support.
- β¨ Added python 3.11 legacy support for Linux OS environments. - π₯ Deprecated python 3.7 legacy support. - π Migrated python version to 3.9 in deploy_docs.yml workflow.
β¦ython 3.11.x - More information: pytest-dev/pytest#10874
- Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: pytest-dev/pytest#10874
- Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: pytest-dev/pytest#10874
- Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: pytest-dev/pytest#10874
- Temporary fix for AST constructor depth mismatch in pytest on python 3.11.x, More information: pytest-dev/pytest#10874
β¦ixed #369) [#370] π§ Setup.py: - Removed support for python-3.7 legacies - π Raised `python_requires` to `>=3.8`. Thereby python `3.7` and any before legacy are no longer supported. - π₯ Removed `3.7` legacy from Programming Language metadata. - π©Ή Readded latest patch to `uvicorn`, `starlette`, `pyzmq` dependencies. - π Pinned pyzmq==24.0.1. Asyncio: - π©Ή Formatted TemplateResponse class parameters w.r.t new changes. CI: - π· Updated Azure Pipeline workflow. - β¨ Added python 3.11 legacy support for MacOS environments. - π₯ Deprecated python 3.7 legacy support. - π· Updated Appveyor Pipeline workflow. - β¨ Added python 3.11 legacy support for Windows OS environments. - π₯ Deprecated python 3.7 legacy support. -π· Updated GitHub CI Pipeline workflow. - β¨ Added python 3.11 legacy support for Linux OS environments. - π₯ Deprecated python 3.7 legacy support. - π Migrated python version to 3.9 in deploy_docs.yml workflow. - π Temporary fix for AST constructor depth mismatch in pytest on python `3.11.x`, More information: pytest-dev/pytest#10874 - Made temporary fix platform independent. - Extended fix to all Webgear_RTC tests. - βοΈ Increased code coverage. - π Fixed condition logic bug. Maintenance: - β‘οΈ Added GitHub sponsors and dropped liberapay from Funding.yml. Docs: - π Updated minimum python to version `3.8` while installing vidgear. - π¨ Updated API-specific dependencies. - βοΈ Fixed hyperlinks.
- π© Implemented new `kill` argument to `close()` method to forcefully kill ZMQ context instead of graceful exit only in the `receive` mode. - π Updated logging.
β¦d. (Fixes #372) - π©Ή Fixed "mss" backend disabled when `monitor` parameter is not defined. Stabilizer Class: - π₯ Removed redundant code - βοΈ Fixed typos.
β¦ixes #372) - π Updated information related to Supported Dimensional Attributes in ScreenGear docs. - βοΈ Fixed typos and context. - π± Added new asset `screengear_region.png`. - π Fixed missing `compression_mode` flags in WriteGear API docs.
β¦Fixes #374) - β¨ Added new `subscriber_timeout` integer optional parameter to support timeout with `pattern=2` or PUBLISHER-SUBSCRIBER pattern. - π§βπ» Receiver will exit safely if timeout defined(any value(in milliseconds) > 0), and timeout occurs in Receiver Mode with `pattern=2`. - π¨ Note: Default behavior still is to block the thread till infinite time. - π Updated logging.
- β¨ Added a new feature to enable detached subprocess creation on Windows within the WriteGear API. - π§βπ» This enhancement enhances the process management capabilities of the module. - βΏοΈ Use Case: This can be useful while creating an exe file for a python script that uses WriteGear API. On windows even after creating the exe file in windowed mode or no-console mode, the ffmpeg.exe command line window would pop up while its being used by WriteGear API. - π© Added new `ffmpeg_subprocess_creation_window` Boolean flag to enable this feature. - β‘οΈThis feature can be enabled both in logging and silent mode.
- β¨ Added new `-disable_ffmpeg_window` optional Boolean flag to enable patch that prevents FFmpeg creation window from opening when building .exe files on Windows OS. - β‘οΈNote: Now `-disable_ffmpeg_window` optional Boolean flag is only available on Windows OS with logging disabled(`logging=False`) in compression mode. - π© Removed `ffmpeg_subprocess_creation_window` class parameter. - π₯ Disabled this patch for logging mode. - π₯ Removed redundant code. - π Updated logging.
β¦ter in WriteGear.
β¦meter in WriteGear.
**NetGear:** - β¨ Added new `kill` parameter to `close()` method to forcefully kill ZMQ context instead of graceful exit only in the `receive` mode. - β¨ Added new `subscriber_timeout` integer optional parameter to support timeout with `pattern=2` or PUBLISHER-SUBSCRIBER pattern. - π§βπ» Receiver will exit safely if timeout defined(any value(in milliseconds) > 0), and timeout occurs in Receiver Mode with `pattern=2`. - π¨ Note: Default behavior still is to block the thread till infinite time. - π Updated logging. **WriteGear:** - β¨ Added new `-disable_ffmpeg_window` optional Boolean flag to enable patch that prevents FFmpeg creation window from opening when building .exe files on Windows OS. - β‘οΈNote: `-disable_ffmpeg_window` optional Boolean flag is only available on Windows OS with logging disabled(`logging=False`) in compression mode. - π§βπ» This enhancement enhances the process management capabilities of the module. - βΏοΈ Use Case: This can be useful while creating an exe file for a python script that uses WriteGear API. On windows even after creating the exe file in windowed mode or no-console mode, the ffmpeg.exe command line window would pop up while its being used by WriteGear API. - π₯ Disabled this patch for logging mode. - π₯ Removed redundant code. - π Updated logging. **ScreenGear:** - π Fixed swapped region dimensions bug with dxcam backend. - π©Ή Fixed "mss" backend disabled when `monitor` parameter is not defined. **Stabilizer Class:** - π₯ Removed redundant code **CI:** - π· Added kill argument to close() method in various NetGear tests. - π· Updated tests for subscriber_timeout optional Integer parameter in NetGear. - π· Updated tests for disable_ffmpeg_window optional Boolean parameter in WriteGear. - π Fixed NetGear tests bugs. **Docs:** - π Updated information related to Supported Dimensional Attributes in ScreenGear docs. - π± Added new asset `screengear_region.png`. - π Fixed missing `compression_mode` flags in WriteGear API docs. - π Added doc for subscriber_timeout optional Integer parameter in NetGear. - π Added doc for disable_ffmpeg_window optional Boolean parameter in WriteGear. - βοΈ Fixed typos and context.
This was
linked to
issues
Sep 10, 2023
Codecov ReportPatch coverage is
π’ Thoughts on this report? Let us know!. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BUG π
Vidgear api's error, flaw or fault
ENHANCEMENT β‘
New Feature/Addition/Improvement
MAINTENANCE ποΈ
Just sorting things out!
NEW RELEASE π₯
New Release. Yay!
PENDING TESTS π§ͺ
Waiting for CI tests to complete successfully.
WORK IN PROGRESS π§
currently been worked on.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief Description
New vidgear stable release is here that introduces several enhancements, updates, and bug fixes to the codebase.π
Changes:
This PR includes a series of updates and improvements to different parts of the project:
New Features β¨
kill
parameter toclose()
method to forcefully kill ZMQ context instead of graceful exit only in thereceive
mode.subscriber_timeout
integer optional parameter to support timeout withpattern=2
(or Publisher-Subscriber) pattern.pattern=2
.-disable_ffmpeg_window
optional Boolean flag to enable patch that prevents FFmpeg creation window from opening when building.exe
files on Windows OS. (PR by @ibtsam3301)-disable_ffmpeg_window
optional Boolean flag is only available on Windows OS with logging disabled(logging=False
) in compression mode..exe
file for a python script that uses WriteGear API. On windows even after creating the.exe
file in windowed mode or no-console mode, theffmpeg.exe
command line window would pop up while its being used by WriteGear API.3.11.x
legacies.0.3.1
.subscriber_timeout
optional Integer parameter in NetGear.disable_ffmpeg_window
optional Boolean parameter in WriteGear.screengear_region.png
.Updates/Improvements β‘οΈ
uvicorn
,starlette
,pyzmq
dependencies.3.7
legacy from Programming Language metadata.Funding.yml
.3.8
while installing vidgear in docs.3.9
indeploy_docs.yml
workflow.3.7
legacy support.subscriber_timeout
optional Integer parameter in NetGear.disable_ffmpeg_window
optional Boolean parameter in WriteGear.Breaking Updates/Changes π₯
python_requires
to>=3.8
. Thereby python3.7
and any before legacy are no longer supported.Bug-fixes π
monitor
parameter is not defined.compression_mode
flags in WriteGear API docs.3.11.x
, More information: Occasional AST constructor depth mismatchΒ pytest-dev/pytest#10874Requirements / Checklist
Related Issue
#369
#316
#359
#360
#362
Context
VidGear's next milestone release i.e.
v0.3.2
with changes that are required to enhance the library's functionality, improve user experience, address issues and bugs, ensure compatibility with the latest Python version, and maintain the overall quality and reliability of the codebase. They make the library more robust and user-friendly, benefiting both current and future users of the software.Types of changes
Screenshots (if available):
https://abhitronix.github.io/vidgear/v0.3.2-dev/