Re: [IronPython] Curious about the development cycle and community involvement

2009-10-15 Thread Vernon Cole
There are many (otherwise intelligent seeming) managers with just such confused opinions about software. Some managers at the company I worked for until recently did not trust any open source code "because it might be insecure." Therefore, I was not supposed to use CPython, but IronPython was oka

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-15 Thread Count László de Almásy
from the FAQ-- "there are a few key benefits to limiting IronPython checkins to Microsoft employees. The most important being that some of our users have stated that they would be unable to install IronPython if it contained non-Microsoft intellectual property due to their employers' policies. We'd

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-14 Thread Dino Viehland
Tyler wrote: > Less than awesome. but a fair point. Do issues like this get logged back to > bugs.python.org? (IMHO that's a bug with Python, no reason to use > sre) It depends upon the issue. In this case I haven't logged something yet as I just realized this last week and haven't investigated i

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-14 Thread tyler
On Wed, 14 Oct 2009, Dino Viehland wrote: > > That said, if relative imports are borked, you don't really meet the > > "2.6 compatibility" bullet on the roadmap ;) > > This is a bug w/ relating to PEP 366 (Main module explicit relative > imports). I've added a simple repro to the bug and will

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-14 Thread Dino Viehland
> That said, if relative imports are borked, you don't really meet the > "2.6 compatibility" bullet on the roadmap ;) This is a bug w/ relating to PEP 366 (Main module explicit relative imports). I've added a simple repro to the bug and will look at fixing it for RC2. That being said json isn't

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-14 Thread Michael Foord
ment. Cheers -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of ty...@monkeypox.org Sent: Monday, October 12, 2009 8:03 PM To: users@lists.ironpython.com Subject: [IronPython] Curious about the development cycle and community invo

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-14 Thread Seo Sanghyeon
2009/10/14 : > One last question, if I were to run a fork of the Subversion tree > (git-svn(1) woot) which branch should I be using? I see IronPython_Main > and IronPython_2_6 in trunk/ and I'm not sure which contains active > development. IronPython_Main does. -- Seo Sanghyeon

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-13 Thread tyler
iginal Message- > From: users-boun...@lists.ironpython.com > [mailto:users-boun...@lists.ironpython.com] On Behalf Of ty...@monkeypox.org > Sent: Monday, October 12, 2009 8:03 PM > To: users@lists.ironpython.com > Subject: [IronPython] Curious about the development cycle and commun

Re: [IronPython] Curious about the development cycle and community involvement

2009-10-13 Thread David DiCato
.@monkeypox.org Sent: Monday, October 12, 2009 8:03 PM To: users@lists.ironpython.com Subject: [IronPython] Curious about the development cycle and community involvement Howdy, I'm a CPython developer by trade, but I've been watching IronPython evolve and have recently started p

[IronPython] Curious about the development cycle and community involvement

2009-10-12 Thread tyler
Howdy, I'm a CPython developer by trade, but I've been watching IronPython evolve and have recently started playing around with 2.6rc1 for a number of smaller projects [1][2]. While evaluating IronPython, I've run across a couple of issues [3] that I think I'm capable of helping to fix but I notic