| 1 |
Hello, |
| 2 |
|
| 3 |
The consensus of bug 452122 [1] was that pysqlite2 shall be deprecated |
| 4 |
and masked for removal, and all packages needing it shall be modified |
| 5 |
to depend on sqlite flag of Python. |
| 6 |
|
| 7 |
A short rationale for those who didn't follow the bug: 'pysqlite2' was |
| 8 |
practically imported into successive Python versions as 'sqlite3' |
| 9 |
module. As far as I'm aware, it is currently practically unmaintained |
| 10 |
and does not support Python 3. |
| 11 |
|
| 12 |
Theoretically, Python 2.5 version of 'sqlite3' is older (has less |
| 13 |
features) than 'pysqlite2'. However, a) I didn't see a single package |
| 14 |
having trouble with that, b) I think the support for other versions |
| 15 |
shouldn't introduce additional work unless it is really desired |
| 16 |
by users. |
| 17 |
|
| 18 |
Anyway, the plan is to do the following: |
| 19 |
|
| 20 |
1) make sure that all packages which support 'sqlite3' module have |
| 21 |
proper deps (either one-of deps, or dep on sqlite3 only), |
| 22 |
|
| 23 |
2) fix the remaining packages to use 'sqlite3' instead of 'pysqlite2', |
| 24 |
|
| 25 |
3) mask dev-python/pysqlite2 for removal, |
| 26 |
|
| 27 |
4) PROFIT for a month or two, |
| 28 |
|
| 29 |
5) remove dev-python/pysqlite2 from any-of deps in the packages which |
| 30 |
still had it, |
| 31 |
|
| 32 |
6) remove dev-python/pysqlite2. |
| 33 |
|
| 34 |
What are your thoughts? |
| 35 |
|
| 36 |
[1]:https://bugs.gentoo.org/show_bug.cgi?id=452122 |
| 37 |
|
| 38 |
-- |
| 39 |
Best regards, |
| 40 |
Michał Górny |
Archives