Replies: 1 comment 1 reply
-
I think that is legacy behavior. This package is quite old and used to be around in the pre 3.7 days, which meant dictionaries did not maintain order by default. So sorting was likely a way of achieving a consistent ordering. Now, I think it makes sense to remove this. Please submit a PR that changes this and notes it in the changelog. I think this should be a minor version bump rather than a patch version bump. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
By default, functions are sorted by name in printout. I would expect/prefer if they were listed in the order I specify them with
%lprun -f fun_b -f fun_a. Currently, the printout lists them in alphabetic orderfun_a,fun_b. The sorting happens here. It can't be deactivated. I wonder why it's being sorted alphabetically in the first place?Context: If I'm profiling multiple functions with long bodies each (common in scientific code...) the output would be easier to navigate if it was in my specified order. This is for "explorative" profiling of a large library where I don't know the bottlenecks beforehand.
Example:
Output:
fun_a,fun_bcontrary to specified orderExpected output:
fun_b,fun_amatching specified orderBeta Was this translation helpful? Give feedback.
All reactions