On Wed, Feb 16, 2011 at 8:18 AM, Brian Curtin <brian.cur...@gmail.com> wrote: > On Wed, Feb 16, 2011 at 08:30, Jeff Hardy <jdha...@gmail.com> wrote: >> >> On Wed, Feb 9, 2011 at 12:47 PM, Vernon Cole <vernondc...@gmail.com> >> wrote: >> > Dear Group: >> > I would like to start a discussion about adding modules to the >> > IronPython >> > distribution which are not in the C-Python standard library. The idea >> > would >> > be to include more batteries. (FePy started out to do that, but has not >> > been seriously updated since IronPython 2.0 came out with a real, >> > genuine >> > Windows installer.) Good idea, or Bad? >> >> We certainly don't have to restrict ourselves to the same set of >> batteries as CPython. However, I'd be cautious about adding in too >> much simply because we don't have a huge pool of committers at the >> moment. > > Something to be careful of is inclusion of external code that still evolves > outside of the stdlib. When I install 2.7.1 complete with xyz library, a > week later when the author comes out with a great new feature, my install is > already out of date.
That's my biggest concern. As someone said, the stdlib is where code goes to die :). Another consideration is that the Python stdlib may one day become its own project, and we may not want to diverge from it. - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
