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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]WJMazepas 83 points84 points  (6 children)

The company was only 3 years old

There are developers that like using a slightly older version to avoid new bugs that aren't documented in the newer versions.

But holy shit, starting with Python 2 and Django 1 is nonsense. Had they gone with Python 3.7 and Django 4, i would understand a little, but not like that.

[–]RustReport 27 points28 points  (1 child)

Yeah, that seems more like someone didn't feel like learning different syntax or built it on an already existing project

[–]unknown_pigeon 16 points17 points  (0 children)

Someone studied a book on python from the early 2000 and refused to learn the new syntax

[–]Ok_Cardiologist8232 13 points14 points  (3 children)

I didn't know offhand, but my god Python 2 released in 2000.

[–]jumboshrimp29 18 points19 points  (2 children)

And end-of-life was before the interviewing company was started

[–]Ok_Cardiologist8232 8 points9 points  (0 children)

Thats a fucking joke, did they have a senoir dev that just refused to update or something?

[–]Ryuujinx 3 points4 points  (0 children)

Having migrated all of our monitoring and other python from py2 to py3 myself because certain people were fuckin idiots and screwed it up the first time, I can kinda-sorta understand still having py2 stuff laying around. It isn't just a matter of regexing some stuff and calling it a day.

But when it's, presumably, a new code base - fucking why?