Re: [Ironpython-users] .NET Foundation

2014-04-04 Thread Nicholas Devenish
On 4 Apr 2014, at 10:39, Jeff Hardy wrote: > I am having a hard time figuring out what the point of the .NET Foundation > is, though, other than "advancing the conversation". I tought they tried this > once with the CodePlex/Outercurve foundation and it didn't go anywhere. > If I’ve read the

Re: [Ironpython-users] Calling len() on a DynamicObject instance?

2013-10-10 Thread Nicholas Devenish
On 10 Oct 2013, at 17:36, Jeff Hardy wrote: > I haven't looked at the implementation of len() yet, so I could be > wrong, but my guess is that if your object doesn't implement IList (or > something else with .Count) it will look for a __len__ method > (http://bit.ly/16TDkIJ) on the object. This

[Ironpython-users] Calling len() on a DynamicObject instance?

2013-10-10 Thread Nicholas Devenish
Hi All, I have a DynamicObject subclass that is being passed into IronPython. Sometimes, this subclass represents a collection - at which point it is currently either Enumerated through TryConvert or Indexed by TryGetIndex. However, when in python code calling len(myobject), I get the error "le

Re: [Ironpython-users] No module named datetime

2012-12-18 Thread Nicholas Devenish
Hi Ian, The default runtime files for IronPython don't include the python standard library - they are installed when you install IronPython development, which is why it works on your development machine. The solution is to either include the standard library sources, and set up your applicatio

[Ironpython-users] Linq exception, only when debugging

2012-11-18 Thread Nicholas Devenish
I've come across a new error in my quest to use sqlalchemy; When running a query, I get the exception: Unable to cast object of type 'System.Linq.Expressions.FieldExpression' to type 'System.Linq.Expressions.BlockExpression'. The debugger launches to a line that passes along the results o

Re: [Ironpython-users] Differences with pyc-compiled assemblies?

2012-11-12 Thread Nicholas Devenish
ts to the site. For now, importing directly seems to work, or I'll play around with removing the call/warning to see if that works - it's only a deprecation. Many thanks, Nick On 12 Nov 2012, at 16:05, Jeff Hardy wrote: > On Mon, Nov 12, 2012 at 2:03 AM, Nicholas Devenish wr

Re: [Ironpython-users] Differences with pyc-compiled assemblies?

2012-11-12 Thread Nicholas Devenish
Hi Jeff again, > In inspect.py, just before line 758, it looks at co.co_argcount and > co.co_varnames and assumes that they are the same length, but my guess > is that they might not be when compiled with pyc. If you can figure > out exactly what getargspec is being called on, that might help make

Re: [Ironpython-users] Differences with pyc-compiled assemblies?

2012-11-11 Thread Nicholas Devenish
On 11 Nov 2012, at 23:06, Jeff Hardy wrote: > SQLAlchemy works on IronPython? I didn't know that. Very cool. Is > there anything that has to be done or does it just work out of the > box? It's supposed to work out of the box - one of the reasons I decided to go with IronPython for my current pr

[Ironpython-users] Differences with pyc-compiled assemblies?

2012-11-11 Thread Nicholas Devenish
I'm seeing weird differences between importing plain packages and adding references to the compiled versions. Specifically, between importing sqlalchemy (0.7.9, from tarball, also 0.8.0b1) as a directory structure and as compiled, the uncompiled version works perfectly, whereas the compiled vers