http://docs.python.org/py3k/howto/webservers.html

The path to the interpreter in the shebang (#!/usr/bin/env python) must be currect.


Sorry man there are a great many distractions here.

In same file, "intermangled with Python” and it has a “Publisher” which destignates"

intermingled?
designates?

Thanks, Dave.

"Another problem ist the basic concept"

                 is

much easier as is is specially designed

more easily and is especially designed

Some more typos:
"The benefit from this approach is that WSGI applications can be deployed much easier as is is specially designed to host WSGI applications"
s/is is/it is/

"Pylons is much like TurboGears with ab even"
s/ab/an/

Once you finish reading it I'll fix them all at once.

There is a number of middlewares

      are

you can rely an already existing

       rely on an

There is an incredible number of frameworks
s/is/are/

The majority of users is best 
s/is/are/

o work together as good as possible.
s/good/well/

jects can be saven in a st
s/saven/saved/

Thank you.  I'm through for now.

David, can you provide these changes as a unified diff against the subversion trunk?

I apologize for the noise.
Yes, I'll read the article carefully and provide changes as a unified
diff against the subversion trunk.

On Wed, 2010-03-24 at 08:20 +0000, Martin v. Löwis wrote:
> Martin v. Löwis <martin@v.loewis.de> added the comment:
> 
> David, can you provide these changes as a unified diff against the subversion trunk?
> 
> ----------
> nosy: +loewis
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue8218>
> _______________________________________

See also #8234 that has a patch with some rephrasing too.

Here is a patch that fixes the typos found by David and Yuv and rephrases a couple of parts.

s/framewors/frameworks/g

The rest of the patch seems good to me. Note that “the majority of users is” is as correct as “the majority of users are”, choosing one is a matter of preference.

'is' may be technically correct, however it will sound wrong to a native speaker's ear, at least in America.

It seems that a lot of non-native speakers (of English) are participating in this thread. By nature, this is something that native speakers should resolve. Unless I'm mistaken (and Ezio actually *does* speak English as a first language), I propose that one of the native speakers provide a patch (perhaps based on Ezio's patch), and that all non-native speakers abstain from commenting on what they believe is English grammar.

I went through and made a lot of grammar corrections and rewording throughout the file. See attached patch.

I have no idea if this doc is technically correct. I only made grammar changes since I'm not a big web developer, but it could probably use a look from someone who is pretty knowledgeable on the topic.

I noticed that “a user” is “he” in the current text; gender-neutral 
language may be more in conformity with the recent diversity statement.

Regards

My first patch removed a lot of the he/him/his wording, but now that you mentioned it found another one. Updated the patch.

Another patch. This contains all the patches from Brian Curtin's issue8218_v3.diff patch along with more edits, including
an -> in
teh -> the
wordspushedtogether spaced out
unnecessary _a_ words _is_ taken out

There's also an invalid link to an image just after the title "The low-level view":
-.. .. image:: http.png
+.. image:: http.png

The image is not there though, and in r66294 only the document has been added.

This is a reST comment.

If the image is missing, then the whole line can be removed.

Is there a main author for this fileN? If so, they can say whether they left the link as a reminder to put the image back later, or if they were just afraid of real version control <0.4 wink>

The author is Marek Kubica, but he doesn't seem to be registered to this tracker.

I do know something about web development, so I did a more extensive edit.  I'm not saying I've brought it completely up to date or fixed any inaccuracies, but I did change the tone here and there, tightened up a bunch of the language, clarified a few things, and updated a few statements.

Fixed in r79781 (trunk), r79782 (release26-maint), r79783 (py3k) and r79784 (release31-maint).
Thanks to all!