Closed ray-grointel closed 2 years ago
I recognize that the latest version pyvirtualdisplay==0.2.5
doesn't have this issue; but older version users, and current version users who version-lock PyVirtualDisplay
in their setups may have issues in the future.
See also #47
I think if PyVirtualDisplay version is locked then EasyProcess version should be also locked. PyVirtualDisplay and EasyProcess are compatible if they are upgraded at the same time. There may be problem if the dependency (EasyProcess) is upgraded only, but I think it is not a bug.
I think if PyVirtualDisplay version is locked then EasyProcess version should be also locked. PyVirtualDisplay and EasyProcess are compatible if they are upgraded at the same time. There may be problem if the dependency (EasyProcess) is upgraded only, but I think it is not a bug.
I agree with you, but not all people know they should upgrade easyprocess if they want to make all test cases pass. So I guess there should be some warning or other msg in pyvirtualdisplay to notify tester they should use right version. :)
"...not all people know they should upgrade easyprocess if they want to make all test cases pass..."
If you have a test case which doesn't pass then please send information about it. (use case,code,error message,versions)
I merged pull requests for both on conda-forge, conda would take care to upgrade a dependency too if a rule was added. I would only add >= rules. An exact fixation can someone else do for his own package.
A new version of
EasyProcess
(v0.3) was released. https://pypi.org/project/EasyProcess/#history, that has removed deprecated functionscheck
andcheck_installed
. See: https://github.com/ponty/EasyProcess/commit/a75d640 and https://github.com/ponty/EasyProcess/commit/8f410e0This is now breaking PyVirtualDisplay (v0.2.1):