Skip to content

Conversation

gillins
Copy link
Member

@gillins gillins commented Sep 11, 2025

No description provided.

@gillins gillins requested a review from neilflood September 11, 2025 23:09
@neilflood
Copy link
Member

I think I would change the emphasis in the introduction. While obviously this is important for developers who want timing information, more importantly it supports developers trying to build in logical timing information to present to their users. So, the developer is the intended audience of the timinghooks package, but their own users are the intended users of the resulting timing information. The developer decides what logical groupings make sense for their code, but this makes it easy for these to be available in final production code, without lots of extra time.time() and print() statements. Does that make sense?

Possibly also worth noting that while it can be installed separately, it is likely that including this module with the code for the developer's own software is a more appropriate way to use it (at least, I think so ?). That avoids having it as a separate dependency, with all the potential traps involved.

The most useful statistic provided is the 'total'. The others are there for more detailed analysis if desired, but probably much less useful in general.

I possibly should add all of the above points to the doco for the package itself......

@neilflood
Copy link
Member

Not sure if I am helping. See what you think......

@gillins gillins merged commit 5900c04 into ubarsc:main Sep 15, 2025
@gillins gillins deleted the timinghooks branch September 15, 2025 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants