Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for subclasses (0.4 sec)

  1. RELEASE.md

            will no longer uprank input data of shape `(batch_size,)` to become
            `(batch_size, 1)`. This enables `Model` subclasses to process scalar
            data in their `train_step()`/`test_step()`/`predict_step()` methods. \
            Note that this change may break certain subclassed models. You can
            revert back to the previous behavior by adding upranking yourself in the
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Mon Aug 18 20:54:38 UTC 2025
    - 740K bytes
    - Viewed (2)
  2. docs/en/docs/release-notes.md

    avoids/fixes a potential security issue: as the returned object is passed directly to Pydantic, if the returned object was a subclass of the `response_model` (e.g. you return a `UserInDB` that inherits from `User` but contains extra fields, like `hashed_password`, and `User` is used in the `response_model`), it would still pass the validation (because `UserInDB` is a subclass of `User`) and the object would be returned as-is, including the `hashed_password`. To fix this, the declared `response_model`...
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Fri Sep 05 12:48:45 UTC 2025
    - 544.1K bytes
    - Viewed (0)
Back to top