Huge +1 on everything Tom said, except the point about the docs:
Calling out quality packages in some way from the docs
>
The nice thing about developer communities is that they're fairly emergent.
Consensus is usually formed all the way from the very bottom, on up. This
works well.
On Fri, Jun 28, 2013 at 5:33 AM, Warren Smith wrote:
> Is anyone aware of a reason why the built-in time template filter does not
> have timezone support? The built-in date template filter has timezone
> support, but I wanting to use the TIME_FORMAT default stuff linked
Is anyone aware of a reason why the built-in time template filter does not
have timezone support? The built-in date template filter has timezone
support, but I wanting to use the TIME_FORMAT default stuff linked to the
time filter.
Was timezone considered to be not relevant for the time
Hi Karol,
Thanks for bringing that up. I'll start by saying that I would love to
see richer Web API support in core Django - in my opinion there are
absolutely some fundamentals that could be addressed. However, I
personally think that the benefit that we'd get probably isn't (yet?) worth