The problem is not that loop itself, is comparing the pointer not the values.

I doubt it's a bug.

You tried something like 137 ** 484116095749277306305823515203559673336730587743919594525320099154177818624.

What you expect, computing enormous power with arbitrary precision arithmetic?

@ZeroIntensity, could you argue your decisions?

math.h pow() wouldnt do this ;) but being objects is logic, but maybe an exception

math.h pow() wouldnt do this ;)

math.h is not for arbitrary precision integer arithmetic.

@ZeroIntensity, could you argue your decisions?

I didn't mean to remove pending, GitHub did it automatically when I applied other labels. I agree with you that using massive exponents will take... very long, to say the least.

math.h pow() wouldnt do this ;) but being objects is logic, but maybe an exception

What exception do you expect?

    a << a
    ~~^^~~
OverflowError: too many digits in integer

but with pow there is no error control and is keep allocating all the time

OverflowError comes up when you try to convert a very large Python int to a C integer. It doesn't come up with Python-to-Python calls.

>>> a
484116095749277306305823515203559673336730587743919594525320099154177818624
>>> b
137
>>> a**b
Traceback (most recent call last):
  File "<python-input-7>", line 1, in <module>
    a**b
    ~^^~
ValueError: Exceeds the limit (4300 digits) for integer string conversion; use sys.set_int_max_str_digits() to increase the limit
>>>

in this way there is a ValueError, here there is a limit, in the other case not

Because it's a much smaller operation. pow(a, b) is not the same complexity as pow(b, a). Multiplying 484116095749277306305823515203559673336730587743919594525320099154177818624 only 137 times is a lot faster than the other way around.

sure, well a**b has limits of digits but b**a not, well I just notify, you know better if it worth to check it.

regards.

OverflowError: too many digits in integer

But your problem is not the shift - it's power: b**a (I corrected my message above).

ValueError: Exceeds the limit (4300 digits) for integer string conversion; use sys.set_int_max_str_digits() to increase the limit

This message coming from limits in binary->decimal conversion of the output, not from computing of the power.

in this way there is a ValueError, here there is a limit, in the other case not

It's because limiting "other cases" will ruin sane computations of people.

It's easy to estimate size of your power:

>>> a = 241; b = 137; a = b << a
>>> a*math.log2(b)  # bit length
3.4362715795059602e+75

Wikipedia knows something like the quettabyte - it's 10**30 bytes...

sure, well ab has limits of digits but ba not

No. Neither power has "digits limit", except from coming from hardware limitations (available memory, etc).

You can read about integer conversion string limitations here:
https://docs.python.org/3/library/stdtypes.html#int-max-str-digits

(BTW, I suspect this odd limit will produce new issues like that.)

The ValueError needs first to compute the result to trigger the exception, and in this case is not computable.

Languages like nodejs or ruby answers Infitity directly, but is other philosopy.

But well, It makes sense not implementing power limits and don't limiting other more powerful hardwares, I close the ticket.

thanks.

Languages like nodejs or ruby answers Infitity directly

Are you sure? Are you using big integers on whose languages or trying to compute floating-point powers?

but is other philosopy

Or reading of the documentation;-)