Update plot xlim #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should fix pythonprofilers#195. Increment should reflect the largest increment with respect to the previous line, which is not what the previous code was doing. If run in a for loop, for some reason it was accumulating the increments. I also disabled a test that was assuming that the increment of a function that deletes its temporaries need to be zero, which given the above should not be its behaviour.
Switch to entry_points for scripts
Fixes pythonprofilers#195 "large negative increment values"
All python n00bs should use `pip` these days. Those who shouldn't are not n00bs and won't be needing help from the readme.
Stop recommending `easy_install`
Previously, if the profiling was run on multiple same-named functions in different classes or modules, the plot legend did not make clear which bracket measured which function.
…legend Make function legend in mprof plot unambiguous
Optionally propagate the exit code
fix max_iter calc when float is given
Handle unicode files in a Python 2 and 3 compatible fassion using io.open
%memit: fix repeats for short-living statements
Store child processes by PID
Update README.rst
feat(peak): adds --func optional argument
Adapted from an answer to "Graphing a process's memory usage" on [Stack Overflow](https://stackoverflow.com/a/62876993/111424). Memory profiler is exactly the tool I've been looking for. But the Usage section of the README makes it seem so complicated to use that it scared me away! The Stack Overflow answer gets straight to the point and shows how simple it is to use. I think it deserves to be at the top of the README.
Add Quick Start to README
Fix typos: Relevant arguments
The last Travis year was a year ago. https://travis-ci.org/github/pythonprofilers/memory_profiler/builds
Delete .travis.yml
GitHub Action to lint Python code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I changed the plotting data to fit the xlim window, as I found that y-axis window are not nicely rescaled.
Related to pythonprofilers#105 (comment)