I ran into a problem trying to use inclusgion_tag() in combination
with a template that used the url tag with #5034 applied.
First, #5034, which patches the url tag to use request.urlconf if it's
been set, checks for an instance of RequestContext, rather than the
key 'request'. This could be
On Sun, 2008-06-08 at 22:24 -0700, Russell Keith-Magee wrote:
>
>
> On Jun 9, 12:53 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
> > Hi gang,
> >
> > I've been hunting down some bugs with serialization of multi-table
> > inheritance, and I need a sanity check on something that I want
On Wed, 2008-06-25 at 11:54 +0200, Tomas Kopecek wrote:
> Hello,
> In django.utils.synch is located RWLock. When you try enter the same
> lock twice (probably in some subprocedure) you can't. I think that
> correct semantics is that you had acquired this lock in this thread so
> you should
On Fri, 2008-06-27 at 17:33 +0300, Antonis Christofides wrote:
> Hi,
>
> There are essentially two things that you can do with a block:
> (1) define it (or redefine it); and (2) insert it somewhere in a
> template. The block tag thus performs different functions depending
> on circumstances:
>
On Fri, Jun 27, 2008 at 8:31 PM, Simon Willison <[EMAIL PROTECTED]> wrote:
> I've got code for this lying round which I'd be happy to donate if
> people agree this is the right approach.
I personally much prefer this approach. I've worked in a couple
communities where personal attacks were quite
>
> The problem with this is it requires state on the server, which means . . .
I don't think it's necessary to implement this in such a way that additional
server state is stored. Instead, you could let the confirmation token be a
hash of the internal user state -- including, most importantly,
On Jun 28, 1:12 am, Luke Plant <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] said the following:
> > I'd suggest making the code to change the password a one-use-only
> > item though, so that even if someone did sniff the code, it'd be
> > useless after that.
>
> The problem with this is it
On Friday 27 June 2008 23:06:57 Collin Grady wrote:
> [EMAIL PROTECTED] said the following:
> I'd suggest making the code to change the password a one-use-only
> item though, so that even if someone did sniff the code, it'd be
> useless after that.
The problem with this is it requires state on
On 12 jun, 21:37, "Leo Soto M." <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 12, 2008 at 8:35 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
> [...]
>
> > Since then I've opened ticket [2]#7420 with a patch
>
> I see that part of the patch deals with the fact that the underlying
> adapter prefer to
[EMAIL PROTECTED] said the following:
> It sounds like what you are advocating is changing the password reset
> to work similar to the way activation works in James Bennett's django-
> registration, is that correct?
Similar to that is what it sounds like - I'm definitely +1 on this - a
lot of
It sounds like what you are advocating is changing the password reset
to work similar to the way activation works in James Bennett's django-
registration, is that correct?
On Jun 27, 4:01 pm, Luke Plant <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Currently password reset is done without any
Hi all,
Currently password reset is done without any confirmation, so all you
have to do is know someone's email and a Django site that they use
(assuming it uses the default password reset code) and you can change
their password. In this way, you only have to make about 1
request/minute to
On Fri, Jun 27, 2008 at 5:55 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
>
> On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
>
>> All PostgresSQL supports in terms of *storage* is
>> a fixedtimezoneoffset, not the actual zoneinfo name; this isn't
>> very useful, and causes problems
Full test pass on Ubuntu Hardy Heron, with python 2.5, and sqlite3. I
also did some general testing of uploading files, which were
succesful, and I was able to observe large uploads going to my /tmp
dir.
On Jun 27, 4:41 am, David Reynolds <[EMAIL PROTECTED]>
wrote:
> Jacob,
>
> Hopefully this
On Fri, Jun 27, 2008 at 11:36 AM, rskm1 <[EMAIL PROTECTED]> wrote:
>
>> Help me out here: how can I make it more obvious? You missed that;
>> others often do to. Can you share with me some insights on how you
>> missed it?
>
> I'll chime in. Basic rule of thumb for GUIs:
> * If it's going to
> Help me out here: how can I make it more obvious? You missed that;
> others often do to. Can you share with me some insights on how you
> missed it?
I'll chime in. Basic rule of thumb for GUIs:
* If it's going to fail _ANYWAY_, just GRAY IT OUT!!
In other words, make the form-input fields of
On Fri, Jun 27, 2008 at 4:33 PM, Antonis Christofides
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> There are essentially two things that you can do with a block:
> (1) define it (or redefine it); and (2) insert it somewhere in a
> template. The block tag thus performs different functions depending
>
Hi,
There are essentially two things that you can do with a block:
(1) define it (or redefine it); and (2) insert it somewhere in a
template. The block tag thus performs different functions depending
on circumstances:
* If a block tag with the same name exists in an inherited
template, then
On Fri, Jun 27, 2008 at 1:58 PM, Dipankar Sarkar
<[EMAIL PROTECTED]> wrote:
>
> Hey guys
>
> I and a coupla more django developers recently released a micro-
> blogging platform called kwippy (http://kwippy.com) ... currently it
> is in beta and invite only (obv mail me to get an instant invite)
Hey guys
I and a coupla more django developers recently released a micro-
blogging platform called kwippy (http://kwippy.com) ... currently it
is in beta and invite only (obv mail me to get an instant invite)
We need to get more people to use the service and help us test our
infrastructure. We
On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> All PostgresSQL supports in terms of *storage* is
> a fixedtimezoneoffset, not the actual zoneinfo name; this isn't
> very useful, and causes problems such as the above.
Actually, in PostgreSQL TIMESTAMP WITH TIME ZONE does NOT store
I don't think that this should be included in the 'must have' list (to
avoid postponing 1.0 date). What I want is to consider this feature
for the may be list, so if a good patch is ready before 1.0 beta, it
could be commited. So if it's not ready on that time, then we forget
this feature for
> I think Django is really wonderful, but I am puzzled that it contains
> so few "ordering features". We often have the case that a user wants
> to select from a list of possible choices (normal select) *plus* wants
> to specify an ordering. Typically in applications this is done using
> up/down
Jacob,
Hopefully this will be of some use..
On 26 Jun 2008, at 8:14 pm, Jacob Kaplan-Moss wrote:
> * Running the test suite -- coverage is quite good now, but I've only
> been able to test on a limited set of OSes/DBs. Looks elsewhere just
> in case, very good.
I've just checked the branch
On Fri, Jun 27, 2008 at 3:23 AM, Marc Garcia <[EMAIL PROTECTED]> wrote:
>
> Could it be added to 1.0 maybe list? I think that those features are
> essential for developing not only international websites, also for
> developing non international websites for most countries (not US, of
> course ;).
On Fri, Jun 27, 2008 at 4:29 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El jue, 26-06-2008 a las 06:58 +0800, Russell Keith-Magee escribió:
>> >> My preferred solution here would be to provide a way for test cases to
>> >> substitute a top level URL pattern object for the duration of the
>> >>
El jue, 26-06-2008 a las 06:58 +0800, Russell Keith-Magee escribió:
> >> My preferred solution here would be to provide a way for test cases to
> >> substitute a top level URL pattern object for the duration of the
> >> test. For example:
> >
A patch in these lines is now attached to #7521, the
cleavage between two young mountains
earn many $$
by working on on-line
spend your pleasure time in on-line
its a better chance for u
***
http://glamourworldpriya.blogspot.com/
***
28 matches
Mail list logo
