1313 </ h2 >
1414 < p >
1515 BPL supports all of the standard < a href =
16- "http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/specialnames.html ">
16+ "http://www.python.org/doc/current/ref/specialnames.html ">
1717 special method names</ a > supported by real Python class instances < em >
1818 except</ em > < code > __complex__</ code > (more on the reasons < a href =
1919 "#reasons "> below</ a > ). In addition, it can quickly and easily expose
@@ -33,7 +33,7 @@ <h2><a name="general">Basic Customization</a></h2>
3333 Python provides a number of special operators for basic customization of a
3434 class. Only a brief description is provided below; more complete
3535 documentation can be found < a
36- href ="http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/customization.html "> here</ a > .
36+ href ="http://www.python.org/doc/current/ref/customization.html "> here</ a > .
3737
3838 < dl >
3939 < dt >
@@ -114,7 +114,7 @@ <h2><a name="numeric">Numeric Operators</a></h2>
114114< p >
115115 Numeric operators can be exposed manually, by < code > def</ code > ing C++
116116 [member] functions that support the standard Python < a
117- href ="http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/numeric-types.html "> numeric
117+ href ="http://www.python.org/doc/current/ref/numeric-types.html "> numeric
118118 protocols</ a > . This is the same basic technique used to expose
119119 < code > to_string()</ code > as < code > __str__()</ code > above, and is < a
120120 href ="#numeric_manual "> covered in detail below</ a > . BPL also supports
@@ -398,7 +398,7 @@ <h3><a name="ternary_pow">The Ternary <code>pow()</code> Operator</a></h3>
398398< h2 > < a name ="numeric_table "> Table of Automatically Wrapped Methods</ a > </ h2 >
399399 < p >
400400 BPL can automatically wrap the following < a href =
401- "http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/specialnames.html ">
401+ "http://www.python.org/doc/current/ref/specialnames.html ">
402402 special methods</ a > :
403403
404404 < p >
@@ -672,12 +672,12 @@ <h2><a name="sequence_and_mapping">Sequence and Mapping Operators</a></h2>
672672
673673 < p >
674674 It is a better idea to support the standard < a
675- href ="http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/sequence-types.html "> Python
675+ href ="http://www.python.org/doc/current/ref/sequence-types.html "> Python
676676 sequence and mapping protocols</ a > for your wrapped containers. These
677677 operators have to be wrapped manually because there are no corresponding
678678 C++ operators that could be used for automatic wrapping. The Python
679679 documentation lists the relevant < a href =
680- "http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/sequence-types.html ">
680+ "http://www.python.org/doc/current/ref/sequence-types.html ">
681681 container operators</ a > . In particular, expose __getitem__, __setitem__
682682 and remember to raise the appropriate Python exceptions
683683 (< code > PyExc_IndexError</ code > for sequences,
@@ -773,7 +773,7 @@ <h2><a name="getter_setter">Customized Attribute Access</a></h2>
773773
774774 < p >
775775 Just like built-in Python classes, BPL extension classes support < a
776- href ="http://www.pythonlabs.com/pub/www. python.org/doc/current/ref/attribute-access.html "> special
776+ href ="http://www.python.org/doc/current/ref/attribute-access.html "> special
777777 the usual attribute access methods</ a > < code > __getattr__</ code > ,
778778 < code > __setattr__</ code > , and < code > __delattr__</ code > .
779779 Because writing these functions can
0 commit comments