Re: Model Equality Checking -- Does it need more power?

Hey, On Apr 26, 2:39 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > [...] > there isn't a consistent, automatic way to determine which columns to > exclude, an explicit function is going to be more useful. That's what the Meta field is for ;) Anyway, I don't think it's particularily useful

Re: Model Equality Checking -- Does it need more power?

On Thu, 2007-04-26 at 06:20 +, Mike Axiak wrote: > Hi, > > The common use-case is if you just want to check to see if two objects > are 'equal' in the sense that they contain the same data. For > instance, you may want to see if a wiki was double-posted or other see > if two users are the sam

Re: Templates: short comments {##} eats text

On Wed, 2007-04-25 at 08:38 -0600, Lakin Wecker wrote: > > > 2. If we want to enable multi-line comments, we need to > allow newlines > > in tag's content: > > We don't want to allow newlines in tags. That decision has > already been > mad

Re: Model Equality Checking -- Does it need more power?

Hi, The common use-case is if you just want to check to see if two objects are 'equal' in the sense that they contain the same data. For instance, you may want to see if a wiki was double-posted or other see if two users are the same (same email, same first and last name, just differing in their

Re: Model Equality Checking -- Does it need more power?

Hey Michael, On Wed, 2007-04-25 at 22:19 +, Mike Axiak wrote: > Hello, > > After some discussion in IRC I've written a patch to add an is_equal > method to the models. > (http://code.djangoproject.org/ticket/4157) > > However, there was some question over whether this should be named > is_e

Re: RESTful API

2007/4/25, John Sutherland <[EMAIL PROTECTED]>: > > Evening, > > I've put the RESTful API code that I mentioned in ticket 2553[1]. A > few people have requested the code and so it's now in a Google code > project: > > > Ideas? Suggestions? Requests? Abou

Re: Templates: short comments {##} eats text

Thanks Michael, Now that you actually said it, I realize that this is the conclusion I've been slowly coming too. Thanks for listening. Lakin On 4/25/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > > On Wed, Apr 25, Lakin Wecker wrote: > > > I know that the devs probably don't want anyone to

Re: MEDIA_URL template tag/context processor/etc again

I'm still convinced this is a very common use-case. I like Amr's take on it: We don't introduce any context bloating We don't require templates to use RequestContext --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Model Equality Checking -- Does it need more power?

Hello, After some discussion in IRC I've written a patch to add an is_equal method to the models. (http://code.djangoproject.org/ticket/4157) However, there was some question over whether this should be named is_equal or __eq__. The current patch uses a Meta field to determine what fields should

Re: Maintaining a patched Django (was re: Templates: short comments {##} eats text)

> What tools do you use to manage your patched version? I use svk for getting my patches updated and regenerated if changes happened to the trunk and some lame gentoo-ebuild to install django including my patches. I pasted my ebuild here: http://dpaste.com/hold/9042/ Some script to rebuild the

Re: Maintaining a patched Django (was re: Templates: short comments {##} eats text)

On 4/25/07, Andrew Durdin <[EMAIL PROTECTED]> wrote: > I've been using a patched version of Django for some time, but it's > highly inconvenient (I'm using a "vendor branch" strategy as described > in the subversion book); so I'm looking for a different way to manage > this sort of thing. > > Wha

Re: Maintaining a patched Django (was re: Templates: short comments {##} eats text)

On Wed, Apr 25, Andrew Durdin wrote: > > On Apr 25, 4:46 pm, Michael Radziej <[EMAIL PROTECTED]> wrote: > > > > My own patch stack currently comprises 22 patches ... and it's still ok and > > quite manageable. I'm still up to date with svn. > > I've been using a patched version of Django for so

Maintaining a patched Django (was re: Templates: short comments {##} eats text)

On Apr 25, 4:46 pm, Michael Radziej <[EMAIL PROTECTED]> wrote: > > My own patch stack currently comprises 22 patches ... and it's still ok and > quite manageable. I'm still up to date with svn. I've been using a patched version of Django for some time, but it's highly inconvenient (I'm using a "v

Re: Templates: short comments {##} eats text

On Wed, Apr 25, Lakin Wecker wrote: > I know that the devs probably don't want anyone to bring this up again, so > feel free to ignore me, but I really need to get this off my chest. > > I'm extremely frustrated by the newlines decision. I understand you, but can only recommend what I usually

Re: Templates: short comments {##} eats text

> > 2. If we want to enable multi-line comments, we need to allow newlines > > in tag's content: > > We don't want to allow newlines in tags. That decision has already been > made and reaffirmed a number of times. I know that the devs probably don't want anyone to bring this up again, so feel fre

Re: RESTful API

Looks cool... views.py (line 26): mimetype = MIMETYPE.get(format, 'text/plain') Should that be _MIMETYPE? Earlier you declare a _MIMETYPE dictionary, but I don't see MIMETYPE anywhere. --~--~-~--~~~---~--~~ You received this message because you are subscribed t

Re: MEDIA_URL template tag/context processor/etc again

If I understand correctly and context bloat is the problem, I'd like to point that my patch at #4105 doesn't have this problem as it gives a tag instead, to be used like this: {% media "path/to/media/file.xyz" %} Cheers, - Amr On Apr 25, 1:33 pm, "Simon G." <[EMAIL PROTECTED]> wrote: > Evening

Re: The locmem patch and development progress

I wasn't advocating creating new branches or stuff, just *saying* on the website whether the current dev branch (svn trunk) is in heavy dev, feature freeze or bugfixes only. It's only a matter of communication, I certainly did not advocate maintaining a new "stable but cuting edge" svn branch. Re

MEDIA_URL template tag/context processor/etc again

Evening all, There's been a long history of people asking for some way of easily using the MEDIA_URL setting in templates. At a quick glance, I get #1278, #3818, #2532, and #4105. These have all been marked wontfix, and I closed this last one to match. The reasoning for the wontfix is that this

Re: The locmem patch and development progress

-1 What's the benefit of that over our current system where 0.96 is stable (except for major security fixes), and the active development is going on in trunk? This has been documented: http://www.djangoproject.com/weblog/2007/apr/06/changes/ - people should be using the 0.96 release on productio

Re: The locmem patch and development progress

On Apr 25, 9:50 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > use a kernel or gcc-like terminology for the branches. +1 User can use a stable SVN version (with bugfix state) and there exist a heavy dev branch for experimentals. This branch can have a "feature freeze state". In this time t

Re: The locmem patch and development progress

As an bug reporter, I have a small suggestion to make: use a kernel or gcc-like terminology for the branches. The main page could list 0.96 and (trunk or dev or 0.97) and clearly state that the 0.96 branch is only accepting bugfixes and that the trunk branch is under heavy dev, with fixes delayed

Re: The locmem patch and development progress

On Wed, 2007-04-25 at 00:24 -0700, Simon G. wrote: [...] > Maybe we could tag these somehow ("outstanding"?) so that the next > time a dev. gets some ticket time, they can glance over them and give > some feedback (wontfix, pls. improve patch, will-do-it-when-I-have- > time, etc). If it's marked

Re: The locmem patch and development progress

Evening all, Speaking as a triager, I originally thought that an "easy-fix" category would help solve these issues. However, after doing quite a bit of ticket twiddling, these easy fix/ low hanging fruit don't hang around very long anyway. The tend to get closed pretty quickly, even without tria