<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>We’ve recently been discussing a bug ( <a
href="http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=16323">http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=16323</a>
) internally and thought we’d get some broader input on it. Just so
you don’t have to click on this link this bug is all about how properties
get imported and additionally how we deal with static classes in the face of
import.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>There’s several different aspects to this. First
we have whether the class you’re doing an import from is a static class
or an instance class. Next we have whether the user is doing an import *
or from import. And finally we have whether the members being extracted are
properties/methods and whether they’re instance or static members.
Let’s take a look at each of those…<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>First if the class is a static class life is pretty
good. A .NET static class is much like a Python module. For example
consider the class System.Math. This contains a bunch of static methods
and some read-only fields. Doing from System.Math import * seems
perfectly reasonable in this case. We’re currently thinking about
treating these types much like a module with __all__ defined on it - and we’ll
even add __all__ to the type. The current thoughts on what goes into
__all__ is:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>__all__ contains all members <b>except</b>:<o:p></o:p></p>
<p class=MsoNormal>
__doc__/__class__<o:p></o:p></p>
<p class=MsoNormal>
Properties/indexers<o:p></o:p></p>
<p class=MsoNormal>
Non-const/read-only fields<o:p></o:p></p>
<p class=MsoNormal>
Built-in methods/functions inherited from non-static types (really just object
unless you use ilasm to create your static type)<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Next we have import * vs. from import. Import * should
naturally respect __all__ so for static classes it will follow the above
rules. From staticClass import x should allow importing of anything from
a module as long as it exists – so it’ll work the same way for
static classes as well. That will allow “from System.Environment
import CommandLine” to work will bring in the value for the command line.
Because non-static types won’t have __all__ we will disallow from
System.DateTime import *.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Now it starts to get tricky when you have a non-static class
because we have instance vs static members. To enable a better story w/
.NET we would like to enable from System.DateTime import Parse – supporting
the import of static functions. But the interesting question then becomes
should we allow from System.DateTime import Now – a static property?
Finally, should we allow from System.DateTime import AddMonths – an instance
method?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>So in summary the static classes seem to be straight
forward. Instance members and non-static classes make the story much more
complicated. We’d love to hear what everyone thinks about the
trickier cases or the plan in general.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>