I think I have the first idea why the tests are failing:
[bin] ./IronPythonConsole.exe
IronPython 0.9.6 on .NET 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
def testgenerator():
.. for i in range(0,10):
.. yield i
..
testgenerator
function testgenerator
if not (type(process) == types.GeneratorType):
raise Simerror(Fatal SimPy error: activating function which+
is not a generator (contains no 'yield'))
I suspect that the type system on IronPython is somehow different from that
in CPython.
given
Selon Klaus Muller [EMAIL PROTECTED]:
Stan,
Your assertion must be:
assert type(gentest()) == types.GeneratorType,
_not_:
assert type(gentest) == types.GeneratorType.
The call of a generator function generates a generator object.
You are right, sorry!!
there we are:
[bin] python
Selon Klaus Muller [EMAIL PROTECTED]:
Good work! What type does IronPython actually return for a generator?
a generated type...
type '__main__+gentest0'
not looking like a generator...
Stan.
Klaus Müller
-Original Message-
From: Stanislas Pinte [mailto:[EMAIL PROTECTED]
Title: [IronPython] New proposed exception model for IronPython
Your proposal is essentially what we have today (we have a separate
exception hierarchy that represents Python exceptions that is not correlated
with the CLR exception hierarchy in any way). This actually leads to *less*
