Re: How about a Django apps public repository?
>> As far as I can tell the way to do this is to modify *every* >> *view* *in* *my* *project* to pass either the user or a >> RequestContext. > > The link I gave you is to not do that, but add a processor that will add the > user to the context. I think you might be missing the bit that says: "Finally, we change our view code to use RequestContext instead of the base Context class." Joe --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: How about a Django apps public repository?
> On the linked thread have you checked:
> http://www.b-list.org/weblog/2006/06/14/django-tips-template-context-processors?
> You can use a context processor to make {{ user }} available on all
> templates.
Unless I'm missing something, that link says the same as what I'm
saying, namely that you need to use RequestContext everywhere if you
want your apps to be pluggable.
Now, this seems to me to be a rather crucial and earth-shattering,
given that
a) It means basically abandoning the principle of keeping data nicely
partitioned and making stuff available 'everywhere'.
b) I don't think the django tutorials even mention RequestContext once;
I don't really understand why no-one apart from me seems to think this
is important. Now, I'm a huge django fan, but frankly this seems like
the kind of skank that repelled me from all the php frameworks I tried
(and yes, I'm trolling in the hope of getting some kind of response...)
Joe
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: How about a Django apps public repository?
Ok, here's an attempt to elicit some kind of response, having failed last time I asked this question: http://groups.google.com/group/django-developers/browse_frm/thread/5b5b9070f8ca36d7 If I submit a reusable app, should its views pass a RequestContext to the templates or not? If they don't, they'll break projects eg. with templatetags that require request information. So if our apps have any aspirations to reusability, does that mean we should *always* pass RequestContexts, and that vanilla Contexts are essentially deprecated? Joe --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: One-to-one not to be used?
SmileyChris wrote: > According to the docs: > > "The semantics of one-to-one relationships will be changing soon, so we > don't recommend you use them. If that doesn't scare you away, keep > reading." > > It scares me a bit. Can anyone expand on the "changing semantics" or > point me to an existing discussion? Is this the kind of thing you're looking for? http://code.djangoproject.com/wiki/ModelInheritance --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Trac error on code.djangoproject.com
Nope, still broken here. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
