Dear Dino, Thanks again. I do not want IPY team to implement dupulicated quit() function. I have to use standard Lib at your suggession. I'm a bit confused standard Lib and runtime implementation. Since my enjoying platform is not Windows/LINUX, but Mac OS X Panther, Apple's terminal does not permit me to use Cntl+D shortcut to quit Ipy sesseion, it was annoying for me to do "import sys; sys.exit()" many times.
Regards, 2008/1/3, Dino Viehland <[EMAIL PROTECTED]>: > On quit(): quit is actually not defined by the runtime implementation of > Python, rather it's part of the standard library (defined in site.py and > installed w/ the setquit function). > > Running w/ the standard library set (or just from CPython's Lib dir) will > result in that functionality being available and works even in v1.0: > > 16:52:12.23 > C:\Python25\Lib > C:\Product\Released\IronPython-1.0\ipy.exe > IronPython 1.0.60816 on .NET 2.0.50727.1433 > Copyright (c) Microsoft Corporation. All rights reserved. > >>> quit() > > 16:52:41.39 > C:\Python25\Lib > > > I'd rather not duplicate the functionality in the runtime - is there a reason > you can't use the std lib (other than we don't include it by default? :) ). > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of HEMMI, Shigeru > Sent: Sunday, December 23, 2007 4:00 AM > To: Discussion of IronPython > Subject: Re: [IronPython] IronPython 1.1.1 wish-list? > > Hello, > > If the bug, > http://lists.ironpython.com/htdig.cgi/users-ironpython.com/2007-February/004500.html > is fixed or somebody shows me a good example how to inherit "file" > class in IronPython > 1.1, I will be happy. > > 2nd, please provide quit() function, which eases my interactive > IronPython session. > > Regards, > > > > > 2007/12/18, Dino Viehland <[EMAIL PROTECTED]>: > > > > > > > > > > Are there any particular bugs you'd like to see fixed in IronPython 1.1.1? > > > > > > > > We're planning on updating the 1.1 release w/ a targeted set of bug fixes. > > Unfortunately we've started to use the CodePlex bug list to track primarily > > 2.0 bugs. We can still use this to find the highest ranked bugs that aren't > > fixed in v1.1 and target those to be back ported - but it's possible we > > might miss something important. So I'd thought I'd ask: what do you want > > fixed? > > > > > > > > Note the idea here is to keep these fixes small and keep the release stable, > > so please no fix "type(type) is type" J. And of course if you don't know > > how bad it'll be feel free to suggest it anyway. Thanks! > > _______________________________________________ > > 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 > _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
