[issue215658] Minor spelling mistakes in tutorial of beta2 documentation

[admin]

Change by admin :


___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue215658] Minor spelling mistakes in tutorial of beta2 documentation

[admin]

Change by admin :


--
github: None -> 33235

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Closing this since the related PRs are merged.

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Thanks much @rhettinger and the team for all the work on documentation. This is 
my first patch and I am pretty amazed at the smooth experience for a beginner 
like me with GitHub and helpful bots. I hope to contribute more.

Just wanted to leave a note that this was inspired by the Rust book's work 
where they have a CI running with aspell to make sure that there are no 
spelling mistakes in the book. It would require a personal dictionary where all 
the valid words have to be added. I think given the rate of documentation 
changes that go into the repository having a personal dictionary will result in 
merge conflicts and not a feasible option but I just want to put this idea 
here. The initial work requires me to a manual scan of 10k words and hence I 
might have missed some words or assumed some spellings as correct. I think this 
can be used for code comments as well but would require even more attention 
since the dictionary file will be large.

Reference : 
https://github.com/rust-lang/book/blob/a5c9f1f9fbcda0a6e16ea80e64452b33006f4127/ci/spellcheck.sh#L56

Command to generate a personal file : 

cd Docs && find . -iname '*rst' | xargs -I{} sh -c "aspell --master=en_US 
--extra-dicts=en_GB --ignore 3 list < {}" | sort | uniq > typos.txt

typos.txt : https://gist.github.com/tirkarthi/d49ac3fdce93c1e3ab4b85b5e1c82b49

Thanks again :)

--

___
Python tracker 
<https://bugs.python.org/issue33859>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Thanks for finding these mistakes :-)

--
nosy: +rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset c5ff553ae717c33f86d4fa984ee92de71c467f2a by Serhiy Storchaka 
(Xtreak) in branch '3.6':
[3.6] bpo-33859: Fix spelling mistakes in docs. (GH-7691). (GH-7750)
https://github.com/python/cpython/commit/c5ff553ae717c33f86d4fa984ee92de71c467f2a


--

___
Python tracker 
<https://bugs.python.org/issue33859>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
pull_requests: +7358

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[miss-islington]

miss-islington  added the comment:


New changeset 416e488415cacec98778da11da401c1b94d92c10 by Miss Islington (bot) 
in branch '3.7':
bpo-33859: Fix spelling mistakes in docs. (GH-7691)
https://github.com/python/cpython/commit/416e488415cacec98778da11da401c1b94d92c10


--
nosy: +miss-islington

___
Python tracker 
<https://bugs.python.org/issue33859>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[miss-islington]

Change by miss-islington :


--
pull_requests: +7356

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset c151f7846d6d900c22edaaa77f5f7771b529099e by Serhiy Storchaka 
(Xtreak) in branch 'master':
bpo-33859: Fix spelling mistakes in docs. (GH-7691)
https://github.com/python/cpython/commit/c151f7846d6d900c22edaaa77f5f7771b529099e


--
nosy: +serhiy.storchaka

___
Python tracker 
<https://bugs.python.org/issue33859>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
keywords: +patch
pull_requests: +7304
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33859] Spelling mistakes found using aspell

[Karthikeyan Singaravelan]

New submission from Karthikeyan Singaravelan :

I have found some typos in docs folder using aspell. I have fixed them. The 
changes are as below : 

Doc/library/codecs.rst - cypher - cipher
Doc/library/email.rst - Protcol - Protocol
Doc/library/importlib.rst - abstact - abstract
Doc/library/xmlrpc.client.rst - unmarsalling - unmarshalling
Doc/license.rst - aheared to - adhered to
Doc/using/cmdline.rst - descibed - described
Doc/whatsnew/3.3.rst - accumlated - accumulated
Doc/whatsnew/3.6.rst - Lollilop - Lollipop
Doc/whatsnew/3.7.rst - direcory - directory

Find typos - 

find . -iname '*rst' | xargs -I{} sh -c "aspell --master=en_US 
--extra-dicts=en_GB --ignore 3 list < {}" | sort | uniq > typos.txt

Ignore case

tr '[:upper:]' '[:lower:]' < typos.txt | sort | uniq | less

This requires manually looking at output of less and then making changes.

--
assignee: docs@python
components: Documentation
messages: 319510
nosy: docs@python, xtreak
priority: normal
severity: normal
status: open
title: Spelling mistakes found using aspell
type: enhancement
versions: Python 3.8

___
Python tracker 
<https://bugs.python.org/issue33859>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Roundup Robot]

Roundup Robot added the comment:

New changeset d234dd21374a by Ezio Melotti in branch '2.7':
#18705: fix a number of typos.  Patch by Févry Thibault.
http://hg.python.org/cpython/rev/d234dd21374a

New changeset e07f104133d5 by Ezio Melotti in branch '3.3':
#18705: fix a number of typos.  Patch by Févry Thibault.
http://hg.python.org/cpython/rev/e07f104133d5

New changeset a9ee869cae40 by Ezio Melotti in branch 'default':
#18705: merge with 3.3.
http://hg.python.org/cpython/rev/a9ee869cae40

--
nosy: +python-dev

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Ezio Melotti]

Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

--
assignee: docs@python - ezio.melotti
resolution:  - fixed
stage: patch review - committed/rejected
status: open - closed
versions: +Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files

[Roundup Robot]

Roundup Robot added the comment:

New changeset 5295ed192ffd by Ezio Melotti in branch '2.7':
#18741: fix more typos.  Patch by Févry Thibault.
http://hg.python.org/cpython/rev/5295ed192ffd

New changeset 9e4685d703d4 by Ezio Melotti in branch '3.3':
#18741: fix more typos.  Patch by Févry Thibault.
http://hg.python.org/cpython/rev/9e4685d703d4

New changeset b3236989f869 by Ezio Melotti in branch 'default':
#18741: merge with 3.3.
http://hg.python.org/cpython/rev/b3236989f869

--
nosy: +python-dev

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18741
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files

[Ezio Melotti]

Ezio Melotti added the comment:

Fixed, thanks for the patch!

--
assignee: docs@python - ezio.melotti
resolution:  - fixed
stage: patch review - committed/rejected
status: open - closed
versions: +Python 2.7, Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18741
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Ezio Melotti]

Ezio Melotti added the comment:

Févry, do you want to make an updated patch that includes also everytime as 
suggested by Terry?
I think some of the typos of the current patch have also been fixed by the 
other patches you submitted.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Févry Thibault]

Févry Thibault added the comment:

Updated the patch.

--
Added file: http://bugs.python.org/file31337/typos.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Roundup Robot]

Roundup Robot added the comment:

