On Jul 29, 2:54 pm, Simon Greenhill <[EMAIL PROTECTED]> wrote:
> Hmm... off the top of my head -
[snip]
Cool, I've included those as an example of more details.
Feel free to update the following if anyone feels it needs it...
http://code.djangoproject.com/wiki/DjangoSuccessStories
Now we just n
On 7/28/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> It's definitely up for discussion, and I'm not tied to the current
> tutorial in any way. My personal preference is to replace the official
> tutorial with the first few chapters of the Django book, once that's
> been published, because thos
On Jul 30, 2:33 pm, "Mario Gonzalez" <[EMAIL PROTECTED]> wrote:
> Hello! one week ago I opened this
> tickethttp://code.djangoproject.com/ticket/4928please take a look when you
> can. It's got a patch also.
Reviewed.
--~--~-~--~~~---~--~~
You received this mess
On 7/29/07, Mario Gonzalez <[EMAIL PROTECTED]> wrote:
> Hello! one week ago I opened this ticket
> http://code.djangoproject.com/ticket/4928 please take a look when you
> can. It's got a patch also.
Hey, Mario --
Thanks for the ticket and patch; we'll get to it as soon as we can.
However, you s
Hello! one week ago I opened this ticket
http://code.djangoproject.com/ticket/4928 please take a look when you
can. It's got a patch also.
Regards!
--
http://www.advogato.org/person/mgonzalez/
--~--~-~--~~~---~--~~
You received this message because you are subs
Interesting that this is being brought up because I was thinking about
this very thing this morning. There appears to be lots of questions
about the tutorial on the IRC channel and I can remember when I went
through it again recently with someone there were a couple places
where we felt like thin
On Jul 29, 10:19 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Reverse URL construction (especially w.r.t things like HTTP
> redirects) is the big missing part.
We obviously need some way to get the SCRIPT_NAME from request to the
reverse resolver. Can we rely on SCRIPT_NAME remaining a con
On Jul 30, 4:38 am, "Rob Hudson" <[EMAIL PROTECTED]> wrote:
> What would the 5 or 6 questions be?
>
> -Rob
Hmm... off the top of my head -
1) Why did you choose Django?
2) What were the other alternatives?
3) What benefits did you get from Django?
4) What problems did you run into? is there
On 7/29/07, Simon G. <[EMAIL PROTECTED]> wrote:
> 4) Politely ask some of the big Django sites if they could answer 5 or
> 6 questions (e.g. pownce, tabblo, etc)
>
> If you get a few "big" names in there, then others should follow.
What would the 5 or 6 questions be?
-Rob
--~--~-~--~---
On 7/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > 1) Set up a page on the wiki with instructions and suggested outline
> > of a success story.
> > 2) Post a "Call for Success Stories" somehow, maybe via the weekly updates.
> > 3) Keep an eye on the page and linked pages.
>
> If you're
Writing a one-size-fits-all tutorial is hard.
Do you target an expert Python programmer with no Django experience?
A Java web developer with lots of experience but little knowledge of
Python?
A complete beginner to Python and web development?
I tried writing a tutorial -- www.instantdjango.com -
Cool - I'll leave that up to you then! I had a quick play around with
ReST generation to see if there was an easy way to catch errors, but
didn't spot anything, and I don't have the time ATM to dig into it in
detail (I have a Ph.D to write in the next 10 months...), but if I get
more free time th
Great idea!
> 1) Set up a page on the wiki with instructions and suggested outline
> of a success story.
> 2) Post a "Call for Success Stories" somehow, maybe via the weekly updates.
> 3) Keep an eye on the page and linked pages.
4) Politely ask some of the big Django sites if they could answer
On Jul 29, 10:30 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sat, 2007-07-28 at 23:20 +, Graham Dumpleton wrote:
>
> [...]
>
> > FWIW, I know I said that SCRIPT_NAME can't be calculated in
> > mod_python. Well, that isn't strictly true.
>
> > If you are using mod_python 3.3.1 and ha
14 matches
Mail list logo