From: Frank W. <fwi...@gm...> - 2009-02-28 17:54:41
|
>From weblog http://fwierzbicki.blogspot.com/2009/02/hoffstadters-law-and-jython-25.html Hoffstadter's Law states: "It always takes longer than you think, even when you consider Hoffstadter's Law." I thought by now I'd have a Jython 2.5 release, but alas I do not. I keep wanting to get just one more feature in, but I think the time has come to freeze things and get to release candidates. Most of 2.5 is quite solid, and it's time to get it out. I plan to put together what I think will be the last beta for Jython 2.5 this Friday. Some things are not going to make it in, for example I don't think ctypes will make it for 2.5.0. I looked over what we have so far and what I think it would take me to implement it, and I don't feel confident that I can really get it together as quickly as I would like and still feel sure it would be solid. My C skills are just a little too rusty to whip that together quickly. I may make ctypes my personal sprint target for PyCon 2009 since there will be lots of ctypes knowledge floating around, particularly from the PyPy folks whose ctypes work will make up a good chunk of Jython's support. I'm going to try to get modjy integrated into trunk, but if I don't make it by this Friday it will just have to stay separate for this release. Jythonc work has moved to the "clamp" project that Charlie Groves started on github. Hopefully we can get that together at the same time or shortly after 2.5.0 releases. If any committers have something they would like to get in at the last moment, now would be the time! -Frank |
From: Leo S. M. <leo...@gm...> - 2009-03-02 01:15:10
|
On Sat, Feb 28, 2009 at 2:54 PM, Frank Wierzbicki <fwi...@gm...> wrote: > >From weblog http://fwierzbicki.blogspot.com/2009/02/hoffstadters-law-and-jython-25.html > > Hoffstadter's Law states: "It always takes longer than you think, even > when you consider Hoffstadter's Law." > > I thought by now I'd have a Jython 2.5 release, but alas I do not. I > keep wanting to get just one more feature in, but I think the time has > come to freeze things and get to release candidates. Most of 2.5 is > quite solid, and it's time to get it out. I plan to put together what > I think will be the last beta for Jython 2.5 this Friday. I think that'd be great. All of us have nice features we would want in 2.5.0, but I agree that getting it out and add more goodies later is a wise plan :) -- Leo Soto M. http://blog.leosoto.com |
From: John S. <jo...@sz...> - 2009-03-03 22:21:28
|
On Sat, Feb 28, 2009 at 12:54 PM, Frank Wierzbicki <fwi...@gm...> wrote: > >From weblog http://fwierzbicki.blogspot.com/2009/02/hoffstadters-law-and-jython-25.html > > Hoffstadter's Law states: "It always takes longer than you think, even > when you consider Hoffstadter's Law." > > I thought by now I'd have a Jython 2.5 release, but alas I do not. I > keep wanting to get just one more feature in, but I think the time has > come to freeze things and get to release candidates. Most of 2.5 is > quite solid, and it's time to get it out. I plan to put together what > I think will be the last beta for Jython 2.5 this Friday. > > Some things are not going to make it in, for example I don't think > ctypes will make it for 2.5.0. I looked over what we have so far and > what I think it would take me to implement it, and I don't feel > confident that I can really get it together as quickly as I would like > and still feel sure it would be solid. My C skills are just a little > too rusty to whip that together quickly. I may make ctypes my personal > sprint target for PyCon 2009 since there will be lots of ctypes > knowledge floating around, particularly from the PyPy folks whose > ctypes work will make up a good chunk of Jython's support. I'm going > to try to get modjy integrated into trunk, but if I don't make it by > this Friday it will just have to stay separate for this release. > Jythonc work has moved to the "clamp" project that Charlie Groves > started on github. Hopefully we can get that together at the same time > or shortly after 2.5.0 releases. It's been hard to find time with Real Life, but I'm staying for sprints and was looking to help out with ctypes support. I know C *very* well. I'd be more than happy to help while I'm there. FWIW, I've looked at the actual ctypes module, and was heading down the path of reimplementing that in Python and use jna to actually communicate to the shared library... but looking at PyPy, they've done all the hard work. What is that we need to expose? What needs to be written? BTW, I won't be offended if you tell me to jump off a bridge... especially since I haven't helped since last time. -John |
From: Frank W. <fwi...@gm...> - 2009-03-03 23:15:24
|
On Tue, Mar 3, 2009 at 5:21 PM, John Szakmeister <jo...@sz...> wrote: > It's been hard to find time with Real Life, but I'm staying for > sprints and was looking to help out with ctypes support. I know C > *very* well. > > I'd be more than happy to help while I'm there. FWIW, I've looked at > the actual ctypes module, and was heading down the path of > reimplementing that in Python and use jna to actually communicate to > the shared library... but looking at PyPy, they've done all the hard > work. What is that we need to expose? What needs to be written? Jim Baker started to port over PyPy's support. The result so far is [jython-home]/LIb/_rawffi.py and [jython-home]/Lib/test/test__rawffi.py. It looks like Jim was porting test by test from the same file in PyPy (test__rawffi.py). If you are already familiar with PyPy's approach this stuff should look pretty familiar. We are using JNA as the internal part for the parts that PyPy does in rpython, then we plan to just use the pure python parts from PyPy as-is. I still hope to freeze this Friday - do you think you could have it together by then? It would be great if you could, it was a hard decision for me to drop it. BTW, even if you do just push it forward without it being enough for Friday, I think we'd still like to get it in for 2.5.1. Thanks! -Frank |
From: Frank W. <fwi...@gm...> - 2009-03-03 23:25:06
|
On Tue, Mar 3, 2009 at 6:15 PM, Frank Wierzbicki <fwi...@gm...> wrote: > from PyPy as-is. I still hope to freeze this Friday - do you think > you could have it together by then? I'm sorry, just read back and I see that you are talking about doing this at the sprints -- which is still great, I think 2.5.1 is really the right time for it. Thanks! -Frank |
From: John S. <jo...@sz...> - 2009-03-04 00:45:57
|
On Tue, Mar 3, 2009 at 6:16 PM, Frank Wierzbicki <fwi...@gm...> wrote: > On Tue, Mar 3, 2009 at 6:15 PM, Frank Wierzbicki <fwi...@gm...> wrote: >> from PyPy as-is. I still hope to freeze this Friday - do you think >> you could have it together by then? > I'm sorry, just read back and I see that you are talking about doing > this at the sprints -- which is still great, I think 2.5.1 is really > the right time for it. I doubt I can get it done by Friday (I just have too much going on), but I absolutely believe we can crank it out at PyCon. Later! -John |
From: Frank W. <fwi...@gm...> - 2009-03-04 03:03:31
|
On Tue, Mar 3, 2009 at 7:45 PM, John Szakmeister <jo...@sz...> wrote: > On Tue, Mar 3, 2009 at 6:16 PM, Frank Wierzbicki <fwi...@gm...> wrote: >> On Tue, Mar 3, 2009 at 6:15 PM, Frank Wierzbicki <fwi...@gm...> wrote: >>> from PyPy as-is. I still hope to freeze this Friday - do you think >>> you could have it together by then? >> I'm sorry, just read back and I see that you are talking about doing >> this at the sprints -- which is still great, I think 2.5.1 is really >> the right time for it. > > I doubt I can get it done by Friday (I just have too much going on), > but I absolutely believe we can crank it out at PyCon. Really, it's great that you want to work on it at PyCon - just some misreading on my part, thanks! -Frank |