Goodconf

Latest version: v6.0.0

Safety actively analyzes 710445 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

3.1.0

========================

- Fixed type display in Markdown generation
- Changed markdown output format (trailing spaces were problematic).

3.0.1

====================

- pin to pydantic < 2 due to breaking changes in 2.0

3.0.0

==================

- TOML files are now supported as configuration source
- Python 3.11 and 3.10 are now officially supported
- Python 3.6 is no longer officially supported
- Requires Pydantic 1.7+
- Variables can now be set during class initialization

2.0.1

====================

- Change to newer syntax for safe loading yaml

2.0.0

===================

- **Backwards Incompatible Release**
Internals replaced with `pydantic <https://pypi.org/project/pydantic/>`_. Users can either pin to ``1.0.0`` or update their code as follows:

- Replace ``goodconf.Value`` with ``goodconf.Field``.
- Replace ``help`` keyword argument with ``description`` in ``Field`` (previously ``Value``).
- Remove ``cast_as`` keyword argument from ``Field`` (previously ``Value``). Standard Python type annotations are now used.
- Move ``file_env_var`` and ``default_files`` keyword arguments used in class initialization to a sub-class named ``Config``

Given a version ``1`` class that looks like this:

.. code:: python

from goodconf import GoodConf, Value

class AppConfig(GoodConf):
"Configuration for My App"
DEBUG = Value(default=False, help="Toggle debugging.")
MAX_REQUESTS = Value(cast_as=int)

config = AppConfig(default_files=["config.yml"])

A class updated for version `2` would be:

.. code:: python

from goodconf import GoodConf, Field

class AppConfig(GoodConf):
"Configuration for My App"
DEBUG: bool = Field(default=False, description="Toggle debugging.")
MAX_REQUESTS: int

class Config:
default_files=["config.yml"]

config = AppConfig()

2.0b3

=====================

- Environment variables take precedence over configuration files in the event of a conflict

Page 2 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.