On Mar 26, 1:33 pm, cas...@gmail.com wrote:
> On Sunday, March 25, 2012 9:59:56 PM UTC-7, Mensanator wrote:
> > OK, GMPY is now called GMPY2. No big deal, I can import as GMPY.
>
> > But why were scan0 and scan1 changed to bit_scan0 and bit_scan1?
>
> > What's the justification for that? I use thos
On Sunday, March 25, 2012 9:59:56 PM UTC-7, Mensanator wrote:
> OK, GMPY is now called GMPY2. No big deal, I can import as GMPY.
>
> But why were scan0 and scan1 changed to bit_scan0 and bit_scan1?
>
> What's the justification for that? I use those functions extensively
> in my library of Collatz
On Mar 26, 10:39 am, Terry Reedy wrote:
> On 3/26/2012 12:59 AM, Mensanator wrote:
>
> > OK, GMPY is now called GMPY2. No big deal, I can import as GMPY.
>
> > But why were scan0 and scan1 changed to bit_scan0 and bit_scan1?
>
> Guess: Either the functions changed or they want to regularize their
On 3/26/2012 12:59 AM, Mensanator wrote:
OK, GMPY is now called GMPY2. No big deal, I can import as GMPY.
But why were scan0 and scan1 changed to bit_scan0 and bit_scan1?
Guess: Either the functions changed or they want to regularize their names.
What's the justification for that? I use thos
On Mar 26, 2:59 pm, Mensanator wrote:
> OK, GMPY is now called GMPY2. No big deal, I can import as GMPY.
> But why were scan0 and scan1 changed to bit_scan0 and bit_scan1?
Python is not gmpy. You might be better served asking the project
maintainer(s).
> What's the justification for that? I use
OK, GMPY is now called GMPY2. No big deal, I can import as GMPY.
But why were scan0 and scan1 changed to bit_scan0 and bit_scan1?
What's the justification for that? I use those functions extensively
in my library of Collatz utilities and I had to re-edit them for no
obvious reason.
--
http://ma
