On Mon, Apr 19, 2010 at 12:14 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> On Mon, Apr 19, 2010 at 10:38 AM, David Zhou <da...@nodnod.net> wrote:
>> The specific number of point releases to remain compatible with can
>> probably be quibbled over, but I think th
On Mon, Apr 19, 2010 at 11:31 AM, Jacob Kaplan-Moss wrote:
> On Mon, Apr 19, 2010 at 10:19 AM, orokusaki wrote:
>> The release of Django 1.0 comes with a promise of API stability and
>> forwards-compatibility. In a nutshell, this means that code you
On Wed, Dec 30, 2009 at 3:29 PM, Alex Gaynor wrote:
> The video I linked earlier had a critical point that I think a lot of
> people are missing, adding a single filter may not add a lot to the
> developer's burden directly but it impacts the perceptions (and
> realities)
On Wed, Dec 30, 2009 at 1:37 PM, Ian Kelly wrote:
> All of which could be handled just as well or better using CSS, unless
> there's something I'm missing, which is the reason I asked.
Using CSS to truncate email addresses defeats the purpose of
truncating email
On Tue, Aug 18, 2009 at 1:35 PM, Yuri Baburov wrote:
>
> In example, I want some django 3rd-party or contrib package with
> autocomplete fields, ajax validation, ajax form sending and inline
> property editing.
> I want to be able to integrate it into admin interface and
On Fri, May 8, 2009 at 9:58 AM, Edwin Wong wrote
>
> Having followed the group here for some time, anybody posting a job
> posting or similar off-topic posting tends to be a first time poster,
> and in most cases it's very obvious that they never even bothered to
> read the
email. There's not some
secret ORM API that is being purposefully withheld.
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post t
On Sat, Dec 6, 2008 at 10:02 AM, Ludvig Ericson
<[EMAIL PROTECTED]> wrote:
>
> On Dec 6, 2008, at 09:07, David Zhou wrote:
>> Is it possible to reword the introduction on the Django Book website
>> (http://www.djangobook.com/) or perhaps somehow update it?
>
> I f
ificant sections that new users would come across -- such as the
admin -- that I feel it would be better to unambiguously direct them
to documentation we *know* to be completely up to date.
--
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received
t if you use it
99% of the time, and if a vast majority of people are using it or
something similar 99% of the time, then render_to_response should be
changed to align with actual usage.
--
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received
> tone more mature than your average mailing list. :)
>
> You damn kids and your fancy "DVCS" tools. Emacs backups are the only
> revision control I've ever needed!
You mean *VIM* backups, don't you?!!
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~-
it, and we'll see you in a few days for DjangoCon.
Congrats to the entire Django team!
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
I like the filter idea -- maybe something like 'required' It could be
similar to marking things as safe for the autoescaping.
Default behavior should be silent failures, and authors can explicitly
set variable calls to fail visibly.
So with Simon's original example, the template author
te running at
domain.com, using FCGI for both will dramatically reduce memory
requirements.
You don't really want to be embedding both a PHP and a Python
interpreter in each non-media Apache call.
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You
milestone, and will
probably draw in a lot of people -- I think it'd be beneficial to
make sure all the documentation is in place before the big rush :)
---
David Zhou
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
15 matches
Mail list logo