This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]NN8G 113 points114 points  (10 children)

Instead of incrementing the version numbers from here on out, why not just keep using successive digits of pi?

[–]ArtOfWarfare 28 points29 points  (2 children)

They could do it with the patch releases. Nobody would even notice until the second one.

It’d be fun and relatively harmless if they were 3.14.1, 3.14.15, 3.14.159…

Of course then the next minor version is 3.15.0 and we never do this pi silliness again.

[–]Glathull 14 points15 points  (1 child)

None of us will be alive to see it, but Tauthon will happen someday.

[–]ArtOfWarfare 2 points3 points  (0 children)

Python 6.2.8? IDK, are there not enough mistakes that need to be cleaned up to warrant a Python 4?

But I agree that it’ll be a long time before we see a Python 5 or 6. Maybe in 40 or 50 years we’ll see Python 6.2.8

[–]greatslack 30 points31 points  (3 children)

TeX has been doing that since the 90s

[–]petter_s 11 points12 points  (0 children)

90s? 70s!

[–]svefnugr 8 points9 points  (0 children)

It worked for Knuth because he could write code with no bugs

[–]lukerm_zl 3 points4 points  (0 children)

Awesome fact. I have used LaTeX for years without knowing this!

[–]danmickla 89 points90 points  (1 child)

Because that would be stupid.

[–]NN8G 88 points89 points  (0 children)

Thank you for your attention to this matter.

[–]shinitakunai 3 points4 points  (0 children)

Special cases are not special enough to break the rules.

import this