Message363008
All the examples you mentioned seems to me to fix code, instead of breaking it.
About 1e300**10000, it's not a bug at all. No one can stop you to full your RAM in many other ways :-D
About conventions, it does not seems to me that Python cares about other languages very much, if it's more natural for normal people to expect a result instead of a consolidated one among devs. See `1 / 2 == 0.5`, for example.
> But by your own feature request, this would return an int and your
"feature" would bite you
You're citing the *optional* extra to the original idea. We can agree it is not a good addition at all.
I continue to think that nE+m, where n and m are integers, should return an integer. If this can break old code, I'm the first to think it should not be implemented, but I don't see any problem (yet). |
|
Date |
User |
Action |
Args |
2020-02-29 19:46:04 | Marco Sulla | set | recipients:
+ Marco Sulla, eric.smith, steven.daprano, zach.ware |
2020-02-29 19:46:04 | Marco Sulla | set | messageid: <1583005564.89.0.802306273552.issue39788@roundup.psfhosted.org> |
2020-02-29 19:46:04 | Marco Sulla | link | issue39788 messages |
2020-02-29 19:46:04 | Marco Sulla | create | |
|