Re: [Ironpython-users] struct pack / unpack not thread safe?

2012-09-20 Thread Jeff Hardy
Thanks for bringing this up. Unfortunately the bug database is so deep that some important ones have fallen through the cracks. - Jeff On Thu, Sep 20, 2012 at 7:56 AM, John Dickinson wrote: > Sorry, I've just found this: http://ironpython.codeplex.com/workitem/30228 > so I see that it is a bug.

Re: [Ironpython-users] Separating return values from printed values?

2012-09-20 Thread Doug Blank
On Thu, Sep 20, 2012 at 11:48 AM, Keith Rome wrote: > That should be fine. My example was the simplest way possible to spin up a > script, so I didn't bother with an explicit scope. But that doesn't change > anything really. Also if you re-use the same engine many times, you only > really need

Re: [Ironpython-users] Separating return values from printed values?

2012-09-20 Thread Keith Rome
That should be fine. My example was the simplest way possible to spin up a script, so I didn't bother with an explicit scope. But that doesn't change anything really. Also if you re-use the same engine many times, you only really need to wire up the custom output writer once - after initial engi

[Ironpython-users] IronPython, Daily Digest 9/19/2012

2012-09-20 Thread no_reply
Hi ironpython, Here's your Daily Digest of new issues for project "IronPython". In today's digest:ISSUES 1. [New issue] boolean type from databinding is not json compatible 2. [New issue] Lower casing non-ASCII characters does not work 3. [New comment] Lower casing non-ASCII characters does not

Re: [Ironpython-users] struct pack / unpack not thread safe?

2012-09-20 Thread John Dickinson
http://ironpython.codeplex.com/workitem/30228 On Thu, Sep 20, 2012 at 3:56 PM, John Dickinson wrote: > Sorry, I've just found this: http://ironpython.codeplex.com/workitem/30228so > I see that it is a bug. > > On Thu, Sep 20, 2012 at 3:48 PM, John Dickinson wrote: > >> I have at least two threa

Re: [Ironpython-users] struct pack / unpack not thread safe?

2012-09-20 Thread John Dickinson
Sorry, I've just found this: http://ironpython.codeplex.com/workitem/30228so I see that it is a bug. On Thu, Sep 20, 2012 at 3:48 PM, John Dickinson wrote: > I have at least two threads that end up calling struct.pack and > struct.unpack, and regularly get two exceptions: "SystemError: Object >

[Ironpython-users] struct pack / unpack not thread safe?

2012-09-20 Thread John Dickinson
I have at least two threads that end up calling struct.pack and struct.unpack, and regularly get two exceptions: "SystemError: Object reference not set to an instance of an object." and "SystemError: The LinkedList node does not belong to current LinkedList.". The following code reproduces the prob

Re: [Ironpython-users] Separating return values from printed values?

2012-09-20 Thread Doug Blank
On Thu, Sep 20, 2012 at 1:37 AM, Keith Rome wrote: > This might give you what you need (hooking in via the runtime output writer, > which is where the print function routes to), it seems to work for my quick > test: > > using System; > using System.IO; > using System.Text; > using IronPython.Hos