When testing a script using the IronPython interactive window in
Visual Studio, the path variable in system.sys is a bunch of meaningless
directories:
» import sys
» sys.path
['.', 'C:\\PROGRAM FILES (X86)\\MICROSOFT VISUAL STUDIO
Hi there,
Im not sure this is something related to IronPython doing something
differently, but we are trying to call
ReportViewer.ServerReport.Render from IronPython and we get expected
Reference,but found null
We call it this way in VB.NET
exportBytes =
This is tracked by
http://ironpython.codeplex.com/workitem/29077
Very anonying. It makes importing many standard libs fail.
-原始邮件-
From: Federico Vaggi
Sent: Friday, January 28, 2011 2:39 AM
To: Discussion of IronPython
Subject: [IronPython] Visual Studio Interactive Shell Search
Federico wrote:
When testing a script using the IronPython interactive window in Visual
Studio,
the path variable in system.sys is a bunch of meaningless
directories:
import sys
sys.path
['.', 'C:\\PROGRAM FILES (X86)\\MICROSOFT VISUAL STUDIO
Opening visual studio with no project open, and running the Ironpython
interactive window, gives me this:
» import sys
» sys.path
['.', 'C:\\PROGRAM FILES (X86)\\MICROSOFT VISUAL STUDIO
10.0\\COMMON7\\IDE\\EXTENSIONS\\MICROSOFT\\IRONSTUDIO\\0.4\\Lib',
'C:\\PROGRAM FILES (X86)\\MICROSOFT
Federico wrote:
Opening visual studio with no project open, and running the Ironpython
interactive window, gives me this:
import sys
sys.path
['.', 'C:\\PROGRAM FILES (X86)\\MICROSOFT VISUAL STUDIO
10.0\\COMMON7\\IDE\\EXTENSIONS\\MICROSOFT\\IRONSTUDIO\\0.4\\Lib',
'C:\\PROGRAM FILES
I'd like to propose the following release schedule for IronPython 2.7:
Beta 2 - February 6
RC1 - February 20
RC2 - February 27
RTM - March 6
The need for a Beta 3 release could push those dates back by up to two
weeks. Also, I may reevaluate based on the rate of bugs being fixed -
if lots of
