I have cp34837, cp34892, cp34910 fixed. I will make a PR. I also have some workarounds where I am not clear if they should get into release:
1. cp32331 - better unicode success rate in real application, but decreased number of unit test passed 2. update to installer to modify PATH and register .py extension. This could make users of both cpython and ironpython under windows unhappy. 3. importable version of multiprocessing - just to avoid import errors, this sounds a bit like cp34959 any comments on last 3 items are welcome. --pawel On Thu, Feb 27, 2014 at 10:07 PM, Jeff Hardy <jdha...@gmail.com> wrote: > I know everyone wants to hear about ItonPython 3, but it's time to > talk about IronPython 2.7 for a bit. Enough changes have accumulated > (thanks Pawel!) that it's probably time for another release. I'm > thinking Beta 1 around March 17, Beta 2 around April 1, and an > RC/final around April 15. Does anybody have anything they want to get > in but needs more time than that? The next release will probably be > around October. > > There's a bunch of low-hanging fruit in the issue tracker that could > conceivably make it in. I just created the 2.7.5 release on CodePlex, > so if you have edit access and you want something in 2.7.5, move it; > if you don't, leave a comment or an email here and I'll add it to > 2.7.5. > > If you have something you want fixed, the best way is to do it > yourself, and if you need any help, feel free to ask! > > - Jeff > _______________________________________________ > Ironpython-users mailing list > Ironpython-users@python.org > https://mail.python.org/mailman/listinfo/ironpython-users _______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
