On Sun, 2007-06-17 at 01:58 +, [EMAIL PROTECTED] wrote:
>
>
> On Jun 16, 6:45 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > On 6/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> > > However all that is beside the point. The patch that Jonas has posted in
> > > #4590 is just to
Since this has come up, may I point you to this discussion over here:
http://groups.google.com/group/Django-I18N/browse_thread/thread/3f5dfb2a9a10f904/54365cef61f62f21?lnk=st&q=&rnum=1#54365cef61f62f21
About ticket 4147: http://code.djangoproject.com/ticket/4147
On Jun 17, 4:58 am, "[EMAIL PR
On Jun 16, 6:45 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 6/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > However all that is beside the point. The patch that Jonas has posted in
> > #4590 is just to change the default settings. I'm not sure if that's
> > worth doing or no
On 6/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> However all that is beside the point. The patch that Jonas has posted in
> #4590 is just to change the default settings. I'm not sure if that's
> worth doing or not. Currently I'm somewhere between -0 and +0, since
> it's completely withi
On Sun, 2007-06-17 at 02:50 +0200, Julian 'Julik' Tarkhanov wrote:
>
> On Jun 17, 2007, at 2:46 AM, Jonas wrote:
>
> >
> >
> > On 17 jun, 01:14, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > > Where do you propose this be used? At the database level, your DB
> > > will
> > > store date/time v
On Jun 17, 2007, at 2:46 AM, Jonas wrote:
>
> On 17 jun, 01:14, "James Bennett" <[EMAIL PROTECTED]> wrote:
>> Where do you propose this be used? At the database level, your DB
>> will
>> store date/time values in whatever internal format it prefers.
> Yes, I think that should be stored so at th
On 17 jun, 01:14, "James Bennett" <[EMAIL PROTECTED]> wrote:
> Where do you propose this be used? At the database level, your DB will
> store date/time values in whatever internal format it prefers.
Yes, I think that should be stored so at the database level.
> At the
> level of input and output
On 6/16/07, Jonas <[EMAIL PROTECTED]> wrote:
> I think that Django should use an international standard date and time
> format.
Where do you propose this be used? At the database level, your DB will
store date/time values in whatever internal format it prefers. At the
level of input and output to
For if you want follow that standard I've added a patch:
http://code.djangoproject.com/ticket/4590
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dja
I think that Django should use an international standard date and time
format.
For more information:
http://www.cl.cam.ac.uk/~mgk25/iso-time.html
http://www.w3.org/QA/Tips/iso-date
http://en.wikipedia.org/wiki/ISO_8601
--~--~-~--~~~---~--~~
You received this mess
This is the third weekly status update for my Summer of Code project,
a generic REST interface for Django [1].
I spent the SoC-part of this week mostly thinking about automated URL
pattern generation, wrote some code and added a few tests that
demonstrate how to use this feature. Currently, you c
On Sat, 2007-06-16 at 20:15 +, dimas wrote:
> Hello all,
>
> Is it hard to port multidb features against trunk?
>
> Or any info on how ready is it to get merged?
Perhaps you might want to read this:
http://groups.google.com/group/django-developers/browse_frm/thread/18d57576c054701e/c391e06e
Hello all,
Is it hard to port multidb features against trunk?
Or any info on how ready is it to get merged?
Thanks in advance.
WBR,
dimas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
Hello all,
Is it hard to port multidb features against trunk?
Or any info on how ready is it to get merged?
Thanks in advance.
WBR,
dimas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group
I've created the ticket(http://code.djangoproject.com/ticket/4589) and
uploaded a patch, i post it here for you discuss, it's quite simple and
i hope it to be accepted ：
> Currently, admin interface use app label to group models into sections and
> use app label as the section name, but i think u
Hi guys!
I've found 2 bugs in thumbnails contrib package, in the file django/
contrib/thumbnails/base.py:
1) in the line 33-34:
...
if os.path.splitext(filename)[1] != '.jpg':
filename.append('.jpg')
...
The filename variable is a string, this should be:
...
if os.path.splitext(filename)[
16 matches
Mail list logo