New changeset c75b8d5fa016 by Ezio Melotti in branch '2.7':
#18466: fix more typos.  Patch by Févry Thibault.
http://hg.python.org/cpython/rev/c75b8d5fa016

New changeset 61227b4c169f by Ezio Melotti in branch '3.3':
#18466: fix more typos.  Patch by Févry Thibault.
http://hg.python.org/cpython/rev/61227b4c169f

New changeset 4cc308acd26d by Ezio Melotti in branch 'default':
#18466: merge with 3.3.
http://hg.python.org/cpython/rev/4cc308acd26d

--
nosy: +python-dev

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Ezio Melotti]

Ezio Melotti added the comment:

Fixed, thanks for the patch!

--
assignee:  - ezio.melotti
resolution:  - fixed
stage: patch review - committed/rejected
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files

[Ezio Melotti]

Changes by Ezio Melotti ezio.melo...@gmail.com:


--
nosy: +ezio.melotti
stage:  - patch review

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18741
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Ezio Melotti]

Ezio Melotti added the comment:

See also #18741.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files

[Antoine Pitrou]

Changes by Antoine Pitrou pit...@free.fr:


--
nosy: +serhiy.storchaka

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18741
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Antoine Pitrou]

Changes by Antoine Pitrou pit...@free.fr:


--
nosy: +serhiy.storchaka

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

I'm not spelling expert Antoine. :-)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files

[Févry Thibault]

New submission from Févry Thibault:

Using the same tool described in issue 18705, I fixed more typos.

--
assignee: docs@python
components: Documentation
files: another_typo_patch.diff
keywords: patch
messages: 195216
nosy: docs@python, iwontbecreative
priority: normal
severity: normal
status: open
title: Fix typos/spelling mistakes in Lib/*/*/.py files
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31294/another_typo_patch.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18741
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix arround 100 typos/spelling mistakes

[Mark Dickinson]

Mark Dickinson added the comment:

Thanks for the patch.

I don't think there's a strict policy about using American spellings in the 
source;  I think spellings like 'behaviour' and 'grey' should be left alone.

--
nosy: +mark.dickinson

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix arround 100 typos/spelling mistakes

[Févry Thibault]

Févry Thibault added the comment:

 I don't think there's a strict policy about using American spellings in the 
 source;  I think spellings like 'behaviour' and 'grey' should be left alone.

I didn't really know whether to change them or not and did not find an answer 
in the devguide (Might be worth documenting it ?) so I decided to change it :/.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix arround 100 typos/spelling mistakes

[Févry Thibault]

Févry Thibault added the comment:

Updated the patch to no longer change BE to AE and fixed two mistakes in my 
correction.

--
Added file: http://bugs.python.org/file31231/spelling_Lib.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Févry Thibault]

Changes by Févry Thibault thibaultfe...@gmail.com:


