zlacker

[parent] [thread] 5 comments
1. MangoT+(OP)[view] [source] 2025-12-06 20:06:17
> With the benefit of hindsight, though, Python 3 could have been done as a non-breaking upgrade.

Not without enormous and unnecessary pain.

replies(2): >>JoshTr+y1 >>SoftTa+GQ
2. JoshTr+y1[view] [source] 2025-12-06 20:20:49
>>MangoT+(OP)
It would absolutely have been harder. But the pain of going that path might potentially have been less than the pain of the Python 2 to Python 3 transition. Or, possibly, it wouldn't have been; I'm not claiming the tradeoff is obvious even in hindsight here.
replies(1): >>MangoT+kW
3. SoftTa+GQ[view] [source] 2025-12-07 05:52:59
>>MangoT+(OP)
Pain on whose part? There was certainly pain porting all the code that had to be ported to Python 3 so that the Python developers could have an easier time.
replies(2): >>MangoT+FU >>MangoT+EW
◧◩
4. MangoT+FU[view] [source] [discussion] 2025-12-07 06:48:22
>>SoftTa+GQ
> There was certainly pain porting all the code that had to be ported to Python 3

Bitch bitch bitch bitch bitch bitch bitch bitch

Adding parentheses to print isn't that hard, especially with tooling to do it for you. You fucking spoiled brat, you deserved to be beat

◧◩
5. MangoT+kW[view] [source] [discussion] 2025-12-07 07:12:29
>>JoshTr+y1
I think you have causation reversed: it would have been at least two orders of magnitude greater to act like moving to python 3 was harder than staying. But you do you boo :emoji-kissey-face:
◧◩
6. MangoT+EW[view] [source] [discussion] 2025-12-07 07:14:38
>>SoftTa+GQ
Yes, exactly. customers need to stop acting like a bitch if they wanna be taken seriously
[go to top]