# Dependence on Python 2.7 **URL:** \ **Category:** General Discussion\ **Created:** [May 8, 2025, 9:15pm UTC](https://klipper.discourse.group/t/dependence-on-python-2-7/23343 "2025-05-08T21:15:56Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\ **Post date:** [May 9, 2025, 6:03am UTC](https://klipper.discourse.group/t/dependence-on-python-2-7/23343/7 "2025-05-09T06:03:23Z")
If you look at the script: > It installs Klipper on an rPi which has Octopi running on it - if you read through it, you’ll see that the script itself uses resources that Octopi loaded in for its use (ie Python 2.7). @pigaro If you look at the Klipper master scripts repository: > **[klipper/scripts at master · Klipper3d/klipper](https://github.com/Klipper3d/klipper/tree/master/scripts)** > > Klipper is a 3d-printer firmware. Contribute to Klipper3d/klipper development by creating an account on GitHub. You’ll see that the last time there was updates made to `install-octopi.sh` was four years ago (by Kevin). Since then (actually just less than four years ago) Klipper migration to Python 3.\* started: [Upcoming v0.10.0 Release](https://klipper.discourse.group/t/upcoming-v0-10-0-release/791) Based on these dates and the fact that you seem to be the first person who has issue with `install-octopi.sh` that I can find, I don’t think it’s a viable method for installing Klipper with Octopi. As I am writing this post, I see that @EddyMI3D has provided you with a basic installation and connection workflow for using Octopi with Klipper. This will undoubtedly be the most expedient way for you to get the two software packages working together. --- _[View the full topic](https://klipper.discourse.group/t/dependence-on-python-2-7/23343)._