Opened 10 years ago

Closed 8 years ago

#3827 closed (wontfix)

Correct Plural Form for words that end in "y".

Reported by: martin@… Owned by: Adrian Holovaty
Component: Core (Management commands) Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In my models.py file I was using:

class Story(models.Model):

and expecting it to work fine and display stories when it needs to be plural.

Unfortuantly it displayed "Storys" on the main admin page.

This needs to be fixed.

Change History (3)

comment:1 Changed 10 years ago by Adrian Holovaty

Resolution: wontfix
Status: newclosed

To specify the plural form, define verbose_name_plural in your class Meta. Django intentionally does not include a English-language pluralization engine.

comment:2 Changed 8 years ago by Django Trac

Resolution: wontfix
Status: closedreopened
Version: 0.96SVN

Could this be re-investigated on the grounds that:

a) There's not much documentation on the verbose_name_plural setting (at least none that's obvious under Model or admin).

b) Most frameworks tend to append ies instead of ys (CakePHP, Ruby etc) as a matter of simplicity for the developer.

c) English is the de-facto standard, otherwise we wouldn't be using an automatic plural 's' in the first place. Heck, the entire framework is english based - may as well do it right.

d) Non-English speakers can utilise the verbose_name_plural if required.

e) Making the development process 'easier', and less trawling through search engines, would certainly help the framework's credibility.

f) It will be harder to make a 'significant' change like this later - better to do it before it's too late.

I respect the comment made by Adrian but it's more of a matter of convenience than annoying non-english speakers (which can be covered in point c).

As an interim solution, to save the average developer time finding the 'solution' to this problem, could verbose_name_plural be explained more evidently in the documentation or by the manage scripts when creating new models?

Would it be possible to have a more permanent fix in place, if my above points are agreed to, before version 1.0 to limit future incompatability?

comment:3 Changed 8 years ago by Karen Tracey

Resolution: wontfix
Status: reopenedclosed

Per http://www.djangoproject.com/documentation/contributing/ please don't reopen issues that have been marked wontfix. Instead, bring up the issue on the developer's list, where you'll reach a wider audience to gauge if there is sufficient interest to revisit the decision.

Note: See TracTickets for help on using tickets.
Back to Top