--
title: Fix arround 100 typos/spelling mistakes - Fix typos/spelling mistakes 
in Lib/*.py files

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix typos/spelling mistakes in Lib/*.py files

[Mark Dickinson]

Mark Dickinson added the comment:

Thanks for the update.  All the changes in the updated patch look good to me.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Ezio Melotti]

Changes by Ezio Melotti ezio.melo...@gmail.com:


--
nosy: +ezio.melotti
stage:  - patch review

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix arround 100 typos/spelling mistakes

[Févry Thibault]

New submission from Févry Thibault:

In issue 18466 I had said I was planning to write a tool that checks python 
source code to see if they are spelling mistakes in comments/strings. As it was 
said there, the big issue was the fact that python has so many non-english 
words and that docstrings often had variable names in them, so I had to work 
arround the issue and add a personal word list.

I only applied the tool to Lib/*.py yet, as it takes some time to check 
false-positives and I didn't want to end with patches too big to be reviewed.

--
assignee: docs@python
components: Documentation
files: spelling_Lib.diff
keywords: patch
messages: 194850
nosy: docs@python, iwontbecreative
priority: normal
severity: normal
status: open
title: Fix arround 100 typos/spelling mistakes
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31223/spelling_Lib.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix arround 100 typos/spelling mistakes

[Févry Thibault]

Févry Thibault added the comment:

Note that I am not a very good python programmer so the attached script may 
look ugly to you, but it works.

--
versions: +Python 3.3
Added file: http://bugs.python.org/file31224/spell.py

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18705] Fix arround 100 typos/spelling mistakes

[Févry Thibault]

Févry Thibault added the comment:

And here is a python_words.txt so you have to press enter less times :)

--
Added file: http://bugs.python.org/file31225/python_words.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18705
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Févry Thibault]

Févry Thibault added the comment:

See issue 18705 for a basic script.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Ramchandra Apte]

Ramchandra Apte added the comment:

Hmm... once I actually created a short (50 lines) script which spell-checked 
the comments. Problem is that many technical words (GCC, for example) were 
marked incorrect by the spell-checker (Enchant), resulting in about 1000+ 
incorrectly spelled words.

--
nosy: +Ramchandra Apte

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Terry J. Reedy]

Terry J. Reedy added the comment:

'everytime' is not an English word and should be corrected; hardcoded should be 
hard-coded. Could you at least describe your script. My fantasy is being able 
to check text parts of files with the help of a program such as LibreOffice.

--
nosy: +terry.reedy
versions: +Python 2.7, Python 3.3, Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Févry Thibault]

Févry Thibault added the comment:

Terry Reedy : The scripts needs to be improved and I won't be able to access my 
computer until mid August so I don't think I will be able to do anything until 
then. But the script should be able to do that if I work on it a bit. I would 
use python enchant rather than libre-office for spell-checking and would need a 
text file about words specifics to python that should not be reported. I'll 
work on it once I get back (8th August) and when it is a bit more polished I'll 
update this post.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue18466] Spelling mistakes in various code comments.

[Févry Thibault]

New submission from Févry Thibault:

The attached patch fixes spelling mistakes found on various comments, mainly in 
/Lib/. I choose not to correct things like 'everytime' since the main goal was 
to improve readability and not turn useful technical comments into English 
litterature. I hope this is fine.


[These were found using a script, if anyone wants I could post it somewhere 
after I polish it].

--
files: spelling.patch
keywords: patch
messages: 193120
nosy: iwontbecreative
priority: normal
severity: normal
status: open
title: Spelling mistakes in various code comments.
type: enhancement
Added file: http://bugs.python.org/file30930/spelling.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18466
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Re: Spelling mistakes!

[Antoon Pardon]

Op 2006-01-12, [EMAIL PROTECTED] schreef [EMAIL PROTECTED]:

 Antoon But now we are back to my first doubt. Sure unit test will be
 Antoon helpfull in finding out there is a bug. I doubt they are that
 Antoon helpfull in tracking the bug (at least this kind).

 This thread seems to be going in circles.  Maybe it's time to simply drop it
 and move onto other things.  The clear evidence from people who admit to
 having practical experience using unit tests (or pylint or pychecker) is
 that catching misspellings is an extremely shallow bug to find and fix if
 you use the tools at your disposal.

I have no problem with the statement: 

  Spelling errors are easy to fix if you use the tools at your disposal.

But that statement doesn't limit the tools to unit testing.

-- 
Antoon Pardon
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Antoon Pardon]

Op 2006-01-11, Hans Nowak schreef [EMAIL PROTECTED]:
 Antoon Pardon wrote:

 Op 2006-01-10, Terry Hancock schreef [EMAIL PROTECTED]:
 
In unit testing, you write the code, then write code to test
the code, which must correctly identify the methods in the
code. So you have to type 'everything' twice.
 
 But you don't type attribute names twice in unit tests,
 because attributes are in general implementation details
 that are of no concern to the tester. So unit tests can
 not introduce the redundancy to find out a missed spelled
 attribute in some methods.

 I wouldn't call attributes implementation details, at least not in 
 Python.  And while it is true that unit tests might not find the 
 misspelling *directly* (i.e. you rarely test if you have misspelled 
 something), your tests should definitely show unexpected behavior and 
 results, if that attribute is of any importance.  Otherwise there's a 
 loophole in your tests. :-)

But now we are back to my first doubt. Sure unit test will be
helpfull in finding out there is a bug. I doubt they are that
helpfull in tracking the bug (at least this kind).

-- 
Antoon Pardon
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

Antoon But now we are back to my first doubt. Sure unit test will be
Antoon helpfull in finding out there is a bug. I doubt they are that
Antoon helpfull in tracking the bug (at least this kind).

This thread seems to be going in circles.  Maybe it's time to simply drop it
and move onto other things.  The clear evidence from people who admit to
having practical experience using unit tests (or pylint or pychecker) is
that catching misspellings is an extremely shallow bug to find and fix if
you use the tools at your disposal.

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Terry Hancock]

On Wed, 11 Jan 2006 06:57:06 +
Steve Holden [EMAIL PROTECTED] wrote:
 Terry Hancock wrote:
 [...]
  
  The ideal of don't repeat yourself seems to get
  nudged out by repeat yourself exactly once when it's
  really important to get it right. ;-)
  
 I suppose most readers aren't old enough to remember the
 punch card  days, when you would hand your work in on
 coding sheets to the punch  room and it would be punched
 onto cards using huge machines (anyone  remember the 026
 and 029 punches?).

Punch cards were still in use for students at The University
of Texas as late as 1986, so I'm old enough to remember.
(Yes, the CS department had terminals and editors, but some
classes still required cards -- I guess it was supposed to
build character ;-)).  However, I wasn't a CS student, so
I never had to use one. ;-)  We had VT-220 terminals in the
Astronomy computer lab, which is where I first learned to
use Unix, Fortran, and other fun things. :-)

-- 
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Antoon Pardon]

Op 2006-01-10, Terry Hancock schreef [EMAIL PROTECTED]:
 On 9 Jan 2006 11:21:10 GMT
 Antoon Pardon [EMAIL PROTECTED] wrote:
 Op 2006-01-06, Terry Hancock schreef
 [EMAIL PROTECTED]:
  On 6 Jan 2006 07:30:41 -0800
  KraftDiner [EMAIL PROTECTED] wrote:
  in an init method I declare a variable 
 self.someLongName  
  later in a different method of the class I use
  self.sumLongName
  Now I really meant self.someLongName.
  In fact I don't want a variable called sumLongName.
  Frankly how are you ever to know if this type of error
 is  occuring?
 
  Both unit tests and interfaces are useful for
  catching simple errors like this one.  There is a
  'unittest' module in the Python standard library, and
  'interface' modules are available from the Zope 3
  project and PyProtocols, both are good.
 
 I don't think unit tests are that helpfull in this case.
 Unit tests help you in finding out there is a bug, they
 don't help that much in tracking down a bug.
 
 I for some reason a person is reading over the difference
 between sumLongName and someLongName and doesn't notice
 the different spelling in his source a unit test won't
 be of much help.

 Well, if you are doing fairly frequent unit tests, then you
 will have written a unit test to test the someLongName
 method, and if you manage to type sumLongName in BOTH the
 code and the unit test, then there must be some Freudian
 reason you really did want to use sumLongName. ;-)

Who says someLongName is a method?

 It's a bit like the standard practice of making you type a
 password twice. In fact, most of the common bug avoidance
 methods in programming all come down to this -- you have to
 type the same thing twice in two different places to get
 the result.

 C and C++ make you do declarations -- so you have
 to mention the name before you can use it.  You have to type
 the variable names twice.

But that is not an accepted idea here in c.p.l. I also find
it strange that redundancy via type declarations is so hard
resisted here and is then defended with the argument it
isn't needed is you test sufficiently (with unit tests)
which is also a kind of redundancy.

 Interfaces define the publically viewable parts of a
 class, then you have to actually create them in a separate
 class definition.  You have to type the methods twice.

 In unit testing, you write the code, then write code to test
 the code, which must correctly identify the methods in the
 code. So you have to type 'everything' twice.

But you don't type attribute names twice in unit tests,
because attributes are in general implementation details
that are of no concern to the tester. So unit tests can
not introduce the redundancy to find out a missed spelled
attribute in some methods.

 The ideal of don't repeat yourself seems to get
 nudged out by repeat yourself exactly once when it's
 really important to get it right. ;-)

 It's really just a fancy way to force you to proof-read your
 own work carefully enough (which is tricky because you 
 tend to ignore stuff that's too repetitious).

Yes and you also tend to read over your own spelling errors.

-- 
Antoon Pardon
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Mike Meyer]

Dennis Lee Bieber [EMAIL PROTECTED] writes:
 On Wed, 11 Jan 2006 06:57:06 +, Steve Holden [EMAIL PROTECTED]
 declaimed the following in comp.lang.python:
 I suppose most readers aren't old enough to remember the punch card 
 days, when you would hand your work in on coding sheets to the punch 
 room and it would be punched onto cards using huge machines (anyone 
 remember the 026 and 029 punches?).
   FORTRAN and COBOL on 029s -- and had to submit the school ID card to
 check-out a drum; coding a drum card was actually taught in the COBOL
 class.

Pretty much everything on the 029. Like you, I had to punch things
myself. And had a drum card with one track for FORTRAN and a second
for ALGOL.

Of course, I was employed to work with them. At one point, I actually
helped someone do data processing with the card sorter.

 mike
-- 
Mike Meyer [EMAIL PROTECTED]  http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

Steve I suppose most readers aren't old enough to remember the punch
Steve card days, when you would hand your work in on coding sheets to
Steve the punch room and it would be punched onto cards using huge
Steve machines (anyone remember the 026 and 029 punches?).

I do remember the IBM Model 29 punch card machines, though as a student
nobody was there to punch my cards or verify them for me...  :-(

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Hans Nowak]

Antoon Pardon wrote:

 Op 2006-01-10, Terry Hancock schreef [EMAIL PROTECTED]:
 
In unit testing, you write the code, then write code to test
the code, which must correctly identify the methods in the
code. So you have to type 'everything' twice.
 
 But you don't type attribute names twice in unit tests,
 because attributes are in general implementation details
 that are of no concern to the tester. So unit tests can
 not introduce the redundancy to find out a missed spelled
 attribute in some methods.

I wouldn't call attributes implementation details, at least not in 
Python.  And while it is true that unit tests might not find the 
misspelling *directly* (i.e. you rarely test if you have misspelled 
something), your tests should definitely show unexpected behavior and 
results, if that attribute is of any importance.  Otherwise there's a 
loophole in your tests. :-)

-- 
Hans Nowak
http://zephyrfalcon.org/
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Antoon Pardon]

Op 2006-01-09, Xavier Morel schreef [EMAIL PROTECTED]:
 Antoon Pardon wrote:
 I don't think unit tests are that helpful in this case.
 Unit tests help you in finding out there is a bug, they
 don't help that much in tracking down a bug.
 
 I for some reason a person is reading over the difference
 between sumLongName and someLongName and doesn't notice
 the different spelling in his source a unit test won't
 be of much help.
 
 Since
 1- The unit test will obviously fail in this case, telling you in which 
 code unit the issue is

Not in general. Several unit tests can fail. And if you have a variable
spelled differently, the code unit that fails is not dependant on which
occurence was spelled correct and which was spelled wrong. So it is very
well possible that the code unit with the issue is the one in which the
variable is spelled correctly.

 2- Unit Test favor extremely modular coding with very short increments 
 (as a somewhat extreme example, Robert Martin gets nervous if his test 
 suites don't validate the code every 5 minutes, you usually don't write 
 200 lines and their unit tests in 5 minutes)

I have a unit test that takes at leas 2 minutes. If I would validate
each five minutes I wouldn't get any work done.

 We can deduce that unit testing will detect the typo extremely early and 
 that the field of research will span about 5 to 10 lines, making the 
 tracking quite easy to perform.

Not necessary. You may have started with misspelling the variable and
spelled it correctly in your last edit session. Doing your research
in the 5 to 10 lines last edited will then reveal nothing.

-- 
Antoon Pardon
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Terry Hancock]

On 9 Jan 2006 11:21:10 GMT
Antoon Pardon [EMAIL PROTECTED] wrote:
 Op 2006-01-06, Terry Hancock schreef
 [EMAIL PROTECTED]:
  On 6 Jan 2006 07:30:41 -0800
  KraftDiner [EMAIL PROTECTED] wrote:
  in an init method I declare a variable 
 self.someLongName  
  later in a different method of the class I use
  self.sumLongName
  Now I really meant self.someLongName.
  In fact I don't want a variable called sumLongName.
  Frankly how are you ever to know if this type of error
 is  occuring?
 
  Both unit tests and interfaces are useful for
  catching simple errors like this one.  There is a
  'unittest' module in the Python standard library, and
  'interface' modules are available from the Zope 3
  project and PyProtocols, both are good.
 
 I don't think unit tests are that helpfull in this case.
 Unit tests help you in finding out there is a bug, they
 don't help that much in tracking down a bug.
 
 I for some reason a person is reading over the difference
 between sumLongName and someLongName and doesn't notice
 the different spelling in his source a unit test won't
 be of much help.

Well, if you are doing fairly frequent unit tests, then you
will have written a unit test to test the someLongName
method, and if you manage to type sumLongName in BOTH the
code and the unit test, then there must be some Freudian
reason you really did want to use sumLongName. ;-)

It's a bit like the standard practice of making you type a
password twice. In fact, most of the common bug avoidance
methods in programming all come down to this -- you have to
type the same thing twice in two different places to get
the result.

C and C++ make you do declarations -- so you have
to mention the name before you can use it.  You have to type
the variable names twice.

Interfaces define the publically viewable parts of a
class, then you have to actually create them in a separate
class definition.  You have to type the methods twice.

In unit testing, you write the code, then write code to test
the code, which must correctly identify the methods in the
code. So you have to type 'everything' twice.

And so on.

The ideal of don't repeat yourself seems to get
nudged out by repeat yourself exactly once when it's
really important to get it right. ;-)

It's really just a fancy way to force you to proof-read your
own work carefully enough (which is tricky because you 
tend to ignore stuff that's too repetitious).

Cheers,
Terry

-- 
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Peter Hansen]

Sybren Stuvel wrote:
 Xavier Morel enlightened us with:
1- The unit test will obviously fail in this case, telling you in
which code unit the issue is
 
 Given the assumption the same mistake hasn't been made in the test as
 well.

If the spelling in the test matches the spelling in the code, then 
obviously it isn't a mistake at all!  0.5 wink

-Peter

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Steve Holden]

Terry Hancock wrote:
[...]
 
 The ideal of don't repeat yourself seems to get
 nudged out by repeat yourself exactly once when it's
 really important to get it right. ;-)
 
I suppose most readers aren't old enough to remember the punch card 
days, when you would hand your work in on coding sheets to the punch 
room and it would be punched onto cards using huge machines (anyone 
remember the 026 and 029 punches?).

Before you got the cards back they were processed twice: one operator 
would actually punch the cards, and another would re-key the same input 
on a verifier machine that alerted them to any differences between what 
was on the card and what was keyed.

 It's really just a fancy way to force you to proof-read your
 own work carefully enough (which is tricky because you 
 tend to ignore stuff that's too repetitious).
 
That's why two different operators would do the punching and the verifying.

regards
  Steve
-- 
Steve Holden   +44 150 684 7255  +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006  www.python.org/pycon/

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Sybren Stuvel]

[EMAIL PROTECTED] enlightened us with:
 Terry But not faster than use a dict server!  Why not just use (e.g.)
 Terry kdict? 

 Maybe because not everybody has it?

Lame excuse. If you don't have something but you do want to use it,
you get it. If everybody just used what they had at one point in time,
and never acquired anything new, the world certainly would look
different.

Sybren
-- 
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself? 
 Frank Zappa
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Sybren Stuvel]

Walter S. Leipold enlightened us with:
 [Gee, I hope their were no spelling misteaks inn that paragraph...]
 
 It should be where

Sybren
-- 
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself? 
 Frank Zappa
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Michele Simionato]

[EMAIL PROTECTED] wrote:
  The OP sort of seemed like he was pining
 for attribute declarations.  __slots__ is the closest thing Python has to
 them.  I don't use them myself (since I've basically avoided new-style
 classes so far).

 Skip

No, slots are a memory optimization trick and should NOT be used as
declarations.
You can find a few posts of the Martellibot on the subject. I even
wrote a recipe
to tell people who want static declarations how to implement them
without slots:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/252158

 Michele Simionato

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Michele Simionato]

I like to play devil's advocate here, so I will say that in this case
using automatic testing
will increase your probability of spelling mistakes: I do most of my
spelling mistakes 
in the test cases! 0.5 wink

Michele Simionato

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Antoon Pardon]

Op 2006-01-06, Terry Hancock schreef [EMAIL PROTECTED]:
 On 6 Jan 2006 07:30:41 -0800
 KraftDiner [EMAIL PROTECTED] wrote:
 I've spent hours trying to find a bug that was a simple
 spelling mistake.

 You're not the first. ;-)

 in an init method I declare a variable  self.someLongName
 
 later in a different method of the class I use
 self.sumLongName
 Now I really meant self.someLongName.
 In fact I don't want a variable called sumLongName.
 Frankly how are you ever to know if this type of error is
 occuring?

 Both unit tests and interfaces are useful for catching
 simple errors like this one.  There is a 'unittest' module
 in the Python standard library, and 'interface' modules are
 available from the Zope 3 project and PyProtocols, both are
 good.

I don't think unit tests are that helpfull in this case.
Unit tests help you in finding out there is a bug, they
don't help that much in tracking down a bug.

I for some reason a person is reading over the difference
between sumLongName and someLongName and doesn't notice
the different spelling in his source a unit test won't
be of much help.

-- 
Antoon Pardon
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Xavier Morel]

Antoon Pardon wrote:
 I don't think unit tests are that helpful in this case.
 Unit tests help you in finding out there is a bug, they
 don't help that much in tracking down a bug.
 
 I for some reason a person is reading over the difference
 between sumLongName and someLongName and doesn't notice
 the different spelling in his source a unit test won't
 be of much help.
 
Since
1- The unit test will obviously fail in this case, telling you in which 
code unit the issue is
2- Unit Test favor extremely modular coding with very short increments 
(as a somewhat extreme example, Robert Martin gets nervous if his test 
suites don't validate the code every 5 minutes, you usually don't write 
200 lines and their unit tests in 5 minutes)

We can deduce that unit testing will detect the typo extremely early and 
that the field of research will span about 5 to 10 lines, making the 
tracking quite easy to perform.
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

Terry But not faster than use a dict server!  Why not just use (e.g.)
Terry kdict? 

 Maybe because not everybody has it?

Sybren Lame excuse. If you don't have something but you do want to use
Sybren it, you get it.

I don't think I want it badly enough to figure out how to get it to work on
my Mac.  (I'm assuming the k prefix implies it's part of KDE.)  I'm happy
to continue googling for words I want defined.

Sybren If everybody just used what they had at one point in time, and
Sybren never acquired anything new, the world certainly would look
Sybren different.

I'm not sure what in my response suggested to you that I never install new
software on my computers.

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Sybren Stuvel]

Xavier Morel enlightened us with:
 1- The unit test will obviously fail in this case, telling you in
 which code unit the issue is

Given the assumption the same mistake hasn't been made in the test as
well.

Sybren
-- 
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself? 
 Frank Zappa
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Mike Meyer]

[EMAIL PROTECTED] writes:
 Terry But not faster than use a dict server!  Why not just use (e.g.)
 Terry kdict? 

  Maybe because not everybody has it?

 Sybren Lame excuse. If you don't have something but you do want to use
 Sybren it, you get it.

 I don't think I want it badly enough to figure out how to get it to work on
 my Mac.  (I'm assuming the k prefix implies it's part of KDE.)  I'm happy
 to continue googling for words I want defined.

On the Mac, use Butler. I *can't* say enough good things about Butler
on the Mac - it actually makes the UI bearable.

For this case, I can search any of Google, Wikipedia or Websters
online (both the dictionary and the thesarus) by typing the
appropriate hotkey, the word, and the enter key.

So not only does this make using google for spelling checking faster,
it makes it equally easy to check an online dictionary. Butler comes
preconfigured for either Webster or Dictionary.com, as well as
Wikipedia and some specialty dictionaries, and it's trivial to add a
search on any search engine that does a GET query.

   mike
-- 
Mike Meyer [EMAIL PROTECTED]  http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[bb]

[EMAIL PROTECTED] wrote:

 
 Terry But not faster than use a dict server!  Why not just use (e.g.)
 Terry kdict?
 
  Maybe because not everybody has it?
 
 Sybren Lame excuse. If you don't have something but you do want to
 use Sybren it, you get it.
 
 I don't think I want it badly enough to figure out how to get it to work
 on
 my Mac.  (I'm assuming the k prefix implies it's part of KDE.)  I'm
 happy to continue googling for words I want defined.

kdict is, as you correctly assume, part of KDE. But it's just an interface
to query a dict server. And there are command line clients for that as
well.

-- 
Listen to the wise old man:
http://nobelprize.org/literature/laureates/2005/pinter-lecture.html
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Steve Holden]

KraftDiner wrote:
 I've spent hours trying to find a bug that was a simple spelling
 mistake.
 
 in an init method I declare a variable  self.someLongName
 
 later in a different method of the class I use
 self.sumLongName
 Now I really meant self.someLongName.
 In fact I don't want a variable called sumLongName.
 Frankly how are you ever to know if this type of error is occuring?
 
pychecker
-- 
Steve Holden   +44 150 684 7255  +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006  www.python.org/pycon/

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Jorgen Grahn]

On Sat, 07 Jan 2006 08:57:24 -0500, Peter Hansen [EMAIL PROTECTED] wrote:

[British/American English]

 Hah!  Canucks r00l!  Most of those words look about equally good to us 
 most of the time.  (And it's not because of the beer!)  (But our beer 
 r00lz too.)

And so does primairy, secondairy and similar frenchifications of
English words, to some of you ... I'll think twice before agreeing to
maintain software written by people from Montréal again.

(Fortunately, that software was written in a static programming language.)

/Jorgen

-- 
  // Jorgen Grahn grahn@Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.dyndns.org  R'lyeh wgah'nagl fhtagn!
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Jorgen Grahn]

On Fri, 6 Jan 2006 23:46:42 -0600, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 I do tend to be a bit brief with my names and recognizing an identifier as
 an abbreviation don't bother me the way a misspelled word does.  Maybe I've
 been using Unix systems for too long with their brief command names like mv
 and grep.

I like to think of it as everybody else having spent too /little/ time with
Unix systems ;-)

/Jorgen

-- 
  // Jorgen Grahn grahn@Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.dyndns.org  R'lyeh wgah'nagl fhtagn!
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Sybren Stuvel]

[EMAIL PROTECTED] enlightened us with:
 I'm one of those people who, for better or worse, is a good speller.
 Words just look right or wrong to me and it bothers me when they
 look wrong.

Same here. I have to use code that has childs instead of
children... I also can't stand then vs than mixups... And what's
up with using Google to check for spelling? I have a dictionary for
that, works a lot better!

Sybren
-- 
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself? 
 Frank Zappa
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

Sybren And what's up with using Google to check for spelling? I have a
Sybren dictionary for that, works a lot better!

A couple things:

1. It's generally faster than reaching for the dictionary.

2. The hit count for a word and its misspelling gives me some measure of
   how the rest of the online English-speaking world thinks that word is
   spelled.

3. Some recent words like podcast aren't in the now ancient dictionary
   on my shelf.  Other words have gained new meanings since my
   dictionary was published.

Okay, so that's a few things... wink

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Terry Hancock]

On Sun, 8 Jan 2006 08:58:48 -0600
[EMAIL PROTECTED] wrote:
 Sybren And what's up with using Google to check for spelling? I have a
 Sybren dictionary for that, works a lot better!
 
 A couple things:
 
 1. It's generally faster than reaching for the
 dictionary.

But not faster than use a dict server!
Why not just use (e.g.) kdict? That's what I do. It's got to
be at least as accurate as Google, and much more likely to
give me the right answer.

 2. The hit count for a word and its misspelling gives
 me some measure of
how the rest of the online English-speaking world
thinks that word is spelled.

This is useful for words that don't really exist.
Or rather, that do exist, but are not documented. ;-)

 3. Some recent words like podcast aren't in the now
 ancient dictionary
on my shelf.  Other words have gained new meanings
since my dictionary was published.

Same comment -- Google is good as a backup, but I'd much
rather use a dictionary to look up words than a search
engine.  Wikipedia is another good resource for newer words,
brand names, jargon, and slang.

BTW, one of the most common programming spelling errors is
deprecate versus depreciate -- I wonder how many people
actually realize that both words exist, but have entirely
different meanings?

deprecate means to be declared unworthy or no longer to
be used by an authority and is pronounced de-pre-KATE,
while depreciate means to go down in financial value and
is pronounced de-PRE-she-ATE.

An awful lot of people seem to think that deprecate is a
misspelling of depreciate and then correct the spelling.
But then, they must have a funny idea of what it means when
a software feature is deprecated.  Maybe they think it's
like the opposite of appreciate or something? (We
don't appreciate your code anymore). ;-)

I suppose some smart alec is going to argue that it goes
down in value because an authority declared it unworthy.
Would be about par for the course. ;-)

-- 
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Robin Becker]

Chris F.A. Johnson wrote:
 On 2006-01-08, Terry Hancock wrote:
 
BTW, one of the most common programming spelling errors is
deprecate versus depreciate -- I wonder how many people
actually realize that both words exist, but have entirely
different meanings?
 
 
The words overlap in meaning. Both can mean to disparage or
belittle.
 
Some dictionaries give 'depreciate' as a definition of 'deprecate'.
 
 

Well if someone told me my investments were deprecated I'd take that 
differently to them being depreciated.
-- 
Robin Becker
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Chris F.A. Johnson]

On 2006-01-08, Terry Hancock wrote:

 BTW, one of the most common programming spelling errors is
 deprecate versus depreciate -- I wonder how many people
 actually realize that both words exist, but have entirely
 different meanings?

   The words overlap in meaning. Both can mean to disparage or
   belittle.

   Some dictionaries give 'depreciate' as a definition of 'deprecate'.


-- 
   Chris F.A. Johnson, author   |http://cfaj.freeshell.org
   Shell Scripting Recipes: |  My code in this post, if any,
   A Problem-Solution Approach  |  is released under the
   2005, Apress | GNU General Public Licence
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Chris F.A. Johnson]

On 2006-01-08, Robin Becker wrote:
 Chris F.A. Johnson wrote:
 On 2006-01-08, Terry Hancock wrote:
 
BTW, one of the most common programming spelling errors is
deprecate versus depreciate -- I wonder how many people
actually realize that both words exist, but have entirely
different meanings?
 
 
The words overlap in meaning. Both can mean to disparage or
belittle.
 
Some dictionaries give 'depreciate' as a definition of 'deprecate'.

 Well if someone told me my investments were deprecated I'd take that 
 differently to them being depreciated.

   That's why I said overlap, not that they are the same.

-- 
   Chris F.A. Johnson, author   |http://cfaj.freeshell.org
   Shell Scripting Recipes: |  My code in this post, if any,
   A Problem-Solution Approach  |  is released under the
   2005, Apress | GNU General Public Licence
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

 1. It's generally faster than reaching for the dictionary.

Terry But not faster than use a dict server!  Why not just use (e.g.)
Terry kdict? 

Maybe because not everybody has it?

% kdict
-bash: kdict: command not found

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Walter S. Leipold]

Terry Hancock ([EMAIL PROTECTED]) writes:
 BTW, one of the most common programming spelling errors is
 deprecate versus depreciate -- I wonder how many people
 actually realize that both words exist, but have entirely
 different meanings?  

That's a common spelling error, yes, but..  The number-one spelling error
among today's semi-literates is writing it's for the third-person neuter
possessive instead of its.  (These folks frequently write her's instead
of hers and who's instead of whose as well, but, strangely, hardly
ever write hi's for the masculine form.)  A native English speaker's
spelling of its is a very accurate measure of his general literacy.  

[Gee, I hope their were no spelling misteaks inn that paragraph...]

-- Walt
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Sam Pointon]

[EMAIL PROTECTED] wrote:
  In fact, googling for referer and referrer reports a similar
  number of hits, unlike most misspellings.

 Terry You know, I almost mentioned that myself. Drives me crazy.

 Me too.  I'm one of those people who, for better or worse, is a good
 speller.  Words just look right or wrong to me and it bothers me when they
 look wrong.

What's worse is the closely related problem of British/American
English, though you sort of get used to it after typing
s/colour/color/g or s/serialise/serialize/g for the thousandth time.
The words look wrong to me, but they're correct in the context.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Peter Hansen]

Sam Pointon wrote:
 What's worse is the closely related problem of British/American
 English, though you sort of get used to it after typing
 s/colour/color/g or s/serialise/serialize/g for the thousandth time.
 The words look wrong to me, but they're correct in the context.

Hah!  Canucks r00l!  Most of those words look about equally good to us 
most of the time.  (And it's not because of the beer!)  (But our beer 
r00lz too.)

-Peter Freezing-my-ass-off-in-Uxbridge Hansen

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Alan Kennedy]

[EMAIL PROTECTED]
 Aside from the other responses (unittests, pychecker/pylint), you might also
 consider using __slots__ for new-style classes:

I've been shouted at for suggesting exactly that! :-)

http://groups.google.com/group/comp.lang.python/msg/fa453d925b912917

how-come-aahz-didn't-shout-at-you-ly'yrs,

-- 
alan kennedy
--
email alan:  http://xhaus.com/contact/alan
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

 Aside from the other responses (unittests, pychecker/pylint), you
 might also consider using __slots__ for new-style classes:

Alan I've been shouted at for suggesting exactly that! :-)

Maybe Aahz didn't notice my post.  The OP sort of seemed like he was pining
for attribute declarations.  __slots__ is the closest thing Python has to
them.  I don't use them myself (since I've basically avoided new-style
classes so far).

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Aahz]

In article [EMAIL PROTECTED],
Alan Kennedy  [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]

 Aside from the other responses (unittests, pychecker/pylint), you might also
 consider using __slots__ for new-style classes:

I've been shouted at for suggesting exactly that! :-)

http://groups.google.com/group/comp.lang.python/msg/fa453d925b912917

how-come-aahz-didn't-shout-at-you-ly'yrs,

Because I've been busy.  I'd been saving Skip's post for when I had
enough time to do it justice, but your URL saves me the trouble.  ;-)
-- 
Aahz ([EMAIL PROTECTED])   * http://www.pythoncraft.com/

19. A language that doesn't affect the way you think about programming,
is not worth knowing.  --Alan Perlis
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Scott David Daniels]

Terry Hancock wrote:
 One thing I've figured out is that using the full spelling
 of a word instead of groovy programmer abbreviations makes
 it a lot easier to remember the names of things.  Of course,
 like everything, that can be taken too far, so I still use
 things like bkg_clr too.

Yeah, it's a real pain to constantly type breakage_clear every time.
:-)

--Scott David Daniels
[EMAIL PROTECTED]
-- 
http://mail.python.org/mailman/listinfo/python-list

Spelling mistakes!

[KraftDiner]

I've spent hours trying to find a bug that was a simple spelling
mistake.

in an init method I declare a variable  self.someLongName

later in a different method of the class I use
self.sumLongName
Now I really meant self.someLongName.
In fact I don't want a variable called sumLongName.
Frankly how are you ever to know if this type of error is occuring?

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Heiko Wundram]

KraftDiner wrote:
 Frankly how are you ever to know if this type of error is occuring?

By the traceback:

[EMAIL PROTECTED] ~ $ python
Python 2.4.2 (#1, Dec 22 2005, 17:27:39)
[GCC 4.0.2 (Gentoo 4.0.2-r2, pie-8.7.8)] on linux2
Type help, copyright, credits or license for more information.
 class x(object):
...   def __init__(self):
... self.somename = hello
...   def somemethod(self):
... print self.sumname
...
 a = x()
 a.somemethod()
Traceback (most recent call last):
  File stdin, line 1, in ?
  File stdin, line 5, in somemethod
AttributeError: 'x' object has no attribute 'sumname'


AttributeError describes just this. And please don't start the war on how
much better compiled languages are because they catch this kind of error at
compile time. They simply are not.

--- Heiko.
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Fuzzyman]

VBScript allows you to specify that variable names be declared. I used
to think this was good - until I realised that Python allows you to
dynamically assign attributes in namespaces using all sorts of tricks.

(Setattr, using __dict__ etc).

It's just not possible with Python. Rarely happens to me in practise
and is easy to fix.

All the best,

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[KraftDiner]

try this:

class x(object):
   def __init__(self):
  self.someName = hello
   def someMethod(self):
  self.sumName = bye

find that bug.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Xavier Morel]

KraftDiner wrote:
 I've spent hours trying to find a bug that was a simple spelling
 mistake.
 
 in an init method I declare a variable  self.someLongName
 
 later in a different method of the class I use
 self.sumLongName
 Now I really meant self.someLongName.
 In fact I don't want a variable called sumLongName.
 Frankly how are you ever to know if this type of error is occuring?
 

PyChecker and PyLint sound like the perfect remedy to this issue (I know 
one of them is able to warn you if you *create* an attribute outside of 
__init__, maybe both are but at least one of them is)

I just run them when I save my files, they don't take long and even 
though the default configuration is *extremely* annoying (especially 
PyLint's, it generates heaps of warnings) once configured to one's need, 
they're extremely valuable for both personal and team development.
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Jean-Paul Calderone]

On 6 Jan 2006 07:57:04 -0800, KraftDiner [EMAIL PROTECTED] wrote:
try this:

class x(object):
   def __init__(self):
  self.someName = hello
   def someMethod(self):
  self.sumName = bye

find that bug.


[EMAIL PROTECTED]:~$ cat  xobj.py
class x(object):
def __init__(self):
self.someName = hello
def someMethod(self):
self.sumName = bye
[EMAIL PROTECTED]:~$ cat  test_xobj.py
from twisted.trial import unittest

import xobj

class XObjTestCase(unittest.TestCase):
def testSomeName(self):
x = xobj.x()
self.assertEquals(x.someName, hello)
x.someMethod()
self.assertEquals(x.someName, bye)
[EMAIL PROTECTED]:~$ trial test_xobj.py 
Running 1 tests.
test_xobj
  XObjTestCase
testSomeName ...   [FAIL]

=
[FAIL]: test_xobj.XObjTestCase.testSomeName

  File /home/exarkun/test_xobj.py, line 10, in testSomeName
self.assertEquals(x.someName, bye)
twisted.trial.unittest.FailTest: 'hello' != 'bye'
-
Ran 1 tests in 0.278s

FAILED (failures=1)
[EMAIL PROTECTED]:~$ 

Hope this helps,

Jean-Paul
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[André]

KraftDiner wrote:
 try this:

 class x(object):
def __init__(self):
   self.someName = hello
def someMethod(self):
   self.sumName = bye

 find that bug.

Write a test for each method before writing the method.

Write the code once; read it critically (at least) twice.

If you find that too difficult, use a different programming language
(one in which you have to declare every variable) and become less
productive.

A.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Peter Hansen]

KraftDiner wrote:
 try this:
 
 class x(object):
def __init__(self):
   self.someName = hello
def someMethod(self):
   self.sumName = bye
 
 find that bug.

You forgot to include unit tests for someMethod().  Those would have 
caught the bug.

The reality is that if you aren't doing unit testing, you aren't 
catching other bugs either, bugs which aren't caught by the compile-time 
tests in other languages and which aren't caught by PyChecker or PyLint 
either.  Bugs which are probably much more common than typos like the 
above, too.

Still, if you are really bothered by these things frequently, I believe 
recipes have been posted in the past which *do* allow you to avoid many 
such problems, by declaring the acceptable attribute names somewhere and 
using one of Python's many hooks to intercept and check attribute 
setting.  Check the archives or the CookBook.

-Peter

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

 try this:
 class x(object):
def __init__(self):
   self.someName = hello
def someMethod(self):
   self.sumName = bye

 find that bug.

Aside from the other responses (unittests, pychecker/pylint), you might also
consider using __slots__ for new-style classes:

class x(object):
   __slots__ = ('someName',)
   def __init__(self):
  self.someName = hello
   def someMethod(self):
  self.sumName = bye

my_x = x()
my_x.someMethod()

When run you will get this output:

Traceback (most recent call last):
  File slot.py, line 9, in module
my_x.someMethod()
  File slot.py, line 6, in someMethod
self.sumName = bye
AttributeError: 'x' object has no attribute 'sumName'

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Terry Hancock]

On 6 Jan 2006 07:30:41 -0800
KraftDiner [EMAIL PROTECTED] wrote:
 I've spent hours trying to find a bug that was a simple
 spelling mistake.

You're not the first. ;-)

 in an init method I declare a variable  self.someLongName
 
 later in a different method of the class I use
 self.sumLongName
 Now I really meant self.someLongName.
 In fact I don't want a variable called sumLongName.
 Frankly how are you ever to know if this type of error is
 occuring?

Both unit tests and interfaces are useful for catching
simple errors like this one.  There is a 'unittest' module
in the Python standard library, and 'interface' modules are
available from the Zope 3 project and PyProtocols, both are
good.

Once you know you have a problem like this (or you've
decided to change a spelling), you can track down the
problem using grep, fix it with sed or use Python itself to
do the job if you really want to.

I once misspelled a name in a set of API methods, which was
very embarrassing (I spelled fovea as fovia).  So then I
had to go through and change it, and report it in as an API
change so that a patch became a minor version upgrade. 
Duh. Next time I use a dictionary before freezing an API!

Cheers,
Terry

-- 
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Steven D'Aprano]

On Fri, 06 Jan 2006 17:23:27 -0600, Terry Hancock wrote:

 I once misspelled a name in a set of API methods, which was
 very embarrassing (I spelled fovea as fovia).  So then I
 had to go through and change it, and report it in as an API
 change so that a patch became a minor version upgrade. 
 Duh. Next time I use a dictionary before freezing an API!


Can you please explain what you mean by that? Use a dictionary how?

-- 
Steven.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Paul Rubin]

Steven D'Aprano [EMAIL PROTECTED] writes:
  Duh. Next time I use a dictionary before freezing an API!
 Can you please explain what you mean by that? Use a dictionary how?

Use a dictionary by looking up words in it to check the spelling.
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

  Duh. Next time I use a dictionary before freezing an API!

 Can you please explain what you mean by that? Use a dictionary how?

Paul Use a dictionary by looking up words in it to check the spelling.

I think the most widely spread API misspelling must be referer, as in the
HTTP_REFERER header in the HTTP spec:

http://en.wikipedia.org/wiki/Referer

In fact, googling for referer and referrer reports a similar number of
hits, unlike most misspellings.

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Steven D'Aprano]

On Fri, 06 Jan 2006 17:29:32 -0800, Paul Rubin wrote:

 Steven D'Aprano [EMAIL PROTECTED] writes:
  Duh. Next time I use a dictionary before freezing an API!
 Can you please explain what you mean by that? Use a dictionary how?
 
 Use a dictionary by looking up words in it to check the spelling.

D'oh! I was thinking a dictionary like {}.


-- 
Steven.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Terry Hancock]

On Sat, 07 Jan 2006 14:03:10 +1100
Steven D'Aprano [EMAIL PROTECTED] wrote:

 On Fri, 06 Jan 2006 17:29:32 -0800, Paul Rubin wrote:
 
  Steven D'Aprano [EMAIL PROTECTED] writes:
   Duh. Next time I use a dictionary before freezing an
 API!  Can you please explain what you mean by that? Use
 a dictionary how?
  
  Use a dictionary by looking up words in it to check the
  spelling.
 
 D'oh! I was thinking a dictionary like {}.

Yeah, I meant like Websters', should've been clearer, I
guess, given the venue of this discussion. ;-)

-- 
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Terry Hancock]

On Fri, 6 Jan 2006 19:51:22 -0600
[EMAIL PROTECTED] wrote:
   Duh. Next time I use a dictionary before freezing
 an API!
 
  Can you please explain what you mean by that? Use a
 dictionary how?
 
 Paul Use a dictionary by looking up words in it to
 check the spelling.
 
 I think the most widely spread API misspelling must be
 referer, as in the HTTP_REFERER header in the HTTP spec:
 
 http://en.wikipedia.org/wiki/Referer
 
 In fact, googling for referer and referrer reports a
 similar number of hits, unlike most misspellings.

You know, I almost mentioned that myself. Drives me crazy.

One thing I've figured out is that using the full spelling
of a word instead of groovy programmer abbreviations makes
it a lot easier to remember the names of things.  Of course,
like everything, that can be taken too far, so I still use
things like bkg_clr too.  Old habits are hard to break.

-- 
Terry Hancock ([EMAIL PROTECTED])
Anansi Spaceworks http://www.AnansiSpaceworks.com

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[skip]

 In fact, googling for referer and referrer reports a similar
 number of hits, unlike most misspellings.

Terry You know, I almost mentioned that myself. Drives me crazy.

Me too.  I'm one of those people who, for better or worse, is a good
speller.  Words just look right or wrong to me and it bothers me when they
look wrong.

Terry One thing I've figured out is that using the full spelling
Terry of a word instead of groovy programmer abbreviations makes
Terry it a lot easier to remember the names of things.  Of course,
Terry like everything, that can be taken too far, so I still use
Terry things like bkg_clr too.  Old habits are hard to break.

I do tend to be a bit brief with my names and recognizing an identifier as
an abbreviation don't bother me the way a misspelled word does.  Maybe I've
been using Unix systems for too long with their brief command names like mv
and grep.  I prefer not to write big_honkin_long_names any more than I have
to either.

Skip
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Spelling mistakes!

[Alex Martelli]

KraftDiner [EMAIL PROTECTED] wrote:
   ...
 Frankly how are you ever to know if this type of error is occuring?

http://en.wikipedia.org/wiki/Unit_testing .


Alex
-- 
http://mail.python.org/mailman/listinfo/python-list