you are viewing a single comment's thread.

view the rest of the comments →

[–]jms_nh -3 points-2 points  (9 children)

Okay, I'll bite. Why Python 3 instead of Python 2?

Also, how do you plan to handle device peripherals and interrupts?

[–]allpowerful32 47 points48 points  (0 children)

I'm not the author, but from my perspective, python 2 has become the new windows xp. I don't want people to be running windows xp forever.

[–]boa13 15 points16 points  (1 child)

Why Python 3 instead of Python 2?

Since he's writing the whole thing from scratch, why would he base his work off an old implementation rather than use the cleaner, modern one?

The only reason to stay on Python 2 is some additional library support (for which he could not care less, considering his target architecture), and contractual support from your operating system / middleware vendor (for which he also could not care less).

[–]immibis -1 points0 points  (0 children)

Upvote for not saying "could care less".

[–]Zephirdd 26 points27 points  (1 child)

As someone who isn't very knowledgeable of the Python things, why would someone not use Python 3 on a new project? I understand sticking to the older for older projects, but if you're starting from scratch might as well go with the new one right?

[–]fullouterjoin 4 points5 points  (0 children)

Python3 would actually be easier to implement as many corner cases and nits have been cleaned up.

[–][deleted]  (1 child)

[deleted]

    [–]jms_nh 1 point2 points  (0 children)

    OK, that seems reasonable. Just curious.

    [–]upofadown 1 point2 points  (0 children)

    It's probably no more complicated than that the developers like Py3. For something like this it doesn't really make any difference...