Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#28227 closed Bug (fixed)

Make BaseRangeField importable at django.contrib.postgres.forms as documented

Reported by: Matthew Schinckel Owned by: nobody
Component: contrib.postgres Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

​https://docs.djangoproject.com/en/1.10/ref/contrib/postgres/fields/#defining-your-own-range-types

BaseRangeField is not available in "django.contrib.postgres.forms", only "django.contrib.postgres.forms.ranges".

Change History (5)

comment:1 by Matthew Schinckel, 7 years ago

Component: Uncategorized → contrib.postgres

comment:2 by Claude Paroz, 7 years ago

Easy pickings: set
Triage Stage: Unreviewed → Accepted
Type: Uncategorized → Bug

I think that both BaseRangeField and RangeWidget should be included in the __all__ list. I suspect their absence in that list was an oversight when those classes have been added.

comment:3 by Tom Forbes, 7 years ago

Has patch: set

I made a patch here: ​https://github.com/django/django/pull/8526

I hope this is sufficient?

comment:4 by Tim Graham <timograham@…>, 7 years ago

Resolution: → fixed
Status: new → closed

In e9c7f118:

Fixed #28227 -- Allowed importing BaseRangeField/RangeWidget from contrib.postgres.forms.

comment:5 by Tim Graham, 7 years ago

Summary: Custom Range documentation refers to non-importable class → Make BaseRangeField importable at django.contrib.postgres.forms as documented
Note: See TracTickets for help on using tickets.
Back to Top