the1conf 1.2.3__tar.gz → 1.3.0__tar.gz

{the1conf-1.2.3 → the1conf-1.3.0}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: the1conf
-Version: 1.2.3
+Version: 1.3.0
 Summary: All in one configuration management tool for your python applications.
 License-Expression: MIT
 License-File: LICENSE
 Keywords: configuration,settings,cli,click,pydantic
 Author: Eric CHASTAN
 Author-email: eric@chastan.consulting
-Requires-Python: >=3.12,<3.13
+Requires-Python: >=3.12
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: Operating System :: OS Independent
@@ -268,7 +268,11 @@ All these path are unified into OS independent variables:
 - `user_home`: The path to the current user's home directory.
 
 3. **Execution Stage Variable**: The `exec_stage` variable is particularly useful for differentiating configurations based on the execution stage (ie. environment) like development, production, test, etc. 
-This variable is predefined  but users needs to set its value either through the command line of in an environment variable named.
+This variable is predefined  but users needs to set its value either through the command line or in an environment variable. You have different options to pass it value:
+- **Command Line Argument**: Using the Click integration, you can pass `--stage`,`--env` or `--exec-stage` argument to set the execution stage.
+- **Environment Variable**: You can set the `EXEC_STAGE`, `STAGE` or `ENV` environment variable to define the execution stage.
+- **Pass a value to resolve_vars()** : You can also directly pass the execution stage value in the `values` dictionary when calling `resolve_vars()`.
+- **Redefine the variable**: You can redefine the `exec_stage` variable in your configuration class if you want to set a different default , different keys or change its behavior.
 
 ## Key Lookup with Fallback
 

{the1conf-1.2.3 → the1conf-1.3.0}/README.md

@@ -244,7 +244,11 @@ All these path are unified into OS independent variables:
 - `user_home`: The path to the current user's home directory.
 
 3. **Execution Stage Variable**: The `exec_stage` variable is particularly useful for differentiating configurations based on the execution stage (ie. environment) like development, production, test, etc. 
-This variable is predefined  but users needs to set its value either through the command line of in an environment variable named.
+This variable is predefined  but users needs to set its value either through the command line or in an environment variable. You have different options to pass it value:
+- **Command Line Argument**: Using the Click integration, you can pass `--stage`,`--env` or `--exec-stage` argument to set the execution stage.
+- **Environment Variable**: You can set the `EXEC_STAGE`, `STAGE` or `ENV` environment variable to define the execution stage.
+- **Pass a value to resolve_vars()** : You can also directly pass the execution stage value in the `values` dictionary when calling `resolve_vars()`.
+- **Redefine the variable**: You can redefine the `exec_stage` variable in your configuration class if you want to set a different default , different keys or change its behavior.
 
 ## Key Lookup with Fallback
 

{the1conf-1.2.3 → the1conf-1.3.0}/pyproject.toml

@@ -1,9 +1,9 @@
 [project]
 name = "the1conf"
-version = "1.2.3"
+version = "1.3.0"
 description = "All in one configuration management tool for your python applications."
 readme = "README.md"
-requires-python = ">=3.12,<3.13"
+requires-python = ">=3.12"
 license = "MIT"
 license-files = ["LICENSE"]
 authors = [
@@ -46,7 +46,7 @@ packages = [
 autopep8 = ">=2.3.2"
 black = ">=26.1.0"
 ipykernel = ">=7.1.0"
-ipython = ">=9.6.0"
+ipython = ">=9.60"
 jupyter = ">=1.1.1"
 mypy = ">=1.19.1"
 pyls-black = ">=0.4.7"