Re: typecast_date() argument format

Thanks Malcom, I did search and found at least a similar (closed) ticket (#659). Yes, I agree the slicing is a workaround, and does not look like a definite solution at all. On Oct 7, 12:24 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-10-07 at 16:02 +, jv wrote

Re: typecast_date() argument format

ding works. On Oct 7, 11:40 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-10-07 at 15:30 +, jv wrote: > > Hello all. > > > I wonder if the function typecast_date() on /usr/lib/python2.5/site- > > packages/django/db/backends/util.py:58

typecast_date() argument format

Hello all. I wonder if the function typecast_date() on /usr/lib/python2.5/site- packages/django/db/backends/util.py:58 assumes the string 's' to be of '-MM-DD' format. Here's the function in question (as of r6460): def typecast_date(s): return s and datetime.date(*map(int, s.split('-'))

[patch] Add support for IP, IP:PORT, or PORT command-line arguments

This patch (http://code.djangoproject.com/ticket/2461) adds support for, e.g., $ python manage.py runserver 192.168.1.150 ## if no port, then 8000 is assumed [...] $ python manage.py runserver 2552 ## if no IP address, then 127.0.0.1 is assumed [...] $ python manage.py runserver 192.168.1.1

[patch] manage.py: Add support for IP, IP:PORT, or PORT command-line arguments

This patch (http://code.djangoproject.com/ticket/2461) adds support for, e.g., $ python manage.py runserver 192.168.1.150 ## if no port, then 8000 is assumed [...] $ python manage.py runserver 2552 ## if no IP address, then 127.0.0.1 is assumed [...] $ python manage.py runserver 192.168.1