Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for _Ctype_ (0.13 sec)

  1. fastapi/utils.py

            field_info = field_info or FieldInfo(
                annotation=type_, default=default, alias=alias
            )
        else:
            field_info = field_info or FieldInfo()
        kwargs = {"name": name, "field_info": field_info}
        if PYDANTIC_V2:
            kwargs.update({"mode": mode})
        else:
            kwargs.update(
                {
                    "type_": type_,
                    "class_validators": class_validators,
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sat Aug 31 23:46:03 UTC 2024
    - 7.8K bytes
    - Viewed (0)
  2. tests/test_compat.py

        from fastapi._compat import is_pv1_scalar_field
    
        field_info = FieldInfo()
        field = ModelField(
            name="foo",
            field_info=field_info,
            type_=Union[str, List[int]],
            class_validators={},
            model_config=BaseConfig,
        )
        assert not is_pv1_scalar_field(field)
    
    
    @needs_pydanticv2
    def test_get_model_config():
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Wed Sep 11 07:45:30 UTC 2024
    - 3.5K bytes
    - Viewed (0)
  3. docs/pt/docs/history-design-future.md

    </blockquote>
    
    ## Investigação
    
    Ao usar todas as alternativas anteriores, eu tive a chance de aprender com todas elas, aproveitar ideias e combiná-las da melhor maneira que encontrei para mim e para os times de desenvolvedores com os quais trabalhava.
    
    Por exemplo, estava claro que idealmente ele deveria ser baseado nos _type hints_ padrões do Python.
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Mon Jul 29 23:35:07 UTC 2024
    - 4.5K bytes
    - Viewed (0)
Back to top