pythonclock.org has been live for a long while now because of this
(fun fact, when I hired Python developers, questions about Python major version updates where frequent, and sometimes asked about Python 2.8 schedule, and even someone asked if PEP404 ring a bell... It’s not an interview question directly, but the pep number with the Python version 2.8 not found makes it such a perfect one that once you read about it, it’s a difficult one to forget, so I used this as a super small data point to have an idea (amongst everything else) if the senior developer I’m hiring slightly tries to keep up to date with the main language that pays his bills ;)
(as I wrote, that’s a super small detail in my Python interview data sheet, more a fun fact to give bonus point if they remember about it than anything else... but it’s amazing how many "senior" Python developers were clueless about Python 2 end of life one year ago. It really surprised me a lot!
pythonclock.org has been live for a long while now because of this (fun fact, when I hired Python developers, questions about Python major version updates where frequent, and sometimes asked about Python 2.8 schedule, and even someone asked if PEP404 ring a bell... It’s not an interview question directly, but the pep number with the Python version 2.8 not found makes it such a perfect one that once you read about it, it’s a difficult one to forget, so I used this as a super small data point to have an idea (amongst everything else) if the senior developer I’m hiring slightly tries to keep up to date with the main language that pays his bills ;) (as I wrote, that’s a super small detail in my Python interview data sheet, more a fun fact to give bonus point if they remember about it than anything else... but it’s amazing how many "senior" Python developers were clueless about Python 2 end of life one year ago. It really surprised me a lot!