The problem is that you have always done it wrongPython is not quite Python on a pi5.
There is the complication of needing to use a VENV which does seem to trip an awful lot of people up.
This bad practice of mixing distribution packages with directly installed modules via PIP has led to many problems, some of which were very difficult to recognize.
This is not Python's fault. This is a new chip that works completely differently than the previous one. The most commonly used library RPi.GPIO has been provided by a developer who, as far as I know, has nothing to do with the RPi Foundation.And don't forget the python libraries that worked on all previous models of pi that don't work on the 5.
I'm thinking mainly of gpio. That trips lots of folks up too...
Blame the Docs of RPi, but not Python!
Statistics: Posted by DeaD_EyE — Mon Mar 24, 2025 8:53 am