Closed andrei-a-papou closed 4 years ago
From what I can see from here, the most obvious reason for this error is that your Python version does not match the Python specifier from the package (Python >= 3.7
).
Actually, I did not test my script with other versions. I am going to release a new version, less restrictive about Python version. Let me know if you have any other problem. Thanks for the feedback.
Can you please give me your Python version?
I just tried with Python 3.5. Unfortunately I used some features that are not available before Python 3.7 (for example the auto
from the enum
package).
If you want to make it Python 3.5 compatible, PRs are welcome :wink: (or I will do it when I'll time) To run from a local repo:
pip install .
@AlexisBRENON thanks for a prompt response!
My python version is:
python3 -V
Python 3.5.3
So you are probably right, it's a version issue. Unfortunately, I know very little python3 to submit a PR :)
I'll keep an eye on this repo, though, and wait for an update, whenever it comes. Thanks again!
I just made a new release which is Python3.5 compatible (from what I tested). You should be able to install it now. Let me know if you encounter other issues.
By the way, you should probably not use a virtualenv to install it, or you will be not able to use it easily (you will have to activate your virtual environment before calling the entrypoint).
Alexis, thank you. It installs now and seems to run great.
Windows are moved smoothly and seamlessly, much nicer and with no flicker compared to the homegrown xdotool
- and wmctrl
-based script that I currently use.
I will switch to move-to-monitor
now and report any errors or suggestions.
Again, thanks a lot!
Hello, and thank you for this utility. I'd love to try it out, but am currently unable to install.
Running Debian Stretch here.
I can't install locally, only in a virtual environment. Setting it up as usual:
The result is:
I tried upgrading
pip
inside the virtualenv and try again, but it also failed:I would appreciate any pointers on how to proceed at this point. Either fixing the virtualenv installation, or maybe running it from a local cloned repo?
Thank you.