Pip install rpaframework not working

WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘NewConnectionError(’<pip._vendor.urllib3.connection.HTTPSConnection object at 0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it’)’: /simple/setuptools/
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Any lead would be a great help…

Are you using our tooling to setup your environment, or did you run into this problem on manual setup?

Are you behind some firewall/proxy that could be blocking your connection. If so, see this documentation: Firewall and network proxy requirements

1 Like

yes, on manual setup.
pip install rpaframework is not working but other libraries are working(pandas,numpy,openpyxl etc)

Which pip and python versions are you running?
The bug reason behind using RCC and the recommended conda.yaml is to also control the versions of these two as they can cause all sorts of problems.

BR, Kari

Python version=3.9.10(current version),
pip version=22.1.2,
we tried with python 3.10 but didn’t work.

The installation seems to work when using rcc and conda.yaml
…so calling rcc ht vars conda.yaml where conda.yaml contains the following passes without errors.

- conda-forge
- python=3.9.10
- pip=22.1.2
- pip:
  - rpaframework==15.0.0

…this was on Windows so there could be platform-specific dependencies that are missing wheels for specific python versions that could be causing this, but the error also still points to network problems.

BR, Kari

1 Like

Now the rpaframework got installed and the version is 7.6.0 not the latest one that is 15.0.0
Python version=3.9.10,
pip version=21.3.1

Just to be sure, have you used rcc alongside a conda.yaml containing the deps recommended by @Kari above? If not, can you provide more details about the manual process you’re doing to prepare the environment for the robot? (and why aren’t you running the bot through rcc)

We strongly recommend using our tooling and having a valid robot structure: Your first .robot

Right now we are trying to install all the packages and for rpaframework an old version got installed instead of latest(15.0.0) .Is it Ok to work with 7.6.0 version?

Can you please share you conda.yaml?

And are you using our tooling? If not, I highly recommend you do, so that you can get rid of these problems which come when you try to manually manage environments.

Normally these kind of problems come from using dependencies, that conflict, so dependency resolution can only resolve to something old.

And of course you can use what ever old version you want, but I would not recommend that, because there are many major versions after that old version.

I think the key things we need to know and can help on are:

  • What packages are you installing?
  • How are you installing them?
  • Are you locking down version numbers?

…if you are not using rcc and conda.yaml you are definitely missing out on quite a bit, as it is built to avoid these “works on my machine” -cases. RCC does not care what you have installed on your machine but rather creates an isolated environment for your bot.

v7.6.0 is really out-of-date for rpaframework and the fact that you are getting that version suggests that you have some dependency collisions or some local cache is providing that version for you.

I’d say the quickest test you can run is the following (assuming you are on Windows):

curl -o rcc.exe https://downloads.robocorp.com/rcc/releases/latest/windows64/rcc.exe
rcc create example
..select "Standard Robot Framework template"
cd example

…then put your dependencies in the conda.yaml and

rcc run

This tells if the problem is between the dependencies of your bot OR is some setup on your machine breaking the dependency resolution.

BR, Kari