Good afternoon,
I hope you can assist. I have decided to learn some programming and have downloaded Python as it appears to offer the advantage of being logical without being over complicated.
I have installed Python 3.4 on my Mac which is running OS X 10.10.1 Yosemite.
When I open the program Idle I get the message
>>> WARNING: The version of Tcl/Tk (8.5.9) in use may be unstable.
Visit http://www.python.org/download/mac/tcltk/ for current information.
I tried typing in some lines of code copied from a Python tutorial I found on the Python website
After Hours Programming Python 3 Tutorial <http://www.afterhoursprogramming.com/tutorial/Python/Overview/> (Python 3)
Although the code ran OK on the tutorial website it produced errors when I typed it in Idle.
I visited the site quoted in the error message and as a result of information given there I downloaded and installed Wish 8.6 which has version Tcl 8.6 & Tk 8.6 (8.6.3)
However I still got the same error message. I, therefore, uninstalled Python and downloaded it again from the Python website and reinstalled it in the hope that it would recognise the new version of Tcl/Tk.
But, the same error message still appears. The program Idle does not seem to recognise that I have Tcl8.6 &Tk 8.6.3 installed instead of Tcl/Tk 8.5.9
There must be a simple error I am making, but I do not know what it is.
This is the first time that I have tried anything like programming and I would appreciate assistance if possible.
Kind Regards
Peter McCahy
Documentation of math.factorial function says [1]:
> Raises ValueError if x is not integral or is negative.
It should be changed to:
> Raises ValueError if x is negative or TypeError if it is not integral.
It's applicable for Python versions 2.7 and 3.4. I didn't check it for
other versions.
Doc/library/math.rst file.
Thanks
[1] https://docs.python.org/3/library/math.html#math.factorial
New submission from Damien Marié:
The Nose project moved from Google Code to Github, the link in the unittest documentation didn't change.
How to reproduce:
- Go to https://docs.python.org/3.5/library/unittest.html
- Click on nose (in the "See also" section)
- See the Google Code project being moved to github
How to fix:
Replace the link with the readthedocs page ( https://nose.readthedocs.org/en/latest/ ) or the github page
----------
assignee: docs@python
components: Documentation
messages: 233148
nosy: docs@python, mariedam
priority: normal
severity: normal
status: open
title: Link to the nose project obsolete
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue23125>
_______________________________________
Jan Kaliszewski added the comment:
My concerns are now being addressed in the issue19548.
----------
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue19539>
_______________________________________
A few remarks from a perspective of a person who still does not
understand all nooks and crannies of the Python codecs system and the
*codecs* module.
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst
File Doc/library/codecs.rst (right):
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:24: but there are also codecs that encode text to
text, and bytes to bytes.
Shouldn't be a note about arbitrary-types codecs added *here*?
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:164: .. function:: register_error(name,
error_handler)
For this function and the functions described below, the above sentence
"To simplify access to the various codecs, the module provides these
additional functions which use :func:`lookup` for the codec lookup:"
(line 112) is not appropriate. Some other sentence should be placed
here (introducing error-handling-related functions.
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:182: Decoding and translating works similarly,
except :exc:`UnicodeDecodeError` or
Possible beginner's questions: What is "translating"? When it is
performed? How can it be differentiated from subsequent encoding +
decoding?
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:250: :func:`open` function; the ``'b'`` is
automatically added.
I would add something like: "Please note that when you need to use just
an ordinary :term:`text encoding` the built-in :func:`open` function is
the recommended (and, typically, more efficient) way to operate on text
files".
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:325: .. _surrogateescape:
Should be moved to the place above the ".. _error-handlers:" line (341).
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:335: Each codec has to define four interfaces to
make it usable as codec in Python:
Possible beginner's questions: is a codec an instance of :class:`Codec`?
Or of :class:`CodecInfo`? What does it mean that it define those *four*
intefraces? How is it related to the
stateless/incremental/decoder/encoder and stream writer/reader classes
described below? Why here only *four* interfaces and not *six*
interfaces are mentioned? (i.e., what about *incremental encoder* and
*incremental decoder?*)
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:687: providing the *errors* keyword argument.
These parameters are defined:
The "parameters" word does not seem to be the correct term here...
http://bugs.python.org/review/19548/diff/13486/Doc/library/codecs.rst#newco…
Doc/library/codecs.rst:689: * ``'strict'`` Raise :exc:`ValueError` (or a
subclass); this is the default.
Only these three and not, e.g. 'surrogateescape'?
Shouldn't be a reference to ".. _error-handlers:" be used here instead
of this enumeration? (with a caution that the "only for encoding"
handlers are disallowed)
http://bugs.python.org/review/19548/
Akira Li added the comment:
Two minor details:
1. It is possible that `fileno(stdout) != 1` even in C [1].
I don't know what happens if the code from the answer is
run on Windows.
In principle, it may break eryksun's workaround. I don't
know how likely it is in practice.
2. you can redirect at the file descriptor level in Python [2]
using os.dup2(). I don't know whether the code in the
answer works on Windows.
[1] http://stackoverflow.com/questions/25516375/is-it-possible-that-filenostdou…
[2] http://stackoverflow.com/questions/4675728/redirect-stdout-to-a-file-in-pyt…
----------
nosy: +akira
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue22673>
_______________________________________