chutils 3.1.0__tar.gz → 3.2.0__tar.gz

chutils-3.2.0/.chutilsignore

@@ -0,0 +1,6 @@
+.idea/
+.pytest_cache/
+.venv/
+dist/
+build/
+*.egg-info/

{chutils-3.1.0 → chutils-3.2.0}/.gitignore

@@ -1,185 +1,186 @@
-# Byte-compiled / optimized / DLL files
-__pycache__/
-*.py[cod]
-*$py.class
-
-# C extensions
-*.so
-
-# Distribution / packaging
-.Python
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-wheels/
-share/python-wheels/
-*.egg-info/
-.installed.cfg
-*.egg
-MANIFEST
-
-# PyInstaller
-#  Usually these files are written by a python script from a template
-#  before PyInstaller builds the exe, so as to inject date/other infos into it.
-*.manifest
-*.spec
-
-# Installer logs
-pip-log.txt
-pip-delete-this-directory.txt
-
-# Unit test / coverage reports
-htmlcov/
-.tox/
-.nox/
-.coverage
-.coverage.*
-.cache
-nosetests.xml
-coverage.xml
-*.cover
-*.py,cover
-.hypothesis/
-.pytest_cache/
-cover/
-
-# Translations
-*.mo
-*.pot
-
-# Django stuff:
-*.log
-local_settings.py
-db.sqlite3
-db.sqlite3-journal
-
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
-# PyBuilder
-.pybuilder/
-target/
-
-# Jupyter Notebook
-.ipynb_checkpoints
-
-# IPython
-profile_default/
-ipython_config.py
-
-# pyenv
-#   For a library or package, you might want to ignore these files since the code is
-#   intended to run in multiple environments; otherwise, check them in:
-# .python-version
-
-# pipenv
-#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
-#   However, in case of collaboration, if having platform-specific dependencies or dependencies
-#   having no cross-platform support, pipenv may install dependencies that don't work, or not
-#   install all needed dependencies.
-#Pipfile.lock
-
-# UV
-#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#uv.lock
-
-# poetry
-#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-#poetry.lock
-
-# pdm
-#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#pdm.lock
-#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
-#   in version control.
-#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
-.pdm.toml
-.pdm-python
-.pdm-build/
-
-# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
-__pypackages__/
-
-# Celery stuff
-celerybeat-schedule
-celerybeat.pid
-
-# SageMath parsed files
-*.sage.py
-
-# Environments
-.env
-.venv
-env/
-venv/
-ENV/
-env.bak/
-venv.bak/
-!examples/.env
-
-# Spyder project settings
-.spyderproject
-.spyproject
-
-# Rope project settings
-.ropeproject
-
-# mkdocs documentation
-/site
-
-# mypy
-.mypy_cache/
-.dmypy.json
-dmypy.json
-
-# Pyre type checker
-.pyre/
-
-# pytype static type analyzer
-.pytype/
-
-# Cython debug symbols
-cython_debug/
-
-# PyCharm
-#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
-#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
-#  and can be added to the global gitignore or merged into this file.  For a more nuclear
-#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
-.idea/
-
-# Ruff stuff:
-.ruff_cache/
-
-# PyPI configuration file
-.pypirc
-
-# Project-specific documentation
-PUBLISHING.md
-project.txt
-changelog.txt
-*.log.*
-*.log
-
-# Local chutils cache
-.chutils/
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+!examples/.env
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Project-specific documentation
+PUBLISHING.md
+project.txt
+changelog.txt
+*.log.*
+*.log
+
+# Local chutils cache
+.chutils/
+.chutils_dashboard_history.json

