| aFlag | I don't think >, <, <= and >= would be removed in py3.0 that makes no sense |
| hydan | if those operators are used, a TypeError will occur according to his presentation s |
| habnabit | But WHY? |
| qebab | according to whos presentation? |
| hydan | guido rossum |
| aFlag | what's the link? |
| hydan | his python 3000 presentation at google and oreilly conference serach python 3000 on google let me find his blog.. http://www.artima.com/weblogs/viewpost.jsp?thread=196889 there |
| habnabit | The presentation is 1.5 hors. hours. Where is the part about the comparison operators? |
| hydan | download the slides |
| habnabit | Don't have powerpoint. :P |
| hydan | hmm. it's toward the end if you use google video, you can click play then grab the scroll bar and scroll through the entire video that will display all the slides |
| habnabit | I found it. It sounds like he just means that comparing objects of different types will raise a ValueError? |
| hydan | it's slide number nine on the slides |
| habnabit | Er, TypeError. REMOVING it would just be stupid. |
| kosh | different types that don't make sense to compare so int to string will probably give an error |
| habnabit | Right. |
| kosh | int, float, decimal, long won't |
| hydan | hmm oook |
| kosh | so don't do if somegenerator > somefunc etc et |
| habnabit | I mean, what sense would it make to remove those from the language? :P |
| kosh | just supposed to prevent stupid comparisons |
| habnabit | kosh, hydan was saying that those operators were going to be completely removed from python. |
| hydan | that's what i understood him as saying. |
| KirkMcDonald | Which is patently ridiculous. |