The package does depend on dev-python/pysqlite:2 but not on Python implementation USE=sqlite. The pysqlite package is no longer maintained and compatible with Python 2 only; while the builtin 'sqlite3' module is basically a maintained clone/fork of pysqlite. If the package actually imports pysqlite2 unconditionally, please check whether it wouldn't work with the builtin 'sqlite3' module as well. If it does, upstream should probably fix the package to import 'sqlite3' *at least* when 'pysqlite2' is not available. If it doesn't, please let us know and we will know that pysqlite needs to be kept in the tree. If the package simply supports 'sqlite3', please let us know or update the deps. However, the latter is unnecessary since the 'old' Python eclass doesn't provide a proper way to do this, and we may decide to drop pysqlite entirely after getting feedback for the packages depending on it.
The code uses pysqlite2 only. Need to investigate if it would work with sqlite3.
Fix committed. Could someone try to find upstream bug tracker and upstream it?
From my understanding, because pysqlite has been removed, and the ebuild already replaces the pysqlite import with sqlite3 import, this bug is fixed?