[SOLVED] Thonny not starting

henca · 07-06-2022, 01:03 PM

Quote:

Originally Posted by SAJM

Code:

slpkg

is new to me.

https://slackbuilds.org/repository/1.../?search=slpkg

https://dslackw.gitlab.io/slpkg/

It is yet another tool to learn, but it will make life a lot easier when installing software with many and recursive dependencies.

regards Henrik

SAJM · 07-07-2022, 09:41 AM

I used slpkg but one of the dependencies did not install and to make matters worse no log file detailing why was created.

Code:

writing UNKNOWN.egg-info/PKG-INFO
writing top-level names to UNKNOWN.egg-info/top_level.txt
writing dependency_links to UNKNOWN.egg-info/dependency_links.txt
writing manifest file 'UNKNOWN.egg-info/SOURCES.txt'
reading manifest file 'UNKNOWN.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'UNKNOWN.egg-info/SOURCES.txt'
Copying UNKNOWN.egg-info to /tmp/SBo/package-asttokens/usr/lib64/python2.7/site-packages/UNKNOWN-0.0.0-py2.7.egg-info
running install_scripts
running install
Traceback (most recent call last):
  File "setup.py", line 11, in <module>
    setup()
  File "/usr/lib64/python3.7/site-packages/setuptools/__init__.py", line 143, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib64/python3.7/distutils/dist.py", line 984, in run_command
    cmd_obj.ensure_finalized()
  File "/usr/lib64/python3.7/distutils/cmd.py", line 107, in ensure_finalized
    self.finalize_options()
  File "/usr/lib64/python3.7/site-packages/setuptools/command/install.py", line 38, in finalize_options
    orig.install.finalize_options(self)
  File "/usr/lib64/python3.7/distutils/command/install.py", line 368, in finalize_options
    ('build_lib', 'build_lib'))
  File "/usr/lib64/python3.7/distutils/cmd.py", line 286, in set_undefined_options
    src_cmd_obj = self.distribution.get_command_obj(src_cmd)
  File "/usr/lib64/python3.7/distutils/dist.py", line 857, in get_command_obj
    klass = self.get_command_class(command)
  File "/usr/lib64/python3.7/site-packages/setuptools/dist.py", line 707, in get_command_class
    self.cmdclass[command] = cmdclass = ep.load()
  File "/usr/lib64/python3.7/site-packages/pkg_resources/__init__.py", line 2346, in load
    return self.resolve()
  File "/usr/lib64/python3.7/site-packages/pkg_resources/__init__.py", line 2352, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
ModuleNotFoundError: No module named 'setuptools.command.build'
Total build time for the package asttokens : 1 Min 25 Sec

+==============================================================================
| Some error on the package asttokens-2.0.4 [ FAILED ]
+==============================================================================
| See the log file in '/var/log/slpkg/sbo/build_logs' directory or read the README file
+==============================================================================

bash-4.3# nano /var/log/slpkg/sbo/build_logs
bash-4.3#

SAJM · 07-07-2022, 10:10 AM

What on earth is "egg-info"?
I can find very little on it.
It seems to be a python thing not asttokens

Dunc. · 07-07-2022, 10:50 AM

I am spotting a bit of a theme here as Thonny is used to program the pico too. I could not get it to build either. I believe I ran pip to install it.

Code:

pip install thonny

Hope that helps.

Dunc.

SAJM · 07-07-2022, 11:23 AM

Quote:

Originally Posted by Dunc.

I am spotting a bit of a theme here as Thonny is used to program the pico too. I could not get it to build either. I believe I ran pip to install it.

Code:

pip install thonny

Hope that helps.

Dunc.

You are correct about the pico pi
pip is a minefield!

pan64 · 07-07-2022, 11:32 AM

Quote:

Originally Posted by SAJM

You are correct about the pico pi
pip is a minefield!

not really. In general, you need to learn the tool before using it, otherwise you may be in for some surprises.
pip is a relatively complex package management software for python with a lot of features. And also it has a very good documentation.

SAJM · 07-07-2022, 11:49 AM

Here is the problem that I cannot get my head round.

Thonny can be complied from Slackbuild or built using sbopkg or slpkg.

Yet there are number of postings here that say install it using pip?

Very confusing.

Dunc. · 07-07-2022, 12:20 PM

I tried using the slackbuild for installing thonny. It did not work perhaps because aarch64 is not very well established yet. I feel sure with enough patience I could have found an answer but I had just got my new toy a raspberry pico and I wanted to try it out. Thonny is mentioned in the pico documentation for programming it with the micropython version of python. I took the easy option of using pip to install it. I think the slackbuild would have done a better job of installing thonny. The menu entry does not have an icon but it works and for me that is the main issue.

