On 1/31/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> I'm looking to see how many other australians are interested in
> Django, and also to get a list of people interested in some casual
> django work (if I get any) on the side.
>
> --
> [EMAIL PROTECTED] -- blog: http://feh.holsman.net/ -- PH: +
On 1/17/06, Matthew Marshall <[EMAIL PROTECTED]> wrote:
> Minor nitpick, but could we use 'class_' instead of 'klass'?
Sorry for the slow response on this. It's all set:
http://code.djangoproject.com/changeset/2193
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com | chicagocrime.org
Ian Holsman wrote:
> I'm looking to see how many other australians are interested in
> Django, and also to get a list of people interested in some casual
> django work (if I get any) on the side.
I'm in Sydney.
Might be available if work comes up; depends upon other commitments.
Definitely inter
Melbourne 'Djypsy' here.
--
Lach
http://illuminosity.net/
Yes, sort of. TurboGears is using what they're calling the "open
template plug-in engine" something or rather. The underlying effect is
it provides a unified way to render templates. It's still undergoing
some fine-tuning, and is not part of TurboGears itself. Here's the
'spec' for making a templa
On 01/31/06 22:25, Ian Holsman wrote:
are you proposing a standard interface to templating languages in python
ala WSGI but for templates?
There's currently a discussion about just that on the python web-sig
mailing list.
http://mail.python.org/pipermail/web-sig/2006-January/thread.html#1
On 1/31/06, Jason Davies <[EMAIL PROTECTED]> wrote:
> I've been following the changes in magic-removal and I've noticed
> various niggly bugs (especially in the latest round of updates) when
> testing my code. Just simple things, e.g. get_object() should be get()
> in some of Django's contrib app
Hi,
I've been following the changes in magic-removal and I've noticed
various niggly bugs (especially in the latest round of updates) when
testing my code. Just simple things, e.g. get_object() should be get()
in some of Django's contrib apps.
Do you want me to open tickets for them or is that
OK..
If I get some spare cash in search of a home I'll ping the people who
responded. .. thanks!
On 1/31/06, Simon Greener <[EMAIL PROTECTED]> wrote:
>
> Ian and Russell,
>
> I currently am learning Django for a mini "open source" project
> that I am working on. But I am still learning about Djan
are you proposing a standard interface to templating languages in python
ala WSGI but for templates?
On 2/1/06, Ben Bangert <[EMAIL PROTECTED]> wrote:
>
> Adrian Holovaty wrote:
> > Anybody care to tackle the separation of Django templates? The main
> > thing is decoupling it from django.core.se
Hehe. A month ago I tried to use the django template for my pocoo
project but it ended up in rewriting the template engine. Not because
it was impossible to strip it out. (It worked quite well) but for pocoo
I wanted a better syntax for the filters.
But personally I find the idea of spliting them
jfyi,
GvR wrote also:
>> Regarding a standard, there is sort of a standard
>> developing, that TurboGears has pioneered, and Pylons also
>> supports. It's called template plug-ins:
>> http://www.turbogears.com/docs/plugins/template.html
>
> Thanks for the pointer! Perhaps it is right -- if other fr
Adrian Holovaty wrote:
> Anybody care to tackle the separation of Django templates? The main
> thing is decoupling it from django.core.settings (and, hence,
> DJANGO_SETTINGS_MODULE), of which I'm not sure what the best approach
> would be. Note that in the magic-removal branch, the template syste
Thanxs very much it solved my problem :)
Mary Adel
Software Developper
ITrize-Egypt 13 Naguib Hashad medan elhegaz heliopolis
email: [EMAIL PROTECTED]
Office: +202 - 6236612 EXT. 102
Mobile: +2012 5241719
> Original Message
> Subject: Re: Tinymce
> From: "scum" <[EMAIL PRO
Brant Harris wrote:
> I wonder if with the new "with syntax", you could do something like:
>
> with 404_on_error:
>Articles.objects.filter(name__startswith="Whatever")
>
> That'd be sweet.
>
Yeah, I think there is a lot of funky stuff that can be done with
'with'. Unfortunately we are stuc
I wonder if with the new "with syntax", you could do something like:
with 404_on_error:
Articles.objects.filter(name__startswith="Whatever")
That'd be sweet.
On 1/31/06, Robert Wittams <[EMAIL PROTECTED]> wrote:
>
> I think Lukes ideas are probably the way forward.
>
> However, another possi
I think Lukes ideas are probably the way forward.
However, another possibility would be a 404 wrapper for a set, eg
404_on_error(Articles.objects).filter(name__startswith="Whatever")
Effectively this creates a version of the "set" that has a different
error policy. Not sure if this would work i
On Tuesday 31 January 2006 17:23, Brant Harris wrote:
> I always thought the functionality should be within the object:
> Person.objects.filter_or_404(pk=2)
> Person.objects.filter(pk=2).or_404()
That's nasty! You'd have HTTP methods as part of QuerySet.
I think for the usual case (at least f
On 1/31/06, Brant Harris <[EMAIL PROTECTED]> wrote:
> I always thought the functionality should be within the object:
> Person.objects.filter_or_404(pk=2)
> Person.objects.filter(pk=2).or_404()
That couples models to the HTTP-request layer. Models don't care about
whether they're being used in We
I always thought the functionality should be within the object:
Person.objects.filter_or_404(pk=2)
Person.objects.filter(pk=2).or_404()
On 1/31/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> The descriptor-fields implementation is firming up, which is good. Now
> it's time to start changing a
Try changing your js variable to
js = ('js/tiny_mce/tiny_mce.js','js/tiny_mce/textareas.js'),
For some reason on my installation, the /media/ is automagically added.
The descriptor-fields implementation is firming up, which is good. Now
it's time to start changing all the various bits inside Django to use
the new descriptor-fields syntax.
Two that come to mind are the get_object_or_404() and
get_list_or_404() shortcuts. Currently they accept a model and
**kwa
On 1/31/06, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Won't it be cool if django splits the tree into different reusable packages,
> developed and maintained by you folks only. One can say there are almost
> independent, but it requires lots of familiarity in django to understand
> this, an outsi
Hi all,One of the first thought that came to my mind when I read django documentation is, Django is really a set of related projects, Django ORM, Django Templates and Django Webframework, and can be used independently of each other. Came across this post by Guido:
http://www.artima.com/weblogs/vie
Ian and Russell,
I currently am learning Django for a mini "open source" project
that I am working on. But I am still learning about Django, complicated
by not knowing Python, PHP, MySQL but heh, I'll get there. Not
interested
in doing any contract work but am interested in what other Auss
Russell Keith-Magee wrote:
> I have a need - or, at least, larger plans for a need.
>
> Short version - don't just think about instances of Q() itself. You can also
> use any objects descendent from, or objects that meet the Q() intereface.
> This allows the end user to define queries that Djang
26 matches
Mail list logo
