D’oh:
django/contrib/admin/util.py django/contrib/admindocs/utils.py django/contrib/comments/views/utils.py django/contrib/formtools/utils.py django/contrib/gis/db/backends/util.py django/contrib/gis/tests/utils.py django/contrib/localflavor/it/util.py django/contrib/localflavor/se/utils.py django/contrib/localflavor/uy/util.py django/contrib/messages/utils.py django/core/files/utils.py django/core/mail/utils.py django/db/backends/util.py django/db/utils.py django/forms/util.py django/http/utils.py django/test/utils.py tests/regressiontests/forms/util.py
Comments:
Yeah let's fix those, I never know when to use “util” and when it's “utils”
I also never know when to use "util" or "utils" =/
You skipped the entire util (or is it utils...) directory :)
I advocate for utils!
Funny coincidence.. just earlier today I was searching for something and was amused by the following:
$ find django (...)
...
django/http/utils.py
...
django/utils/http.py
:)
+1 for utils
Yes, when you see utilities file it is immediately clear what the purpose of it is :-)
Away with that evil - name the modules accordingly!
+1 for utils. which is be more reasonable(since we always dump a lot of utility functions into this file).
forms.py
models.py
views.py
so... yeah go with utils.py :-)
For what it is worth I would also advocate using utils.py. That's what I use personally and it seems the majority in the existing Django cases.
+1 on utils unless the file does one single thing
I'm for maybe_useful_maybe_not.
Because it usually is.
I'm not sure how "util" got in there. The preference has always been "utils"...
+1 for utils
I prefer "support".
How about "tools"?
Leave a comment: