After profiling the method I saw no different instructions being executed on the first and second calls, therefore it isn’t a behavior from the library that does delay operations as I erroneously said before. My guess is due to the .pyc not being created yet, by the second time it will take advantage of this and run faster.
I don’t think this would be an issue in production since the .pyc are going to be there after the first call.