With all the new found interest in localflavor/ contributions, I've
started to see a pattern that could cause us trouble:
Many locales have the native names using characters outside of the ASCII
range. So people put "# -*- coding: utf-8 -*-" at the top of their file
and then include the proper
On Fri, 2007-03-30 at 04:15 +, Nicolas E. Lara G. wrote:
> Other than using uncommon names for the url one could just use the
> most obvious name and let the url tag have a disambiguation function
> so if the name is: "name" you could write both:
> {% url 'name' %} and {% url 'myapp.name' %}
Other than using uncommon names for the url one could just use the
most obvious name and let the url tag have a disambiguation function
so if the name is: "name" you could write both:
{% url 'name' %} and {% url 'myapp.name' %} (or "myapp/name" or
"myapp-name")
With this you could keep the url
In the book "Building Scalable Web Sites", Cal Henderson suggests
putting (possibly abbreviated) app call stacks in SQL comments to
enable logging and performance on the DB backend to be more easily
tied to application paths.
This sounds like a great idea to me.
MySQL, PGSQL and SQLite all
On Fri, 2007-03-30 at 01:57 +, SmileyChris wrote:
> On Mar 28, 9:57 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> > I've done some thinking on this, too, and I think the cleanest way to
> > solve it would be to introduce optional names for URL patterns.
> > Something like this:
> >
> >
On 3/29/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> Can a core developer please check in the missing file from the ticket
> (it's in the patch, it just wasn't committed it seems):
> http://code.djangoproject.com/ticket/3799
It's in, as of [4857]. There's a new django.contrib.webdesign package:
On Mar 28, 9:57 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> I've done some thinking on this, too, and I think the cleanest way to
> solve it would be to introduce optional names for URL patterns.
> Something like this:
>
> url(r'^objects/$', some_view, name='object_view'),
>
On Mar 27, 4:57 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> I've done some thinking on this, too, and I think the cleanest way to
> solve it would be to introduce optional names for URL patterns.
> Something like this:
>
> url(r'^objects/$', some_view, name='object_view'),
>
On 3/29/07, topper <[EMAIL PROTECTED]> wrote:
> Still, $HOME is a normal UNIX environmental variable, and because
> Django does use those in other places (i.e django_settings), a user
> could think that environment variables are accessible from Django. And
> when the user is told in Template
On 3/30/07, topper <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've just (maybe stupidly on my behalf) spent an hour digging through
> Django code to find out why Django thought the template at $HOME/web/
> my_site/templates/home_page.html doesn't exist. The answer is that I
> in the TEMPLATE_DIRS
On 3/30/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> Can a core developer please check in the missing file from the ticket
> (it's in the patch, it just wasn't committed it seems):
> http://code.djangoproject.com/ticket/3799
That was me - I forgot to svn add the new file. Apologies to all for
Hi all,
We're starting to see some localflavour patches drift in, which is
great (e.g. it: #3866, fi: #3847, ja: #3715 ). However, we should be
briefly documenting these - it could simply just be a list of what's
in there so far.
I'll work up a patch for this sometime, but just wondered where
On 3/29/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-03-29 at 07:07 +, Mir Nazim wrote:
> > Hello all,
> >
> > First let me thanks all developer for a great thing like Django.
> >
> > Now can anybody tell me about the status of Django's SQLAlchemy
> > branch. I could not
On 3/29/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> Can a core developer please check in the missing file from the ticket
> (it's in the patch, it just wasn't committed it seems):
> http://code.djangoproject.com/ticket/3799
I'll take care of it. FYI, while I'm at it, I'm going to move it into
a
Can a core developer please check in the missing file from the ticket
(it's in the patch, it just wasn't committed it seems):
http://code.djangoproject.com/ticket/3799
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
> I don't like newlines within tags purely for aesthetic reasons. A tag
> is a bite-sized, atomic unit. If it's spread over multiple lines, it
> turns into some strange mushy, ugly thing.
>
> Yes, this is highly subjective. I realize that, and I shudder at the
> thought of a 30-message
On 3/29/07, Noah Slater <[EMAIL PROTECTED]> wrote:
> I have been instructed by mtredinnick to bring the discussion here.
>
> Can someone please justify why this wont be fixed?
See also this thread from earlier today which covers some
technical/performance reasons:
On 3/29/07, Noah Slater <[EMAIL PROTECTED]> wrote:
> Please see "Tags cannot contain newlines":
>
> http://code.djangoproject.com/ticket/1147
>
> I have been instructed by mtredinnick to bring the discussion here.
>
> Can someone please justify why this wont be fixed?
I don't like newlines
Hello,
Please see "Tags cannot contain newlines":
http://code.djangoproject.com/ticket/1147
I have been instructed by mtredinnick to bring the discussion here.
Can someone please justify why this wont be fixed?
Thanks,
Noah
--~--~-~--~~~---~--~~
You
Maybe you can't find it because it's "wontfix" :))
http://code.djangoproject.com/ticket/3326
On 3/29/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, 2007-03-29 at 21:05 +0800, Russell Keith-Magee wrote:
> > Hi all,
> >
> > I just noticed that my RSS reader has stopped providing
Jonas Maurus wrote:
>> I think he was suggesting in the form, not each field:
I did :)
> I see that this would allow Django to be backwards-compatible by
> introducing this new parameter, so I could go for that because I think
> backwards-compatibility is very important. I still disagree with
On 3/29/07, Ted <[EMAIL PROTECTED]> wrote:
> Were I work we have had to do this very thing to support I18N in our
> forms. Something as simple as a ":" is not a given. Maybe I want a
> " :" instead? This could be a form parameter or even a locale setting.
FWIW I think the ideal would be for the
We have the following tag. It's well over 80 characters long (103), and for
our own sanity we'd prefer to use a newline within the tag.
We went looking for this bug report and I was told to discuss this on
django-dev (thanks Jacob):
http://code.djangoproject.com/ticket/1147
Is this a
Were I work we have had to do this very thing to support I18N in our
forms. Something as simple as a ":" is not a given. Maybe I want a
" :" instead? This could be a form parameter or even a locale setting.
My 2 cents,
Ted
On Mar 29, 9:10 am, "Todd O'Bryan" <[EMAIL PROTECTED]> wrote:
> On Thu,
On Thu, 2007-03-29 at 21:05 +0800, Russell Keith-Magee wrote:
> Hi all,
>
> I just noticed that my RSS reader has stopped providing notifications
> of new and closed tickets.
>
> The problem appears to be caused by Django's RSS feed. For example, if
> you follow the RSS link at the bottom of
I think the OP is correct, if you want the label to end with a
colon ... then add the colon to the label. It doesn't get any simpler
than that. Any other solution just gets in the way.
i.
--~--~-~--~~~---~--~~
You received this message because you are
On Thu, 2007-03-29 at 13:02 +, Jonas Maurus wrote:
> > I think there are lots of situations where you need to normalize the
> > labels with some string. Why not just make it an optional parameter to
> > the Form class with a default value.. maybe ":"?
> >
> > Rune
>
> so that would make
>
Hi all,
I just noticed that my RSS reader has stopped providing notifications
of new and closed tickets.
The problem appears to be caused by Django's RSS feed. For example, if
you follow the RSS link at the bottom of the the default timeline page
http://code.djangoproject.com/timeline
you get
On Mar 29, 2:07 pm, "bromer" <[EMAIL PROTECTED]> wrote:
> On Mar 29, 1:38 pm, "Jonas Maurus" <[EMAIL PROTECTED]> wrote:
>
> > Also, there simply are languages where this punctuation doesn't make
> > sense. Adding it automatically then telling international users that
> > they have to write a lot
On Mar 29, 1:38 pm, "Jonas Maurus" <[EMAIL PROTECTED]> wrote:
> Also, there simply are languages where this punctuation doesn't make
> sense. Adding it automatically then telling international users that
> they have to write a lot more code, because english developers wanted
> to save one
Hello all,
First let me thanks all developer for a great thing like Django.
Now can anybody tell me about the status of Django's SQLAlchemy
branch. I could not find any place describing the status on
code.djangoproject.com.
Regards.
--~--~-~--~~~---~--~~
You
31 matches
Mail list logo
