On Wednesday 29 December 2010, Luke Plant wrote:
> On Wed, 2010-12-29 at 11:20 +0200, Shai Berger wrote:
> > On Wednesday 29 December 2010 05:24:06 Russell Keith-Magee wrote:
> > > As for "do we intend to solve this issue" -- you haven't been exactly
> > > clear as to what the issue *is* -- or rath
Hi,
I just updated the cbv_refactor branch to use the generic class based views
from Django trunk. I hope everything works as supposed.
I would appreciate any help on writing documentation - even if its just a
draft but its a beginning ;-)
Looking forward to feedback!
Cheers,
steph
Migue
Hey Jonas :)
> Let's assume for a moment we use your idea and provide a couple of different
> backends to store your translations. How would third party applications ship
> default translations then? At the moment they use gettext pofiles and it
> works like a charm. Let's assume now for my projec
On 31 December 2010 05:44, Simon Meers wrote:
>
>> I don't know how many people actually used that feature (I never did),
>> but it seems like it was a bit accidental. As we are speaking about a
>> development server, I don't find this feature very useful as (most of
>> the time) you want to run i
Okay let's leave the database content problem besides here.
Let's assume for a moment we use your idea and provide a couple of different
backends to store your translations. How would third party applications ship
default translations then? At the moment they use gettext pofiles and it
works li
On 31.12.2010, at 00:25, Łukasz Rekucki wrote:
> Hi,
>
> I'm not sure about resolution for this ticket[1]. Initially this looks
> like a regression. On the other hand, it was never documented that
> "runserver" accepted anything other than an IP:port pair.
>
> I don't know how many people actual