{chutils-3.1.0 → chutils-3.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: chutils
-Version: 3.1.0
+Version: 3.2.0
 Summary: Набор простых и удобных утилит для Python, который избавляет от рутины при работе с конфигурацией и логированием в новых проектах.
 Author-email: Chu4hel <sergeiivanov636@gmail.com>
 License-Expression: MIT
@@ -9,14 +9,23 @@ Requires-Python: <3.15,>=3.10
 Requires-Dist: exceptiongroup>=1.2.2; python_version < '3.11'
 Requires-Dist: python-dotenv>=1.2.2
 Requires-Dist: pyyaml>=6.0.3
+Provides-Extra: aws
+Requires-Dist: boto3>=1.34.0; extra == 'aws'
 Provides-Extra: captcha
 Requires-Dist: httpx>=0.27.0; extra == 'captcha'
 Provides-Extra: crypto
 Requires-Dist: cryptography>=42.0.0; extra == 'crypto'
 Provides-Extra: date
 Requires-Dist: python-dateutil>=2.9.0; extra == 'date'
+Provides-Extra: db
+Requires-Dist: aiosqlite>=0.20.0; extra == 'db'
+Requires-Dist: alembic>=1.13.0; extra == 'db'
+Requires-Dist: asyncpg>=0.29.0; extra == 'db'
+Requires-Dist: sqlalchemy>=2.0.0; extra == 'db'
 Provides-Extra: full
+Requires-Dist: boto3>=1.34.0; extra == 'full'
 Requires-Dist: cryptography>=42.0.0; extra == 'full'
+Requires-Dist: google-cloud-secret-manager>=2.20.0; extra == 'full'
 Requires-Dist: httpx>=0.27.0; extra == 'full'
 Requires-Dist: keyring>=25.7.0; extra == 'full'
 Requires-Dist: opentelemetry-api>=1.41.1; extra == 'full'
@@ -32,6 +41,8 @@ Requires-Dist: rapidfuzz>=3.9.0; extra == 'full'
 Requires-Dist: rich>=15.0.0; extra == 'full'
 Requires-Dist: selenium>=4.27.0; extra == 'full'
 Requires-Dist: watchdog>=6.0.0; extra == 'full'
+Provides-Extra: gcp
+Requires-Dist: google-cloud-secret-manager>=2.20.0; extra == 'gcp'
 Provides-Extra: json
 Requires-Dist: python-json-logger>=3.2.1; extra == 'json'
 Provides-Extra: metrics
@@ -278,20 +289,71 @@ To use this feature, install `watchdog`:
 
 ### 3. Secret Management
 
-`SecretManager` looks for secrets in the following order: **Keyring > .env File > Environment Variables**.
+`SecretManager` provides a unified abstraction for managing secrets using a custom chain of providers (`SecretProvider`)
+and automatic fallback logic.
+
+By default, `SecretManager` searches for secrets in the following order: **Keyring > .env File > Environment Variables
+**.
 
 ```python
 from chutils import SecretManager
 
 secrets = SecretManager("my_awesome_app")
 
-# Save once
+# Save secret (will be written to the first writable provider in the chain)
 secrets.save_secret("API_KEY", "secret-value-123")
 
-# Use everywhere
+# Retrieve secret
 key = secrets.get_secret("API_KEY")
 ```
 
+#### Built-in Providers
+
+You can configure the providers list explicitly:
+
+```python
+from chutils import SecretManager
+from chutils.secret_manager.providers import KeyringProvider, DotEnvProvider, EnvProvider
+
+secrets = SecretManager(
+    service_name="my_app",
+    providers=[
+        KeyringProvider(),
+        DotEnvProvider(),
+        EnvProvider()
+    ]
+)
+```
+
+#### Cloud Secret Managers
+
+The library supports transparent integration with AWS Secrets Manager and Google Secret Manager:
+
+```python
+from chutils import SecretManager
+from chutils.secret_manager.providers import AWSSecretManagerProvider, GCPSecretManagerProvider, EnvProvider
+
+# Initialize cloud providers (requires installation of chutils[aws,gcp])
+aws_provider = AWSSecretManagerProvider(region_name="us-east-1")
+gcp_provider = GCPSecretManagerProvider(project_id="my-gcp-project")
+
+# Create a SecretManager with the chain: AWS -> GCP -> Environment Variables.
+# If AWS or GCP calls fail due to network/permissions or the secret is missing,
+# SecretManager logs a warning and automatically falls back to EnvProvider.
+secrets = SecretManager(
+    service_name="my_service",
+    providers=[aws_provider, gcp_provider, EnvProvider()]
+)
+```
+
+Install cloud dependencies:
+
+```bash
+pip install chutils[aws]   # For AWS (boto3)
+pip install chutils[gcp]   # For GCP (google-cloud-secret-manager)
+pip install chutils[all]   # For all optional packages
+```
+
 #### Disabling Keyring (Optional)
 
 In environments like Docker or CI/CD where `keyring` is unavailable, you can suppress warnings and skip the check:

{chutils-3.1.0 → chutils-3.2.0}/README.md

@@ -217,20 +217,71 @@ To use this feature, install `watchdog`:
 
 ### 3. Secret Management
 
-`SecretManager` looks for secrets in the following order: **Keyring > .env File > Environment Variables**.
+`SecretManager` provides a unified abstraction for managing secrets using a custom chain of providers (`SecretProvider`)
+and automatic fallback logic.
+
+By default, `SecretManager` searches for secrets in the following order: **Keyring > .env File > Environment Variables
+**.
 
 ```python
 from chutils import SecretManager
 
 secrets = SecretManager("my_awesome_app")
 
-# Save once
+# Save secret (will be written to the first writable provider in the chain)
 secrets.save_secret("API_KEY", "secret-value-123")
 
-# Use everywhere
+# Retrieve secret
 key = secrets.get_secret("API_KEY")
 ```
 
+#### Built-in Providers
+
+You can configure the providers list explicitly:
+
+```python
+from chutils import SecretManager
+from chutils.secret_manager.providers import KeyringProvider, DotEnvProvider, EnvProvider
+
+secrets = SecretManager(
+    service_name="my_app",
+    providers=[
+        KeyringProvider(),
+        DotEnvProvider(),
+        EnvProvider()
+    ]
+)
+```
+
+#### Cloud Secret Managers
+
+The library supports transparent integration with AWS Secrets Manager and Google Secret Manager:
+
+```python
+from chutils import SecretManager
+from chutils.secret_manager.providers import AWSSecretManagerProvider, GCPSecretManagerProvider, EnvProvider
+
+# Initialize cloud providers (requires installation of chutils[aws,gcp])
+aws_provider = AWSSecretManagerProvider(region_name="us-east-1")
+gcp_provider = GCPSecretManagerProvider(project_id="my-gcp-project")
+
+# Create a SecretManager with the chain: AWS -> GCP -> Environment Variables.
+# If AWS or GCP calls fail due to network/permissions or the secret is missing,
+# SecretManager logs a warning and automatically falls back to EnvProvider.
+secrets = SecretManager(
+    service_name="my_service",
+    providers=[aws_provider, gcp_provider, EnvProvider()]
+)
+```
+
+Install cloud dependencies:
+
+```bash
+pip install chutils[aws]   # For AWS (boto3)
+pip install chutils[gcp]   # For GCP (google-cloud-secret-manager)
+pip install chutils[all]   # For all optional packages
+```
+
 #### Disabling Keyring (Optional)
 
 In environments like Docker or CI/CD where `keyring` is unavailable, you can suppress warnings and skip the check: