Quote:
Originally Posted by teckk
Does another Slacker know what slack package contains tcl/tk? Python3.7 + comes with tkinter. But it won't work without tk.
This
http://tcl.sourceforge.net/
|
Good question, which shouldn't be a problem if OP did a full install of Slackware 14.2. Because while Python3 is a third party package (14.2 comes with Python2 only), SLackware 14.2 comes with tk.
Quote:
Originally Posted by FlinchX
@SAJM Did you have a full 14.2 install before you started to install SBo things?
Quote:
Originally Posted by SAJM
It was a few years ago but as far as I remember, yes.
|
|
Can you explicitly check if you have the tk package installed? The tk package that you can see here:
https://slackware.uk/slackware/slack...ackware64/tcl/
Quote:
Originally Posted by SAJM
Code:
bash-4.3# python3
Python 3.7.2 (default, Jul 2 2022, 13:59:41)
[GCC 5.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> python -m tkinter
|
Please, you don't `python -m tkinter` INSIDE a Python interactive session, thisi s a shell command. Since this is not obvious to you, IMHO you're just complicating your life a lot by using an outdated version of Slackware where you need to install Python 3 as third party.
I assume you're a casual Slackware user? How much sense does it make to you to just install Slackware 15.0 (it's already like half an year old, it comes with Python3 as well, so you won't have to do that part yourself), properly update it after installing (by upgrading packages from patches/packages, either manually, or with slackpkg), then just install thonny from slackbuilds.org the right way (like I suggested in my first answer in this thread - generate the queue with sqg, then load it in sbopkg and let it do the job)?
Quote:
Originally Posted by SAJM
How do I tell pip to use python3?
|
You don't "tell pip to use python3". Pip is the Python package manager. For
http://slackbuilds.org/repository/14.2/python/python3/ pip comes as part of that package and is named "pip3", to avoid name clashes with "pip" which is the pip for the system Python2 install in vanilla Slackware 14.2 Or you can invoke pip as a module through the python interpreter, for python3 at least, because I don't remember if this is true for python2 as well. Thus `python3 -m pip` would be the same as 'pip3' for the Python3 installed via SBo for Slackware 14.2
Quote:
Originally Posted by SAJM
Here is the problem I think
|
In situations like this (when you lack enough understanding of the problem) making assumptions is risky. Any wrong assumption that you make and apply will only make matters worse.
Quote:
Originally Posted by SAJM
Do I uninstall python2.
|
Why would you do that? Uninstalling python2, which is a vanilla 14.2 package, makes your Slackware install not being a full install anymore. And incomplete installs of Slackware most of the time are the main reason why further installing third party software goes wrong. Python3 from SBo that is provided for Slackware 14.2 does not interfere with the default python2 that comes with vanilla Slackware. It is stated explicitly here
http://slackbuilds.org/slackbuilds/1...python3/README
Quote:
Originally Posted by SAJM
Not sure what this is telling me?
Code:
bash-4.3# sbofind pip
|
sbofind is yet another third party frontend to SBo, not even related to sbopkg. By involving it in this context, you're adding yet another layer of complexity and confusion. You don't need to look for pip on SBo. See what I wrote about pip vs pip3 above.
Quote:
Originally Posted by SAJM
That's it. I'm defeated
|
Good. Feel free to consider my suggestion above then. About moving to Slackware 15.0, starting from scratch, and do things the right way, not the way you think it's right.
Quote:
Originally Posted by SAJM
I could uninstall Python 2 but as I mentioned earlier I'm nervous about messing something else up that may be depending on it.
|
The chances are very high that you will break some other vanilla packages that depend on it. This is the main reason why running full vanilla Slackware installs is the norm.
Quote:
Originally Posted by SAJM
However when I do this:
Code:
bash-4.3# which tk
which: no tk in (/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)
|
Why would you do this? tk is a package name. which looks for commands.