Microsoft making Python.NET

[Greg]

The following article from microsoft describes a workaroind for a bug
in hte beta version of VISUAL PYTHON DOT NET

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaskdr/html/askgui04032001.asp

When did microsoft put python into the visual studio beta? How did
this not make big news in developmnt circles?

A.E.



Here is the body of the article:

FIX: Memory Leak after pickling in Visual Python .NET Beta 1

View products that this article applies to.
This article was previously published under Q114345321
IMPORTANT: This article contains information about modifying the
registry. Before you modify the registry, make sure to back it up and
make sure that you understand how to restore the registry if a problem
occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in
the Microsoft Knowledge Base: 

114345321/8 Description of the Microsoft Windows Registry 

SYMPTOMS
When pickling an object containing a cyclic graph, the Visual Python
.NET Beta 1 can create references that will not be garbage collected. 

CAUSE
Visual Python .NET Beta 1 does not impose a recursion limit by
default. In this mode, an objects references are evaluated lazily
durring pickling. If the garbage collector runs durring this process,
some objects can be incorrectly referenced.
The failure is due to registry key data that was installed by Visual
Python .NET Beta 1. 

RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that you can solve problems that result
from using Registry Editor incorrectly. Use Registry Editor at your
own risk.

Open Regedit.exe and browse to
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\P++\RecursionLimit.
To be safe, back up this registry key: From the File menu, click
Export and save the key to an .reg file.
Set the RecusionLimit key from 0 to 1000.

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products
that are listed at the beginning of this article. This bug will be
corrected in Visual Python .NET (2004). 

The information in this article applies to:
Microsoft Visual Studio .NET 8.0, Beta 1