Yonatan Goldschmidt

Fix crc32c's __main__ for Python 3

3

By the way, https://github.com/PyCQA/pylint/issues/2571 was fixed in pylint 2.10, but I see that we're using 2.6 so I don't want to do the upgrade in this small fix PR. ---...

[Linux] Read & parse /proc/pid/auxv

10

## Summary * OS: Linux * Type: new-api ## Description The auxiliary vector exposes useful information about processes, and is available at `/proc/pid/auxv`. Many values are given as addresses in...

[Linux] Properly raise ZombieProcess in exe() method

2

## Summary * OS: Linux * Bug fix: yes * Type: core * Fixes: None ## Description `psutil.Process(pid).exe()` returns `""` for zombie processes, incorrectly. It should raise `ZombieProcess`, and return...

## Summary * OS: General * Type: core / performance ## Description Certain per-process getter APIs (such as `Process.cmdline()`, `Process.environ()`) can be used in case the user knows that a...

Changing the type of an object at runtime

3

Surprisingly, Python allows you to change the `__class__` attribute of an object: ``` In [1]: class A: ...: def __init__(self): ...: self.x = 5 ...: self.y = "hi" ...: ...:...

Dumping outputs without interrupting the profiling

2

Hi @benfred , we're using py-spy in our [gProfiler](https://github.com/Granulate/gprofiler/) which is a system-wide continuous profiler. gProfiler continuously scans for new processes and invokes py-spy on them. Every set interval ("profiling...

Inspired by [async-profler's](https://github.com/jvm-profiling-tools/async-profiler) `-g` option, which shows method's full signature, so `java/io/File.list` becomes `java/io/File.list()[Ljava/lang/String;` for example. We can add something similar in py-spy: we already have the "read locals" logic...

add `from __future__ import annotations` if adding forward-reference annotations

8

``` $ cat a.py class A: def f(self): return self $ cat b.py import a a.A().f() $ monkeytype run b.py $ monkeytype apply a class A: def f(self) -> A:...

Here's how it looks:  This PR uses metadata included in the output of `perf script --header`. Other `stackcollapse` scripts can be modified to output relevant metadata as comments, and...

`perf script` accepts `--header` which prints a bunch of metadata about the recording as comments (prefixed with `#`) before printing the stacks themselves. `stackcollapse-perf.pl` knows this and skips the comments....