I'm trying to figure out if my Python code will safely handle dates beyond January 19, 2038, on a 32-bit Raspberry Pi OS. Specifically, I'm using the function `datetime.fromtimestamp(date_epoch).strftime("%A, %d.%m.%Y")`. Once we hit the epoch limit of 2,147,483,647, will this code still give me correct results? I'm currently using Python 3.11.2, but I want to know if there's a version that's prepared for this issue. How does Python perform with dates after 2038, especially on the 32-bit Raspbian OS? I came across some discussions indicating Python might be safe for up to 10,000 years into the future, but what's the current situation regarding the Year 2038 problem?
4 Answers
Honestly, you should definitely alter the date and give it a test. It’s the best way to see how your code will behave! Just make sure to keep track of any odd outputs.
Are you genuinely planning on running your code on a 32-bit Raspberry Pi in 2038? Seems a bit dated, doesn't it?
To directly test this out, you could set up a simple loop that increments the time by a day and logs the output. This way, you'll see the exact moment your Raspberry Pi starts to struggle with dates. Based on what I know, on a 32-bit system, the problem will occur as soon as you hit that January 19, 2038 threshold. You could also run a quick test with something like `import datetime; print(datetime.datetime.fromtimestamp(2200000000).strftime("%A, %d.%m.%Y"))` to see it in action.
Did you try implementing the code mentioned in that GitHub issue to see if you can reproduce the problem? It might give you clearer insights!
Yeah, but remember the Y2K bug? Folks were already worrying about 2038 back in 2000, and here we are, still discussing it 25 years later. Some people will definitely be using 32-bit Raspberry Pis in 13 years!