Hi,
splitter.py line 137
replace sys.maxint with something else otherwise 64 bit boxes will
break as long as python 2.5 isn't here.
-1 is working for python 2.4 , otherwise 0xffffffff should be
sufficient.
I'm sorry but i haven't tested a test build.
regards
Uwe
I only muck with python to get things done, so some of the idiomatic things
aren't always clear to me. Is the intention of the maxint here to append to
the end of the list? In that case, why not use append, or use the actual
length of the array?
(And, won't -1 *not* do the right thing?)
Anyway, it's true that sys.maxint breaks on x86_64.
On Tue, Mar 28, 2006 at 10:36:39PM +0200, Uwe Hoffmann wrote:
splitter.py line 137
replace sys.maxint with something else otherwise 64 bit boxes will
break as long as python 2.5 isn't here.
-1 is working for python 2.4 , otherwise 0xffffffff should be
sufficient.
--
Matthew Miller mattdm@mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
Uwe Hoffmann wrote:
Hi,
splitter.py line 137
replace sys.maxint with something else otherwise 64 bit boxes will
break as long as python 2.5 isn't here.-1 is working for python 2.4 , otherwise 0xffffffff should be
sufficient.
How about using len(self._windows) ?
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
That makes sense to me -- in fact, seems better, 'cause hey, that's actually
what is _meant_. 
On Wed, Mar 29, 2006 at 08:17:12PM -0800, Robin Dunn wrote:
> splitter.py line 137
> replace sys.maxint with something else otherwise 64 bit boxes will
> break as long as python 2.5 isn't here.
> -1 is working for python 2.4 , otherwise 0xffffffff should be
> sufficient.
How about using len(self._windows) ?
--
Matthew Miller mattdm@mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>