Thanks Dave for the much appreciate feedback.
- Sylvain
Dave Fugate wrote:
> The reason we've been releasing 2.0 as monthly alphas is that the Dynamic
> Language Runtime is still solidifying with improvements being made for
> IronRuby among other things. While we could release a single alpha (
2007/10/3, Kelie <[EMAIL PROTECTED]>:
> why many posts in this newsgroup don't wrap properly in browser? tried
> both ie and firefox and had the same problem. so i had to drag the
> horizontal scroll bar when viewing posts. is it just me?
No it isn't. I see the same problem.
--
Seo Sanghyeon
___
The reason we've been releasing 2.0 as monthly alphas is that the Dynamic
Language Runtime is still solidifying with improvements being made for IronRuby
among other things. While we could release a single alpha (or two) a month
prior to 2.0 beta 1, we like to integrate feedback from the commun
Hello all,
For IronPython the default recursion limit is maxint: 2147483647
This is too deep for .NET - and infinite recursion causes the process to
be terminated with a stack overflow exception.
You can fix this by calling "sys.setrecursionlimit(something)" with
something sensible - but an un
We've been focusing on improving the DLR since the release of IronPython 2.0
Alpha 1, and as such have had few resources to develop concrete plans for a
1.1.1 release. I know there are a few bugs you'd like to get fixed WRT 1.1
(None.__doc__, urllib support, etc). If people vote for these on C
2007/10/3, Sylvain Hellegouarch <[EMAIL PROTECTED]>:
> /me hopes he'll manage to get it compiled with mono this time.
I forgot to mention this, but there is a Mono bug to track IronPython
2.0 Alpha x>1 (Alpha 1 compiles fine) compilation problem.
https://bugzilla.novell.com/show_bug.cgi?id=325478
Oh sweet news.
However, what is the big showstopper to become a beta? A fifth alpha
means there must be something quite blocking down the line.
/me hopes he'll manage to get it compiled with mono this time.
- Sylvain
Dave Fugate wrote:
> Hi, IronPython 2.0 Alpha 5 will be released after we wra
Dave Fugate wrote:
> Hi, IronPython 2.0 Alpha 5 will be released after we wrap up work on a number
> of high priority bug fixes. This is scheduled to be completed at the end of
> this week which means it's likely 2.0A5 will become available sometime next
> week.
>
And what about 1.1.1 ? Som
hello,
why many posts in this newsgroup don't wrap properly in browser? tried
both ie and firefox and had the same problem. so i had to drag the
horizontal scroll bar when viewing posts. is it just me?
thanks.
--
Kelie
___
Users mailing list
Users@lis
Hi, IronPython 2.0 Alpha 5 will be released after we wrap up work on a number
of high priority bug fixes. This is scheduled to be completed at the end of
this week which means it's likely 2.0A5 will become available sometime next
week.
Dave
-Original Message-
From: [EMAIL PROTECTED] [
Thanks for the report Davy. Looks like it's been fixed with some recent
changes in the last month (see below), but I'll be sure to add a test against
this.
E:\ >ipy
IronPython console: IronPython 2.0 (2.0.0.00) on .NET 2.0.50727.1416
Copyright (c) Microsoft Corporation. All rights reserved.
>>>
Hi all,
I was wondering if there was any news about the next available release?
Will it be a beta or still an alpha? When may we expect it?
Just to feed my curiosity :)
Thanks,
- Sylvain
___
Users mailing list
Users@lists.ironpython.com
http://lists.i
IronPython console: IronPython 2.0A4 (2.0.10904.02) on .NET 2.0.50727.31
Copyright (c) Microsoft Corporation. All rights reserved.
>>> import clr
>>> clr.AddReference("System.Windows.Forms")
>>> from System.Windows.Forms import *
>>> control = TextBox()
>>> print control.__class__.__name__
Tracebac
On 10/2/07, Michael Foord <[EMAIL PROTECTED]> wrote:
> I mean that ConfigObj should work with IronPython - if it doesn't I'll
> fix it.
It is working great with IP :-)
Davy
--
Davy Mitchell
Blog - http://www.latedecember.co.uk/sites/personal/davy/
Twitter - http://twitter.com/daftspaniel
Skype
Davy Mitchell wrote:
> On 10/2/07, JoeSox <[EMAIL PROTECTED]> wrote:
>
>> Feel free to look at pswrdgeniron (IronPython GUI for pswrdgen).
>> http://www.codeproject.com/useritems/pswrdgeniron.asp
>> The module opens itself and reads in the first few lines, which each
>> setting is defined in ord
On 10/1/07, Andrew Schaeffer <[EMAIL PROTECTED]> wrote:
> Use .NET app.config file.
Thanks for this Andrew. Works well for read-only stuff.
Limitation for me is the need for a exe. To get the following example
to work you need a ipy.exe.config
IronPython console: IronPython 2.0A4 (2.0.10904.02) o
On 10/2/07, JoeSox <[EMAIL PROTECTED]> wrote:
> Feel free to look at pswrdgeniron (IronPython GUI for pswrdgen).
> http://www.codeproject.com/useritems/pswrdgeniron.asp
> The module opens itself and reads in the first few lines, which each
> setting is defined in order on a line. I used format of
I pinged the dev who's been working on this (he's actually on another team),
here's the response I got:
We have not done comprehensive performance tests to find out differences
between the two. Some time ago I tried to put a timer into test_cominterop.py
where it iterated through an Excel 20x20
Interesting. Which of the two is "better"? Is there a performance tradeoff
turning it on or off with COM objects which do or do not implement IDispatch?
Thanks,
-Lee
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dino Viehland
Sent: Tuesday, October 0
This enables using new support for COM objects that uses COM's IDispatch
interface instead of trying to get a TypeInfo for the object and use that to
invoke it. With it enabled we'll first check for IDispatch then to see if we
can get the TypeInfo, w/o it we'll check for the TypeInfo (via
IPro
Hi,
Can anyone eleaborate a bit more on the -X:PreferComDispatch option?
Does it mean extended support for standard libraries? What does the
prefer part stand for as in prefer com over what?
BR
Martin
___
Users mailing list
Users@lists.ironpython.com
h
21 matches
Mail list logo
