This is the object handling output entries populating. It also handles the logo choice based on some system detections.

Relies on the first found packages manager to list the installed packages

ANSI Terminal colors using 8-bit values (256 available) Instantiated using a `bright` int and `value` int, similar to a `Colors` tuple. S

Custom entry gathering info based on configuration options

Values present in `DEFAULT_CONFIG` dictionary are required. New optional values may be added with `Utility.update_recursive` method. If

Relies on the `netifaces` module to detect LAN IP addresses

Simple terminal detection based on the `TERM` environment variable. It also displays the colors palette afterwards.

Retrieve kernel identity. [GNU/LINUX] If user-enabled, implement a version comparison against upstream data.

Simple wrapper to `archey.processes` to provide the number of running processes as an entry.

Archey own exception class

This enumeration lists supported operating systems (keys). Values contain their respective `distro` identifier. See <https://distro.readt

ANSI terminal colors enumeration. See <https://web.archive.org/web/20200627145120/http://www.termsys.demon.co.uk/vtansi.htm> or <https

Simple shell path detection based either on the `SHELL` environment variable or the local administrative database.

Uses `wmctrl` to retrieve some information about the window manager. If not available, fall back on a simple iteration over the processes.

This class provides results serialization for external usages. At the moment, only JSON has been implemented. Feel free to contribute to

Read system file with fallback on `platform` module to retrieve the system host-name

Retrieves the session name of the current logged in user

At startup, instantiate this class and set up some attributes according to their respective environment variable value.

At startup, instantiate this class to populate a list of running processes

Parse `/proc/cpuinfo` file to retrieve model names. If no information could be retrieved, call `lscpu`. `value` attribute is populated a

This class defines our custom assertion methods being used in Archey unit testing

Return static values for macOS and Windows. On Linux, use extensive environment variables processing to find known identifiers. Fallback

Uses `df` to compute disk usage across devices

Uses `distro` and `platform` modules to retrieve distribution and architecture information

An enumeration to store and declare each one of our entries. The string representation of keys will act as entries names. Values will be

Module base class

Relies on `lspci` or `pciconf` to retrieve graphical device(s) information

This class contains helper methods we commonly use in our entry unit tests.

System load average detection entry

Uses multiple methods to retrieve some information about the host hardware

First tries to use the `free` command to retrieve RAM usage. If not available, falls back on the parsing of `/proc/meminfo` file.

Taken from : <https://stackoverflow.com/q/6760685/10599709> This meta-class allows us to declare `Configuration` as a singleton. This way

Style base-class supporting terminal escape sequences for bold, colour, etc. Supports an arbitrary number of display attributes.

Tries to compute an average temperature from `sensors` (LM-Sensors). If not available, falls back on system thermal zones files (GNU/Linux)

Simple test cases to check `API` formatting behaviors.

Here, we mock the `open` call on `/proc/cpuinfo` with fake content. In some cases, `lscpu` output is being mocked too.

Test cases for the `Style` and `Colors` (enumeration / utility) classes

Simple test cases to check the behavior of `Configuration` singleton utility class. Values will be manually set in the tests below.

This class implements test cases for the custom Archey unit testing framework (#inception)

Custom entry unit test cases

DesktopEnvironment test cases

Here, we mock `subprocess.run` calls to disk utility tools.

Test cases for the `Distributions` (enumeration / utility) class.

`Distro` entry simple test cases

Simple test cases for our `Entry` abstract class

Here, we mock the `check_output` call to `lspci` to test the logic

This class implements test cases for our helper methods.

Test cases mocking for `/etc/hostname` file and `platform.node` call

Here, we mock the `platform` module calls and check afterwards that the output is correct.

Here, we mock the `netifaces` usages (interfaces and addresses detection calls)

LoadAverage `output` configuration-based coloration test class

Simple tests checking logos consistency and utility function logic

For this test we have to go through several eventualities : * Laptop / Desktop "regular" environments * Raspberry Pi * Virtual enviro

Simple test cases to check the behavior of the `Output` class.

Here, we mock the `check_output` calls and check afterwards that the outputs are correct. Sorry for the code style, mocking this class

Test cases for the `Processes` (singleton) class. To work around the singleton, we reset the internal `_instances` dictionary. This way,

Here, we mock the `check_output` call to `free` using all three levels of available ram. In the last test, mock with `/proc/meminfo` file ope

For this entry, we'll just verify that the output is non-null.

Test cases for our `Singleton` meta-class

This module verifies Archey temperature detection

For this entry, we'll verify that the output contains what the environment is supposed to give, plus the right number of "colorized" charac

Test cases for `Uptime` entry module

For this entry, we'll simply mock `getpass.getuser` call. If internals happen to fail, `ImportError` might be raised.

Simple test cases to check the behavior of `Utility` singleton utility class. Values will be manually set in the tests below.

Here, we end up mocking calls to `dig` or `urlopen`.

Here, we mock the `check_output` call and check afterwards that the output is correct. We've to test the case where `wmctrl` is not ins

Returns a pretty-formatted string representing the host uptime

Miscellaneous logic used in Archey internals

Uses different ways to retrieve the public IPv{4,6} addresses

A simple (sub-)class inheriting from `Entry` to use in testing.