On Tue, 2006-06-20 at 20:40 +, [EMAIL PROTECTED] wrote:
> i'm having the same issue that is described in ticket #2079 (except the
> fields are just CharFields). the ticket says that the issue was fixed.
> so i updated to the latest build, but i'm still having the problem.
> anyone else seen
I created a 'history_view' which is set up to show X posts from the
date/time passed. which is slightly different to the generic date
based view which shows
you the posts on that day.
you can see it in action here:
http://economy-chat.com/aggy/2006/05/23/23:59:59/
shows me the posts
Simon Willison wrote:
> On 20 Jun 2006, at 16:25, James Bennett wrote:
>
> > Security by annoyance is security that people learn to hate and turn
> > off as soon as they can, so in the end it doesn't really make them any
> > more secure than they were before.
>
> Agreed - which is why I want to
What I mean by a browser game framework is, one that is more complex
than the ones created for Urban Dead (urbandead.com) or Nexus War
(nexuswar.com). I plan on keeping the dynamic aspects you mentioned
available. But basically this will represent something similar to a MUD
only served through
What I mean by a browser game framework is, one that is more complex
than the ones created for Urban Dead (urbandead.com) or Nexus War
(nexuswar.com). I plan on keeping the dynamic aspects you mentioned
available. But basically this will represent something similar to a MUD
only served through
(sorry for monolog...)
Careful readers might note that my two suggestions might conflict.
Bar.foo
If it returns the ForeignKeyField object (or some proxy for it), cant
return the model referred to. Maybe best (something like):
Bar.foo.related_model
to get related model; Bar.foo would
i'm having the same issue that is described in ticket #2079 (except the
fields are just CharFields). the ticket says that the issue was fixed.
so i updated to the latest build, but i'm still having the problem.
anyone else seen this issue with manipulators?
On these same lines, it is more generally a pain to do introspection.
For instance, if I want to know to what field ForeignKeyField "foo" of
model "Bar" refers to, I can find out with:
Bar._meta_get_field( 'foo' ).rel.field_name
But this is certainly not intuitive, and presumably subject to
Currently, if I have:
---
class A( Model ):
pass
class B( Model ):
a = ForeignKey( A )
a = A()
b = B( b = a )
---
Then b.a gets a, and b.a.model returns A.
However, if I just have "B", I think B.a should return A (right
I had plenty of ideas for browser based games and I can't remember
one that I thought Django couldn't handle. In fact, depending on the
game mechanics, certain things are easier.
Power sets / items (loot) are a good example, if your game will have
it. They translate well into Django models.
Adrian Holovaty wrote:
> Thanks for the comments. I'd like to restructure our Trac installation
> into more useful categories, such as: "Still thinking about it,"
> "Patch is good and should be committed with caveats," "Patch isn't
> good enough," and stuff like that. I think more granular
Simon Willison wrote:
>
> On 19 Jun 2006, at 21:00, [EMAIL PROTECTED] wrote:
>
>> anyway, i suppose i will wait for you to elaborate on your
>> reasoning in
>> the wiki this evening. :)
>
> I've written up a proposal for how we can implement auto escaping
> while hopefully keeping most
On Jun 20, 2006, at 6:26 AM, Luke Plant wrote:
> In fact there seems to be a problem with the whole website now -- it's
> very slow, and media.djangoproject.com doesn't seem to be working at
> all.
Yeah, the media server failed early this morning.
It should be fixed now, but I think the updates
On 6/20/06, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> On 20 Jun 2006, at 16:25, James Bennett wrote:
>
> > Security by annoyance is security that people learn to hate and turn
> > off as soon as they can, so in the end it doesn't really make them any
> > more secure than they were before.
>
>
On 20 Jun 2006, at 16:25, James Bennett wrote:
> Security by annoyance is security that people learn to hate and turn
> off as soon as they can, so in the end it doesn't really make them any
> more secure than they were before.
Agreed - which is why I want to try it in a branch and see if it's
On 6/14/06, Brantley Harris <[EMAIL PROTECTED]> wrote:
> > Yeah, refactoring Manipulators is one of the last things I want to
> > have happen before Django goes 1.0.
> Mind if I take a shot at it?
Sure, proposals are definitely welcome.
Adrian
--
Adrian Holovaty
holovaty.com |
On 6/20/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I haven't used the magical versions of Django, but I regard the magic that
> has magically imported models a different thing. In every framework things
> happen automatically, and just calling it "bad magic" is something that
> might result
Adrian Holovaty wrote:
> On 6/20/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>>
>> You're against automatically quoting your data in the database driver?
>> Let's rip it out, bad magic that munges your data behind your back.
>>
>
> I figured somebody might bring up this example, but it
On 20 Jun 2006, at 15:11, Michael Radziej wrote:
> But, looking at the recent bugs in the Admin:
>
> 2006, __str__() output not escaped in breadcrumbs and filters
> 2152, username was not escaped
>
> Perhaps neither of this would be fixed with auto-escaping. But I
> want to
> emphasize that
On 6/20/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> You're against automatically quoting your data in the database driver?
> Let's rip it out, bad magic that munges your data behind your back.
>
I figured somebody might bring up this example, but it isn't quite
analogous. With a
Adrian Holovaty wrote:
> On 6/20/06, Simon Willison <[EMAIL PROTECTED]> wrote:
>> I've written up a proposal for how we can implement auto escaping
>> while hopefully keeping most people happy:
>>
>> http://code.djangoproject.com/wiki/AutoEscaping
>
> I've gotta say, I don't like the concept of
On 6/20/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> I've gotta say, I don't like the concept of auto-escaping on by
> default. I'd rather not have the framework automatically munging my
> data behind my back: it'd be a case of the same type of magic that we
> removed in the magic-removal
On 6/20/06, Simon Willison <[EMAIL PROTECTED]> wrote:
> I've written up a proposal for how we can implement auto escaping
> while hopefully keeping most people happy:
>
> http://code.djangoproject.com/wiki/AutoEscaping
I've gotta say, I don't like the concept of auto-escaping on by
default. I'd
Hey Andrew!
adurdin wrote:
> Michael Radziej wrote:
>> adurdin wrote:
>>> Having the context aware of the primary escaping needs of the output is
>>> a nice idea, but as James Bennett pointed out, the template is what
>>> should be making the decision.
>> I still don't see why. The programmer
On 6/20/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I have managed to get py.test also run doctests with proper database setup
> etc. for
> Django for my own testing. py.test walks through all subdirectories to
> collect test cases.
> Are you interested in this way (i.e., using py.test)?
Viktor wrote:
>
> Django's ORM is not about tables, columns and rows... It's about objects
> (or I'm missing something :)...
I'm been wondering the same thing, but with a different reason. My
guess is that django's not (yet, at any rate) trying to provide a full
ORM, but rather a thin,
Michael Radziej wrote:
>
> adurdin wrote:
>
> You could simply encode the URL, as you currently need to do anyway, and then
> mark it as escaped.
True.
> > Having the context aware of the primary escaping needs of the output is
> > a nice idea, but as James Bennett pointed out, the template is
Uros Trebec wrote:
>
> > To summarize, in the past I've used a time_from/time_thru pair of
> > date/time columns to make it more efficient to retrieve the version of
> > a row as it looked at a particular point in time. Your design of just
> > using change_date makes this more difficult.
>
> I
On 20 Jun 2006, at 12:15, Michael Radziej wrote:
> Perhaps it's also a good idea to add an attribute `raw` to the
> class `escaped`, so that
> you can always access the raw string when it is necessary. In some
> circumstances, such
> as when you pass a complete html table in the context,
On 20 Jun 2006, at 12:02, Todd O'Bryan wrote:
> Couldn't we do something less invasive/complicated?
>
> How about
>
> {{ var }}
>
> by default escapes the contents (in other words, the very first
> filter called on a variable is escape, by default) and
>
> {{ var|raw }}
>
> skips the call to
In fact there seems to be a problem with the whole website now -- it's
very slow, and media.djangoproject.com doesn't seem to be working at
all.
Luke
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
Hey. We came up with this independently. It must be a good idea. :-)
Todd
On Jun 20, 2006, at 5:50 AM, adurdin wrote:
> Simon Willison wrote:
>> I've written up a proposal for how we can implement auto escaping
>> while hopefully keeping most people happy:
>>
>>
Couldn't we do something less invasive/complicated?
How about
{{ var }}
by default escapes the contents (in other words, the very first
filter called on a variable is escape, by default) and
{{ var|raw }}
skips the call to escape?
It breaks backwards compatibility, but maybe there's a way
adurdin wrote:
>
> The main drawback I see with this is that the behaviour of
> {{mylist|count}} is not obviously unescaped.
I meant {{mylist|length}}, of course.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Simon Willison wrote:
> I've written up a proposal for how we can implement auto escaping
> while hopefully keeping most people happy:
>
> http://code.djangoproject.com/wiki/AutoEscaping
A very nice solution, with a good method of automatically flagging
things as escaped or not; but it seems to
Hi,
Why not use Generic Views?
http://www.djangoproject.com/documentation/generic_views/
It answer all the needs you can have for an archive: it organizes
posts by year, month, day, individual post,...
Have also a look at:
http://www.rossp.org/blog/2006/jun/08/django-blog-redux/
Enjoy,
G
On
Hi all,
Still getting to grips with Django, got a quick question:
I'm writing a blog application as my first experiment with Django. I
want to have the main blog page, /path/to/my/site/blog, display the 10
latest blog entries and have a link to so the previous 10 entries
(which links the the
Mikeal Rogers wrote:
> I've been developing some fun stuff with django for about a month now
> and I've been thinking of taking on a big challenge, adding ZODB
> support to Models.
>
> I _love_ the django models, but there are a few things I wish to do
> in which I need a full object
Malcolm Tredinnick wrote:
> Because of the way tests are imported in runtests, it is currently not
> possible to have a subdirectory of modeltests/ and a subdirectory of
> regressiontests/ with the same name (so, for example, I created
> regressiontests/one_to_one_regree/ ). If somebody wants to
I did leaf through a "Booby" book once but I was underwhelmed. Guess I
am too used to Python syntax now.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
I hope it is not totally different! I intend to use Django for
application development. My background is in application development,
application development is why I am here.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On 19 Jun 2006, at 21:00, [EMAIL PROTECTED] wrote:
> anyway, i suppose i will wait for you to elaborate on your
> reasoning in
> the wiki this evening. :)
I've written up a proposal for how we can implement auto escaping
while hopefully keeping most people happy:
42 matches
Mail list logo
