On Tue, Jul 01, 2003 at 05:01:07PM +0300, Mohammed Sameer wrote: > sid and sarge has a python2.2-bsddb3 package but not woody > > $ apt-cache policy python2.2-bsddb3 > python2.2-bsddb3: > Installed: (none) > Candidate: (none) > Version Table: > 3.3.0-5.2 0 > -1 ftp://ftp.jp.debian.org unstable/main Packages > -1 ftp://ftp2.it.debian.org testing/main Packages > > same for python 2.1 > > there is python2.2 but not pybsddb > > I don't think that we need to repackage or hack it if the aim is trying > to push it into debian. since the requirements are in both stable and > unstable > the problem'll be testing the packages. I can fire a request to package > bug report and ask for a sponsor on debian mentors. But still the same > problem. How can it be tested ? > > But if the aim is to provide a woody package for now then i think that > the hack is required. >
Alrighty then.. I think I have the solution to all this mess. I have moved the dict2db.py script to the main pyduali/ pkg. I will start calling it pyduali when packaged (in anticipation for the proper duali work starting very very soon). I simply switched it so it would use whatever dbm is available. I also took care of a little quirk that seems to happen on Windows when generating the dictionary. I simply cannot downgrade to Python 2.1. It does not offer the ability to encode from unicode->any-encoding. I can only decode using the builtin unicode() function. That is not good enough if I were to suport multiple encodings.. so forget it. Woody has 2.2, that's good enough. Let me know if you need anything else. later Mohammed Elzubeir _______________________________________________ Developer mailing list [EMAIL PROTECTED] http://lists.arabeyes.org/mailman/listinfo/developer
