Changed python version requirement to >=3.9 to fix error:
pygobject requires Python <4.0,>=3.9, so it will not be satisfied for
Python >=3.8,<3.9
Changes to be committed:
modified: poetry.lock
modified: pyproject.toml
This allows building with both psutil 6.x and 7.x. Closes#817.
Upstream [1] released psutil 7.0.0 recently, which caused a build failure on nixpkgs ci [2].
Checking release notes [3], `memory_info_ex` was removed (unused in auto-cpufreq),
and minimum python version requirements were increased to what this project uses already anyways.
[1] https://pypi.org/project/psutil/#history
[2] https://hydra.nixos.org/build/292453144/log
[3] https://github.com/giampaolo/psutil/blob/master/HISTORY.rst#700
Tested with:
```patch
diff --git a/flake.nix b/flake.nix
index ab3449b..89a11db 100644
--- a/flake.nix
+++ b/flake.nix
@@ -1,6 +1,6 @@
{
inputs = {
- nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
+ nixpkgs.url = "github:NixOS/nixpkgs/staging-next";
};
outputs = {nixpkgs, ...} @ inputs: let
```
* create a cli for better visual monitor, live and stats
- created a system info module
- created system monitor module
- fixed avg_all_core_temp not defined
* fixed snap package error and added missing implementations
* add config.py and config_event_handler.py
also introduces the utils folder
* update config imports and variables
* add 'pyinotify' dependency
* config: check for changes using threading
* config: handle errors and new eventsx
* config: set_path even if file doesn't exist and make new ConfigParser on every update
* fix get_config call
* config: check for changes on moved file
* call notifier.start() manually to prevent hanging
* config: update comments
* battery: fix config imports
* config: fix config deletion detection
* Add load from user config in XDG_CONFIG_HOME if available (#672)
* Add load from user config from in XDG_CONFIG_HOME if available
This update introduces the flexibility to load the configuration file from
multiple locations, prioritizing user preferences and system standards.
Previously, the configuration was strictly read from a hardcoded
system path (`/etc/auto-cpufreq.conf`). Now, the application first checks if the
user has specified a configuration file path via command line arguments. If not,
it looks for a configuration file in the user's config
directory (`$XDG_CONFIG_HOME/auto-cpufreq/auto-cpufreq.conf`). If neither is
found, it defaults to the original system-wide configuration file.
This allows users to add their auto-cpufreq configuration to their dotfiles.
* If --config is set but invalid, exit with error
* Remove redundant empty string check on config file path
* Remove duplicate isfile check for config path
See also: https://github.com/AdnanHodzic/auto-cpufreq/pull/672#discussion_r1548003119
* Update configuration options in README
See also: #672
* config: move find_config_file function and fix finding home directory
* auto_cpufreq: fix hanging on --daemon, --live, and --monitor
* swap pyinotify for patched version
---------
Co-authored-by: Steven Braun <steven.braun.mz@gmail.com>
