I'm ok with removing the IronPython tools from the installer, but IronRuby's next release will most likely still use IronStudio, so I'd be careful removing it from git.
~Jimmy On Dec 11, 2011, at 4:53 PM, Shahrokh Mortazavi < smor...@exchange.microsoft.com> wrote: +1. Slightly biased tho. *From:* ironpython-users-bounces+smortaz=microsoft....@python.org [mailto: ironpython-users-bounces+smortaz=microsoft....@python.org] *On Behalf Of * Slide *Sent:* Sunday, December 11, 2011 1:25 PM *To:* Jeff Hardy *Cc:* ironpython-users@python.org *Subject:* Re: [Ironpython-users] Removal of IronPython Tools for Visual Studio from 2.7.2 On Sun, Dec 11, 2011 at 1:13 PM, Jeff Hardy <jdha...@gmail.com> wrote: Does anyone have an objections to removing the IronPython Tools for VS from 2.7.2? They're already disabled by default, they're a small annoyance to keep building, and the Python Tools for VS are so much better that I see no point in continuing to include them. - Jeff _______________________________________________ Ironpython-users mailing list Ironpython-users@python.org http://mail.python.org/mailman/listinfo/ironpython-users I'd say definitely do it. -- slide-o-blog http://slide-o-blog.blogspot.com/ _______________________________________________ Ironpython-users mailing list Ironpython-users@python.org http://mail.python.org/mailman/listinfo/ironpython-users
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org http://mail.python.org/mailman/listinfo/ironpython-users
