Guido van Rossum wrote: > (snip) > But I don't think that changing the "from M import v" semantics so > that local assignment to v changes the binding of M.v as well is > defensible. I agree, however, I think that having: from M import v causing a name binding that is broken by local assigment to v *is* defensible and reasonably implementable. Changes to 'v' in M (including by reload of M) would be reflected locally unless someone did: v=something locally. Local assignment would negate an import, as it does now. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
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