memory-leaks

Still reachable: lots of words in many pages.
git clone https://git.kevinlegouguec.net/memory-leaks
Log | Files | Refs | README | LICENSE

commit 8fb1c19e7c3a654eff67552ef09afd1f86761371
parent cf8a3f15ee1c80b874be10cbdd34496b84560f59
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Tue, 14 Jan 2025 23:45:45 +0100

Update Python IDE notes

Diffstat:
Mguides/languages/python.org | 9+++++++++
1 file changed, 9 insertions(+), 0 deletions(-)

diff --git a/guides/languages/python.org b/guides/languages/python.org @@ -18,6 +18,13 @@ Tumbleweed at least does not make it easy: every remnant of the previous versions & the corresponding Python runtime. + - Update 💡 :: The trick is to take the =$y= off. Requires a leap + of faith since neither ~zypper info~ nor zypper completions seem + to know about the unsuffixed names, but ~zypper install~ knows to + look for /capabilities/ instead of packages. Presumably + "installing capabilities" means they will be upgraded + automatically to =$((++yy))= when the time comes? + - I have no idea how to cajole zypper into installing those "suggested" dependencies; =--recommended= does not cut it, =--suggested= does not exist. @@ -38,3 +45,5 @@ Tumbleweed at least does not make it easy: 4 new packages to install. #+end_src + - Update 🫥 :: as of 2025-01-14, Tumbleweed's =python311= packages + no longer suggest nor recommend anything?