[Ironpython-users] IronPython, Daily Digest 4/10/2014

2014-04-11 Thread CodePlex
Hi ironpython, Here's your Daily Digest of new issues for project "IronPython". In today's digest:ISSUES 1. [New issue] IronPython.dll has wrong assembly version 2. [New issue] Try in the browser crash -- ISSUES 1. [New issue] IronPython.dll has wro

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Olof Bjarnason
To just add my relative outsider opinion (new user of IronPython, 5+ year user of CPython). As long as a IronPython version does not adhere 100% to a CPython version, it does not make sense to follow same version name convention. Better then to have a completely different "scale", e.g. 0.xyz. In

Re: [Ironpython-users] SymPy and IronPython 2.7.4

2014-04-11 Thread Andrew Ayre
Hi, I didn't realize that SymPy has a test suite built in. Trying to run it gives: = >>>sympy.test() Traceback (most recent call last): File "", line 1, in File "C:\Program Files (x86)\WizoScript\PythonLib\site-packages\sympy\utilities

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Vernon D. Cole
Compliance is determined by running the same test suite as CPython (the reference implementation). The only tricky part is, should a test fail, determining whether it is testing a language feature (must fix) or an implementation detail (can skip). For example, tests involving the Garbage Collec

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Olof Bjarnason
OK, that sounds like a reasonable way to do it. Very nice that it is automatically verifiable! But it opens more questions from me, sorry. I find this interesting :) So when an automatic test, that is determined to be a implementation detail, fails - how does IronPython "skip" it? Is the actual t

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Jeff Hardy
On Fri, Apr 11, 2014 at 11:02 AM, Olof Bjarnason wrote: > OK, that sounds like a reasonable way to do it. Very nice that it is > automatically verifiable! > > But it opens more questions from me, sorry. I find this interesting :) > > So when an automatic test, that is determined to be a implementa

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Markus Schaber
Hi, Von: Jeff Hardy > On Fri, Apr 11, 2014 at 11:02 AM, Olof Bjarnason > wrote: > > OK, that sounds like a reasonable way to do it. Very nice that it is > > automatically verifiable! > > > > But it opens more questions from me, sorry. I find this interesting :) > > > > So when an automatic test,

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Jeff Hardy
On Fri, Apr 11, 2014 at 11:40 AM, Markus Schaber wrote: > Hi, > > Von: Jeff Hardy >> On Fri, Apr 11, 2014 at 11:02 AM, Olof Bjarnason >> wrote: >> > OK, that sounds like a reasonable way to do it. Very nice that it is >> > automatically verifiable! >> > >> > But it opens more questions from me, s

Re: [Ironpython-users] IronPython 3 Version Number (Was: Item 34263 in 2.7.5?)

2014-04-11 Thread Markus Schaber
Hi, Jeff, Von: Jeff Hardy [mailto:[email protected]] > On Fri, Apr 11, 2014 at 11:40 AM, Markus Schaber > wrote: > > Hi, > > > > Von: Jeff Hardy > >> On Fri, Apr 11, 2014 at 11:02 AM, Olof Bjarnason > >> > >> wrote: > >> > OK, that sounds like a reasonable way to do it. Very nice that it > >> >

Re: [Ironpython-users] SymPy and IronPython 2.7.4

2014-04-11 Thread Pawel Jasinski
it appears to work for me: $ bin/Debug/ipy -X:Frames -c 'import sympy; sympy.test()' = test process starts == executable: C:\cygwin64\home\rejap\github\IronLanguages\bin\Debug\ipy.exe (2.9.9-alpha-0) [IronPython] architecture: 32-bit ca