FYI: I've also contributed a patch for this ticket:
http://code.djangoproject.com/ticket/3624
It adds some extra support so the feeds don't need to hit the
filesystem just to pull in a simple template.
-Rob
On Aug 7, 4:28 am, jorjun <[EMAIL PROTECTED]> wrote:
> Done. Thanks for guidance.
>
> >
On 09-Aug-07, at 1:56 AM, Brantley Harris wrote:
> "hint" seems like the wrong word. "suggest", "guide", "auto",
> "build"?
preview?
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
--~--~-~--~~~---~--~~
You received this message
hi,
I have this model which doesn't work when using select_related(). What
happen is django seems to be in a infinite loop.
class Employee(models.Model):
employee_contract = models.ForeignKey('EmployeeContract',
related_name='contracted_employee')
employee_assignment =
> Sorry, perhaps I don't quite understand how this is different...
> unless you are rendering the field widget manually and somehow adding
> extra choices that aren't in the query set passed to the
> Model*ChoiceField?
There would be one extra choice - the previously selected, and no
longer
On Aug 9, 5:49 am, oggie rob <[EMAIL PROTECTED]> wrote:
> > That could work. The main point of this thread was to see if there are
> > use cases for using the default manager for validation instead of the
> > query set because I couldn't really think of any - but I'm sure there
> > could well be
On 8/8/07, John-Scott <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> I'm trying to integrate S3 support into my Django app using
> http://code.djangoproject.com/wiki/AmazonSimpleStorageService for
> now.
>
> I would like to improve the code so that it might be officially
> integrated into Django
Hello all,
I'm trying to integrate S3 support into my Django app using
http://code.djangoproject.com/wiki/AmazonSimpleStorageService for
now.
I would like to improve the code so that it might be officially
integrated into Django at some point. The first obvious question: Is
this a feature that
On 8/4/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> My goals:
> * Keep the model file as a canonical representation of what the tables
> should look like right now.
> * Keep each migration as an atomic unit.
> * Provide an entry point for raw SQL migrations
> * Provide some validation
On 8/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> What I *do* think is worth fixing is allowing the template system to
> be used on its own, for the simple, common case, without having to
> configure stuff. This is what I was trying to explain in my last
> e-mail. Tom, if we solved that,
On 8/8/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> I think there's a good psychological / community case to be made for
> making django.template available standalone; as I put it earlier, many
> people just don't like importing stuff they don't intend to use, no
> matter how small it may be
On 8/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 8/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > A couple of other areas are going to be at least equally as
> > interesting...
>
> Malcolm has made some *really* good points throughout this thread, and
> I'm convinced that
On 8/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> A couple of other areas are going to be at least equally as
> interesting...
Malcolm has made some *really* good points throughout this thread, and
I'm convinced that going down this path would be a not-so-good idea.
My opinion on it
On 8/8/07, Robert Coup <[EMAIL PROTECTED]> wrote:
> On 08/08/2007, James Bennett <[EMAIL PROTECTED]> wrote:
> >
> > On 8/8/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > > I'd ideally like the Django installer to detect if django.template was
> > > already on the system, and drop Django into the
On 8/8/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> as i said before i'm not wed to it. (actually i feel it's a rather
> minor point) propose a different location. i just want it somewhere
> simple and obvious. (or if you two just hate the keyword, what would
> you like to call it?)
Its
On 08/08/2007, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
>
> i have had this exact situation happen to me before. (rolling out a
> change, then another change reversing it) actually several times. i
> have NEVER had a scenario where client Y says "can you please make sure
> i lose my data?"
>
On 08/08/2007, James Bennett <[EMAIL PROTECTED]> wrote:
>
>
> On 8/8/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > I'd ideally like the Django installer to detect if django.template was
> > already on the system, and drop Django into the same spot. As far as
> > versioning, Django should check for
This code is what I said
from django.conf import settings
class URLNode(Node):
def __init__(self, view_name, args,kwargs,as_name):
self.view_name = view_name
self.args = args
self.kwargs = kwargs
self.as_name = as_name
def render(self, context):
sorry , fix some error
from django.conf import settings
from django.template import Node
class URLNode(Node):
def __init__(self, view_name, args,kwargs,as_name):
self.view_name = view_name
self.args = args
self.kwargs = kwargs
self.as_name = as_name
def
because if I want to get the link first , then get the count number .
if I just use reverse() in my custom tag, I have to write like below
xxx
Digg:{% access_count_url music "rock",112 %}
I write the same things twice , and if I want write a link such as
"add to shopping list" I have to write
Couldn't you just use reverse() in your custom tag?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe
On 8/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> A couple of other areas are going to be at least equally as
> interesting...
I hereby amend my list of worries to include Malcolm's ;)
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
On 8/8/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> I'd ideally like the Django installer to detect if django.template was
> already on the system, and drop Django into the same spot. As far as
> versioning, Django should check for a minimum version of Django
> templates (i.e., the version at the
22 matches
Mail list logo
