On Feb 18, 2009, at 02:13, Malcolm Tredinnick wrote:
>
> On Tue, 2009-02-17 at 18:57 -0600, Jeremy Dunck wrote:
>> On Tue, Feb 17, 2009 at 6:49 PM, Malcolm Tredinnick
>> wrote:
>> ...
>>> I'd be somewhat against this, I think. It's *very* easy to reuse
>>> querysets and inadvertently cause extra
On Feb 19, 12:49 am, Malcolm Tredinnick
wrote:
> On Wed, 2009-02-18 at 04:28 -0800, mrts wrote:
> > The old Field.default_error_messages dict and corresponding
> > logic is no longer required (and removed in my branch) as default
> > error messages live in core/validators now.
>
> It *is* still r
On Feb 19, 10:31 pm, David Larlet wrote:
> Le 19 févr. 09 à 09:58, martin.xu a écrit :
>
>
>
> > I like python 3k.,but I cannot run Django on python 3k?
>
> > Is there any pacth that port Django to Python 3.0?
>
> First result in google:http://wiki.python.org/moin/PortingDjangoTo3k
Even runs
On Wed, Feb 18, 2009 at 11:53 PM, Malcolm Tredinnick
wrote:
> Any particular grounds for doing something spec-compliant feeling
> fragile to you, Ian? Having let this bounce around for 24 hours, I can't
> think of a strong reason not to do it.
Only the hazards of copying an arbitrary select expr
Just yesterday I updated the patch attached to
http://code.djangoproject.com/ticket/7539 so that it will apply against
the current version of Django (the previous patch required Django 0.96).
What are the chances of some form of this patch being included in one of
the next couple of versions o
Le 19 févr. 09 à 09:58, martin.xu a écrit :
>
> I like python 3k.,but I cannot run Django on python 3k?
>
> Is there any pacth that port Django to Python 3.0?
First result in google:
http://wiki.python.org/moin/PortingDjangoTo3k
Regards,
David
--~--~-~--~~~---~
I like python 3k.,but I cannot run Django on python 3k?
Is there any pacth that port Django to Python 3.0?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send em
