On Sat, Jun 02, 2001 at 08:15:21PM -0600, Eric W. Biederman wrote:
> Bob Drzyzgula <[EMAIL PROTECTED]> writes:
>
> > I'll research this a bit more if you like... perhaps
> > there's a patch or a straightforward workaround (other
> > than the obvious "upgrade to Python 2.x").
> >
> > But, I suppose, you can at least take comfort in the fact
> > that it's not a user headspace error...
>
> Given that I haven't really learned python yet, I was suspecting
> lack of knowledge.
I have this same problem -- blame myself first. You'd
think we'd have learned by now, wouldn't you? I was a
bit baffled by your difficulty because I was doing the
testing on the machine with 2.0; if I hadn't seen the
obvious syntax work correctly there, and had instead
been trying to make it work on the machine with 1.5.2,
I'd probably still be tearing my hair out...
> We need reliable handling of unsigned 32 bit
> numbers so upgrade to python 2.0 is likely best, unless there
> is a good workaround.
I'll look into this a bit more tomorrow.
> If the solution is upgraed to 2.0 we need
> a way to check to make certain you are running python 2.0
This part is easy: sys.version will tell you, we
can simply exit if the version isn't high enough.
--Bob
