What can I do about this?

[gene heskett]

Greatings all;

Persuant to my claim the py3.10 is busted, here is a sample. This is me,
trying to make
pronterface, inside a venv: When the package manager version will only
run the gui-less "pronsole"
but nothing else from that all python kit runs as it should or at all.
From the package-managers install in /usr/share/doc/printrun-common/ I
copied requirements.txt
into the venv, and ran this command line:

gene@rock64:~/venv$ pip3 install -r requirements.txt
Defaulting to user installation because normal site-packages is not
writeable
Ignoring pyobjc-framework-Cocoa: markers 'sys_platform == "darwin"'
don't match your environment
Ignoring pyreadline: markers 'sys_platform == "win32"' don't match your
environment
Requirement already satisfied: pyserial>=3.0 in
/usr/lib/python3/dist-packages (from -r requirements.txt (line 1)) (3.5)
Collecting wxPython>=4.1
  Using cached wxPython-4.2.0.tar.gz (71.0 MB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File
"/tmp/pip-install-c9gmbpsr/wxpython_1a0e096c87d84229b709c31ccb920a24/setup.py",
line 27, in <module>
          from buildtools.config import Config, msg, opj, runcmd,
canGetSOName, getSOName
        File
"/tmp/pip-install-c9gmbpsr/wxpython_1a0e096c87d84229b709c31ccb920a24/buildtools/config.py",
line 30, in <module>
          from attrdict import AttrDict
      ModuleNotFoundError: No module named 'attrdict'
      [end of output]

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

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

What do I need to do to fix this? It supposedly works on a rpi4b, but
this is a rock64, V2,
older stuff with 4 gigs of dram.

Thank you for any help you can toss my way.

Cheers, Gene Heskett.

--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[Chris Angelico]

On Mon, 29 Aug 2022 at 08:41, gene heskett <ghes...@shentel.net> wrote:
>
> Greatings all;
>
> Persuant to my claim the py3.10 is busted, here is a sample. This is me,
> trying to make
> pronterface, inside a venv: When the package manager version will only
> run the gui-less "pronsole"
> but nothing else from that all python kit runs as it should or at all.
> From the package-managers install in /usr/share/doc/printrun-common/ I
> copied requirements.txt
> into the venv, and ran this command line:
>
> gene@rock64:~/venv$ pip3 install -r requirements.txt
> Defaulting to user installation because normal site-packages is not
> writeable

I don't think Python 3.10 is busted; it's more likely your venv is not
providing a pip3 command. Try "pip3 --version", "python3 --version",
and then "python3 -m pip install -r requirements.txt".

Why do you keep blaming Python as if it's fundamentally broken?

ChrisA

[Peter J. Holzer]

On 2022-08-28 18:40:17 -0400, gene heskett wrote:
> Persuant to my claim the py3.10 is busted, here is a sample. This is me,
> trying to make
> pronterface, inside a venv: When the package manager version will only run
> the gui-less "pronsole"
> but nothing else from that all python kit runs as it should or at all.
> From the package-managers install in /usr/share/doc/printrun-common/ I
> copied requirements.txt
> into the venv, and ran this command line:
>
> gene@rock64:~/venv$ pip3 install -r requirements.txt

You are almost certainly *not* in a venv here. First, your prompt
doesn't show the name of the venv,

> Defaulting to user installation because normal site-packages is not
> writeable

and second, because of this message, which you don't get if you invoke
pip inside a venv (at least not if you can write it).

So, first thing to do is to create the venv and activate it.

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | h...@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

[Dennis Lee Bieber]

On Sun, 28 Aug 2022 18:40:17 -0400, gene heskett <ghes...@shentel.net>
declaimed the following:

>Collecting wxPython>=4.1
>   Using cached wxPython-4.2.0.tar.gz (71.0 MB)
>   Preparing metadata (setup.py) ... error
>   error: subprocess-exited-with-error
>

>         File
>"/tmp/pip-install-c9gmbpsr/wxpython_1a0e096c87d84229b709c31ccb920a24/buildtools/config.py",
>line 30, in <module>
>           from attrdict import AttrDict
>       ModuleNotFoundError: No module named 'attrdict'
>       [end of output]
>

Well... First I'd ask where you obtained a 4.2.0 tar.gz version of
wxPython? Maybe try overriding it with a 4.1 variant of it -- or whatever
you can find in the OS's package manager.

>
>What do I need to do to fix this? It supposedly works on a rpi4b, but
>this is a rock64, V2,
>older stuff with 4 gigs of dram.
>
>Thank you for any help you can toss my way.
>

Ask in a forum specific to the OS? Heck, what IS the OS on that board,
and how up-to-date is it? The R-Pi is running a Raspberry Foundation
modified Debian Buster or Bullseye (appears they've pulled Buster, oldest
OS in the archive is January's Bullseye release).

This does not appear to really be a Python related problem -- rather it
looks like OS misconfiguration/disagreement.

However, you may wish to review
https://github.com/wxWidgets/Phoenix/issues/2225

Python3.10 is, perhaps, too NEW and various third-party libraries have
not been updated to be compatible with IT. Maybe install a version of
Python3.9 and start over loading all those extra packages.


--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

[gene heskett]

On 8/28/22 19:36, Chris Angelico wrote:
> On Mon, 29 Aug 2022 at 08:41, gene heskett <ghes...@shentel.net> wrote:
>> Greatings all;
>>

>> Persuant to my claim the py3.10 is busted, here is a sample. This is me,
>> trying to make
>> pronterface, inside a venv: When the package manager version will only
>> run the gui-less "pronsole"
>> but nothing else from that all python kit runs as it should or at all.
>> From the package-managers install in /usr/share/doc/printrun-common/ I
>> copied requirements.txt
>> into the venv, and ran this command line:
>>
>> gene@rock64:~/venv$ pip3 install -r requirements.txt

>> Defaulting to user installation because normal site-packages is not
>> writeable

> I don't think Python 3.10 is busted; it's more likely your venv is not
> providing a pip3 command. Try "pip3 --version",

gene@rock64:~/venv$ pip3 --version
pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)
> "python3 --version",
gene@rock64:~/venv$ python3 --version
Python 3.10.4

> and then "python3 -m pip install -r requirements.txt".

gene@rock64:~/venv$ python3 -m pip install -r requirements.txt

Defaulting to user installation because normal site-packages is not
writeable

Ignoring pyobjc-framework-Cocoa: markers 'sys_platform == "darwin"'
don't match your environment
Ignoring pyreadline: markers 'sys_platform == "win32"' don't match your
environment
Requirement already satisfied: pyserial>=3.0 in
/usr/lib/python3/dist-packages (from -r requirements.txt (line 1)) (3.5)

Collecting wxPython>=4.1
  Using cached wxPython-4.2.0.tar.gz (71.0 MB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File

"/tmp/pip-install-g3phtj8f/wxpython_17898b1c7a6f49a690adac623d839514/setup.py",

line 27, in <module>
          from buildtools.config import Config, msg, opj, runcmd,
canGetSOName, getSOName
        File

"/tmp/pip-install-g3phtj8f/wxpython_17898b1c7a6f49a690adac623d839514/buildtools/config.py",

line 30, in <module>
          from attrdict import AttrDict
      ModuleNotFoundError: No module named 'attrdict'
      [end of output]

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

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

>

> Why do you keep blaming Python as if it's fundamentally broken?
>
> ChrisA

Given the above output, do you have a better target? It also fails to
build linuxcnc on
bullseye for armhf, on an rpi4b with 2 gigs of dram.
Works perfectly on buster, but I expect that has been fixed  since linuxcnc
looks like its good to go for inclusion in bookworm.

Take care and stay well Chris.

[gene heskett]

On 8/28/22 19:39, Peter J. Holzer wrote:

> On 2022-08-28 18:40:17 -0400, gene heskett wrote:
>> Persuant to my claim the py3.10 is busted, here is a sample. This is me,
>> trying to make
>> pronterface, inside a venv: When the package manager version will only run
>> the gui-less "pronsole"
>> but nothing else from that all python kit runs as it should or at all.
>> From the package-managers install in /usr/share/doc/printrun-common/ I
>> copied requirements.txt
>> into the venv, and ran this command line:
>>
>> gene@rock64:~/venv$ pip3 install -r requirements.txt

> You are almost certainly *not* in a venv here. First, your prompt
> doesn't show the name of the venv,

I've created that several times, as octoprint won''t run without it either.
I found a way to autostart it on reboots and octoprint seems happy with it

>> Defaulting to user installation because normal site-packages is not
>> writeable

> and second, because of this message, which you don't get if you invoke
> pip inside a venv (at least not if you can write it).
>
> So, first thing to do is to create the venv and activate it.

Procedure? Or a url to it?

Thank you Peter. Take care & stay well.
> hp

[gene heskett]

On 8/28/22 20:51, gene heskett wrote:
> On 8/28/22 19:36, Chris Angelico wrote:
>> On Mon, 29 Aug 2022 at 08:41, gene heskett <ghes...@shentel.net> wrote:
>>> Greatings all;
>>>

>>> Persuant to my claim the py3.10 is busted, here is a sample. This is
>>> me,
>>> trying to make
>>> pronterface, inside a venv: When the package manager version will only
>>> run the gui-less "pronsole"
>>> but nothing else from that all python kit runs as it should or at all.
>>>   From the package-managers install in
>>> /usr/share/doc/printrun-common/ I
>>> copied requirements.txt
>>> into the venv, and ran this command line:
>>>
>>> gene@rock64:~/venv$ pip3 install -r requirements.txt

>>> Defaulting to user installation because normal site-packages is not
>>> writeable

>> I don't think Python 3.10 is busted; it's more likely your venv is not
>> providing a pip3 command. Try "pip3 --version",
> gene@rock64:~/venv$ pip3 --version
> pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)
>>   "python3 --version",
> gene@rock64:~/venv$ python3 --version
> Python 3.10.4
>
>> and then "python3 -m pip install -r requirements.txt".
> gene@rock64:~/venv$ python3 -m pip install -r requirements.txt

> Defaulting to user installation because normal site-packages is not
> writeable

I;ve created a separate venv to install printrun, I does not work either.

So in that venv, I've done a git clone of printrun. Then after that, it
appears there is
no such critter as a wxPython.whl for the arms, only x86_64's. So whats
the diff if it
run ok on a pi, or claims it does. I don't have a spare rpi4b and they
are equ to teeth
for a chicken ATM.

What, on the arms, substitutes for the missing "*.whl" file?

> Take care and stay well Chris.
>
> Cheers, Gene Heskett.

[Roel Schroeven]

Op 29/08/2022 om 2:55 schreef gene heskett:

> On 8/28/22 19:39, Peter J. Holzer wrote:
>> On 2022-08-28 18:40:17 -0400, gene heskett wrote:

>>> Persuant to my claim the py3.10 is busted, here is a sample. This is
>>> me,
>>> trying to make
>>> pronterface, inside a venv: When the package manager version will
>>> only run
>>> the gui-less "pronsole"
>>> but nothing else from that all python kit runs as it should or at all.
>>>  From the package-managers install in /usr/share/doc/printrun-common/ I
>>> copied requirements.txt
>>> into the venv, and ran this command line:
>>>
>>> gene@rock64:~/venv$ pip3 install -r requirements.txt

>> You are almost certainly *not* in a venv here. First, your prompt
>> doesn't show the name of the venv,
> I've created that several times, as octoprint won''t run without it
> either.
> I found a way to autostart it on reboots and octoprint seems happy
> with it

I agree with Peter: it doesn't look as if you are invoking the pip3 in
the venv. Just making the venv-directory the current directory doesn't
activate it.

As a diagnostic, ask the OS which pip3 is actually used:

$ type -a pip3

Does that show the pip3 installed in the venv? Or the system-wide one?
If it's not the pip3 in the venv, well, then that's the problem (or at
least part of the problem). Solution: first check whether the venv
really contains 'pip3' (as opposed to eg. just 'pip'): list the contents
of the bin subdirectory of the venv. If not, use 'pip' or whatever
instead. Then to make sure you use the one in the venv, either activate
the venv or explicitly specify the path when invoking pip/pip3 (and
likewise for python/python3).

So either (assuming you're using bash):

$ source {path_to_venv}/bin/pip3  # activate the venv
$ type -a pip3  # check whether now the correct pip3 is used
$ pip3 install -r requirements.txt  # finally invoke pip3

or:

$ {path_to_venv}/bin/pip3 install -r requirements.txt

Activating the venv is easier if you're going to use multiple commands
in the venv. Note that activating the venv only has effect on the
current shell; other shells are unaffected, and when you close the
current shell the venv is not activated anymore.
Explicitly using the path is easier for one-off calls, or in things like
crontab.

--
"There is no cause so noble that it will not attract fuggheads."
-- Larry Niven

[Mark Bourne]

I think this first line should probably be:

$ source {path_to_venv}/bin/activate # activate the venv

i.e. with `activate` rather than `pip3`?

[gene heskett]

I get different answers in or out of the venv

venv) gene@rock64:~/printrun/Printrun$ type -a pip3
pip3 is /home/gene/printrun/Printrun/venv/bin/pip3
pip3 is /usr/bin/pip3
pip3 is /bin/pip3

or:

gene@rock64:~/src/wxPython-4.2.0$ type -a pip3
pip3 is /usr/bin/pip3
pip3 is /bin/pip3

but with all the build instructions I've now followed, I now have at
least 3 different
venv subdirs scattered about.

one in /home/gene,
one in /home/gene/Octoprint,
and one in /home/gene/printrun

each with its own bin subdir, but not identical contents.

> Does that show the pip3 installed in the venv? Or the system-wide one?
> If it's not the pip3 in the venv, well, then that's the problem (or at
> least part of the problem). Solution: first check whether the venv
> really contains 'pip3' (as opposed to eg. just 'pip'): list the
> contents of the bin subdirectory of the venv.

gene@rock64:~/venv/bin$ ls -l
total 36
-rw-r--r-- 1 gene gene 1982 Aug 21 13:12 activate
-rw-r--r-- 1 gene gene  908 Aug 21 13:12 activate.csh
-rw-r--r-- 1 gene gene 2050 Aug 21 13:12 activate.fish
-rw-r--r-- 1 gene gene 9033 Aug 21 13:12 Activate.ps1
-rwxrwxr-x 1 gene gene  232 Aug 21 13:12 pip
-rwxrwxr-x 1 gene gene  232 Aug 21 13:12 pip3
-rwxrwxr-x 1 gene gene  232 Aug 21 13:12 pip3.10
lrwxrwxrwx 1 gene gene    7 Aug 21 13:11 python -> python3
lrwxrwxrwx 1 gene gene   16 Aug 21 13:11 python3 -> /usr/bin/python3
lrwxrwxrwx 1 gene gene    7 Aug 21 13:11 python3.10 -> python3

> If not, use 'pip' or whatever instead. Then to make sure you use the
> one in the venv, either activate the venv or explicitly specify the
> path when invoking pip/pip3 (and likewise for python/python3).
>
> So either (assuming you're using bash):
>
> $ source {path_to_venv}/bin/pip3  # activate the venv

> $ type -a pip3  # check whether now the correct pip3 is used
> $ pip3 install -r requirements.txt  # finally invoke pip3
>
> or:
>
> $ {path_to_venv}/bin/pip3 install -r requirements.txt
>
> Activating the venv is easier if you're going to use multiple commands
> in the venv. Note that activating the venv only has effect on the
> current shell; other shells are unaffected, and when you close the
> current shell the venv is not activated anymore.
> Explicitly using the path is easier for one-off calls, or in things
> like crontab.
>

I've not had to deal with venv's before. Can more than one of these venv
things
peacefully coexist?  Seems like they should. If there is sufficient nv
memory,
But I am a 100% new bee here. The card itself is a 64GB.

I also have the git clone of wxPython-4.2.0, but nothing I can invoke
there builds it.
But there are no specific linux instructions there, osx and winders
only. The package
managers version of wxPython-4.0.7 apparently is not new enough.

It seems to me these utility's ought to be able to all live in one venv,
or there should be
an env python path that is specific to each application. This would lead
to a huge waste
of nv storage by duplicating a venv for each app, not sensible when the
target of the venv
is a common arm64 system. All broadcom for gpio etc.

Presently, Octoprint works, and so does pronsole which has no gui, but
Octoprint
is a one printer show, and I've a small farm of printers. Most of which have
failed the PETG test ,but that claimed to be PETG compatible, but
quickly failed
when fed a roll of it. PETG is the same plastic forever bottles are made
from, much
stronger than the PLA most folks use for artwork and what I'm doing
needs its
physical strength. It also raises the printhead temp around 50C, which
causes
teflon to slowly ablate with phosgene gas as output. Dangerous stuff,
and high
maintenance too.

What I hope to be the 2nd workhorse  is an Ender 5 Plus, a huge core-xy
thing that
now has a 300C capable head and an orbiter-v2 direct drive, heavy enough
I've
had to restrict  its top speed from its default 500mm. The other printer
is a
Prusa MK3S+ I've about $1500 USD in. It works nice _now_ but came with a
high leakage hot block some gorilla had over tightened and stripped the
heat
break threads, but is slow if fed at cura's default 60mm speeds.

So what should I do next? That includes blowing it all away and starting
over. I have
another rock64. and a kvm swithch on an Amazon truck, be here tomorrow. That
may be my best bet, a separate rock64 and octoprint for each printer.
That at least
looks like it might work. Find a 10+ amp 5 volt supply to run a bunch of
the korean
boards. If the kvm switch works.

Awaiting advice.  Thank you.

[Dennis Lee Bieber]

On Mon, 29 Aug 2022 04:51:13 -0400, gene heskett <ghes...@shentel.net>
declaimed the following:

>What, on the arms, substitutes for the missing "*.whl" file?
>

In Debian -- apt-get
https://packages.debian.org/stable/source/wxpython4.0
of course, that will install things system-wide, not in a virtual
environment, and compatible with the system Python. For Bullseye, that is
still Python 3.9!

pi@rpi3bplus-1:~$ uname -a
Linux rpi3bplus-1 5.15.32-v7+ #1538 SMP Thu Mar 31 19:38:48 BST 2022 armv7l
GNU/Linux
pi@rpi3bplus-1:~$ sudo apt search wxpython
Sorting... Done
Full Text Search... Done
gnumed-client/stable 1.8.5+dfsg-2 all
medical practice management - Client

psychopy/stable 2020.2.10+dfsg-2 all
environment for creating psychology stimuli in Python

pyscanfcs/stable 0.3.6+ds-2+b1 armhf
scientific tool for perpendicular line scanning FCS

python3-genx/stable 3.0.2-1 armhf
differential evolution algorithm for fitting

python3-opengl/stable 3.1.5+dfsg-1 all
Python bindings to OpenGL (Python 3)

python3-pyface/stable 6.1.2-2 all
traits-capable windowing framework

python3-squaremap/stable 1:1.0.5-2 all
wxPython control to display hierarchic data as nested squares

python3-wxgtk-media4.0/stable 4.0.7+dfsg-10 armhf
Python 3 interface to the wxWidgets Cross-platform C++ GUI toolkit
(wx.media)

python3-wxgtk-webview4.0/stable 4.0.7+dfsg-10 armhf
Python 3 interface to the wxWidgets Cross-platform C++ GUI toolkit
(wx.html2)

python3-wxgtk4.0/stable 4.0.7+dfsg-10 armhf
Python 3 interface to the wxWidgets Cross-platform C++ GUI toolkit

soundgrain/stable 6.0.1-2 all
Graphical interface to control granular sound synthesis modules

wxglade/stable 1.0.1-1 all
GUI designer written in Python with wxPython

wxpython-tools/stable 4.0.7+dfsg-10 all
Tools from the wxPython distribution

pi@rpi3bplus-1:~$

pi@rpi3bplus-1:~$ sudo apt install python3-wxgtk4.0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5
Suggested packages:
wx3.0-doc
The following NEW packages will be installed:
libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5 python3-wxgtk4.0
0 upgraded, 3 newly installed, 0 to remove and 161 not upgraded.
Need to get 10.5 MB of archives.
After this operation, 51.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf
libwxbase3.0-0v5 armhf 3.0.5.1+dfsg-2 [918 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf
libwxgtk3.0-gtk3-0v5 armhf 3.0.5.1+dfsg-2 [3650 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf
python3-wxgtk4.0 armhf 4.0.7+dfsg-10 [5970 kB]
Fetched 10.5 MB in 8s (1346 kB/s)
Selecting previously unselected package libwxbase3.0-0v5:armhf.
(Reading database ... 175515 files and directories currently installed.)
Preparing to unpack .../libwxbase3.0-0v5_3.0.5.1+dfsg-2_armhf.deb ...
Unpacking libwxbase3.0-0v5:armhf (3.0.5.1+dfsg-2) ...
Selecting previously unselected package libwxgtk3.0-gtk3-0v5:armhf.
Preparing to unpack .../libwxgtk3.0-gtk3-0v5_3.0.5.1+dfsg-2_armhf.deb ...
Unpacking libwxgtk3.0-gtk3-0v5:armhf (3.0.5.1+dfsg-2) ...
Selecting previously unselected package python3-wxgtk4.0.
Preparing to unpack .../python3-wxgtk4.0_4.0.7+dfsg-10_armhf.deb ...
Unpacking python3-wxgtk4.0 (4.0.7+dfsg-10) ...
Setting up libwxbase3.0-0v5:armhf (3.0.5.1+dfsg-2) ...
Setting up libwxgtk3.0-gtk3-0v5:armhf (3.0.5.1+dfsg-2) ...
Setting up python3-wxgtk4.0 (4.0.7+dfsg-10) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u2) ...
pi@rpi3bplus-1:~$






Or... You wait until somebody builds a Python3.10 ARMHF compatible
wheel.

[Roel Schroeven]

Mark Bourne schreef op 29/08/2022 om 13:02:

> Roel Schroeven wrote:
> > $ source {path_to_venv}/bin/pip3  # activate the venv
>
> I think this first line should probably be:
>
> $ source {path_to_venv}/bin/activate # activate the venv
>
> i.e. with `activate` rather than `pip3`?

Oops, yes, of course. Thank you for the correction!

--

"In the old days, writers used to sit in front of a typewriter and stare out of
the window. Nowadays, because of the marvels of convergent technology, the thing
you type on and the window you stare out of are now the same thing.”
-- Douglas Adams

[gene heskett]

That got me to showstopper #2: (lengthy warniing)

(venv) gene@rock64:~/printrun/Printrun$ ./venv/bin/pip3 install -r
requirements.txt

Ignoring pyobjc-framework-Cocoa: markers 'sys_platform == "darwin"'
don't match your environment
Ignoring pyreadline: markers 'sys_platform == "win32"' don't match your
environment
Requirement already satisfied: pyserial>=3.0 in

./venv/lib/python3.10/site-packages (from -r requirements.txt (line 1))
(3.5)
Collecting wxPython==4.1.0
  Using cached wxPython-4.1.0.tar.gz (65.8 MB)
  Preparing metadata (setup.py) ... done
Collecting numpy>=1.8.2
  Using cached
numpy-1.23.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
(13.9 MB)
Requirement already satisfied: pyglet>=1.1 in
./venv/lib/python3.10/site-packages (from -r requirements.txt (line 4))
(1.5.26)
Collecting cffi
  Using cached
cffi-1.15.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
(449 kB)
Collecting cairocffi
  Using cached cairocffi-1.3.0.tar.gz (88 kB)
  Preparing metadata (setup.py) ... done
Collecting cairosvg>=1.0.9
  Using cached CairoSVG-2.5.2-py3-none-any.whl (45 kB)
Collecting psutil>=2.1
  Using cached psutil-5.9.1-cp310-cp310-linux_aarch64.whl
Collecting lxml>=2.9.1
  Using cached
lxml-4.9.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.manylinux_2_24_aarch64.whl
(6.6 MB)
Collecting appdirs>=1.4.0
  Using cached appdirs-1.4.4-py2.py3-none-any.whl (9.6 kB)
Collecting dbus-python>=1.2.0
  Using cached dbus-python-1.2.18.tar.gz (578 kB)
  Preparing metadata (setup.py) ... done
Collecting pillow
  Using cached Pillow-9.2.0-cp310-cp310-manylinux_2_28_aarch64.whl (3.1 MB)
Collecting six
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting pycparser
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting cssselect2
  Using cached cssselect2-0.6.0-py3-none-any.whl (15 kB)
Collecting tinycss2
  Using cached tinycss2-1.1.1-py3-none-any.whl (21 kB)
Collecting defusedxml
  Using cached defusedxml-0.7.1-py2.py3-none-any.whl (25 kB)
Requirement already satisfied: webencodings in
./venv/lib/python3.10/site-packages (from
cssselect2->cairosvg>=1.0.9->-r requirements.txt (line 7)) (0.5.1)
Using legacy 'setup.py install' for wxPython, since package 'wheel' is
not installed.
Using legacy 'setup.py install' for cairocffi, since package 'wheel' is
not installed.
Using legacy 'setup.py install' for dbus-python, since package 'wheel'
is not installed.
Installing collected packages: dbus-python, appdirs, tinycss2, six,
pycparser, psutil, pillow, numpy, lxml, defusedxml, wxPython,
cssselect2, cffi, cairocffi, cairosvg
  Running setup.py install for dbus-python ... error
  error: subprocess-exited-with-error

  × Running setup.py install for dbus-python did not run successfully.
  │ exit code: 1
  ╰─> [166 lines of output]
      running install
/home/gene/printrun/Printrun/venv/lib/python3.10/site-packages/setuptools/command/install.py:34:
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build
and pip and other standards-based tools.
        warnings.warn(
      running build
      creating
/tmp/pip-install-2zqkrisr/dbus-python_6642a4f761e742d49b75c39a953ceb6b/build
      creating
/tmp/pip-install-2zqkrisr/dbus-python_6642a4f761e742d49b75c39a953ceb6b/build/temp.linux-aarch64-3.10
      checking whether make supports nested variables... yes
      checking whether to enable maintainer-specific portions of
Makefiles... no
      checking for gcc... gcc
      checking whether the C compiler works... yes
      checking for C compiler default output file name... a.out
      checking for suffix of executables...
      checking whether we are cross compiling... no
      checking for suffix of object files... o
      checking whether we are using the GNU C compiler... yes
      checking whether gcc accepts -g... yes
      checking for gcc option to accept ISO C89... none needed
      checking whether gcc understands -c and -o together... yes
      checking how to run the C preprocessor... gcc -E
      checking for grep that handles long lines and -e... /usr/bin/grep
      checking for egrep... /usr/bin/grep -E
      checking for ANSI C header files... yes
      checking for sys/types.h... yes
      checking for sys/stat.h... yes
      checking for stdlib.h... yes
      checking for string.h... yes
      checking for memory.h... yes
      checking for strings.h... yes
      checking for inttypes.h... yes
      checking for stdint.h... yes
      checking for unistd.h... yes
      checking minix/config.h usability... no
      checking minix/config.h presence... no
      checking for minix/config.h... no
      checking whether it is safe to define __EXTENSIONS__... yes
      checking for a BSD-compatible install... /usr/bin/install -c
      checking whether build environment is sane... yes
      checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
      checking for gawk... no
      checking for mawk... mawk
      checking whether make sets $(MAKE)... yes
      checking whether make supports the include directive... yes (GNU
style)
      checking whether UID '1000' is supported by ustar format... yes
      checking whether GID '1000' is supported by ustar format... yes
      checking how to create a ustar tar archive... gnutar
      checking dependency style of gcc... gcc3
      checking build system type... aarch64-unknown-linux-gnu
      checking host system type... aarch64-unknown-linux-gnu
      checking for native Windows host... no
      checking how to print strings... printf
      checking for a sed that does not truncate output... /usr/bin/sed
      checking for fgrep... /usr/bin/grep -F
      checking for ld used by gcc... /usr/bin/ld
      checking if the linker (/usr/bin/ld) is GNU ld... yes
      checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
      checking the name lister (/usr/bin/nm -B) interface... BSD nm
      checking whether ln -s works... yes
      checking the maximum length of command line arguments... 1572864
      checking how to convert aarch64-unknown-linux-gnu file names to
aarch64-unknown-linux-gnu format... func_convert_file_noop
      checking how to convert aarch64-unknown-linux-gnu file names to
toolchain format... func_convert_file_noop
      checking for /usr/bin/ld option to reload object files... -r
      checking for objdump... objdump
      checking how to recognize dependent libraries... pass_all
      checking for dlltool... no
      checking how to associate runtime and link libraries... printf %s\n
      checking for ar... ar
      checking for archiver @FILE support... @
      checking for strip... strip
      checking for ranlib... ranlib
      checking command to parse /usr/bin/nm -B output from gcc object... ok
      checking for sysroot... no
      checking for a working dd... /usr/bin/dd
      checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
      checking for mt... mt
      checking if mt is a manifest tool... no
      checking for dlfcn.h... yes
      checking for objdir... .libs
      checking if gcc supports -fno-rtti -fno-exceptions... no
      checking for gcc option to produce PIC... -fPIC -DPIC
      checking if gcc PIC flag -fPIC -DPIC works... yes
      checking if gcc static flag -static works... yes
      checking if gcc supports -c -o file.o... yes
      checking if gcc supports -c -o file.o... (cached) yes
      checking whether the gcc linker (/usr/bin/ld) supports shared
libraries... yes
      checking whether -lc should be explicitly linked in... no
      checking dynamic linker characteristics... GNU/Linux ld.so
      checking how to hardcode library paths into programs... immediate
      checking whether stripping libraries is possible... yes
      checking if libtool supports shared libraries... yes
      checking whether to build shared libraries... yes
      checking whether to build static libraries... no
      checking for inline... inline
      checking for gawk... (cached) mawk
      checking for python... /home/gene/printrun/Printrun/venv/bin/python3
      checking for a version of Python >= '2.1.0'... yes
      checking for a version of Python >= '2.7'... yes
      checking for the distutils Python package... yes
      checking for Python include path... <string>:1:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
      <string>:1: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      <string>:1: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or
check PEP 632 for potential alternatives
      <string>:1: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      -I/usr/include/python3.10
      checking for Python library path... <stdin>:4:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
      <stdin>:4: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      <stdin>:3: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or
check PEP 632 for potential alternatives
      <stdin>:3: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      <stdin>:2: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or
check PEP 632 for potential alternatives
      <stdin>:2: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      -L/usr/lib/aarch64-linux-gnu -lpython3.10
      checking for Python site-packages path... <string>:1:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
      <string>:1: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      /home/gene/printrun/Printrun/venv/lib/python3.10/site-packages
      checking python extra libraries... <string>:1:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
      <string>:1: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      -lcrypt -ldl  -lm -lm
      checking python extra linking flags... <string>:1:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
      <string>:1: DeprecationWarning: The distutils.sysconfig module is
deprecated, use sysconfig instead
      -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
      checking consistency of all components of python development
environment... yes
      checking for python version... 3.10
      checking for python platform... linux
      checking for python script directory...
${prefix}/lib/python3.10/site-packages
      checking for python extension module directory...
${exec_prefix}/lib/python3.10/site-packages
      <string>:1: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or
check PEP 632 for potential alternatives
      checking python3 module: sphinx... no
      checking python3 module: sphinx_rtd_theme... no
      checking for dbus-run-session... /usr/bin/dbus-run-session
      checking for pkg-config... /usr/bin/pkg-config
      checking pkg-config is at least version 0.9.0... yes
      checking for dbus-1 >= 1.8... no
      configure: error: Package requirements (dbus-1 >= 1.8) were not met:

      No package 'dbus-1' found

      Consider adjusting the PKG_CONFIG_PATH environment variable if you
      installed software in a non-standard prefix.

      Alternatively, you may set the environment variables DBUS_CFLAGS
      and DBUS_LIBS to avoid the need to call pkg-config.
      See the pkg-config man page for more details.

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File

"/tmp/pip-install-2zqkrisr/dbus-python_6642a4f761e742d49b75c39a953ceb6b/setup.py",
line 85, in <module>
          setup(
        File
"/home/gene/printrun/Printrun/venv/lib/python3.10/site-packages/setuptools/__init__.py",
line 153, in setup
          return distutils.core.setup(**attrs)
        File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
          dist.run_commands()
        File "/usr/lib/python3.10/distutils/dist.py", line 966, in
run_commands
          self.run_command(cmd)
        File "/usr/lib/python3.10/distutils/dist.py", line 985, in
run_command
          cmd_obj.run()
        File
"/home/gene/printrun/Printrun/venv/lib/python3.10/site-packages/setuptools/command/install.py",
line 68, in run
          return orig.install.run(self)
        File "/usr/lib/python3.10/distutils/command/install.py", line
619, in run
          self.run_command('build')
        File "/usr/lib/python3.10/distutils/cmd.py", line 313, in
run_command
          self.distribution.run_command(command)
        File "/usr/lib/python3.10/distutils/dist.py", line 985, in
run_command
          cmd_obj.run()
        File
"/tmp/pip-install-2zqkrisr/dbus-python_6642a4f761e742d49b75c39a953ceb6b/setup.py",
line 56, in run
          subprocess.check_call([
        File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command
'['/tmp/pip-install-2zqkrisr/dbus-python_6642a4f761e742d49b75c39a953ceb6b/configure',
'--disable-maintainer-mode',
'PYTHON=/home/gene/printrun/Printrun/venv/bin/python3',
'--prefix=/tmp/pip-install-2zqkrisr/dbus-python_6642a4f761e742d49b75c39a953ceb6b/build/temp.linux-aarch64-3.10/prefix']'
returned non-zero exit status 1.

      [end of output]

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

error: legacy-install-failure

× Encountered error while trying to install package.
╰─> dbus-python

note: This is an issue with the package mentioned above, not pip.

hint: See above for output from the failure.
(venv) gene@rock64:~/printrun/Printrun$


There is help there, but to me its engrish. Next fix?

>>
>> Activating the venv is easier if you're going to use multiple
>> commands in the venv. Note that activating the venv only has effect
>> on the current shell; other shells are unaffected, and when you close
>> the current shell the venv is not activated anymore.
>> Explicitly using the path is easier for one-off calls, or in things
>> like crontab.
>>

Thank you Mark Bourne, this looks like actual progress in what has
turned into a cast iron bitch.
I'll not touch that shell till the next advice is tendered. However
"echo $PKG_CONFIG_PATH" is
null in this venv.

[Peter J. Holzer]

On 2022-08-29 13:43:18 -0400, gene heskett wrote:
> On 8/29/22 12:50, Mark Bourne wrote:
> > Roel Schroeven wrote:

> > > $ pip3 install -r requirements.txt  # finally invoke pip3
> > >
> > > or:
> > >
> > > $ {path_to_venv}/bin/pip3 install -r requirements.txt

> That got me to showstopper #2: (lengthy warniing)
>

[...]

>       checking for dbus-1 >= 1.8... no
>       configure: error: Package requirements (dbus-1 >= 1.8) were not met:
>
>       No package 'dbus-1' found

Since this message comes from configure, it is probably looking
for the development version of the dbus library here.

apt search dbus-1

reveals (among other things):

libdbus-1-dev/jammy 1.12.20-2ubuntu4 amd64
simple interprocess messaging system (development headers)

(this is on Ubuntu, so the version number is probably different, but the
package name should be the same as on Debian.)

So you invoke

apt install libdbus-1-dev

and try again. At which point you will probably discove another missing
library. Rinse and repeat.

Ideally the README should mention such dependencies, but since the exact
names of the packages depend on the distribution, it will often be vague
unless you happen to use the same distribution as the developer.

[Peter J. Holzer]

On 2022-08-29 11:12:17 -0400, gene heskett wrote:
> I've not had to deal with venv's before. Can more than one of these
> venv things peacefully coexist?

Yes. Having multiple venvs is the main reason for their existence.

[Mark Bourne]

To be fair, it was Roel Schroeven who posted the steps and the part
you're quoting here, and others had pointed in the direction of the venv
not having been activated - I just posted a correction to one of Roel's
commands. Sorry, I can't help much with your actual problem, but
hopefully others can.

--
Mark.

[gene heskett]

On 8/29/22 15:12, Peter J. Holzer wrote:

> On 2022-08-29 13:43:18 -0400, gene heskett wrote:
>> On 8/29/22 12:50, Mark Bourne wrote:
>>> Roel Schroeven wrote:

>>>> $ pip3 install -r requirements.txt  # finally invoke pip3
>>>>
>>>> or:
>>>>
>>>> $ {path_to_venv}/bin/pip3 install -r requirements.txt

>> That got me to showstopper #2: (lengthy warniing)
>>

> [...]

>>       checking for dbus-1 >= 1.8... no
>>       configure: error: Package requirements (dbus-1 >= 1.8) were not met:
>>
>>       No package 'dbus-1' found

> Since this message comes from configure, it is probably looking
> for the development version of the dbus library here.
>
> apt search dbus-1
>
> reveals (among other things):
>
> libdbus-1-dev/jammy 1.12.20-2ubuntu4 amd64
> simple interprocess messaging system (development headers)
>
> (this is on Ubuntu, so the version number is probably different, but the
> package name should be the same as on Debian.)
>
> So you invoke
>
> apt install libdbus-1-dev
>
> and try again. At which point you will probably discove another missing
> library. Rinse and repeat.

You left out the wash, ;) The next missing dev was a gtk thingy, but
search only returned
one .dev. One for spice-gtk, and that pulled in around 100 more
packages, and now its stuck
on wxPython for about 35 minutes and, way into swap, like several
hundred megs &
growing. I even went to its keyboard and shut down chromium to give it
more play
room. Didn't seem to help though. But it hasn't errored, and swap is
going  down a
meg here and there. Pounding that poor, cheap sd card all to hell I
expect. At some point,
I'll unpack a startech usb3-sata cable and try an SSD. But I'll not
disturb this just yet.

Works well on an r-pi4b where I can build linuxcnc in half an hour from
the git pull. I
run a 3/4 ton, 80 yo Sheldon lathe with linuxcnc just to see if I could
do it, first on an rpi3b.
Had to build my own realtime kernel and figure out how to install it
because I wanted to
do it on a pi, got black holed on their forum. The amazing part is that
the tarball to install
it is only 28 megs uncompressed.

> Ideally the README should mention such dependencies, but since the exact
> names of the packages depend on the distribution, it will often be vague
> unless you happen to use the same distribution as the developer.

Your forgot to mention that each packager is working in his own sound
proof booth, so
each comes up with a somewhat different way to pound that square peg
into a 7 point hole.
;o)>

It was obviously going to take hours so I took a nap and 4 hours later
it had left out a
few things but kept on going until it hit another showstopper while
building wxPython-4.1.
At which point it spit out 2600 some lines of backtrace.

Ending with this:
     In file included from
../../../../sip/cpp/sip_glcanvaswxGLContext.cpp:10:
      ../../../../sip/cpp/sipAPI_glcanvas.h:865:198: error:
‘wxGLCanvasName’ was not declared in this scope; did you mean ‘wxGLCanvas’?
        865 |     wxGLCanvas(wxWindow *parent, const wxGLAttributes
&dispAttrs, wxWindowID id=wxID_ANY, const wxPoint
&pos=wxDefaultPosition, const wxSize &size=wxDefaultSize, long style=0,
const wxString &name=wxGLCanvasName, const wxPalette &palette=wxNullPalette)
| ^~~~~~~~~~~~~~
| wxGLCanvas

      Waf: Leaving directory
`/tmp/pip-install-1myz6noi/wxpython_5fdcad39f0c544599dd49fdd522391f2/build/waf/3.1/gtk3'
      Build failed
       -> task in '_glcanvas' failed with exit status 1 (run with -v to
display more information)
       -> task in '_glcanvas' failed with exit status 1 (run with -v to
display more information)
       -> task in '_glcanvas' failed with exit status 1 (run with -v to
display more information)
       -> task in '_glcanvas' failed with exit status 1 (run with -v to
display more information)
      Command '"/home/gene/printrun/Printrun/venv/bin/python3"
/tmp/pip-install-1myz6noi/wxpython_5fdcad39f0c544599dd49fdd522391f2/bin/waf-2.0.19
--wx_config=/tmp/pip-install-1myz6noi/wxpython_5fdcad39f0c544599dd49fdd522391f2/build/wxbld/gtk3/wx-config
--gtk3 --python="/home/gene/printrun/Printrun/venv/bin/python3"
--out=build/waf/3.1/gtk3 configure build ' failed with exit code 1.
      Finished command: build_py (100m40.712s)
      Finished command: build (171m37.482s)
      Command '"/home/gene/printrun/Printrun/venv/bin/python3" -u
build.py build' failed with exit code 1.

      [end of output]

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

× Encountered error while trying to install package.

╰─> wxPython

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

================
Now, I have the unpacked tarball of wxPython-4.2.0 sitting in
/home/gene/src.

Where would I mv it to to substituted for the 4.1 since 4.1 isn't quite
ready for prime time?

I changed the 1 to a 2 in requirements.txt, but that exited in a few
seconds after it
downloaded another copy of the tarball, with another error I have see
before while
trying to build it in /home/gene/src's/unpacked_tarball tree.

paste of error:

(venv) gene@rock64:~/printrun/Printrun$ ./venv/bin/pip3 install -r
requirements.txt
Ignoring pyobjc-framework-Cocoa: markers 'sys_platform == "darwin"'
don't match your environment
Ignoring pyreadline: markers 'sys_platform == "win32"' don't match your
environment
Requirement already satisfied: pyserial>=3.0 in
./venv/lib/python3.10/site-packages (from -r requirements.txt (line 1))
(3.5)

Collecting wxPython==4.2.0

  Using cached wxPython-4.2.0.tar.gz (71.0 MB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File

"/tmp/pip-install-x9vpdn0f/wxpython_75085d87ddc7455cb159bbbb95177417/setup.py",

line 27, in <module>
          from buildtools.config import Config, msg, opj, runcmd,
canGetSOName, getSOName
        File

"/tmp/pip-install-x9vpdn0f/wxpython_75085d87ddc7455cb159bbbb95177417/buildtools/config.py",

line 30, in <module>
          from attrdict import AttrDict
      ModuleNotFoundError: No module named 'attrdict'

      [end of output]

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

error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.

hint: See above for details.
(venv) gene@rock64:~/printrun/Printrun$

I've found it , the src tarball.gz. In /home/gene/Downloads.

Is that tarball updatable? Or should I ignore it & go back to wxPython-4.1?
Is it fixable?
> hp
>
Thanks Peter. Take care and stay well.