On Sat, Oct 24, 2009 at 6:50 PM, veena wrote:
>
> Does the commentators have experience with maintaining the i18n django
> project? I do and completely agree with Jonas.
> "Gettext like+Rosetta like" but database driven translation app in
> Django adminwithout translation-makemessages-compilemess
Does the commentators have experience with maintaining the i18n django
project? I do and completely agree with Jonas.
"Gettext like+Rosetta like" but database driven translation app in
Django adminwithout translation-makemessages-compilemessages-restart
apache would be helpful. Import from the get
On Sat, Oct 24, 2009 at 9:32 AM, rjc wrote:
> BTW, we use django evolution since south doesn't support python 2.3
> (again a lot of
> enterprise code is stuck at RHEL4 which is py2.3)
It sounds to me like you already have a solution and some special
needs that make the current choice you have in
On Oct 18, 6:08 pm, berto wrote:
> On Oct 18, 7:24 am, Russell Keith-Magee
> wrote:
>
> > On Sun, Oct 18, 2009 at 6:14 PM, berto wrote:
>
> > kGiven the fact that it takes a long time to setup and teardown
> > Django's test suite, I feel that it is better to leave test execution
> > as a manu
On Saturday 24 October 2009 14:32:58 rjc wrote:
> Schema migration is not an option, it is required for any
> production code (we ship
> a lot of code to out customer's site and regularly publish patches
> that include schema
> changes). You cannot make a site without ORM or schema migration, I
>
Am 25.09.2009 um 22:04 schrieb Simon Willison:
>
> On Sep 25, 4:44 pm, Johannes Dollinger
> wrote:
>> Regarding parity, let me advertise a Signer object again:
>>
>> signer = signed.Signer(
>> key=settings.SECRET_KEY,
>> expire_after=3600
>> )
>>
Schema migration is not an option, it is required for any production
code (we ship
a lot of code to out customer's site and regularly publish patches
that include schema
changes). You cannot make a site without ORM or schema migration, I
see both at the
same level.
BTW, we use django evolution si
