nodd / lineprofilergui Goto Github PK

Useful to estimate how long one has to wait on the next optimization iteration...

• publish on pypi
• add tests/coverage
• add translations
• add licence file
• reference similar projects (spyder and pycharm plugins)
• conda recipe

It looks like a neon right now…
Take #15 into account.

At least basic tests to check if it runs (for starters)
See https://pytest-qt.readthedocs.io/en/latest/index.html

It needs a visual indicator at least, like an icon somewhere

This message is displayed:

 QWindowsWindow::setMouseGrabEnabled: Not setting mouse grab for invisible window QWidgetWindow/'QDockWidgetClassWindow'

I guess it's because the widget is breiefely hidden and shown again as floating, but I don't know what I can do about it. Maybe a Qt bug ? For reference, I use Qt v5.12.9 and pyqt5.

log is useful to know if htere were any problems while running the script, but less so since I can't figure how to have it in realtime (bufferisation problem somewhere). It could be opened via a button for example.

There is no timing for the function declaration, but it would be visually clearer to not gray it out, except for functions that did not run at all.
The problem is with multi-line declarations, we have to not gray-out the whole declaration.

gotta sell the product !

• Github page
• Create new issue / enhancement request

Select an application icon and use it

In regarding pyqt and getting the lineprofiler working, can we document what packages are needed?

Adding a screenshot in the readme will give people most of the information they need on if this is something they want or not. If it looks good and continues to be maintained, I'll add a link to it in the line_profiler README itself.

It requires an additional config value in ui.

Better show that a script is running: mouse pointer, statusbar message...

Allows for quick comparison and less mouseclicks overall.

• windows size/position
• dockwidget status / size / position

Save the last few (10 by default ?) profiling results for easy comparison, switching between them via a qcombobox

In addition, show the execution time/date (start, stop ?) for each run

It could be useful to load a stored .lprof file, for example to have a saved reference.

• hide columns
• group by files (?)
• editor configuration: #9
• dark mode
• history depth: #3

Failed runs, unsuccessfull attempts... It should be possible to remove them from the history without restarting the GUI.

See:

• https://doc.qt.io/qt-5/i18n-source-translation.html
• https://doc.qt.io/qt-5/qtlinguist-hellotr-example.html
• https://doc.qt.io/qt-5/qtlinguist-index.html

Add coloration syntax to the code lines
Check that it is still readable with coloring.

Group results by file, then by functions, instead of the actual behavior o grouping by function only ?
It could be useful when profiling lots of functions in different files, but it can be annoying since it adds another layer to expand/collapse.

It could be an option in the application settings.
It could group only if there is multiple functions in the file, and let the other functions alone.