>> I think there is a third position: make sys.path magic somehow (but
>> have it still (appear to) be a list of strings) so that changes to it
>> affect a behind-the-scenes list of objects which is normally used to
>> do path-ish stuff.
David> I'm not sure I understand Skip's proposal, which may be the same
David> as the following, which strives for backwards compatibility:
David> - Define an alternative path which can have non-strings on it,
David> and define sys.path to be a "view" of the string elements in
David> this superpath.
Yeah, somethin' like that...
Skip
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