Re: [IronPython] 1.1 schedule?

2006-12-01 Thread Dino Viehland
I believe our current thinking is that 1.1 Alpha will actually be sometime next 
week.  That will include most of new functionality that we have written for 1.1 
along with some bug fixing work that we've done (these changes are all 
currently on CodePlex today in source form).

Then we'll ship 1.1 Beta sometime early-ish next year which will mainly be bug 
fixing on top of 1.1 Alpha possibly with some small features that we didn't get 
to for Alpha.

I'll update the release date.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo
Sent: Friday, December 01, 2006 5:27 PM
To: Discussion of IronPython
Subject: [IronPython] 1.1 schedule?

http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=IronPython&ReleaseId=161
says 2006-12-01 for the release date, which have already passed.

Any ETA?

--
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


[IronPython] 1.1 schedule?

2006-12-01 Thread Sanghyeon Seo
http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=IronPython&ReleaseId=161
says 2006-12-01 for the release date, which have already passed.

Any ETA?

-- 
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] Groping in the dark

2006-12-01 Thread Patrick O'Brien

On 12/1/06, William Reade <[EMAIL PROTECTED]> wrote:


Hi Patrick

I haven't been able to see the anomalies you mention -- perhaps the
following sample will help.
---
import clr
clr.AddReference("System.Windows.Forms")

from System.Windows.Forms import (
Application, DockStyle, Form, Keys, MenuStrip, ToolStripMenuItem,
ToolStripSeparator
)



Thanks, William - that example helped a lot.  It looks like the anomalies
are due to my using entirely different classes to build my menu.  I got the
basic menu code from this article:

http://www.devsource.com/article2/0,1895,1989493,00.asp

It uses MainMenu instead of MenuStrip, MenuItem instead of
ToolStripMenuItem, etc.  So I guess there is more than one way to construct
a menu and I better look a bit more carefully at what I'm using to get the
job done.  :-)

Thanks again.

--
Patrick K. O'Brien
Orbtech   http://www.orbtech.com
Schevohttp://www.schevo.org
Louie http://www.pylouie.org
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] engine.Dispose closes the stdout stream

2006-12-01 Thread Dino Viehland
I've looked into this on our side the guidance seems to be that we should add 
an overload of Set* that allows you to specify if we should close the stream or 
not.  This is analogous to the GZipStream constructor 
(http://msdn2.microsoft.com/en-us/library/system.io.compression.gzipstream.gzipstream.aspx).

I've opened bug #6144 to track this 
(http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=6144).


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stute, Detlef 
ALRT/EEG4 (Fa. epos)
Sent: Wednesday, November 29, 2006 3:18 AM
To: users@lists.ironpython.com
Subject: [IronPython] engine.Dispose closes the stdout stream

Hi all,
I redirect the stdout/err ... when I start the python engine


engine = new PythonEngine(eo);

// create stream to get the messages from the python engine
stream = new NotifyingStream();
engine.SetStandardOutput(stream);
engine.SetStandardError(stream);

When I call engine.Dispose() there the streams are closed. Is that the
way the engine should do?
It did not open the streams why does it close them?
Best regards
Detlef Stute
www.seatec-gmbh.com
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] Setting func_name

2006-12-01 Thread Dino Viehland
I've opened CodePlex bug #6142 for this 
(http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=6142).
  Thanks for finding & reporting this!

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo
Sent: Friday, December 01, 2006 7:54 AM
To: Discussion of IronPython
Subject: [IronPython] Setting func_name

This is broken.

>>> def f(): pass
...
>>> f.func_name = 'g'
>>> print f

>>> f.__name__
'f'

--
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] SymbolTable.Empty

2006-12-01 Thread Dino Viehland
Thanks for reporting this.  I'm not too concerned about someone doing this on 
SymbolTable, but for reflected types in general I think it makes sense that we 
should transform null into a string.  I've opened CodePlex bug #6141 
(http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=6141).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo
Sent: Friday, December 01, 2006 3:10 AM
To: Discussion of IronPython
Subject: [IronPython] SymbolTable.Empty

Warning: obscure.

from IronPython.Runtime import SymbolTable
print str(SymbolTable.Empty)

str() should not return any non-strings. Actually, IronPython seems to
enforce this for user types, just like CPython. But it doesn't enforce
this for reflected types, where .NET ToString() can return null.

--
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] unicode object type

2006-12-01 Thread Sylvain Hellegouarch
Fredrik Lundh wrote:
> Sylvain Hellegouarch wrote:
> 
>> Is this the correct behavior?
> 
> yes.  a Python implementation is not required to have a distinct Unicode
> string type; see:
> 
> http://jython.sourceforge.net/docs/differences.html
> 
> 

OK. Thanks for the heads up.
Mind you I find that a bit confusing and I'd rather have the type to
display unicode rather than str in that case. But fair enough.

- Sylvain
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] unicode object type

2006-12-01 Thread Fredrik Lundh
Sylvain Hellegouarch wrote:

> Is this the correct behavior?

yes.  a Python implementation is not required to have a distinct Unicode
string type; see:

http://jython.sourceforge.net/docs/differences.html


___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] Setting func_name

2006-12-01 Thread Sanghyeon Seo
A patch is available.

http://fepy.sourceforge.net/patches.html
patch-ironpython-set-func-name

-- 
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


[IronPython] Setting func_name

2006-12-01 Thread Sanghyeon Seo
This is broken.

>>> def f(): pass
...
>>> f.func_name = 'g'
>>> print f

>>> f.__name__
'f'

-- 
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


Re: [IronPython] Groping in the dark

2006-12-01 Thread William Reade
Hi Patrick

I haven't been able to see the anomalies you mention -- perhaps the 
following sample will help.
---
import clr
clr.AddReference("System.Windows.Forms")

from System.Windows.Forms import (
Application, DockStyle, Form, Keys, MenuStrip, ToolStripMenuItem, 
ToolStripSeparator
)

def SayHi(*_):
print "hi"

f = Form()
f.Text = "Hello multiverse!"

menuStrip = MenuStrip()
menuStrip.Dock = DockStyle.Top
f.Controls.Add(menuStrip)

menu = ToolStripMenuItem()
menu.Text = "SomeMenu"
menuStrip.Items.Add(menu)

menuItem = ToolStripMenuItem()
menuItem.Text = "SomeMenuItem"
menuItem.Click += SayHi
menuItem.ShortcutKeys = Keys.Control | Keys.Q
menu.DropDownItems.Add(menuItem)
menu.DropDownItems.Add(ToolStripSeparator())

Application.Run(f)


Cheers
William

Patrick O'Brien wrote:

> Am I missing something or is everyone else groping around in the dark 
> as much as I am when it comes to figuring out acceptable syntax in 
> IronPython versus other languages supported by the CLR.  What I'm 
> doing is building a simple app in Visual Studio C# 2005 Express to see 
> what objects are available and what properties they have.  I'm also 
> looking at the generated code.  But my translations into Python don't 
> always work out as I expect.  For example, here are some differences 
> I've come across:
>
> For all of these examples I'm using this bit of code:
>
> import clr
> clr.AddReference('System.Windows.Forms')
> import System.Windows.Forms as SWF
>
>
> To add a separator to a menu you need to do this:
>
> Add('-')
>
> Whereas this raises an exception:
>
> Add(SWF.ToolStripSeparator())
>
> Various attempts at adding shortcut keys failed, but this works:
>
> open_item.Shortcut = SWF.Shortcut.CtrlO
>
> Apparently the .ShortcutKeys property does not exist on menu items in 
> IronPython.
>
> So my basic question is how does one learn all these anomalies other 
> than by trial and error?
>
> -- 
> Patrick K. O'Brien
> Orbtech   http://www.orbtech.com
> Schevohttp://www.schevo.org
> Louie http://www.pylouie.org 
>
>
>
>___
>users mailing list
>users@lists.ironpython.com
>http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>  
>

___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


[IronPython] unicode object type

2006-12-01 Thread Sylvain Hellegouarch
CPython

>>> str(None)
'None'
>>> unicode(None)
u'None'
>>> type(unicode(None))

>>> type(unicode('ble'))



IronPython

>>> str(None)
'None'
>>> unicode(None)
'None'
>>> type(unicode(None))

>>> type(unicode('ble'))


Is this the correct behavior?

- Sylvain
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


[IronPython] SymbolTable.Empty

2006-12-01 Thread Sanghyeon Seo
Warning: obscure.

from IronPython.Runtime import SymbolTable
print str(SymbolTable.Empty)

str() should not return any non-strings. Actually, IronPython seems to
enforce this for user types, just like CPython. But it doesn't enforce
this for reflected types, where .NET ToString() can return null.

-- 
Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com