They are implemented as members. Since the __doc__ behaves like any other
member,
The implementation just uses the member semantics. Consider for example:
>>> class c:
... "doc 1"
... print __doc__
... __doc__ = "doc 2"
... print __doc__
...
doc 1
doc 2
>>>
I hope this answers yo
Hi.
I'm not sure if you can help me with this because I don't think it's an
IronPython exclusive problem, but it is the only thing that comes up
broken. I am running VS2005 build 8.0.50110.28 with .NET build
2.0.50110. Last night I tried upgrading to .NET build 2.0.50215,
downloaded from th
What any plan for support VS 2005?
2005/6/15, Martin Maly <[EMAIL PROTECTED]>:
> Hello IronPython community
>
> Now that we have shipped the 0.7.6 release of IronPython we want to
> share our plans for the future releases, how we get from here to the 0.8
> release.
>
> There are two areas in whi
Hello IronPython community
Now that we have shipped the 0.7.6 release of IronPython we want to
share our plans for the future releases, how we get from here to the 0.8
release.
There are two areas in which we want to make broader changes between now
and 0.8. They both relate to the way IronPython
Out of curiosity, how are __doc__ strings being compiled? As a member, or
perhaps as an attribute in the same vein as XML comments in C#?
<>___
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/lis
I know this is a pretty minor issue, but the GotDotNet community
e-mail that has this information is not properly formatted. The e-mail
is formatted as both HTML and Text, and the HTML version does not have
line breaks () where there are newlines (\n), so your
text-bulleted list runs together. (The
Hello IronPython community,
We have just released the version 0.7.6 of IronPython.
The most important changes that this release contains are:
* Filtering of exception call stacks
- by default, we filter the call stack to only show the relevant
stack frames.
- the property PythonEngine.Exce
