apps with the same name

2006-01-13 Thread Joseph Kocherhans
In magic-removal, the admin interface allows for apps with the same names to coexist as long as they are in separate packages. Admin urls are now like /admin/mypackage/myapp/mymodel rather than just /admin/myapp/mymodel. Unfortunately, this doesn't work quite like I'd expect it to. Here's what I

Re: Proposal: Django should support unicode strings

2006-01-13 Thread Maniac
hugo wrote: Looks like a typo: DEFAULT_ENCODING there is actually DEFAULT_CHARSET? Yep. Fixed it. But you could have fixed that yourself, it's a wiki ;-) Will do next time. I didn't have much experience with public wikis and thought I need some special authorisation to correct someth

Re: Proposal: Django should support unicode strings

2006-01-13 Thread hugo
>Looks like a typo: DEFAULT_ENCODING there is actually DEFAULT_CHARSET? Yep. Fixed it. But you could have fixed that yourself, it's a wiki ;-) bye, Georg

Re: Proposal: Django should support unicode strings

2006-01-13 Thread Maniac
hugo wrote: I think that Django should support(use only) python unicode strings. http://code.djangoproject.com/wiki/UnicodeInDjango Looks like a typo: DEFAULT_ENCODING there is actually DEFAULT_CHARSET?

Re: Proposal: Shorter comment tag

2006-01-13 Thread slumtrimpet
+1 Russell makes some very good points. Comments should always be encouraged in code and should be easy to insert in code for debugging purposes. The current {% comment %} blocks are a bit of a pain to write for both of these purposes.

Re: Proposal: Django namespace simplification

2006-01-13 Thread Tom Tobin
On 1/12/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > I like this a lot! SimpleContext is good...Other thoughts? BaseContext?

Re: Proposal: Django namespace simplification

2006-01-13 Thread Adrian Holovaty
On 1/13/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote: > On 1/13/06, Robert Wittams <[EMAIL PROTECTED]> wrote: > > Hm, I actually liked RequestContext and Context : > > +1 Anything's better than DjangoContext. Except maybe DjangoFrameworkContext. Let's go with Context and RequestCo

Re: Proposal: Django namespace simplification

2006-01-13 Thread Jeroen Ruigrok van der Werven
On 1/13/06, Robert Wittams <[EMAIL PROTECTED]> wrote: > Hm, I actually liked RequestContext and Context : +1 > "Simple" implies to me that it is "for the same purpose" as other things > called *Context, but has an easier to understand/trivial implementation. > This isn't really true - its for a d

Re: Proposal: Django namespace simplification

2006-01-13 Thread Robert Wittams
Adrian Holovaty wrote: > On 1/12/06, kmh <[EMAIL PROTECTED]> wrote: > >>Good idea to rename DjangoContext. My favorite alternative: >> >>DjangoContext --> Context >>Context --> PlainContext or SimpleContext > > > I like this a lot! SimpleContext is good...Other thoughts? > > Adrian > > -- >

Re: Proposal: Django namespace simplification

2006-01-13 Thread Maniac
Adrian Holovaty wrote: I like this a lot! SimpleContext is good...Other thoughts? I'd say BaseContext. It's now just a base class for other actually useful contexts.

Re: ifequal support for AND OR

2006-01-13 Thread hugo
>If the templates allowed more complex logic, template designers might >be tempted to write a template that reads "if >last_payment.before(today - 1 year) and not admin". However, this >encodes a business logic decision in the template. Since the template >language does not allow complex queries,

Re: ifequal support for AND OR

2006-01-13 Thread Russell Keith-Magee
On 1/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I definitely understand why business logic should be kept out of the > template; I don't see why adding AND/OR support is any worse than > having if/if not/ifequal/ifnotequal/for. > > During the Snakes & Rubies talk it was mentioned that