Without a doubt, you have limited memory and address space on your computer; for example, for a good 64-bit machine, 64 GB of RAM [[about 2**36 bytes]] and several TB disks (used as a swap space for virtual memory) [[about 2**41 bytes]]. Thus, the "upper bound" of a long Python integer will be the largest represented in available memory - a little less than 256**(2**40) , if you are absolutely not in a hurry and can trade like crazy, a little more than 256**(2*36) (with a small replacement, but not too much) in practice.
Unfortunately, to represent these ridiculously huge numbers in decimal will take quite a lot of time and , therefore, instead of showing them, let me check with you - why would you even care about such a ridiculous sequence of numbers that makes up the "top" border "about which you ask? I think this is more practical, so to speak: especially on a 64-bit machine with a decent amount of RAM and disk, the upper bounds of long integers are way larger than anything you have ever calculated. Technically, a mathematician would insist, of course, they are not endless ... but in practice they can be like that! -)
Alex martelli
source share