[IronPython] codeplex-dlr solution
I've been trying to get all the solutions to compile in the source code and I'm stuck on Codeplex-DLR.sln. It references a few projects that are not there namely: Samples ET_Sample1_CS ShapeScript Sympl Sympl35 Sympl35cponly examples python If I delete these projects then the solution builds fine but I'm just wondering if there's some code that's been missed out and still needs to be committed to github? Richard ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] codeplex-dlr solution
Yes, some code is missing. I'll add Sympl today. Also CodePlex-DLR.sln is not needed any more (some changes might be needed to remove it, I plan to look at it). Dlr.sln - solution that rebuilds everything (Ipy, Irb, test assemblies, etc) IronPython.sln - All Ipy assemblies that ship and their dependencies IronPython.Mono.sln- Same as IronPython.sln but excludes .Net specific projects (WPF) Ruby.sln - All Irb assemblies that ship and their dependencies IronStudio.sln- All tooling (Ipy, Irb + shared components) IronPythonTools.sln - Ipy tooling - I think we should remove this CodePlex-DLR.sln- We should remove this IronRuby.Rack.sln- IronRuby Rack... not sure what the state is. Tomas From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Richard Nienaber Sent: Sunday, January 30, 2011 9:02 AM To: Discussion of IronPython Subject: [IronPython] codeplex-dlr solution I've been trying to get all the solutions to compile in the source code and I'm stuck on Codeplex-DLR.sln. It references a few projects that are not there namely: Samples ET_Sample1_CS ShapeScript Sympl Sympl35 Sympl35cponly examples python If I delete these projects then the solution builds fine but I'm just wondering if there's some code that's been missed out and still needs to be committed to github? Richard ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
[IronPython] Issue Triage
I though I'd help by going through any issues tagged with High importance, unassigned, starting with ones from previous releases and seeing is they are still relevant. Issue 26426, which involves sympy (algebraic manipulation) under ironpython. With the most recent git version of sympy and IronPython 2.7B1, I get a better error message. C:\GITHUB\sympyc:\Program Files\IronPython 2.7\ipy.exe IronPython 2.7 Beta 1 (2.7.0.10) on .NET 4.0.30319.1 Type help, copyright, credits or license for more information. import sympy Traceback (most recent call last): File stdin, line 1, in module File C:\GITHUB\sympy\sympy\__init__.py, line 30, in module File C:\GITHUB\sympy\sympy\core\__init__.py, line 8, in module File C:\GITHUB\sympy\sympy\core\expr.py, line 1008, in module File C:\GITHUB\sympy\sympy\core\mul.py, line 962, in module File C:\GITHUB\sympy\sympy\core\power.py, line 806, in module File C:\GITHUB\sympy\sympy\core\add.py, line 516, in module File C:\GITHUB\sympy\sympy\core\symbol.py, line 6, in module File C:\GITHUB\sympy\sympy\logic\__init__.py, line 1, in module File C:\GITHUB\sympy\sympy\logic\boolalg.py, line 4, in module File C:\GITHUB\sympy\sympy\core\function.py, line 1091, in module ImportError: Cannot import name Integer Line 1091 is : from numbers import Rational, Integer I though the issue was 'Integer' as a reserved word in Ironpython. However, I can create a function or a class named Integer in the interpreter without a problem. Now I'm stuck. Any thoughts on how to proceed ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Proposed Release Schedule for 2.7
I propose we sync IronRuby releases with IronPython as follows: IronRuby - IronPython - date 1.1.2 - Beta 2 - February 6 none - RC1 - February 20 none - RC2 - February 27 1.1.3 - RTM - March 6 Tomas -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jeff Hardy Sent: Friday, January 28, 2011 3:39 PM To: Discussion of IronPython Subject: [IronPython] Proposed Release Schedule for 2.7 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 fixes are coming in, delaying the release may be worthwhile. Obviously, any showstoppers would have an affect as while, but I don't believe there are any of those at the moment. The only current blocker for release is that the test suite does not pass 100%. That will need to be sorted prior to RTM. It's an aggressive schedule, but I think IronPython has gone too long without a release. I'm expecting there to be 2.7.x releases every 4-6 weeks if there are sufficient contributions (like new modules). I want to get the 2.x series behind us so that work can begin on 3.2/3.3. Compatibility with 3.x is going to be much better than 2.x, and with most Python stuff needing porting effort anyway getting IronPython support will be easier. That's going to require some work in the innards, and I'm not sure too many people are familiar with those parts or IronPython yet. I've already updated the version numbers to Beta 2 and fixed the installer bugs that prevented Beta 1 from installing over Alpha 1. At this point, the bugs that get fixed will probably be the ones that have patches, or at least solid repros, attached to them. If you've got a bug that you think *must* be fixed, bring it up here. Does anyone else think this is doable? - Jeff ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Proposed Release Schedule for 2.7
Sounds good to me. Does the DLR version still need to be bumped? - Jeff On Sun, Jan 30, 2011 at 1:37 PM, Tomas Matousek tomas.matou...@microsoft.com wrote: I propose we sync IronRuby releases with IronPython as follows: IronRuby - IronPython - date 1.1.2 - Beta 2 - February 6 none - RC1 - February 20 none - RC2 - February 27 1.1.3 - RTM - March 6 Tomas -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jeff Hardy Sent: Friday, January 28, 2011 3:39 PM To: Discussion of IronPython Subject: [IronPython] Proposed Release Schedule for 2.7 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 fixes are coming in, delaying the release may be worthwhile. Obviously, any showstoppers would have an affect as while, but I don't believe there are any of those at the moment. The only current blocker for release is that the test suite does not pass 100%. That will need to be sorted prior to RTM. It's an aggressive schedule, but I think IronPython has gone too long without a release. I'm expecting there to be 2.7.x releases every 4-6 weeks if there are sufficient contributions (like new modules). I want to get the 2.x series behind us so that work can begin on 3.2/3.3. Compatibility with 3.x is going to be much better than 2.x, and with most Python stuff needing porting effort anyway getting IronPython support will be easier. That's going to require some work in the innards, and I'm not sure too many people are familiar with those parts or IronPython yet. I've already updated the version numbers to Beta 2 and fixed the installer bugs that prevented Beta 1 from installing over Alpha 1. At this point, the bugs that get fixed will probably be the ones that have patches, or at least solid repros, attached to them. If you've got a bug that you think *must* be fixed, bring it up here. Does anyone else think this is doable? - Jeff ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Proposed Release Schedule for 2.7
Yes, there have been changes to outer ring. I'm changing the version right now :) Tomas -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jeff Hardy Sent: Sunday, January 30, 2011 12:49 PM To: Discussion of IronPython Subject: Re: [IronPython] Proposed Release Schedule for 2.7 Sounds good to me. Does the DLR version still need to be bumped? - Jeff On Sun, Jan 30, 2011 at 1:37 PM, Tomas Matousek tomas.matou...@microsoft.com wrote: I propose we sync IronRuby releases with IronPython as follows: IronRuby - IronPython - date 1.1.2 - Beta 2 - February 6 none - RC1 - February 20 none - RC2 - February 27 1.1.3 - RTM - March 6 Tomas -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jeff Hardy Sent: Friday, January 28, 2011 3:39 PM To: Discussion of IronPython Subject: [IronPython] Proposed Release Schedule for 2.7 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 fixes are coming in, delaying the release may be worthwhile. Obviously, any showstoppers would have an affect as while, but I don't believe there are any of those at the moment. The only current blocker for release is that the test suite does not pass 100%. That will need to be sorted prior to RTM. It's an aggressive schedule, but I think IronPython has gone too long without a release. I'm expecting there to be 2.7.x releases every 4-6 weeks if there are sufficient contributions (like new modules). I want to get the 2.x series behind us so that work can begin on 3.2/3.3. Compatibility with 3.x is going to be much better than 2.x, and with most Python stuff needing porting effort anyway getting IronPython support will be easier. That's going to require some work in the innards, and I'm not sure too many people are familiar with those parts or IronPython yet. I've already updated the version numbers to Beta 2 and fixed the installer bugs that prevented Beta 1 from installing over Alpha 1. At this point, the bugs that get fixed will probably be the ones that have patches, or at least solid repros, attached to them. If you've got a bug that you think *must* be fixed, bring it up here. Does anyone else think this is doable? - Jeff ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Issue Triage
There's probably an Integer.py somewhere in sympy and this is probably an import bug. If someone was particularly ambitious they could re-write import by porting CPython's import to IronPython - viola, no more import bugs! :) Otherwise it's all about figuring out how we're differing in import semantics - I usually start import bugs by trying to re-create a simple repro of the issue and then work from there. I always thought import bugs but if you look at the CPython source code it might be much easier. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Bruce Bromberek Sent: Sunday, January 30, 2011 12:22 PM To: Discussion of IronPython Subject: [IronPython] Issue Triage I though I'd help by going through any issues tagged with High importance, unassigned, starting with ones from previous releases and seeing is they are still relevant. Issue 26426, which involves sympy (algebraic manipulation) under ironpython. With the most recent git version of sympy and IronPython 2.7B1, I get a better error message. C:\GITHUB\sympyc:\Program Files\IronPython 2.7\ipy.exe IronPython 2.7 Beta 1 (2.7.0.10) on .NET 4.0.30319.1 Type help, copyright, credits or license for more information. import sympy Traceback (most recent call last): File stdin, line 1, in module File C:\GITHUB\sympy\sympy\__init__.py, line 30, in module File C:\GITHUB\sympy\sympy\core\__init__.py, line 8, in module File C:\GITHUB\sympy\sympy\core\expr.py, line 1008, in module File C:\GITHUB\sympy\sympy\core\mul.py, line 962, in module File C:\GITHUB\sympy\sympy\core\power.py, line 806, in module File C:\GITHUB\sympy\sympy\core\add.py, line 516, in module File C:\GITHUB\sympy\sympy\core\symbol.py, line 6, in module File C:\GITHUB\sympy\sympy\logic\__init__.py, line 1, in module File C:\GITHUB\sympy\sympy\logic\boolalg.py, line 4, in module File C:\GITHUB\sympy\sympy\core\function.py, line 1091, in module ImportError: Cannot import name Integer Line 1091 is : from numbers import Rational, Integer I though the issue was 'Integer' as a reserved word in Ironpython. However, I can create a function or a class named Integer in the interpreter without a problem. Now I'm stuck. Any thoughts on how to proceed ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Sho
There's a nice blog entry on using Solver Foundation to do optimization from IronPython here: http://blogs.msdn.com/b/natbr/archive/2011/01/28/optimization-modeling-using-solver-foundation-and-sho.aspx On Wed, Jan 26, 2011 at 11:51 AM, Sumit Basu sum...@microsoft.com wrote: Thanks for the shout-out, Curt! This is a pretty proud day for us; we’ve been working on Sho for five years and are finally releasing it to the public J The official web site is http://research.microsoft.com/sho The license allows for use non-commercial purposes, which includes academic, personal, and internal use by a commercial entity. You can read the whole license herehttp://research.microsoft.com/en-us/downloads/bc38771b-dc48-475b-8d18-7fe87e1bc2a1/Sho%20License%20Agreement%20(2010-11-03)%20FINAL.rtf, but I’ve copied one bit below which I think might help explain about use by commercial entities: “You may use, copy, reproduce, and distribute this Software for any non-commercial purpose, subject to the restrictions in this Agreement. Some purposes which can be non-commercial are teaching, academic research, public demonstrations and personal experimentation. For clarity, internal use by a commercial entity is considered a non-commercial purpose and is permitted under this Agreement.” In other words, commercial entities can use Sho internally, but can’t ship the bits externally for commercial purposes (more detail on what this means exactly and other aspects in the license itself). -Sumit *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Curt Hagenlocher *Sent:* Wednesday, January 26, 2011 11:23 AM *To:* Discussion of IronPython *Subject:* [IronPython] Sho I thought the people on this list might be interested in the following IronPython-based tooling for technical computing: http://msdn.microsoft.com/en-us/devlabs/gg585581.aspx Disclaimer: I'm not sure what the license is. -Curt ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
