You are not logged in.
Pages: 1
Here's the deal:
Until recently, the pysqlite package was version 1.1.6 - the python namespace is "pysqlite" (i.e. from pysqlite import *)
Now, pysqlite 2.0.3 is considered stable, but the namespace has changed to pysqlite2 (i.e. from pysqlite2 import *).
The problem is, some code may still use (want to use) pysqlite... so, should the AUR packages be two-fold (pysqlite and pysqlite2), or should pysqlite be dropped for pysqlite 2.0 - opinions?
Offline
probably both. gtk and gtk2..
still...sounds messy.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
keep both? they fit alongside each other happily.
Offline
Pages: 1