On Nov 04, Matthias Klose wrote:
> Donovan Baarda writes:
> > On Sun, Nov 04, 2001 at 05:23:30PM +0100, Joel Rosdahl wrote:
> > [...]
> > > But there is a problem: The current (from 1997) upstream version[1]
> > > doesn't work with Python >= 2.0. Now, Berthold Hoellmann, Oleg
> > > Broytmann and o
Donovan Baarda <[EMAIL PROTECTED]> writes:
> I would hope that you also make a python1.5-kjbuckets so that older
> python1.5 programs that used it can still use it. You them also make
> a python2.2-kjbuckets (2.2.0-port.20011104) package if you want
> something newer.
>
> If you want to support t
Donovan Baarda writes:
> On Sun, Nov 04, 2001 at 05:23:30PM +0100, Joel Rosdahl wrote:
> [...]
> > But there is a problem: The current (from 1997) upstream version[1]
> > doesn't work with Python >= 2.0. Now, Berthold Hoellmann, Oleg
> > Broytmann and others have ported[2] kjbuckets to work with n
On Sun, Nov 04, 2001 at 05:23:30PM +0100, Joel Rosdahl wrote:
[...]
> But there is a problem: The current (from 1997) upstream version[1]
> doesn't work with Python >= 2.0. Now, Berthold Hoellmann, Oleg
> Broytmann and others have ported[2] kjbuckets to work with newer
> Pythons, but it's not as o
Joel Rosdahl writes:
> 5) Use date in version, i.e. 2.2.port.20011104 or similar. (Best
>solution I can come up with.)
but use something like 2.2.0.port.011104, so you don't need an epoch
for the next official 2.2.1 version.
Hi,
I maintain python-kjbuckets, so I'm supposed to update it to conform
to the new policy.
But there is a problem: The current (from 1997) upstream version[1]
doesn't work with Python >= 2.0. Now, Berthold Hoellmann, Oleg
Broytmann and others have ported[2] kjbuckets to work with newer
Pythons,
6 matches
Mail list logo