Dunc.

henca · 07-07-2022, 01:35 PM

Quote:

Originally Posted by SAJM

Here is the problem that I cannot get my head round.

Thonny can be complied from Slackbuild or built using sbopkg or slpkg.

Yet there are number of postings here that say install it using pip?

Very confusing.

There are different ways to do things and they have their advantages and disadvantages.

Sbopkg and slpkg are both package managers capable of building and installing packages from source using SlackBuild scripts from slackbuilds.org. The advantage of using such a tool is that the installation will be fully compatible with all tools used to handle Slackware packages. You can then continue to use those tools to remove or upgrade those installed packages.

Pip is kind of a package manager for python, however, it does not know anything about how Slackware handles its packages. Using pip as root to install a package system-wide might mess things up with packages installed by Slackware package management tools. Such a thing might explain why "slpkg health" displays a number less than 100%. Maybe pip has removed or replaced some file installed by a Slackware package.

One safe way to use pip might be to run it as an ordinary user and make sure that everything installed by pip is installed below the home directory of the user. Slackare packages usually do not mess in users home directories.

Usually slpkg is my favorite to install third party packages from slackbuilds.org, but I must admit that I haven't installed Thonny. Sometimes SlackBuild scripts from slackbuilds.org does not work. If that is the case it does not matter which tool you use or if you run the SlackBuilds by hand. If that would be the case with Thonny or some of its dependencies it might be wort trying to install Thonny from some other third party repository or to install Thonny with pip below your home directory.

The disadvantage of using packages from different third party repositories is that those packages might share some dependencies, but those repositories don't keep track of packages from other repositories.

As most good third party packages come from slackbuilds.org I would stick to slackbuilds.org for almost all third party packages and resort to pip if some python package from slackbuilds.org does not work.

regards Henrik

dhalliwe · 07-07-2022, 02:00 PM

Quote:

Thonny can be complied from Slackbuild or built using sbopkg or slpkg.

Yet there are number of postings here that say install it using pip?

Very confusing.

That's because you are not listening to the advice that people are giving you, and figuring out exactly what that advice means.

In order to run, the operating system (in this forum, Slackware Linux) needs to find the executable file for the program.

That executable file may need other programs/libraries in order to run. ("Dependencies")

Installation places these files (from an install package or some other source) into the places the system looks for programs and libraries.

Slackware provides basic tools that will take programs/libraries that are contained in Slackware packages (a particular form of an archive of files) and install them where they need to go. Slackware's basic tools will not resolve/find/install dependencies. You need to do that yourself. You also need to obtain the packages and download them yourself.

Additional tools are available that can be added to Slackware that can also automatically check for updates, resolve dependencies, download packaqes, and install them. Some of these tools only work on updates to Slackware core packages. Others can also handle third-party sources that have additional programs/packages that are not part of core Slackware. These fall under "package management tools".

SlackBuilds.org does not provide packages - it provides scripts that will build packages (after you download the source linked to at SlackBuilds.org). Once you build the package, you can install it yourself - but you need to install it after it is built. Building the package does not do that for you.

Additional software exists that can automatically check SlackBuilds.org to find updates, download stuff, and rebuild packages.

Python comes with its own package management tool called "pip", which will handle downloading new packages and their dependencies - but only for packages that are created for use by your installed version of python. It will not handle anything outside of the python world (e.g., regular Slackware core packages, or other non-python programs.

People have advised you that mixing different package management tools will lead to Bad Places - basically different tools messing with each other and creating confusion. Libraries and programs that don't match, or are installed by one tool and overwritten or removed by another tool. The other tools do not automatically know that you installed (or removed) some software with a different tool.

The differences in methods of installing software are critical, and this is why people keep asking you to provide exactly what steps you took when you said "I installed X...". When you say "I am lost", and people ask you "where were you when you last knew where you were, and what did you do next?", you are not helping people (who are trying to help you) by saying "well, I was at home and went for a drive". Exact details matter.

SAJM · 07-14-2022, 04:22 AM

Hello again!
I've installed 15.0 and have KDE Plasma on the screen.
Just need to get the network up and I will try python3/thonny again.

FlinchX · 07-14-2022, 06:53 PM

Quote:

Originally Posted by SAJM

Hello again!
I've installed 15.0 and have KDE Plasma on the screen.
Just need to get the network up and I will try python3/thonny again.

Python 3 is part of 15.0, so you only need to install thonny from SBo. Not like the last time, but the right way, handling all its dependencies.

But before you start adding third party software, make sure your 15.0 is updated. It's been like half an year since it was released, there are updates that you can install with slackpkg.

SAJM · 07-15-2022, 08:11 AM

Woo Hoo!!!

I used slpkg and it's all working.

Thanks for all the help