I got some private feedback that not supporting Python for .NET with the
initial beta of Visual Python is bad news.  Here is the response I sent to
clarify and explain the situation a bit more:

----------------------------------------------------------------------------
Before you paint everything black and white, let me explain it a bit more:
You will be able to edit Python for .NET code with Visual Python as soon
as it becomes available.  There are no syntax changes for Python for .NET,
so all the editor features like syntax coloring, method lists and tool
tips, code folding and on the fly syntax checking will be available.

You can also use the "External Tools" feature of Visual Python to invoke
the Python for .NET commandline compiler for the source you are currently
editing.

What you don't get in the first beta release is pretty dialog boxes for
the Python for .NET compiler options and you also won't be able to debug
Python for .NET components using the Visual Python debugger.  The debugger
is giving us more problems than we thought; it doesn't work yet even for
classic Python.  That is the reason we do have a Visual Perl beta, but not
a Visual Python beta right now.  As soon as the debugger works, we want to
release Visual Python for people to play with.  Whenever we get debugging
support for Python for .NET working, we'll release that as well.  But we
currently don't have enough information to give a time estimate for it.
----------------------------------------------------------------------------

Happy holidays!
-Jan

_______________________________________________
Python.NET mailing list. To unsubscribe go to http://listserv.ActiveState.com/mailman/subscr
ibe/python.net