Repository navigation
An ortographical typo in Zen of Python text #47614
Description
| BPO | 3364 |
|---|---|
| Nosy | @tim-one, @birkenfeld, @benjaminp |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = 'https://github.com/birkenfeld'
closed_at = <Date 2008-07-15.15:30:36.108>
created_at = <Date 2008-07-15.15:23:57.596>
labels = ['invalid', 'docs']
title = 'An ortographical typo in Zen of Python text'
updated_at = <Date 2008-07-17.15:15:24.175>
user = 'https://bugs.python.org/cheDu'bugs.python.org fields:
activity = <Date 2008-07-17.15:15:24.175>
actor = 'goodger'
assignee = 'georg.brandl'
closed = True
closed_date = <Date 2008-07-15.15:30:36.108>
closer = 'benjamin.peterson'
components = ['Documentation']
creation = <Date 2008-07-15.15:23:57.596>
creator = 'cheDu'
dependencies = []
files = []
hgrepos = []
issue_num = 3364
keywords = []
message_count = 4.0
messages = ['69688', '69689', '69712', '69881']
nosy_count = 4.0
nosy_names = ['tim.peters', 'georg.brandl', 'benjamin.peterson', 'cheDu']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue3364'
versions = ['Python 3.0', 'Python 3.1']
Activity
cheDu commentedon Jul 15, 2008
I hope I chose the correct component type for this issue report. Anyway,
if you do import this in the Python 3.x interactive interpreter, you
get the Zen of Python by Tim Peters. This text has a line which has an
ortographical typo in it. Please look at this line of text from the Zen
of Python:
There should be one-- and preferably only one --obvious way to do it.
Now this line has the typo I am talking about, and the typo is the lack
of a space before the first dash (actually before the double-hyphen) and
the space after the second dash (or double-hyphen).
Please note that the dash punctuation mark is by ortographical rules
separated from the words, so there are two spaces separating a dash from
the surrounding words. By writing the dashes in the way that are in the
above sentence from the Zen of Python, we don't achieve any effect as
sometimes ortographical rules can be broken to create some special
effect in the sentence (like in a line that uses the asteriskes to
emphasize the word 'right' with writing it as *right*), but here in the
above line it is clearly a normal sentence, not needing any special
effect, which is also incorrect from this point of view. So please fix
the above line like this:
There should be one -- and preferably only one -- obvious way to do it.
Consider the fact that the last sentence is written correctly and that
the dash in it is separated from the surrounding words as the
ortographic rules demand. So having one line of text with an incorrectly
used dash and some other line with the correctly used dash, makes the
whole text either inconsistent or just bad. Okay, it isn't *really* bad
but it's incorrect and it needs a little fix. And it's not too much
trouble to add two missing spaces in that line of text.
I think that ortography is our friend in the Python world. ;)
benjaminp commentedon Jul 15, 2008
I'm sorry, but syntax is part of poetry, too. Please stop misusing the
tracker.
tim-one commentedon Jul 15, 2008
I'm afraid you missed the joke ;-) While you believe spaces are
required on both sides of an em dash, there is no consensus on this
point. For example, most (but not all) American authorities say /no/
spaces should be used. That's the joke. In writing a line about "only
one way to do it", I used a device (em dash) for which at least two ways
to do it (with spaces, without spaces) are commonly used, neither of
which is obvious -- and deliberately picked a third way just to rub it in.
This will never change ;-)
cheDu commentedon Jul 17, 2008
You're a strange man, Mr. Peters, a strange man...
On Tue, Jul 15, 2008 at 9:35 PM, Tim Peters <report@bugs.python.org> wrote: