Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] Problem with indexers of generic collections
2. [New comment] Import System does not work when script called from C#
3. [Status update] Rename *.cs files to properly reflect th
Hi,
I'm running embedded IronPython scripts (2.6, .NET 3.5) and I was wondering
what happens with the stuff allocated within the script after the script
has finished? For testing purposes I've been executing the following script
s = set()
for i in range(0, 100):
s.add(i)
...and then watc
On Fri, Feb 10, 2012 at 10:04 AM, Igor Brejc wrote:
> Hi,
>
> I'm running embedded IronPython scripts (2.6, .NET 3.5) and I was wondering
> what happens with the stuff allocated within the script after the script has
> finished? For testing purposes I've been executing the following script
>
> s =
On Fri, Feb 10, 2012 at 7:15 PM, Jeff Hardy wrote:
>
> I believe if you run the code in a separate AppDomain you can unload
> the AppDomain and the code will be collected, which should take
> everything else with it.
>
>
> Yes, I've seen the
http://stackoverflow.com/questions/1664567/embedded-iro
On Fri, Feb 10, 2012 at 7:46 PM, Dino Viehland wrote:
>
>
> Jeff wrote:
> > I'm taking a stab off the top of my head based on my limited knowledge
> of the
> > internals, but I do know that debug code is not collectable.
> > It's possible that the code itself may be holding references that keep
>
Jeff wrote:
> I'm taking a stab off the top of my head based on my limited knowledge of the
> internals, but I do know that debug code is not collectable.
> It's possible that the code itself may be holding references that keep objects
> alive longer than expected.
>
> I believe if you run the c
We won’t call IDispose on them. Usually they’ll follow the pattern of
implementing IDisposable + having a finalizer so they will eventually release
their resources. Also they can be used with the “with” statement so that their
Dispose methods are eagerly called.
From: Igor Brejc [mailto:igor.
We're pleased to announce the release of Python Tools for Visual Studio 1.1
http://pytools.codeplex.com/releases/view/76091. Python Tools for Visual Studio
(PTVS) is an open-source plug-in for Visual Studio which supports programming
with the Python programming language. PTVS supports a broad ra
