classification
Title: RESTART line with no output
Type: behavior Stage: resolved
Components: Documentation, IDLE Versions: Python 3.6, Python 3.4, Python 3.5, Python 2.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: terry.reedy Nosy List: docs@python, python-dev, r.david.murray, sukari, terry.reedy
Priority: normal Keywords:

Created on 2014-11-08 11:23 by sukari, last changed 2015-09-24 05:42 by terry.reedy. This issue is now closed.

Messages (4)
msg230845 - (view) Author: Edward Alexander (sukari) Date: 2014-11-08 11:23
Whenever i run my code on Python IDLE editor,
the output is as follows:

============================== RESTART================================

I am a newbie,it seems i cannot move from this point .
This is my code:
def convert_to_celsius(fahrenheit):
    return (fahrenheit - 32) * 5.0 / 9.0
convert_to_celsius(80)
msg230853 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2014-11-08 12:50
Your code doesn't produce any output (ie: there are no print calls).  I don't use Idle myself, but I'm guessing that is why you don't see anything after the restart line.  If that is the case, do you see a place in whatever help or documentation you have read that it would be appropriate to mention this?  (The distinction is that the REPL window automatically prints the return value of whatever you type in, whereas in a program you get output only if you do the print yourself).
msg251485 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2015-09-24 05:40
New changeset e7bf0727f7df by Terry Jan Reedy in branch '2.7':
Issue #22820: Explain need for *print* when running file from Idle editor.
https://hg.python.org/cpython/rev/e7bf0727f7df

New changeset 824cb25448ab by Terry Jan Reedy in branch '3.4':
Issue #22820: Explain need for *print* when running file from Idle editor.
https://hg.python.org/cpython/rev/824cb25448ab
msg251486 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2015-09-24 05:42
For anyone who reads the doc, the added explanation should help.
History
Date User Action Args
2015-09-24 05:42:59terry.reedysetstatus: open -> closed
versions: + Python 2.7, Python 3.6
messages: + msg251486

assignee: docs@python -> terry.reedy
resolution: fixed
stage: resolved
2015-09-24 05:40:30python-devsetnosy: + python-dev
messages: + msg251485
2014-11-08 12:50:38r.david.murraysetassignee: docs@python
type: crash -> behavior
components: + Documentation
versions: + Python 3.4, Python 3.5, - Python 3.3
nosy: + r.david.murray, docs@python, terry.reedy

messages: + msg230853
2014-11-08 11:23:39sukaricreate