Getting "!!python/object/..." for enums in my schema

[kolanos]

I'm using Django REST Framework with both django-filter and django-enumfields and am seeing the following in my schema:

openapi: 3.0.2
info:
  title: API Documentation
  version: '1.0'
paths:
  /api/v1/addresses/:
    get:
      operationId: listAddress
      description: Returns all addresses.
      parameters:
      - name: page
        required: false
        in: query
        description: A page number within the paginated result set.
        schema:
          type: integer
      - name: city
        required: false
        in: query
        description: city
        schema:
          type: string
      - name: primary
        required: false
        in: query
        description: primary
        schema:
          type: string
      - name: state
        required: false
        in: query
        description: state
        schema:
          type: string
          enum:
          - !!python/object/apply:api.enums.USState
            - AL
          - !!python/object/apply:api.enums.USState
            - AK
          - !!python/object/apply:api.enums.USState
            - AS
          - !!python/object/apply:api.enums.USState
            - AZ
          - !!python/object/apply:api.enums.USState
            - AR
          - !!python/object/apply:api.enums.USState
            - CA
...

Anyone know where these !!python/object/... are coming from and how to fix? I assume it is an incompatibility between DRF, django-filters and django-enumfields -- but am not finding where DRF is pulling these enums from. Other enums (non-query ones) work just fine.

Versions used:

• djangorestframework==3.12.4
• django-filter==2.4.0
• django-enumfields==2.1.1

Thanks in advance.

[kolanos]

Was able to pinpoint the enum schema generation to: https://github.com/carltongibson/django-filter/blob/main/django_filters/rest_framework/backends.py#L168

The !!python/object/... stuff appears to be coming from the YAML encoding. Whatever django-filter is getting for choices, it's just passing that through to the YAML encoder. Doesn't appear to follow the same method that DRF uses to generate the enum schema. The DRF method works with django-enumfields without any changes, though. Would be nice if django-filter just used that method.