Timeline for answer to Why are Python's slice and range upper-bound exclusive? by Levon
Current License: CC BY-SA 4.0
Post Revisions
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2024 at 19:12 | history | edited | mkrieger1 | CC BY-SA 4.0 |
deleted 42 characters in body
|
| Aug 6, 2018 at 12:13 | comment | added | Levon | @YonatanNir It's the same reasoning, and for consistency. Otherwise, you'd have functions with the same name that differ in behavior based on whether default values have been provided or not. I.e., for increasing ranges, range(num) is really the same as range(0, num) and range(0, 1, num). It's easier all around (for API developers, and those using the API) to have consistent behavior. | |
| Aug 6, 2018 at 8:57 | comment | added | CodeMonkey | That might explain why range(num) does not include the upper limit, as you could say the num is only the amount of range which is 0 based. It does not explain why range(lower,upper) does not include it as we specifically requested that upper limit | |
| S Aug 14, 2017 at 13:45 | history | suggested | Solomon Ucko | CC BY-SA 3.0 |
Fixed various mistakes (spelling, grammar, naming, etc.)
|
| Aug 14, 2017 at 12:58 | review | Suggested edits | |||
| S Aug 14, 2017 at 13:45 | |||||
| Apr 12, 2017 at 7:31 | history | edited | URL Rewriter Bot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Jul 9, 2012 at 9:52 | vote | accept | wap26 | ||
| Jul 9, 2012 at 9:52 | |||||
| Jul 6, 2012 at 21:42 | history | edited | Levon | CC BY-SA 3.0 |
added 1 characters in body
|
| Jul 6, 2012 at 20:30 | history | edited | Levon | CC BY-SA 3.0 |
added 42 characters in body
|
| Jul 6, 2012 at 19:02 | history | edited | Levon | CC BY-SA 3.0 |
added 64 characters in body
|
| Jul 6, 2012 at 18:37 | history | edited | Levon | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Jul 6, 2012 at 18:04 | history | answered | Levon | CC BY-SA 3.0 |