Re: Amazon S3 Integration

2007-08-08 Thread Fabien Schwob
Hello, > 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 featu

Re: Simple improvement suggestion for django.contrib.syndication.feeds

2007-08-08 Thread Rob Hudson
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. > > >

Re: schema evolution [testers wanted]

2007-08-08 Thread Kenneth Gonsalves
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

Re: Is this not allowed select_related()

2007-08-08 Thread James Bennett
Please do not post general help questions to the django-developers mailing list; this list is only for discussion of Django's code. For general help, please post questions to the django-users mailing list: http://groups.google.com/group/django-users/ -- "Bureaucrat Conrad, you are technically c

Is this not allowed select_related()

2007-08-08 Thread james_027
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 = models.ForeignKe

Re: ModelChoiceField's clean() uses default manager instead of query set

2007-08-08 Thread oggie rob
> 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 valid

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread limodou
> Plainly put, the system should work without requiring configuration. I agree! -- I like python! UliPad <>: http://code.google.com/p/ulipad/ My Blog: http://www.donews.net/limodou --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: ModelChoiceField's clean() uses default manager instead of query set

2007-08-08 Thread Nick Lane
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 s

Re: Amazon S3 Integration

2007-08-08 Thread Jay Parlar
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 at

Amazon S3 Integration

2007-08-08 Thread John-Scott
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 o

Re: ModelChoiceField's clean() uses default manager instead of query set

2007-08-08 Thread oggie rob
> 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 some. Like the one I explained? :) I think the strongest argume

Re: schema evolution [testers wanted]

2007-08-08 Thread Brantley Harris
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 that

Adding hooks to methods that generate SQL in django/core/management.py

2007-08-08 Thread George Vilches
I find that on a few occasions, I've needed to generate extra SQL for both creation and deletion tasks when I'm executing "manage.py syncdb" (or sql, or reset, sqlclear, etc., pretty much all of the SQL generation commands). Currently, if you use only use syncdb for everything, you can do thi

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread Tom Tobin
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, w

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread Adrian Holovaty
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 byte-wi

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread Tom Tobin
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 goin

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread Adrian Holovaty
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 at

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread Tom Tobin
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 sam

Re: schema evolution (new and improved)

2007-08-08 Thread Russell Keith-Magee
On 8/8/07, Derek Anderson <[EMAIL PROTECTED]> wrote: > > > 1) Isn't the list of known schema fingerprints just the list of keys > > in the migration graph/dictionary? > > no. it adds ordering. (the keys are a set remember) we wouldn't need > it if python had something similar to java's LinkedHa

Re: schema evolution (new and improved)

2007-08-08 Thread Russell Keith-Magee
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

Re: schema evolution (new and improved)

2007-08-08 Thread Robert Coup
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?" >

Re: Breaking out Django templates into a standalone library

2007-08-08 Thread Robert Coup
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

Re: Improvement suggestion for {% url %}

2007-08-08 Thread !张沈鹏(电子科大 08年毕业)
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): fr

Re: Improvement suggestion for {% url %}

2007-08-08 Thread !张沈鹏(电子科大 08年毕业)
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 re

Re: Improvement suggestion for {% url %}

2007-08-08 Thread !张沈鹏(电子科大 08年毕业)
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 the

Re: Improvement suggestion for {% url %}

2007-08-08 Thread Collin Grady
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 f