why did GMPY change the names of its functions?

[alex23]

On Mar 26, 2:59 pm, Mensanator <mensana... at aol.com> 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 those functions extensively
> in my library of Collatz utilities  and I had to re-edit them for no
> obvious reason.

Well, the obvious reason is that it's a different version which offers
no promise of API backwards compatibility.