> I will certainly give up before this delay. > At the moment, 1/3 of the files in the test suite pass without error, > they were zero yesterday. > We need volunteers to help us and implement the failing/missing parts!
0 to 1/3 is big progress. Sounds to me like the <6 mo time frame might be the right one. I unfortunately can't contribute code/patches at this point (I don't have the time-freedom or competence in JIT's or C++ to try), but when you have 64-bit code that supports the multiprocessing module ready for end-user testing, I'll be eager to install it and try it against my code, and of course I'll let you know of any problems. Sounds like it's not quite there yet, but I'll continue to follow developments. Perhaps popping up here sometimes to ask again about progress. I'm excited about the work on 64-bit and multiprocessing... Best, Gary -- Gary Robinson CTO Emergent Discovery, LLC personal email: [email protected] work email: [email protected] Company: http://www.emergentdiscovery.com Blog: http://www.garyrobinson.net On Sep 24, 2010, at 12:56 PM, Amaury Forgeot d'Arc wrote: > Hi, > 2010/9/24 Gary Robinson <[email protected]>: >>> "Longer than you want" >> >> Ain't that the truth! :) >> >> And yet, if you felt like one of the following blocks if time was more >> likely than the others, I'd be very interested in knowing: >> >> < 6 months >> < 1 year >> < 2 years > > I will certainly give up before this delay. > At the moment, 1/3 of the files in the test suite pass without error, > they were zero yesterday. > We need volunteers to help us and implement the failing/missing parts! > > -- > Amaury Forgeot d'Arc _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
