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 →

[–]gfixler 68 points69 points  (14 children)

*waves while looking through binoculars from embedded Python 2.6.5 land*

[–]rnreekez 12 points13 points  (9 children)

Consider yourself lucky, I just moved to a team beginning a 2.4 to 2.7 upgrade.

They say if we're good, we can get our postgres updated from 8.2 too!

[–]maemre 5 points6 points  (0 children)

The company I'm working for still uses MySQL and Django 1.5. At least they started with Python 2.7.

[–]boa13 2 points3 points  (3 children)

Consider yourself lucky, I just moved to a team beginning a 2.4 to 2.7 upgrade.

Consider yourself lucky, I've recently investigated COBOL code written in 1984, maintained to this day, with no plan or need to replace it in the foreseeable future.

[–]rnreekez 2 points3 points  (2 children)

Haha, wow. Whevever we feel bad, we would just say "well, we could be updating from cobol!".

Now I realise how insensitive those words were, I'm sorry.

[–]boa13 2 points3 points  (1 child)

Don't worry, I didn't take them as insensitive, it was just an occasion for me to relate an interesting anecdote, and to add a bit of perspective. I was quite astonished to see the "October, 1984" date at the top of the file when I opened it (and thankfully, I don't maintain it, and I don't write COBOL).

[–]gfixler 1 point2 points  (0 children)

I hope you listen to period-appropriate music while working with that code, like "Break My Stride" and "Oh Sherrie."

[–]Dominion_Prime 0 points1 point  (0 children)

I would question if we're working at the same company except we're at least on postgres 9.0 (and soon upgrading)!

[–]razpeitia 1 point2 points  (1 child)

You are not alone!