Re: [IronPython] IronPython and SSIS issue - need help...bad

2009-02-06 Thread Rob Weiss
Carl, Thanks for the help, looking forward to the update. Bill, I can get the package to run fine using dtsexec and it runs in VS BIS IDE, It also runs with a C# app I wrote, so I am not having an issue other than trying to get it to run under IP (on either a windows dev box with everything

Re: [IronPython] Resolver One 1.4 beta - with IronPython 2.0

2009-02-06 Thread Vineet Jain (gmail)
Hi Giles, Do you know where I can download the beta from? Vineet -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Giles Thomas Sent: Tuesday, February 03, 2009 1:50 PM To: IronPython list Subject: [IronPython] Resolver

[IronPython] repr() results with uint, etc.

2009-02-06 Thread Jeff Slutter
I have functions (in C#) that return results as everything from byte, sbyte, System.UInt16, int, uint, float, etc. If I use repr() on the returned value within IP2.0 only bool, int, int64, float, double and string types print out a nice value using repr. The other types (byte, char, sbyte,

Re: [IronPython] repr() results with uint, etc.

2009-02-06 Thread Dino Viehland
There's no existing functionality to do this but we could add __repr__ overloads onto the built-in types. They would presumably return something like: System.UInt32(1) or: UInt32(1) Could you open a bug? -Original Message- From: users-boun...@lists.ironpython.com

Re: [IronPython] repr() results with uint, etc.

2009-02-06 Thread Jeff Slutter
Ok, looking at the source, I see the issue in: public static string Repr(CodeContext/*!*/ context, object o) Is it safe to add these types in to there like: if ((s = o as string) != null) return StringOps.__repr__(s); if (o is int) return Int32Ops.__repr__((int)o);

Re: [IronPython] repr() results with uint, etc.

2009-02-06 Thread Dino Viehland
And the correct change to the source code would be adding __repr__ methods to the various *Ops types (Int16Ops, UInt16Ops, etc...) which return the correct formatting. Presumably by updating the scripts that generate these types. OTOH there's nothing particularly unsafe about your changes