There is also a lot of indexing and thus bounds checking in the Rust code. The vectors are not pre-allocated with a reasonable capacity, thus they need to reallocate quite often.
You should also check whether NaiveDateTime::parse_from_str is perhaps the bottleneck – for that, use a profiler.
I reckon this is not your first question of the form "Why is Rust slower than <Python code with no context>". This is not a helpful way to frame questions. If you are really curious why it's slower, then use a profiler and check it for yourself. If you are merely trying to subvert the question to say Rust is slow, then refrain from posting.
Yes, t! run more than 1 time. I ran it in evcxr, and I thought the first time of running t! would count time of compiling. But by testing it in diffrent running time, I found out running times make no difference.
Of course I am not just tring to say Rust is slow, which makes no sense to me, and no doubtly Rust is much faster than Python. I am just to lean the tricks to write fase Rust code. Profiling is fine, but for now I am just avoid writting some apparenmental "wrong" codes such as being in these simple code.
Thanks for your reply.