Scalene doesn't make use of exit codes
See original GitHub issueI’d expect that scalene <SOMETHING>
returns an error code to the calling shell.
Instead it always returns 0
.
This is also an issue when trying to set up CI for the scalene build itself since the scalene <SOMETHING>
succeeds even when there is something wrong with building libscalene.so
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Scalene: internal error: unable to find Python allocator ...
When starting scalene (with poetry run python -m scalene my_script.py ), I get the error Scalene: internal error: unable to find Python ...
Read more >scalene - PyPI
Scalene highlights hotspots (code accounting for significant percentages of CPU time or memory allocation) in red, making them even easier to spot. Scalene...
Read more >Scalene: a high-performance, high-precision CPU and ...
My personal POV is that the best way to optimize your Python code is to use native code (whether as libraries or through...
Read more >That time I optimized a Python program by 5000x - Reddit
TL;DR I used our Scalene profiler (pip install scalene) and some math to make an example program run 5000x faster.
Read more >TALK / Emery Berger / Scalene - YouTube
Scalene is a high-performance CPU and memory profiler for Python that does a number of things that other Python profilers do not and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I didn’t make a PR for upstream nixpkgs, here’s an excerpt of my private
overlay.nix
for my initial packaging attempt. I have to admit that I didn’t look much further into it since last year:Fixed the first issue with https://github.com/emeryberger/scalene/commit/20beb7003cef2485880420a034637c7479550243; updated on pip. Thanks for the report!
Second issue: so if I understand it, the problem you are describing in the second part is that
scalene
silently fails to run when its shared library is not present (failing over to doing CPU-only profiling). I’m not sure what the best alternative is here. Isn’t it better to just check for a failed build?