-
-
Notifications
You must be signed in to change notification settings - Fork 255
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
"setuptools" and "pkg_resources" usage #417
Comments
Thanks for opening this issue, a maintainer will get back to you shortly! In the meantime:
|
@olk-m Thank you for bringing up these important points regarding the use of ProblemYou're correct that relying on
SolutionInstead of adding a runtime dependency on
|
Discussions are not enabled for this repository and I do not want to create too much noise by opening a new issue. I could contact you via email, but maybe this comment will be useful for someone. There are two use cases:
In case you will need that, also added you as a collaborator. |
@alessio-locatelli Thanks for this great suggestion! This would indeed be valuable for developers using vidgear. I really appreciate your initiative in creating a setup and adding me as a collaborator. Could you open a dedicated issue for this? It'll help us track and discuss the addition properly. Looking forward to working on this! |
I want to discuss two things:
1. Expecting
from pkg_resources import parse_version
to be resolved may be a mistake.Explanation:
from pkg_resources import parse_version
requiressetuptools
, butsetuptools
is missing by default in Debian and Fedora Docker images.Possible solutions:
ImportError
and do not check versions.setuptools
manually on their side.setuptools
to thevidgear
mandatory dependencies.parse_version
function.I can submit a PR, but I want to hear your opinion.
2.
DeprecationWarning
If in my first question you will decide to keep using this function, the import should be updated.
VidGear Version
0.3.3
Python version
3.12.4
Operating System version
fedora:40 Docker image
The text was updated successfully, but these errors were encountered: