...6<#7419#>2.1<#7419#><#7419#>2.1<#7419#>
<#30#>Some descriptions sorely lack explanations of the exceptions that may be raised --- this will be fixed in a future version of this document.<#30#>
...10<#7481#>2.2<#7481#><#7481#>2.2<#7481#>
<#4939#>As a consequence, the list [1, 2] is considered equal to [1.0, 2.0], and similar for tuples.<#4939#>
...files.38 <#7632#>2.3<#7632#><#7632#>2.3<#7632#>
<#5069#>Specifying a buffer size currently has no effect on systems that don't have setvbuf(). The interface to specify the buffer size is not done using a method that calls setvbuf(), because that may dump core when called after any I/O has been performed, and there's no reliable way to determine whether this is the case.<#5069#>
...#math183#undefined.40 <#7637#>2.4<#7637#><#7637#>2.4<#7637#>
<#1196#>In the current implementation, local variable bindings cannot normally be affected this way, but variables retrieved from other scopes can be. This may change.<#1196#>
... avaialble.<#7643#>3.1<#7643#><#7643#>3.1<#7643#>
<#1208#>at least in theory --- it is possible to specify at build time that one or more of these modules should be excluded, but it would be antisocial to do so.<#1208#>
...59<#7665#>3.2<#7665#><#7665#>3.2<#7665#>
<#1700#>The name of this module stems from a bit of terminology used by the designers of Modula-3 (amongst others), who use the term ``marshalling'' for shipping of data around in a self-contained form. Strictly speaking, ``to marshal'' means to convert some data from internal to external form (in an RPC buffer for instance) and ``unmarshalling'' for the reverse process.<#1700#>
... available.<#7673#>4.1<#7673#><#7673#>4.1<#7673#>
<#1798#>at least in theory --- it is possible to botch the library installation or to sabotage the module search path so that these modules cannot be found.<#1798#>
...below.117 <#7721#>8.1<#7721#><#7721#>8.1<#7721#>
<#3368#>The Python version of STDWIN does not support draw procedures; all drawing requests are reported as draw events.<#3368#>