Re: [IronPython] IronPython 2.7B1 non-default install location not working

2011-01-10 Thread yngipy hernan
On Sat, Jan 8, 2011 at 10:45 PM, Jeff Hardy wrote: > On Sat, Jan 8, 2011 at 7:19 PM, yngipy hernan wrote: > > Hi All, > > I seem to remember that this was already reported in CodePlex but I can't > > find it. Anyway, what I have observed was that if I install IronPython > 2.7B1 > > in a non-defa

Re: [IronPython] Adding Unit Tests

2011-01-10 Thread Dino Viehland
To add a new test you can modify the %DLR_Root%\Test\IronPython.tests file and add something like: test_csv_cpy %DLR_ROOT%\Languages\IronPython\Internal\ipy.bat Test\test_csv.py 60 false false false fals

[IronPython] Adding Unit Tests

2011-01-10 Thread Slide
As I am developing an implementation of the _csv module that I would eventually like to contribute to the community, what is the best way to add unit tests to the current suite? I have been using the unit test in the CPython sources for the csv module to test my _csv implementation. Is there an eas

Re: [IronPython] What is a good way to determine OS platform with IronPython?

2011-01-10 Thread Doug Blank
> Doug wrote: >> > On Mon, Jan 10, 2011 at 3:37 PM, Douglas Blank >> > wrote: >> >> Now that IronPython runs on other operating systems, what is the >> >> recommended way to determine the os when running IP? >> > >> > `os.name` is probably what you want. There was some discussion on >> > python-de

Re: [IronPython] What is a good way to determine OS platform with IronPython?

2011-01-10 Thread Dino Viehland
Doug wrote: > > On Mon, Jan 10, 2011 at 3:37 PM, Douglas Blank > > wrote: > >> Now that IronPython runs on other operating systems, what is the > >> recommended way to determine the os when running IP? > > > > `os.name` is probably what you want. There was some discussion on > > python-dev about a

Re: [IronPython] What is a good way to determine OS platform with IronPython?

2011-01-10 Thread Doug Blank
> On Mon, Jan 10, 2011 at 3:37 PM, Douglas Blank > wrote: >> Now that IronPython runs on other operating systems, what is the >> recommended way to determine the os when running IP? > > `os.name` is probably what you want. There was some discussion on > python-dev about a module (or extension to s

Re: [IronPython] What is a good way to determine OS platform with IronPython?

2011-01-10 Thread Jeff Hardy
On Mon, Jan 10, 2011 at 3:37 PM, Douglas Blank wrote: > Now that IronPython runs on other operating systems, what is the recommended > way to determine the os when running IP? `os.name` is probably what you want. There was some discussion on python-dev about a module (or extension to sys?) that

[IronPython] What is a good way to determine OS platform with IronPython?

2011-01-10 Thread Douglas Blank
Now that IronPython runs on other operating systems, what is the recommended way to determine the os when running IP? sys.platform returns 'cli' across all, and sys.builtin_module_names includes 'nt' on all. Perhaps something like: def platform(): data = sys.getwindowsversion() # major, mi

Re: [IronPython] Rescue clause?

2011-01-10 Thread Jeff Hardy
On Mon, Jan 10, 2011 at 11:22 AM, Daniel Jennings wrote: > Is there some sort of crazy IronPython rescue keyword, or is this just from > an IronRuby copy/paste? From http://ironpython.net/documentation/dotnet/ : > > *snip* > > When I googled it I only ran into Ruby docs discussing ‘rescue’, so I a

[IronPython] Rescue clause?

2011-01-10 Thread Daniel Jennings
Is there some sort of crazy IronPython rescue keyword, or is this just from an IronRuby copy/paste? From http://ironpython.net/documentation/dotnet/ : Given that raise results in the creation of both a Python exception object and a .NET exception object, and given that rescue can catch both Pyth

[IronPython] PyCon 2011 - Full talk and tutorial list now available!

2011-01-10 Thread Michael Foord
I'm very pleased to announce, on behalf of the PyCon 2011 Program committee, and entire PyCon 2011 volunteer staff, that the full list of PyCon 2011 talks is now public, and available! This was an especially hard year for the PyCon program committee: we had over 200 proposals for only 95 total s