pinard@iro.umontreal.ca (Fran=E7ois Pinard) writes: > >> I'm not sure what should best be done. 1) The documentation might be > >> modified to explain the limitation, so other users do not trip up on i= t. > >> 2) `encoding.lookup()' might merely return None in case `getregentry' = is > >> not defined in the imported module, or else, 3) it could make sure tha= t it > >> imports modules exclusively from within the `encodings' package. >=20 > > This is what Python 2.3, and Python 2.2.2 will do. >=20 > Hi, Martin. >=20 > I added "1)", "2)" and "3)" in the original text for clarity. Will Python > 2.2.2 and 2.3 do "3)", or all of "1)", "2)" and "3)"? Oops, it's 2) that Python 2.3 will do. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4