Kevin wrote: > 2) They don't care if Python stores objects, strings, or bananas in > sys.path, so long as=20 >=20 > sys.path=3Dmap(str,sys.path)=20 >=20 > results in a human-readable path and does not change how imports = occur. quick question: would the following variation of feeling #2 be = acceptable: > 2) They don't care if Python stores objects, strings, or bananas in > sys.path, so long as=20 >=20 > sys.path=3Dmap(str,sys.path)=20 + + on a sys.path set up by the Python interpreter itself > results in a human-readable path and does not change how imports = occur. (note that today's Python already allows you to violate the above rule, = by adding non-string objects with cunningly constructed __str__ methods...) </F>
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