author Benoit Jacob <>
Tue, 08 Jul 2014 17:23:17 -0400
changeset 206789 e5f8bd650ef1a7a0bfbee817a5e434b9fc5c62a0
parent 152013 ed0b6a11532d2905ce3c5c55f230b0e89b8971dd
permissions -rw-r--r--
Bug 1035394 - Fix dangerous public destructors in dom - r=ehsan


A collection of ideas and notes about stuff to implement in future versions.
"#NNN" occurrences refer to bug tracker issues at:


 * #387: system-wide connections (netstat).
 * OpenBSD support.

 * #371: CPU temperature (apparently OSX and Linux only; on Linux it requires
   lm-sensors lib).

 * #250: net ifaces speed.

 * (Linux) resource limit get/set - see man prlimit.

 * on Windows is slow:

 * Windows binary for Python 3.3 64-bit.

 * #269: expose network ifaces RX/TW queues.


 * #355: Android support.

 * #276: GNU/Hurd support.

 * NetBSD support?

 * DranflyBSD support?

 * AIX support?

 * examples/ (same as 'pidof' cli tool)

 * examples/ (same as 'pstree' cli tool)
    * get_threads() should also return thread names in order to implement it

 * examples/ (using tk).

 * system-wide # open file descriptors:

 * Number of system threads.
    * Windows:

 * #357: what CPU a process is on.

 * thread names:


 * [Linux]: process cgroups ( They look
   similar to prlimit() in terms of functionality but uglier (they should allow
   limiting per-process network IO resources though, which is great). Needs
   further reading.

 * cpu_percent(): current default interval is 0.1 so that by default it will
   produce a meaningful value. It represents a trap in case the user iterates
   over multiple processes though, as it introduces a big slowdown.
   Should it default to 0.0?

 * Rename connection ntuple's fields 'local_address', 'remote_address' to
   'laddr', 'raddr'  (note in accordance with

 * Process per-cpus percent (XXX Windows only?), see:!topic/psutil/ErrKTxAbu50

 * Should we expose OS constants (psutil.WINDOWS, psutil.OSX etc.)?

 * Python 3.3. exposed different sched.h functions:
   It might be worth to take a look and figure out whether we can include some
   of those in psutil.
   Also, we can probably reimplement wait_pid() on POSIX which is currently
   implemented as a busy-loop.

 * Certain systems (XXX figure out which ones exactly) provide CPU times about
   process children. On those systems Process.get_cpu_times() might return
   a (user, system, user_children, system_children) ntuple.