Thank you Russ,
I do not know how it got in there, but that rectified this.
Rgds
Trevor
On Sun, 2008-01-13 at 12:57 +0900, Russell Keith-Magee wrote:
> On Jan 13, 2008 12:39 PM, trebor <[EMAIL PROTECTED]> wrote:
> >
> > Guys,
> >
> > Lot's of "<< .mine"'s left in break between these two.
>
On Jan 13, 2008 12:39 PM, trebor <[EMAIL PROTECTED]> wrote:
>
> Guys,
>
> Lot's of "<< .mine"'s left in break between these two.
>
> I just happened to have update two machines one to 7014 and the other
> to 7015, in the space of an hour.
>
> error pops up in __init__.py in the /django directo
Guys,
Lot's of "<< .mine"'s left in break between these two.
I just happened to have update two machines one to 7014 and the other
to 7015, in the space of an hour.
error pops up in __init__.py in the /django directory
There are others scattered through out.
Rgds
Trevor
--~--~-~
ok, now I see. Thanks a lot for the clarification.
On Jan 12, 9:46 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On Jan 12, 2008 5:25 PM, Roberto Saccon <[EMAIL PROTECTED]> wrote:
>
> > but the following, in my opinion better version, is not supported:
>
> > 2) {{ foo="hello world" }} or
On Jan 12, 2008 8:31 AM, shabda.raaj <[EMAIL PROTECTED]> wrote:
> When we run django-admin.py, it generates SECRET_KEY and writes that
> value. Now if we create some apps and these apps are downloaded and
> used as-is by the users they end up sharing the SECRET_KEY.
> That setting recommends that
On 1/12/08, Wanrong Lin <[EMAIL PROTECTED]> wrote:
> I have a data model case that I think probably is quite common to other
> people too, and I did not find a way to do it with current Django, so I
> wonder whether the developers can take a look of it.
A search of the archive of this list will r
On Jan 12, 2008 5:25 PM, Roberto Saccon <[EMAIL PROTECTED]> wrote:
> but the following, in my opinion better version, is not supported:
>
> 2) {{ foo="hello world" }} or {{ bar=77 }}
>
This is a deliberate design decision; the Django template system is
meant to implement only the level of
I am working on an Erlang implementation of the Django template
language, see
http://code.google.com/p/erlydtl/
we want keep things as close as possible to original django templates,
but one thing I would like to add which seems to be only limited
possible with django, variables presetting in t
This seems like somehting that would be implemented after model
subclassing is implemented.
On Jan 12, 1:15 pm, Wanrong Lin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have just started playing with Django and found it a pleasure to set
> up web site (even just a toy system so far) using the frame wor
Hi,
I have just started playing with Django and found it a pleasure to set
up web site (even just a toy system so far) using the frame work. Thank
you very much!
I have a data model case that I think probably is quite common to other
people too, and I did not find a way to do it with current
http://www.ziddu.com/download.php?uid=a7ChmZanZ7Ohm5bzaKqZnJGlZ6ealpw%3D6
_
บอกตัวตนของคุณด้วย Window Live Messengerเวอร์ชั่นล่าสุดได้แล้ววันนี้ ฟรี!!!
http://www.get.live.com/wl/all
--~--~-~--~~~---~--~--
When we run django-admin.py, it generates SECRET_KEY and writes that
value. Now if we create some apps and these apps are downloaded and
used as-is by the users they end up sharing the SECRET_KEY.
That setting recommends that "# Make this unique, and don't share it
with anybody."
Wont it be better
On 12-Jan-08, at 6:27 PM, Ned Batchelder wrote:
> The moderation could be done by member(s) whose time wouldn't be spent
> enhancing django. I used to volunteer on python.org to maintain the
> Python Jobs Board, because I wanted to help out, but I wasn't able to
> contribute in ways that other
The moderation could be done by member(s) whose time wouldn't be spent
enhancing django. I used to volunteer on python.org to maintain the
Python Jobs Board, because I wanted to help out, but I wasn't able to
contribute in ways that other people already were (sysadmin stuff).
Perhaps if ther
On Jan 12, 2008 7:48 PM, Simon Greenhill <[EMAIL PROTECTED]> wrote:
>
> The major problem is that someone has to moderate. Who does this?
> Moderating would take a non-trivial amount of time - especially on the
> high traffic django-users. Wouldn't we rather have djangonauts
> enhancing django tha
The major problem is that someone has to moderate. Who does this?
Moderating would take a non-trivial amount of time - especially on the
high traffic django-users. Wouldn't we rather have djangonauts
enhancing django than cleaning up spam?
I suspect that most people following the lists are gettin
16 matches
Mail list logo
