In it, the developers were advised of inspect.callargs and other options besides eval. After some timing tests, the followup ends:
> as it stands now, the execution time should be dominated by what the function is actually doing (and for wall clock time, we’ve just arrived from the network). So we’ll probably deprecate our neat eval trick in favour of getcallargs.
In it, the developers were advised of inspect.callargs and other options besides eval. After some timing tests, the followup ends:
> as it stands now, the execution time should be dominated by what the function is actually doing (and for wall clock time, we’ve just arrived from the network). So we’ll probably deprecate our neat eval trick in favour of getcallargs.