What were you doing?
Like many of us, I'm trying to work with Python 3 to make sure that my plugins will weather the test of time.
So I setup a standard OctoPi-imaged rig, then basically:
mv ~/oprint ~/oprint.py2virtualenv -p python3 oprintsource oprint/bin/activatepip install --upgrade pippip install https://get.octoprint.org/latest
ERROR: Package 'OctoPrint' requires a different Python: 3.7.3 not in '>=2.7.9,<3'
Interesting fact: For whatever reasons, I've gone through this routine perhaps five times already, testing different scenarios and saving each to their own microSD.
Request
What might be nice is a turnkey OctoPi image which pulls the latest Buster Lite as well as the latest OctoPrint 1.4rc_something_ from the devel branch. In theory, it would still have the classic ~/oprint as the virtual environment location, just with Python 3.7.3 instead of Py2 throughout. Kudos if it's Pi4-friendly.
So basically—and with some instructions for how to pull this—one would:
- Use Etcher to pull from some URL this IMG
- Do the standard
/boot/octopi-wpa-supplicant.txt thing
- Boot it up
Remoting in would reveal a vanilla OctoPrint installation, just now Python 3—savvy.
I would suggest that this would benefit people in the plugin development space in the interim period before OP 1.4 is released.
What did you expect to happen?
I'd forgotten that we don't get Python 3 support until 1.4 which isn't released to master yet. But I suppose I naively expected this to work.
What happened instead?
The scenario requires the would-be tester to be able to install some as-yet-released OctoPrint version on the devel branch.
Did the same happen when running OctoPrint in safe mode?
N/A
Version of OctoPi
Presumably it would have been 1.3.11 at that point for OctoPrint and this would have been the daily build which includes Buster.
Printer model & used firmware incl. version
N/A
Screenshot(s)/video(s) showing the problem:
N/A
I have read the FAQ.
What were you doing?
Like many of us, I'm trying to work with Python 3 to make sure that my plugins will weather the test of time.
So I setup a standard OctoPi-imaged rig, then basically:
mv ~/oprint ~/oprint.py2virtualenv -p python3 oprintsource oprint/bin/activatepip install --upgrade pippip install https://get.octoprint.org/latestERROR: Package 'OctoPrint' requires a different Python: 3.7.3 not in '>=2.7.9,<3'Interesting fact: For whatever reasons, I've gone through this routine perhaps five times already, testing different scenarios and saving each to their own microSD.
Request
What might be nice is a turnkey OctoPi image which pulls the latest Buster Lite as well as the latest OctoPrint 1.4rc_something_ from the
develbranch. In theory, it would still have the classic~/oprintas the virtual environment location, just with Python 3.7.3 instead of Py2 throughout. Kudos if it's Pi4-friendly.So basically—and with some instructions for how to pull this—one would:
/boot/octopi-wpa-supplicant.txtthingRemoting in would reveal a vanilla OctoPrint installation, just now Python 3—savvy.
I would suggest that this would benefit people in the plugin development space in the interim period before OP 1.4 is released.
What did you expect to happen?
I'd forgotten that we don't get Python 3 support until 1.4 which isn't released to
masteryet. But I suppose I naively expected this to work.What happened instead?
The scenario requires the would-be tester to be able to install some as-yet-released OctoPrint version on the
develbranch.Did the same happen when running OctoPrint in safe mode?
N/A
Version of OctoPi
Presumably it would have been 1.3.11 at that point for OctoPrint and this would have been the daily build which includes Buster.
Printer model & used firmware incl. version
N/A
Screenshot(s)/video(s) showing the problem:
N/A
I have read the FAQ.