On 10月19日, 下午4时34分, "Michael P. Jung" wrote:
> > There is a templatetags {% include 'x.html' %}, it's very nice. may a
> > templatetags like {% include no-parse "x.html"} is needed. It's so
> > powerful to improve the speed of include some static files which has
> > no
For reference purposes, I started a branch of django on bitbucket with
a contrib.messages app heavily based on django_notify (only
renamed/updated to reflect the API on the wiki):
http://bitbucket.org/tobias.mcnulty/django-contrib-messages/
It's a work in progress and I'll be updating it in the
I've written something called a 'CompositeField' which basicly does what
you're looking for by grouping fields together. Assume you want to have
an AddressField you could define it the following way:
class AddressField(CompositeField):
def __init__(self, blank=False):
On Tue, Oct 20, 2009 at 2:50 PM, thierry wrote:
>
> Hello everybody,
>
> I'm working on a scientific project and Django has been chosen to
> develop our database model. I'd like to develop a
> 'PhysicalQuantityField' that manages a value and its relative unit.
>
> The
On Oct 19, 4:13 pm, mrts wrote:
> now. Maintaining your own branches on GitHub or
> BitBucket off the corresponding Django SVN mirrors
> is easy and effortless, so it's time to put the
> grudges behind and happily fork and branch Django
It seems like the word "fork" is
Hello everybody,
I'm working on a scientific project and Django has been chosen to
develop our database model. I'd like to develop a
'PhysicalQuantityField' that manages a value and its relative unit.
The first way to do this stuff is to translate the couple (value,unit)
into a string and use
This is something I attempted once to do over a small GET wrapper by
adding __not; any __not query would be passed to exclude(). Would that
be a solution to the problem?
J. Leclanche / Adys
On Tue, Oct 20, 2009 at 6:31 PM, Michael P. Jung wrote:
>
> rm>
On Oct 20, 5:26 pm, Jacob Kaplan-Moss wrote:
> I don't have time to teach you how to communicate professionally.
I don't presume to speak for Yuri (or anyone else) but I think it's
not unreasonable that some allowance be given in situations where
miscommunication of tone
On Tue, Oct 20, 2009 at 8:44 AM, Yuri Baburov wrote:
> Moreover, new contributors are considered the least important
> creatures in the world!!!
As they say on Wikipedia, "[citation needed]". This list grows with
every new release:
On Tue, Oct 20, 2009 at 9:35 AM, Yuri Baburov wrote:
> how would you reformulate this in friendly and professional tone so
> this can be discussed?
I don't have time to teach you how to communicate professionally.
Reading your message first makes me feel angry, then
On Tue, Oct 20, 2009 at 10:52 AM, mrts wrote:
> Jacob, I'm afraid you totally misunderstood me.
> My message was intended to encourage people to
> scratch their own itches more now that it's so
> much easier -- and, of course, give back --
> instead of grumbling on the
Jacob, I'm afraid you totally misunderstood me.
My message was intended to encourage people to
scratch their own itches more now that it's so
much easier -- and, of course, give back --
instead of grumbling on the mailing list.
I fail to see how can "so it's time to put the
grudges behind and
Russell Keith-Magee wrote:
> On the 'missing something' front, reverse() now takes a 'current_app'
> argument that gives context to the app lookup, which resolves the
> ambiguity from the point of view of the reverse() function.
I saw this one. It doesn't work in this case exactly beacuse of
rm> exclude(x=1).exclude(y=2) translates to NOT (x=1) AND NOT (y=2)
So why do we have __gt, __ge, __lt, __le then? It would be as simple to
have only __le and get rid of the rest as it can easily expressed using
exclude and filter. I know, it's picky, but you get my point.
I don't see why all
> Signed cookies are useful
> for all sorts of things - most importantly, they can be used in place
> of sessions in many places, which improves performance (and overall
> scalability) by removing the need to access a persistent session
> backend on every hit. Set the user's username in a signed
On Tue, Oct 20, 2009 at 10:09 PM, Michael P. Jung wrote:
>
> I'd like to propose a new field lookup __neq which could be used to
> negate a single parameter. It is not ment to make exclude() obsolete, as
> they both have a different scope:
>
> filter(x__neq=1, y__neq=2) would
On Tue, Oct 20, 2009 at 9:23 PM, Jacob Kaplan-Moss wrote:
>
> Hi Yuri, Mart --
>
> I feel that I need to make it clear that I'm not ignoring you, or this
> conversation. However, the tone is so hostile and unprofessional that
> it'd be a waste of my time to try to engage, so
On Tue, Oct 20, 2009 at 10:23 PM, Jacob Kaplan-Moss wrote:
>
> Hi Yuri, Mart --
>
> I feel that I need to make it clear that I'm not ignoring you, or this
> conversation. However, the tone is so hostile and unprofessional that
> it'd be a waste of my time to try to engage, so
Hi Yuri, Mart --
I feel that I need to make it clear that I'm not ignoring you, or this
conversation. However, the tone is so hostile and unprofessional that
it'd be a waste of my time to try to engage, so I'm simply going to
stay out.
Jacob
On di, 2009-10-20 at 16:09 +0200, Michael P. Jung wrote:
> Besides exclude(x=None).exclude(y=None).exclude(z=None) feels less
> intuitive to me than filter(x__neq=None, y__neq=None, y__neq=None).
That's what Q objects are for:
.filter(~Q(x=None),~Q(y=None),~Q(z=None))
or:
Hi folks,
is there a plan to change command compilemessages, so it will ignore
duplicity translations? In my native language it's necessary to have more
than one translation for particular string.
Radovan
--
View this message in context:
On Mon, Oct 19, 2009 at 11:52 PM, Hanne Moa wrote:
>
> It doesn't look like Contrib-06, covering ticket #3011, Allow for
> extendable user module, will be in for 1.2. So: let's think afresh,
> start from scratch, think about what we really, really want. This is
> my pony for
I'd like to propose a new field lookup __neq which could be used to
negate a single parameter. It is not ment to make exclude() obsolete, as
they both have a different scope:
filter(x__neq=1, y__neq=2) would translate to "(x <> 1 AND y <> 2)"
while exclude(x=1, y=2) translates to "NOT (x = 1 AND
Hi Mart,
actually, you are half right. Fork & go.
Still the main reason I wrote wasn't recognized.
Total anarchy in Django team.
Core developers don't agree with each other on who will respond on
what kind of messages, what part of Django contributions is under
their maintenance.
Moreover,
On Tue, Oct 20, 2009 at 5:34 AM, Ivan Sagalaev
wrote:
>
> Hello!
>
> I've just stumbled upon a difficult to understand problem. I have an app
> that has an urlconf which is included in a project under a namespace:
>
> (r'^blog/', include('app.urls',
Join .Net Community
This group represents the Microsoft .Net community. All .net
programmers all around the world are welcome here. In this group
you'll find the latest releases of .Net related products, frameworks,
Upgradation, technologies, IDEs etc. You also can share your
experiences and
2009/10/19 Jeff Anderson
>
> An official "real-life", advanced tutorial would have been wonderful to
> fill
> the gap that I had. It would have saved me quite a bit of *re-learning*
> things,
> which is always annoying.
>
If you can outline some of the gaps you had and
27 matches
Mail list logo