self-operating-computer icon indicating copy to clipboard operation
self-operating-computer copied to clipboard

[PROBLEM] problem during pip install

Open bruwy opened this issue 1 year ago • 12 comments

Describe the bug

While attempting to install the “self-operating-computer” package using the command “python3 -m pip install self-operating-computer”, I encounter an error related to the numpy version 1.26.1. Despite successfully installing various other versions, the 1.26.1 version consistently fails during installation, causing errors every time.

Steps to Reproduce

  1. just running the command.

Screenshots

Screenshot 2024-12-19 at 1 31 55 PM

Additional context

Running on macOS Sequoia, on a M3 Macbook

bruwy avatar Dec 19 '24 16:12 bruwy

I experienced the same problem.

kobor42 avatar Dec 25 '24 19:12 kobor42

any update on this issue? facing the same one here

agupagu avatar Jan 04 '25 11:01 agupagu

Same as well, getting the same issue - macOS Sequoia v15.1

mccormjt avatar Jan 07 '25 04:01 mccormjt

If I use the "--no-deps" flag I can bypass this an get it installed successfully, but then then the "operate" command gives me this error ModuleNotFoundError: No module named 'prompt_toolkit'

mccormjt avatar Jan 07 '25 05:01 mccormjt

Tried again on windows PC using WinGM Terminal and got the same exact issue :/ If there is anything I can do to help debug let me know!

mccormjt avatar Jan 07 '25 07:01 mccormjt

To solve this you will need to use Python 12, it happens if you are using Python 13.

GFerreiroS avatar Jan 20 '25 22:01 GFerreiroS

Using pip to install doesn't work for me too, but I feel like mine is a different error so I made a new issue

kk-spartans avatar Mar 12 '25 13:03 kk-spartans

you need to use a downgraded version of python3. I used 3.11.0

AnkaEnginSBHIS avatar Mar 18 '25 00:03 AnkaEnginSBHIS

I have both tried installing 3.12 and 3.11 versions and it still says the same for me.

Isaczzon avatar Apr 15 '25 21:04 Isaczzon

I have both tried installing 3.12 and 3.11 versions and it still says the same for me.

3.12 worked for a while for me until I got hut with a dependency error that wouldn't go away even in venvs. Just get pyenv or pyenv-win and try different python versions until this is fixed, 3.9 worked for me (even though some deps couldn't use it).

Ironic part is that this just randomly happens (afaik), so pretty hard to find the problem.

kk-spartans avatar Apr 16 '25 11:04 kk-spartans

I have both tried installing 3.12 and 3.11 versions and it still says the same for me.

you need to setup your global version to 3.11.0 using pyenv. Also, make sure that your python venv is using 3.11.0 because if you made the venv before setting 3.11.0 to global, then the venv will be on a different version. So I would suggest setting your global python version to 3.11.0 using pyenv, and the creating a new python venv to install the program and install the requirements inside of.

AnkaEnginSBHIS avatar Apr 16 '25 17:04 AnkaEnginSBHIS

I have both tried installing 3.12 and 3.11 versions and it still says the same for me.

you need to setup your global version to 3.11.0 using pyenv. Also, make sure that your python venv is using 3.11.0 because if you made the venv before setting 3.11.0 to global, then the venv will be on a different version. So I would suggest setting your global python version to 3.11.0 using pyenv, and the creating a new python venv to install the program and install the requirements inside of.

I will say that your response was the solution to the problem. Now I am on next issue #166. Getting closer to get it to work though 👍

Isaczzon avatar Apr 21 '25 20:04 Isaczzon