Curt Hagenlocher wrote:
I believe this was fixed for 2.6, but that the fix is too disruptive
to backport (by a long shot!)
Ah - so it is just the backport that is closed. Fair enough. Sorry for
the noise.
Michael
On Fri, Jul 17, 2009 at 1:55 PM, Michael Foord
<fuzzy...@voidspace.org.uk <mailto:fuzzy...@voidspace.org.uk>> wrote:
Issue 22239 has been closed as 'by design'.
http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=22239&ProjectName=IronPython
<http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=22239&ProjectName=IronPython>
Dino described this as a serious bug when it was pointed out and
it is both extremely unintuitive and problematic - why should
separate scopes (modules) be linked this way when used from the
hosting API?
This seems like a very odd decision.
All the best,
Michael Foord
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
Users mailing list
Users@lists.ironpython.com <mailto:Users@lists.ironpython.com>
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
