Python Scripts : strptime no longer works

[MisterRadish]

The problem

Converting string to datetime using strptime now produces error Error executing script (KeyError): '__import__' when running the script.)
example:
bookingdate = datetime.datetime.strptime("2024-04-01", "%Y-%m-%d")

What version of Home Assistant Core has the issue?

2024.12.0
2024.12.1
2024.12.2

What was the last working version of Home Assistant Core?

2024.11.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Python Scripts

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[gjohansson-ST]

I think you might need to import datetime first instead of using directly.

[home-assistant]

pyscript documentation
pyscript source

[MisterRadish]

I think you might need to import datetime first instead of using directly.

Thank you for the response.

In 2024.11.x
datetime.datetime.strptime("2024-04-01", "%Y-%m-%d") worked correctly without import

in 2024.12.0 if I try
datetime.datetime.strptime("2024-04-01", "%Y-%m-%d") causes " import'" error
Just adding from datetime import datetime causes "import not found" error
Just adding import datetime causes "import not found" error

What has changed and what am I missing?

[MisterRadish]

I think you might need to import datetime first instead of using directly.

Also this issue with integration:Python Scripts not pyscript?

[home-assistant]

python_script documentation
python_script source

[gjohansson-ST]

Nothing changed in the source code and it should work like you had it before so no idea right now actually.
I would need to test myself to see where it goes wrong.

[MisterRadish]

Nothing changed in the source code and it should work like you had it before so no idea right now actually. I would need to test myself to see where it goes wrong.

Further thoughts:-
today = datetime.datetime.now() works ok so the datetime module is accessiable but not the strptime function.

[MisterRadish]

On the off chance anybody else might be experiencing an issue with strptime I have found that:-
dt_util.parse_datetime("2024-05-01") and
datetime.datetime.fromisoformat("2024-05-01") both seem to work as long as your date is in the YY-mm-dd format. Not all my dates are however.

[straub]

In case it helps anyone: I ran into a very similar issue with datetime.datetime.strptime('14:00:00', '%H:%M:%S').time() in my python script under 2024.12. Since I was using it only to get a time object, I was able to replace it with calling datetime.time(14, 0, 0) directly.

This issue helped me identify the problematic call and try alternatives, so thank you! (The specific error I was experiencing was Error executing script (KeyError): '__import__' when running the script.)

[carlos-leopoly]

I have also run to the same issue. I’m using python_script heavily and several logics rely on strptime function. So I’m looking forward to the resolution.
I don’t have the competance and time to fix but I would be happy to help by testing or any other way if needed.

[WhoTheHeck]

I have the same issue since 2024.12.

can not use datetime.datetime.strptime anymore. Thanks to @MisterRadish, I got a workaround working based on datetime.datetime.fromisoformat

[gjohansson-ST]

So I gave this a test now on both dev and 2024.12.0 and I seem to have no issue at all.
Test script:

bookingdate = datetime.datetime.strptime("2024-04-01", "%Y-%m-%d")
logger.info(f"Date {bookingdate}")

Output:

2024-12-11 18:50:46.671 INFO (SyncWorker_5) [homeassistant.components.python_script] Executing testing.py: {}
2024-12-11 18:50:46.672 INFO (SyncWorker_5) [homeassistant.components.python_script.testing.py] Date 2024-04-01 00:00:00
2024-12-11 18:50:46.672 DEBUG (SyncWorker_5) [homeassistant.components.python_script] Output of python_script: `testing.py`:
{}

On dev we are still on py3.12 so I wonder if there is something that has changed here between the python versions that might have an impact.

[MisterRadish]

On dev we are still on py3.12 so I wonder if there is something that has changed here between the python versions that might have an impact.

Yup - the move to python 3.13 in 2024.12.0 could be the cause

[gjohansson-ST]

I can at least at this stage confirm that py3.13 is the cause of the issue

[MisterRadish]

A fix has been released in 2024.12.4. Thank you for your help @gjohansson-ST