Install on Latest Bullseye

[mpv1953]

I am trying to install bright pi on a PiZero 2W with Bullseye (32bit). I am getting the following messages:

---

SetuptoolsDeprecationWarning: setup.py install is deprecated.

---

Please avoid running setup.py directly.
Instead, use pypa/build, pypa/installer or other standards-based tool

---

EasyInstallDeprecationWarning: easy_install command is deprecated.

---

I am not experienced enough to work around these issues. Can you assist?
Thanks,
Mike V

[tvoverbeek]

on my 32-bit Bullseye it installs without problems..
Here is the log from the install:

tvo@rpi32-deb11:~ $ git clone https://github.com/PiSupply/Bright-Pi.git
Cloning into 'Bright-Pi'...
remote: Enumerating objects: 116, done.
remote: Counting objects: 100% (16/16), done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 116 (delta 3), reused 11 (delta 1), pack-reused 100
Receiving objects: 100% (116/116), 10.59 MiB | 7.85 MiB/s, done.
Resolving deltas: 100% (40/40), done.
tvo@rpi32-deb11:~ $ cd Bright-Pi/
tvo@rpi32-deb11:~/Bright-Pi $ sudo python3 setup.py install
running install
running build
running build_py
creating build
creating build/lib
creating build/lib/brightpi
copying brightpi/brightpilib.py -> build/lib/brightpi
copying brightpi/__init__.py -> build/lib/brightpi
running build_scripts
creating build/scripts-3.9
copying and adjusting src/brightpi-test.py -> build/scripts-3.9
changing mode of build/scripts-3.9/brightpi-test.py from 644 to 755
running install_lib
creating /usr/local/lib/python3.9/dist-packages/brightpi
copying build/lib/brightpi/brightpilib.py -> /usr/local/lib/python3.9/dist-packages/brightpi
copying build/lib/brightpi/__init__.py -> /usr/local/lib/python3.9/dist-packages/brightpi
byte-compiling /usr/local/lib/python3.9/dist-packages/brightpi/brightpilib.py to brightpilib.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/brightpi/__init__.py to __init__.cpython-39.pyc
running install_scripts
copying build/scripts-3.9/brightpi-test.py -> /usr/local/bin
changing mode of /usr/local/bin/brightpi-test.py to 755
running install_egg_info
Writing /usr/local/lib/python3.9/dist-packages/brightpi-2.0.egg-info
tvo@rpi32-deb11:~/Bright-Pi $

Are you sure your python3, python3-distutils and oython3-setuptools are uo-to-date?

[mpv1953]

Thanks for the reply. Those packages look good to me. Does this match your installation? Regards, Mike Friday, 27 October 2023, 01:12:29 PM Raspberry Pi Zero 2 W Rev 1.0 Raspbian GNU/Linux 11 (bullseye) (v11.8) Linux 6.1.21-v7+ armv7l GNU/Linux ***@***.***:~ $ sudo apt-get install python3 python3-distutils python3-setuptools Reading package lists... Done Building dependency tree... Done Reading state information... Done python3 is already the newest version (3.9.2-3). python3 set to manually installed. python3-distutils is already the newest version (3.9.2-1). python3-setuptools is already the newest version (52.0.0-4). python3-setuptools set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ***@***.***:~ $

…

