You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
python -m pip install MaaDebugger
Collecting MaaDebugger
Using cached maadebugger-1.3.5-py3-none-any.whl.metadata (923 bytes)
INFO: pip is looking at multiple versions of maadebugger to determine which version is compatible with other requirements. This could take a while.
Using cached maadebugger-1.3.4-py3-none-any.whl.metadata (901 bytes)
Using cached maadebugger-1.3.3-py3-none-any.whl.metadata (655 bytes)
Using cached maadebugger-1.3.2-py3-none-any.whl.metadata (655 bytes)
Using cached maadebugger-1.3.1-py3-none-any.whl.metadata (655 bytes)
Using cached maadebugger-1.3.0-py3-none-any.whl.metadata (629 bytes)
Using cached maadebugger-1.2.1-py3-none-any.whl.metadata (631 bytes)
Using cached maadebugger-1.2.0-py3-none-any.whl.metadata (557 bytes)
INFO: pip is still looking at multiple versions of maadebugger to determine which version is compatible with other requirements. This could take a while.
Using cached maadebugger-1.1.0-py3-none-any.whl.metadata (423 bytes)
Using cached maadebugger-1.0.0-py3-none-any.whl.metadata (273 bytes)
ERROR: Cannot install maadebugger==1.0.0, maadebugger==1.1.0, maadebugger==1.2.0, maadebugger==1.2.1, maadebugger==1.3.0, maadebugger==1.3.1, maadebugger==1.3.2, maadebugger==1.3.3, maadebugger==1.3.4 and maadebugger==1.3.5 because these package versions have conflicting dependencies.
The conflict is caused by:
maadebugger 1.3.5 depends on MaaFw>=2.0.0b4
maadebugger 1.3.4 depends on MaaFw>=2.0.0a5
maadebugger 1.3.3 depends on MaaFw>=2.0.0a5
maadebugger 1.3.2 depends on MaaFw>=2.0.0a5
maadebugger 1.3.1 depends on MaaFw>=2.0.0a5
maadebugger 1.3.0 depends on MaaFw>=2.0.0
maadebugger 1.2.1 depends on MaaFw>=1.7.3
maadebugger 1.2.0 depends on MaaFw>=1.7.3
maadebugger 1.1.0 depends on MaaFw>=1.7.3
maadebugger 1.0.0 depends on MaaFw
To fix this you could try to:
loosen the range of package versions you've specified
remove package versions to allow pip to attempt to solve the dependency conflict
The text was updated successfully, but these errors were encountered:
python -m pip install MaaDebugger
Collecting MaaDebugger
Using cached maadebugger-1.3.5-py3-none-any.whl.metadata (923 bytes)
INFO: pip is looking at multiple versions of maadebugger to determine which version is compatible with other requirements. This could take a while.
Using cached maadebugger-1.3.4-py3-none-any.whl.metadata (901 bytes)
Using cached maadebugger-1.3.3-py3-none-any.whl.metadata (655 bytes)
Using cached maadebugger-1.3.2-py3-none-any.whl.metadata (655 bytes)
Using cached maadebugger-1.3.1-py3-none-any.whl.metadata (655 bytes)
Using cached maadebugger-1.3.0-py3-none-any.whl.metadata (629 bytes)
Using cached maadebugger-1.2.1-py3-none-any.whl.metadata (631 bytes)
Using cached maadebugger-1.2.0-py3-none-any.whl.metadata (557 bytes)
INFO: pip is still looking at multiple versions of maadebugger to determine which version is compatible with other requirements. This could take a while.
Using cached maadebugger-1.1.0-py3-none-any.whl.metadata (423 bytes)
Using cached maadebugger-1.0.0-py3-none-any.whl.metadata (273 bytes)
ERROR: Cannot install maadebugger==1.0.0, maadebugger==1.1.0, maadebugger==1.2.0, maadebugger==1.2.1, maadebugger==1.3.0, maadebugger==1.3.1, maadebugger==1.3.2, maadebugger==1.3.3, maadebugger==1.3.4 and maadebugger==1.3.5 because these package versions have conflicting dependencies.
The conflict is caused by:
maadebugger 1.3.5 depends on MaaFw>=2.0.0b4
maadebugger 1.3.4 depends on MaaFw>=2.0.0a5
maadebugger 1.3.3 depends on MaaFw>=2.0.0a5
maadebugger 1.3.2 depends on MaaFw>=2.0.0a5
maadebugger 1.3.1 depends on MaaFw>=2.0.0a5
maadebugger 1.3.0 depends on MaaFw>=2.0.0
maadebugger 1.2.1 depends on MaaFw>=1.7.3
maadebugger 1.2.0 depends on MaaFw>=1.7.3
maadebugger 1.1.0 depends on MaaFw>=1.7.3
maadebugger 1.0.0 depends on MaaFw
To fix this you could try to:
The text was updated successfully, but these errors were encountered: