[EMAIL PROTECTED] wrote:
I'm not a native speaker, but...
> @@ -114,7 +114,7 @@
> programs, or to test functions during bottom-up program development.
> It is also a handy desk calculator.
>
> -Python allows writing very compact and readable programs. Programs
> +Python enables programs to written compactly and readably. Programs
> written in Python are typically much shorter than equivalent C or
> \Cpp{} programs, for several reasons:
> \begin{itemize}
...shouldn't it be "programs to be written compactly"?
> @@ -1753,8 +1753,8 @@
>
> \begin{methoddesc}[list]{pop}{\optional{i}}
> Remove the item at the given position in the list, and return it. If
> -no index is specified, \code{a.pop()} returns the last item in the
> -list. The item is also removed from the list. (The square brackets
> +no index is specified, \code{a.pop()} removes and returns the last item
> +in the list. The item is also removed from the list. (The square brackets
> around the \var{i} in the method signature denote that the parameter
> is optional, not that you should type square brackets at that
> position. You will see this notation frequently in the
Thats twice the same the same (removal from list).
> @@ -1985,7 +1987,9 @@
> \section{The \keyword{del} statement \label{del}}
>
> There is a way to remove an item from a list given its index instead
> -of its value: the \keyword{del} statement. This can also be used to
> +of its value: the \keyword{del} statement. Unlike the \method{pop()})
> +method which returns a value, the \keyword{del} keyword is a statement
> +and can also be used to
> remove slices from a list (which we did earlier by assignment of an
> empty list to the slice). For example:
The del keyword is a statement?
> @@ -2133,8 +2137,8 @@
> keys. Tuples can be used as keys if they contain only strings,
> numbers, or tuples; if a tuple contains any mutable object either
> directly or indirectly, it cannot be used as a key. You can't use
> -lists as keys, since lists can be modified in place using their
> -\method{append()} and \method{extend()} methods, as well as slice and
> +lists as keys, since lists can be modified in place using methods like
> +\method{append()} and \method{extend()} or modified with slice and
> indexed assignments.
Is the second "modified" necessary?
> @@ -5595,8 +5603,8 @@
> to round it again can't make it better: it was already as good as it
> gets.
>
> -Another consequence is that since 0.1 is not exactly 1/10, adding 0.1
> -to itself 10 times may not yield exactly 1.0, either:
> +Another consequence is that since 0.1 is not exactly 1/10,
> +summing ten values of 0.1 may not yield exactly 1.0, either:
>
> \begin{verbatim}
> >>> sum = 0.0
Is it clear from context that the "0.1 is not exactly 1/10" refers to
floating point only?
> @@ -5637,7 +5645,7 @@
> you can perform an exact analysis of cases like this yourself. Basic
> familiarity with binary floating-point representation is assumed.
>
> -\dfn{Representation error} refers to that some (most, actually)
> +\dfn{Representation error} refers to fact that some (most, actually)
> decimal fractions cannot be represented exactly as binary (base 2)
> fractions. This is the chief reason why Python (or Perl, C, \Cpp,
> Java, Fortran, and many others) often won't display the exact decimal
"...refers to the fact..."?
Reinhold
--
Mail address is perfectly valid!
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
