What can I do about this?

gene heskett gheskett at shentel.net
Mon Aug 29 04:51:13 EDT 2022


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 <gheskett at 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 at 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 at rock64:~/venv$ pip3 --version
> pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)
>>   "python3 --version",
> gene at rock64:~/venv$ python3 --version
> Python 3.10.4
>
>> and then "python3 -m pip install -r requirements.txt".
> gene at 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.
>
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.


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/>



More information about the Python-list mailing list