Richard <rrosn...@gmail.com> writes:
> A packages documentation is always your best friend: https://pypi.org
> /project/idle/
>
Yes it makes it look easy there, but:
import idle
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File ".local/pipx/shared/lib/python3.11/site-packages/idle.py", line 4, in
<module>
from layout import *
ModuleNotFoundError: No module named 'layout'
> Also, python script isn't a necessarily a standalone executable. And
> also, you shouldn't just wildly mix pipx commands with pip commands
> if you don't know what you are doing. Either create a venv with
> python3 -m venv or use pipx, not both. Once created, stick to these
> separate paths. And read the documentation of pipx while you're at
> it. Sure, venvs are easy to handle, as you can just delete them and
> start from scratch, but mixing commands without knowing what one is
> doing is just a recipe for desaster.
>
I don't know what I am doing for sure. But I did not wildly mix, I just
kept trying things until I found something which worked. Most things
didn't, and still don't.
