[SOLVED] Python "typing_extensions" not found with setuptools_scm-8.1.0
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Python "typing_extensions" not found with setuptools_scm-8.1.0
Hi! According to -current changelog, python-typing_extensions is no longer needed with the new python-setuptools_scm-8.1.0, so it was removed. But trying to run Deluge I get an error claiming that typing_extensions module is missing. I tried to recompile Deluge and reinstall all python modules, but the error persists. Installing typing_extensions via pip globally makes Deluge work again. Any idea how to solve this?
so maybe typing-extensions on SBo is not a dependency of python-setuptools_scm anymore but looks like a dependency of some other python module that deluge uses.
so maybe typing-extensions on SBo is not a dependency of python-setuptools_scm anymore but looks like a dependency of some other python module that deluge uses.
Oh, I've thought typing-extensions functions were merged into the new setuptools_scm, but now I see that maybe it was removed because setuptools_scm or any other official package no longer required it. Thanks!
Hrm, I wonder why, libtorrent-rasterbar is the only one in the deluge queue that doesn't build here and that can be fixed by removing the "-Dpython-egg-info=ON " line from the slackbuild or bumping the version to 2.0.10.
You are right though, typing-extensions should only be needed with python versions <3.10. Do you still have some other slackbuilds still built against 3.9 or some other leftover 3.9 cruft?
Hrm, I wonder why, libtorrent-rasterbar is the only one in the deluge queue that doesn't build here and that can be fixed by removing the "-Dpython-egg-info=ON " line from the slackbuild or bumping the version to 2.0.10.
I'm not sure but I recall being able to recompile against current python an older libtorrent-rasterbar by removing the -Dgnutls=$GNUTLS parameter from ponce repository script, but keeping everything else, including the egg-info.
Quote:
Originally Posted by fourtysixandtwo
You are right though, typing-extensions should only be needed with python versions <3.10. Do you still have some other slackbuilds still built against 3.9 or some other leftover 3.9 cruft?
That is what I misunderstood from the changelog message. I thought that typing-extensions components were somehow included in other package, but it seems that its usage was just deprecated, if I'm not wrong.
I'm not sure but I recall being able to recompile against current python an older libtorrent-rasterbar by removing the -Dgnutls=$GNUTLS parameter from ponce repository script, but keeping everything else, including the egg-info.
That is what I misunderstood from the changelog message. I thought that typing-extensions components were somehow included in other package, but it seems that its usage was just deprecated, if I'm not wrong.
-Dgnutls=$GNUTLS doesn't exist in the libtorrent-rasterbar slackbuild which is unchanged from the 15.0 repo. Anyways I'll be mentioning the change to the maintainer as the egg info is going the way of the dodo.
As for typing-extensions, I believe you have some python 3.9>3.11 issues to clean up on your box. I've posted recently for what to search for if you plan on looking into it.
I think there's some misunderstanding about typing-extensions here.
typing-extensions extends typing module from Python's standard library, so that new features could be used on older Python versions. It was added to -current when setuptools-scm started requiring it and -current was still on Python 3.9. Now that Python is upgraded to 3.11 and setuptools-scm added a condition to require typing-extensions only for python < 3.10, it was removed from -current.
This doesn't mean that typing-extensions isn't needed at all, only that nothing in -current depends on it at the moment. If something in deluge's dependency tree requires it, then you need to install it to fulfill that requirement.
I think there's some misunderstanding about typing-extensions here.
typing-extensions extends typing module from Python's standard library, so that new features could be used on older Python versions. It was added to -current when setuptools-scm started requiring it and -current was still on Python 3.9. Now that Python is upgraded to 3.11 and setuptools-scm added a condition to require typing-extensions only for python < 3.10, it was removed from -current.
This doesn't mean that typing-extensions isn't needed at all, only that nothing in -current depends on it at the moment. If something in deluge's dependency tree requires it, then you need to install it to fulfill that requirement.
Nice! Thanks for the explanation, now it makes sense.
Sorry, the confusion was on my part. I had been thinking typing-extensions was removed from ponce's repo and ignoring it was being built. I had been thinking of emailing ponce about it, but didn't because of a situation like this one.
Sorry, the confusion was on my part. I had been thinking typing-extensions was removed from ponce's repo and ignoring it was being built. I had been thinking of emailing ponce about it, but didn't because of a situation like this one.
I removed it but I added it back when I saw Pat removing it from current.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.