Hi Titus,
the endless problems with dbm style interfaces that people run into on 
different Python installs (especially Mac) persuade me that we need to take 
action on the dbsqlite dbm-style interface to sqlite as we had previously 
discussed.  It seems like this would really solve the problem, which has wasted 
so much of our time already.  Looking at issue 3783 in the Python bugs 
database, it looks like no further progress has occurred there, so if we want 
action on this we will have to take it up ourselves. 

I took a look at the dbsqlite code, which suggested the following:

- we would need to implement basic handling of the c / n / w / r mode flags.

- how do you think we should test this prior to pushing it into a Pygr 
maintenance release (such as 0.8.3)? 

One obvious initial test is to run the Pygr test suite using this on mac 10.6 
apple-supplied Python 2.6, which lacks any decent dbm style interface (only dbm 
works, and it lacks any way of iterating...).  Running the full Pygr test suite 
using dbsqlite would at least test it in a wide variety of areas including 
sequence databases, worldbase, etc.  This would at least give us a basic sense 
of whether it solves our relevant Pygr needs...

What are your thoughts on this idea of trying to use sqlite as a dbm / shelve 
replacement?  It's been a long time since we've discussed it.

Yours,

Chris

-- 
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to pygr-...@googlegroups.com.
To unsubscribe from this group, send email to 
pygr-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en.

Reply via email to