On Sat, Oct 10, 2009 at 1:13 AM, Vinay Sajip wrote:
>
> On Oct 8, 6:44 pm, Jacob Kaplan-Moss wrote:
>> We're still gathering feature requests for 1.2
>> (seehttp://code.djangoproject.com/wiki/Version1.2Features), but we're
>> going to work voting differently. Instead of categorizing features
>>
On Oct 9, 4:54 pm, Jacob Kaplan-Moss wrote:
> One big question I have is about performance: have you done any a/b
> testing against trunk to see how much adding logging -- especially
> upon every SQL query -- impacts performance?
>
> For me, at least, performance is going to be the critical facto
On Saturday 10 Oct 2009 11:37:06 am Russell Keith-Magee wrote:
> On Sat, Oct 10, 2009 at 6:55 AM, Rob Hudson wrote:
> > I, too, like the idea of a conference site. It fills a void and
> > sounds useful for upcoming conferences. I wasn't too crazy about the
> > blog idea, and was convinced away
On Sat, Oct 10, 2009 at 6:55 AM, Rob Hudson wrote:
>
> I, too, like the idea of a conference site. It fills a void and
> sounds useful for upcoming conferences. I wasn't too crazy about the
> blog idea, and was convinced away from the snippets idea. So shall we
> call it a conference site and
I, too, like the idea of a conference site. It fills a void and
sounds useful for upcoming conferences. I wasn't too crazy about the
blog idea, and was convinced away from the snippets idea. So shall we
call it a conference site and move on? :)
For a nice reference implementation, I'd like to
Also +1 to the idea of a conference site. I'm +0 on the prospect of
adding features like the ones on the Carsonified site for brevity's
sake. Definitely +1 to the prospect of seeing examples of unit testing
and caching. On a tangent, if there's any design work needed for said
site, I'll be happy t
Today the Django project is issuing a set of releases to remedy a security
issue. This issue was disclosed publicly by a third party on a high-traffic
mailing list, and attempts have been made to exploit it against live Django
installations; as such, we are bypassing our normal policy for security
+1 Simon's idea of a conference site. Adding some features like
http://hello.carsonified.com/ would be cool to have, though it might
be to advance for this kind of tutorial.
Sean
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
Put me down as a other +1 for a full site tutorial, especially one
that covers pip, virtualenv, unit testing and the like.
I have a suggestion for a site, too: How about the conference website
for the next DjangoCon? It's meant to be a community run conference so
the job needs to be done at some
I've done this before: http://thisweekindjango.com/screencasts/
( http://github.com/ericflo/startthedark )
I can attest, from the amount of feedback that I've received about
that series of screencasts, that building an entire website from the
ground up is extremely valuable to beginners. It's al
Russell Keith-Magee kirjoitti:
> On Fri, Oct 9, 2009 at 11:22 PM, Jacob Kaplan-Moss wrote:
>> On Fri, Oct 9, 2009 at 9:41 AM, Rob Hudson wrote:
>>> * How do people feel about a tutorial that covers a complete site?
>> Well, in grand Django tradition, by suggesting this, you've
>> volunteered to
First off, thank you all for responding and discussing this issue.
Responding to Russell's comments on the quality of the patch, I agree
that it needs better test coverage. I've uploaded an updated patch
which covers all exit points of assertFormError. The better tests
confirm that the original p
On Oct 8, 6:44 pm, Jacob Kaplan-Moss wrote:
> We're still gathering feature requests for 1.2
> (seehttp://code.djangoproject.com/wiki/Version1.2Features), but we're
> going to work voting differently. Instead of categorizing features
> into "must-have / should-have / pony" categories, we're goin
On Fri, Oct 9, 2009 at 4:33 AM, Simon Willison wrote:
> For anyone interested in following this, I've just started a
> (currently experimental) branch on GitHub:
>
> http://github.com/simonw/django/tree/logging
One big question I have is about performance: have you done any a/b
testing against t
On Fri, Oct 9, 2009 at 11:22 PM, Jacob Kaplan-Moss wrote:
>
> On Fri, Oct 9, 2009 at 9:41 AM, Rob Hudson wrote:
>> * How do people feel about a tutorial that covers a complete site?
>
> Well, in grand Django tradition, by suggesting this, you've
> volunteered to be in charge :)
>
> But sign me u
On Fri, Oct 9, 2009 at 6:12 AM, Luke Plant wrote:
>
> On Friday 09 October 2009 10:33:28 Simon Willison wrote:
>> For anyone interested in following this, I've just started a
>> (currently experimental) branch on GitHub:
>>
>> http://github.com/simonw/django/tree/logging
>
> Is there some easy wa
Hi Rob --
First, thanks for taking this on. The tutorial indeed needs some good
lovin'; glad to see someone stepping up to the plate. I don't have a
huge amount of bandwidth these days, but I can commit to writing a
bit, and to editing anything you or anyone else writes.
On Fri, Oct 9, 2009 at 9
I'd like to propose the addition of a new tutorial that represents a
complete website, describing everything from start to finish. This
would allow for many more topics to come into play -- things we all
deal with at some point in developing websites using Django. This
would also allow for those
On Oct 9, 11:12 am, Luke Plant wrote:
> >http://github.com/simonw/django/tree/logging
>
> Is there some easy way to see the patch? Preferably a link which will
> just show the diff between the latest of your branch and trunk, but
> failing that, a recipe of commands using git (for those of us wh
On Friday 09 October 2009 10:33:28 Simon Willison wrote:
> For anyone interested in following this, I've just started a
> (currently experimental) branch on GitHub:
>
> http://github.com/simonw/django/tree/logging
Is there some easy way to see the patch? Preferably a link which will
just show
For anyone interested in following this, I've just started a
(currently experimental) branch on GitHub:
http://github.com/simonw/django/tree/logging
So far I've added a 'django' logger which is silent by default, and
hooked up a new CursorLoggingWrapper to log all SQL statements from
the ORM to
21 matches
Mail list logo
