Skip to content

Members with min and or max values should not be allowed to be None  #218

Description

@claudiodsf

Currently, a member specification like the following:

keyword = float(min=0, max=1, default=0.5)

will pass validation when setting keyword = None.

I have therefore to check this afterwards in my code.

I was wondering, whether this could be implemented within ConfigObj.

More generally, there could be an option for allowing/disallowing None values, e.g.,

keyword = float(allow_none=False)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions