Pick a default extension for Django templates
|Reported by:||Allan Odgaard||Owned by:||Adrian Holovaty|
|Cc:||django@…||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
It seems that the default extension for Django templates was HTML and now sort of “not specified”.
I would strongly encourage you to pick a default extension, for example ‘django’ or ‘dhtml’ (not an extension already in use, like ‘html’.)
If you do not make this choice for the user, every user will have to setup these things for themselves, and for the former, that is definitely not trivial.
I would further add that you burden the user with unnecessary choice, choice which not only rule out the previously mentioned “nice defaults” but also lead to inconsistency, as the file extension is today the way majority of “systems” recognize file types, be it operating systems, web servers, applications, or similar.
 On OS X there are document icons for majority of file types. These show the icon of the application which opens the file and the short-name for the type below. A user would never set this up himself, but instead rely on an application to supply the icon, but the mapping is based on file extension, so a mapping for Django can never be created as long as you do not mandate a file extension.
 TextMate (which I am the author of) stores support for a particular language in a bundle (many included by default, but otherwise installed by double-clicking). Within this bundle is stored which file extension it should apply to by default. It is trivial to educate TextMate about additional mappings, yet it is also a FAQ entry because we get the question a lot.