On Fri, Oct 27, 2023 at 10:08 AM Ton van Overbeek ***@***.***> wrote: on my 32-bit Bullseye it installs without problems.. Here is the log from the install: ***@***.***:~ $ git clone https://github.com/PiSupply/Bright-Pi.git Cloning into 'Bright-Pi'... remote: Enumerating objects: 116, done. remote: Counting objects: 100% (16/16), done. remote: Compressing objects: 100% (15/15), done. remote: Total 116 (delta 3), reused 11 (delta 1), pack-reused 100 Receiving objects: 100% (116/116), 10.59 MiB | 7.85 MiB/s, done. Resolving deltas: 100% (40/40), done. ***@***.***:~ $ cd Bright-Pi/ ***@***.***:~/Bright-Pi $ sudo python3 setup.py install running install running build running build_py creating build creating build/lib creating build/lib/brightpi copying brightpi/brightpilib.py -> build/lib/brightpi copying brightpi/__init__.py -> build/lib/brightpi running build_scripts creating build/scripts-3.9 copying and adjusting src/brightpi-test.py -> build/scripts-3.9 changing mode of build/scripts-3.9/brightpi-test.py from 644 to 755 running install_lib creating /usr/local/lib/python3.9/dist-packages/brightpi copying build/lib/brightpi/brightpilib.py -> /usr/local/lib/python3.9/dist-packages/brightpi copying build/lib/brightpi/__init__.py -> /usr/local/lib/python3.9/dist-packages/brightpi byte-compiling /usr/local/lib/python3.9/dist-packages/brightpi/brightpilib.py to brightpilib.cpython-39.pyc byte-compiling /usr/local/lib/python3.9/dist-packages/brightpi/__init__.py to __init__.cpython-39.pyc running install_scripts copying build/scripts-3.9/brightpi-test.py -> /usr/local/bin changing mode of /usr/local/bin/brightpi-test.py to 755 running install_egg_info Writing /usr/local/lib/python3.9/dist-packages/brightpi-2.0.egg-info ***@***.***:~/Bright-Pi $ Are you sure your python3, python3-distutils and oython3-setuptools are uo-to-date? — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHUOE2O7ZSYVMXLD5WNLL4TYBPS7XAVCNFSM6AAAAAA6R6GOGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTGI2DEMRTHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mpv1953]

I forgot to mention something. Does it matter if Bright-Pi/ is not downloaded directly to ~pi? Mine is in /home/pi/projects/Bright-Pi.
Thanks,
Mike

[tvoverbeek]

Should not matter.
How did you download? Did you execute curl -sSL https://pisupp.ly/brightpicode | bash while in /home/pi/projects/Bright-Pi?

[mpv1953]

I did almost exactly that, except pipe it directly to bash.  I like to save to scripts and then execute them that way.  Plus it gives me a chance to review the code.  I learn stuff that way!- MikeOn Oct 27, 2023, at 1:31 PM, Ton van Overbeek ***@***.***> wrote: Should not matter. How did you download? Did you execute curl -sSL https://pisupp.ly/brightpicode | bash while in /home/pi/projects/Bright-Pi? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[tvoverbeek]

Right now I do not know why it does not wok for you.
check if there is something in /usr/local/lib/python3.x/dist-packages and in /usr/local/bin.
Maybe it did install in spite of the warnings.

[mpv1953]

Hi: No joy in either location. Looking at the log you posted earlier in this thread, is there a way to install manually? I am including a list of what's installed on the Pi. Maybe there is a conflict? Thanks for your help. - Mike

…

On Sat, Oct 28, 2023 at 6:25 AM Ton van Overbeek ***@***.***> wrote: Right now I do not know why it does not wok for you. check if there is something in /usr/local/lib/python3.x/dist-packages and in /usr/local/bin. Maybe it did install in spite of the warnings. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHUOE2JAJKVJBTMHVVFU5U3YBUBWNAVCNFSM6AAAAAA6R6GOGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHAYDSNRSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tvoverbeek]

The install procedure copies the brightpi directory from https://github.com/PiSupply/Bright-Pi/tree/master/brightpi to /usr/local/lib/python3.9/dist-packages

tvo@rpi32-deb11:~ $ ls -l /usr/local/lib/python3.9/dist-packages/brightpi
total 16
-rw-r--r-- 1 root root 7572 Oct 27 18:58 brightpilib.py
-rw-r--r-- 1 root root   35 Oct 27 18:58 __init__.py
drwxr-xr-x 2 root root 4096 Oct 27 18:59 __pycache__
tvo@rpi32-deb11:~ $

The __pycache__ directory contains the byte compiled .py files.
It will be created automatically when you run a program using the brightpilib library

The src/brightpi-tet.py is copied to /usr/local/bin:

tvo@rpi32-deb11:~ $ ls -l /usr/local/bin/*.py
-rwxr-xr-x 1 root root 1993 Oct 27 18:59 /usr/local/bin/brightpi-test.py
tvo@rpi32-deb11:~ $