Title: Update docs on Reload()
Type: Stage:
Components: Documentation Versions:
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: skip.montanaro Nosy List: macquigg, skip.montanaro
Priority: normal Keywords:

Created on 2004-03-18 22:06 by macquigg, last changed 2004-03-19 15:30 by skip.montanaro. This issue is now closed.

File name Uploaded Description Edit
LibRefReload.pdf macquigg, 2004-03-18 22:06 reload description with changes highlighted
Messages (2)
msg20267 - (view) Author: David MacQuigg (macquigg) Date: 2004-03-18 22:06
The current description of the reload() function in the 
Library Reference Manual, Release 2.3.3, Section 2.1 
provides lots of detail, but not enough basic 
explanation.  As a result, there is lots of confusion on 
the use of reload, in the mailing lists, and even in texts 
on Python.  The attached PDF file shows the text from 
the manual, with my suggested edits highlighted in 

The main change is to add a much more detailed 
description of what happens when a module is reloaded.  
Reloads were always a mystery to me, until I started 
thinking about what is happening to the namespaces.

A minor edit:  I replaced "re-parse and re-initialize" 
with "re-compile and reload", since I think many users 
won't know exactly what the former terms mean in this 
context.  I'm not very familiar with the documentation, 
so I don't know if the former terms might be preferred, 
so as to be consistent with other documents.

See for 
an introductory description of reload, with examples and 
exercises and a few paragraphs on why reload can never 
work the way many users expect it to.

-- Dave
msg20268 - (view) Author: Skip Montanaro (skip.montanaro) * Date: 2004-03-19 15:30
Logged In: YES 

Accepted with a few changes.
Date User Action Args
2004-03-18 22:06:06macquiggcreate