Post AMSlD6nNJcllSnjO9A by ketmorco@mastodon.technology
 (DIR) More posts by ketmorco@mastodon.technology
 (DIR) Post #AMSl0HFB9o2a6WcLyK by kzimmermann@fosstodon.org
       2022-08-12T20:27:30Z
       
       0 likes, 0 repeats
       
       So #gaupol is the second Python-based package that broke with me on #Artix, the first being #calibre months ago (and still not recovered!). I wonder if this is because of shifting Python versions from the rolling release updates that break some sort of backwards compatibility or something.Anyone has a tip on what I could do to fix this? It's hard to debug because the stack trace only gives me Python grammar-specific error messages, such as an import error.
       
 (DIR) Post #AMSlD6nNJcllSnjO9A by ketmorco@mastodon.technology
       2022-08-12T20:29:48Z
       
       0 likes, 0 repeats
       
       @kzimmermann what's the import error? Unless the packages are just really poorly written they shouldn't break /that/ badly
       
 (DIR) Post #AMTtqeCM3Gif96juXA by kzimmermann@fosstodon.org
       2022-08-13T09:41:22Z
       
       0 likes, 0 repeats
       
       @ketmorco for gaupol is ImportError from `import gaupol` which makes me think it's some problem with the venv being used for it. For calibre it's one of the methods/functions of a module not being available for use. Donno for sure since I'm not with it atm. Something like runtime versioning disparity perhaps? At any rate, I'm wondering if it's the constant rolling releases that broke compatibility or something.