Custom Search
|
Date: November 30, 2006
From: Kent Johnson <kent37@xxxxxxx>
In-reply-to:
<456EEA35.8010705@xxxxxxxxxxxx>
References:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers <456E0C06.2060704@xxxxxxxxxxxxxxxxxx> <456E2778.2060803@xxxxxxx> <456EE01C.3090209@xxxxxxxxxxxxxxxxxx> <456EE3F1.6000401@xxxxxxx> <456EEA35.8010705@xxxxxxxxxxxx>
Raghuram Devarakonda wrote: > I have been using jython 2.1 with jre 1.5 for quite some time now. The > platforms I use on include windows, linux, and solaris. I haven't found > any problems yet but may be I am not exercising the problematic parts. > Are there any specific issues with 1.5 and jython 2.1? I seem to have > downloaded jython in middle 2004. I have not used Jython 2.1 with Java 1.5 myself. When Java 1.5 came out there was some discussion on the list about problems so I avoided it. See the reference below or search the list archives for details. Kent > > Thanks, > Raghu. > > Kent Johnson wrote: >> Paul D. Fernhout wrote: >>> I released stuff myself with Jython that runs on 1.5 (but was built with >>> 1.4.2), but I was using a early slightly modified alpha build of 2.2 I >>> compiled myself; I did not even know Jython 2.1 did not run under 1.5. >>> Thanks for pointing that out. >> The official release of 2.1 does not run on 1.5. There is an unofficial >> build available that works with 1.5. A few more details here: >> http://sourceforge.net/mailarchive/message.php?msg_id=8079716 > > _____________________________________________________________________________ > > ATTENTION: > > The information contained in this message (including any files transmitted > with this message) may contain proprietary, trade secret or other > confidential and/or legally privileged information. Any pricing information > contained in this message or in any files transmitted with this message is > always confidential and cannot be shared with any third parties without prior > written approval from Syncsort. This message is intended to be read only by > the individual or entity to whom it is addressed or by their designee. If the > reader of this message is not the intended recipient, you are on notice that > any use, disclosure, copying or distribution of this message, in any form, is > strictly prohibited. If you have received this message in error, please > immediately notify the sender and/or Syncsort and destroy all copies of this > message in your possession, custody or control. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 30, 2006
From: "Raghuram Devarakonda" <raghu@xxxxxxxxxxxx>
In-reply-to:
<456EE3F1.6000401@xxxxxxx>
References:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers <456E0C06.2060704@xxxxxxxxxxxxxxxxxx> <456E2778.2060803@xxxxxxx> <456EE01C.3090209@xxxxxxxxxxxxxxxxxx> <456EE3F1.6000401@xxxxxxx>
I have been using jython 2.1 with jre 1.5 for quite some time now. The platforms I use on include windows, linux, and solaris. I haven't found any problems yet but may be I am not exercising the problematic parts. Are there any specific issues with 1.5 and jython 2.1? I seem to have downloaded jython in middle 2004. Thanks, Raghu. Kent Johnson wrote: > Paul D. Fernhout wrote: >> I released stuff myself with Jython that runs on 1.5 (but was built with >> 1.4.2), but I was using a early slightly modified alpha build of 2.2 I >> compiled myself; I did not even know Jython 2.1 did not run under 1.5. >> Thanks for pointing that out. > > The official release of 2.1 does not run on 1.5. There is an unofficial > build available that works with 1.5. A few more details here: > http://sourceforge.net/mailarchive/message.php?msg_id=8079716 _____________________________________________________________________________ ATTENTION: The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 30, 2006
From: Kent Johnson <kent37@xxxxxxx>
In-reply-to:
<456EE01C.3090209@xxxxxxxxxxxxxxxxxx>
References:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers <456E0C06.2060704@xxxxxxxxxxxxxxxxxx> <456E2778.2060803@xxxxxxx> <456EE01C.3090209@xxxxxxxxxxxxxxxxxx>
Paul D. Fernhout wrote: > I released stuff myself with Jython that runs on 1.5 (but was built with > 1.4.2), but I was using a early slightly modified alpha build of 2.2 I > compiled myself; I did not even know Jython 2.1 did not run under 1.5. > Thanks for pointing that out. The official release of 2.1 does not run on 1.5. There is an unofficial build available that works with 1.5. A few more details here: http://sourceforge.net/mailarchive/message.php?msg_id=8079716 Kent ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 30, 2006
From: "Paul D. Fernhout" <pdfernhout@xxxxxxxxxxxxxxxxxx>
In-reply-to:
<456E2778.2060803@xxxxxxx>
References:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers <456E0C06.2060704@xxxxxxxxxxxxxxxxxx> <456E2778.2060803@xxxxxxx>
Kent Johnson wrote: > Paul D. Fernhout wrote: > I would like to see support for Java 1.4.2 for the simple reason that > this is the latest release that works with Jython 2.1. I have avoided > upgrading to Java 1.5 for that reason. (I know, there is a build > available that works with 1.5...) I think there is some value in being > able to easily upgrade to Jython 2.2 without having to upgrade Java, and > in particular being able to easily switch between Jython 2.1 and 2.2. > > One very tangible benefit of easy switching will be more testing. I for > one have several medium sized applications written in Jython with > extensive test suites (for the apps). I'm looking forward to trying them > with Jython 2.2 when the beta comes out. If it is difficult to switch > between 2.1 and 2.2 that will make the testing more difficult and adds a > barrier to adoption of 2.2. > > That's my 2 cents, You've certainly convinced me. :-) You make a very good argument for compiling under and releasing for Java 1.4.2 for Jython 2.2. Especially now that the huge hardest hurdle of supporting new classes has been cleared, we will likely see and future releases to come out faster, and those could (from a testing standpoint) then be 1.5 only or later (to make the maintainers' lives easier). I released stuff myself with Jython that runs on 1.5 (but was built with 1.4.2), but I was using a early slightly modified alpha build of 2.2 I compiled myself; I did not even know Jython 2.1 did not run under 1.5. Thanks for pointing that out. --Paul Fernhout ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 30, 2006
From: Kent Johnson <kent37@xxxxxxx>
In-reply-to:
<456E0C06.2060704@xxxxxxxxxxxxxxxxxx>
References:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers <456E0C06.2060704@xxxxxxxxxxxxxxxxxx>
Paul D. Fernhout wrote: > Just to throw my two cents in on this again, *testing* and *maintenance* > is a big part of product development for a community. If no one is > stepping forward to offer to *test* or *maintain* in an ongoing and > serious way Jython on a particular platform, how can anyone really say it > is supported or appropriate for that platform, even if it compiles on it? You make a really good point. The desire and ability of the maintainers to support Java 1.2 should be considered. > So here is my proposal based on the needs for testing and maintenance, not > development. Jython can in theory compile under JDK 1.2 or 1.3. Make a > note of that in the documentation, but don't offer to support that (unless > the person who needs that support is willing to do it themselves, etc.) > Tell people if they want out of the box support for earlier JDKs use > Jython 2.1. Compile and release Jython 2.2 as supported for JDK 1.5 and > later (or if feeling generous, for JDK 1.4.2 forward). I would like to see support for Java 1.4.2 for the simple reason that this is the latest release that works with Jython 2.1. I have avoided upgrading to Java 1.5 for that reason. (I know, there is a build available that works with 1.5...) I think there is some value in being able to easily upgrade to Jython 2.2 without having to upgrade Java, and in particular being able to easily switch between Jython 2.1 and 2.2. One very tangible benefit of easy switching will be more testing. I for one have several medium sized applications written in Jython with extensive test suites (for the apps). I'm looking forward to trying them with Jython 2.2 when the beta comes out. If it is difficult to switch between 2.1 and 2.2 that will make the testing more difficult and adds a barrier to adoption of 2.2. That's my 2 cents, Kent ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: Leo User <leouser126@xxxxxxxxx>
In-reply-to:
<456E0C06.2060704@xxxxxxxxxxxxxxxxxx>
References:
<456E0C06.2060704@xxxxxxxxxxxxxxxxxx>
Someone on the JRuby lists talked about the companies he knows about use the recent version and the last version. So it sounded like in his case 1.4 and 1.5. But he stressed vendors will drop support for 1.4 once 1.6 is out, forcing alot to upgrade to 1.5. 1.6 is just around the corner... Im trying to think of problems Ive ran into by using 1.5 or 1.6 and jython.... leouser --- "Paul D. Fernhout" <pdfernhout@xxxxxxxxxxxxxxxxxx> wrote: > Just to throw my two cents in on this again, > *testing* and *maintenance* > is a big part of product development for a > community. If no one is > stepping forward to offer to *test* or *maintain* in > an ongoing and > serious way Jython on a particular platform, how can > anyone really say it > is supported or appropriate for that platform, even > if it compiles on it? > > It seems to me, even given Jython compiling under > Java 1.2, that Java > 1.4.2 or later (or probably better yet now 1.5 or > later as time has > passed, and 1.4.2 is already on its way out) is the > platform almost all > Jython users who would adopt Jython 2.2 are using. > Those are the Java > platforms a community with limited resources can > say, yes, the program has > been compiled there and heavily tested here, and you > are unlikely to be > extremely dissatisfied if you use it on that > platform. Even simple things > like screen shots, install directions, dealing with > bug fixes, and so on > may differ across platforms. Is most of the > community in a position to > even just speculate on how to fix a bug that, say, > only shows up in JVM > 1.2 or 1.3 (but not in 1.4 or 1.5) if one should pop > up? And, in a > community with limited resources, does anyone really > want to debug and > make these fixes as a priority? Have enough things > changes since then to > make that "promise" to run under 1.2 obsolete > relative to other priorities > even for the people promised? Will such people > really be significantly > harmed if that "promise" is broken and they have to > either stick with > Jython 2.1 or compile and support Jython 2.2 > themselves? Are there any > real Jython users out there who say they really need > a 1.2 version? If so, > please raise your hands. On the other hand, I'd > expect almost everyone > here uses Java 1.4.2 or later (with support for Java > ME being a different > issue, as someone else raised). > > I think Frank made a good decision to keep later > Java features out of > Jython 2.2 so it could in theory run under Java 1.2 > given how far things > had advanced. Someone could now easily compile it > under Java 1.2. and > support it themselves, and that flexibility is a > good thing. But as a > general release which presumably is going to be > supported and maintained > by people on this list, is messing around with bugs > from Java 1.2 or Java > 1.3 going to receive any level of priority here -- > or will they just > become unhappy at an implicit unkept promise that > they will get reasonable > support if Jython 2.2. is said to support those > versions of Java? > > Anyway, I know where people are coming from in terms > of saying that Jython > does not yet depend on JVM or Java features later > than 1.2. But > nonetheless, that dependency is only part of the > whole release and > maintenance cycle. Let me give you a concrete > example -- for one project I > had to be very careful to compile it only under Java > 1.4.2 because the > exact identical code would be compiled differently > under 1.5 and then > would not work under 1.4.2 (a class I used had added > methods in 1.5, thus > changing it's downwardly compatible signature I > think). So, essentially, > if Jython 2.2. is listed as being supported by Java > 1.2, then really any > released version needs to be compiled under Java > 1.2, because the > compatibility of compilation is more assured going > forward then going > backward. So, who here is going to always be willing > to do every binary > checkin for Jython 2.2 bug fixes under a JVM nobody > can easily get > nowadays? And if someone is willing here (I assume > Frank must be doing > development and compilation under 1.2 and plans to > use that for the > release?), how long will that last? So essentially, > a "1.2" compatible > Jython 2.2. is, essentially, just about already > orphaned on release in > that sense (unless, again, someone like Frank is > going to keep Java 1.2 on > his machine from now until whenever bug fixes for > 2.2 are no longer > accepted and new released are not made). > > So here is my proposal based on the needs for > testing and maintenance, not > development. Jython can in theory compile under JDK > 1.2 or 1.3. Make a > note of that in the documentation, but don't offer > to support that (unless > the person who needs that support is willing to do > it themselves, etc.) > Tell people if they want out of the box support for > earlier JDKs use > Jython 2.1. Compile and release Jython 2.2 as > supported for JDK 1.5 and > later (or if feeling generous, for JDK 1.4.2 > forward). > > Anyway, I am sorry if I am steeping on the toes of > JDK 1.2 users (if they > are out there?), but I am ultimately just trying to > make the life easier > for the maintainers of Jython so they can focus on > continuing to move it > forward :-) > > --Paul Fernhout > > Leo User wrote: > > Im not even sure where you'd get a 1.2 Java these > > days. I went looking at Sun's pages and can only > find > > 1.3 onward. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get > the chance to share your > opinions on IT & business topics through brief > surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: "Paul D. Fernhout" <pdfernhout@xxxxxxxxxxxxxxxxxx>
In-reply-to:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers
References:
<710760.22927.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.5 FROM_ENDS_IN_NUMS From: ends in numbers 2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers
Just to throw my two cents in on this again, *testing* and *maintenance* is a big part of product development for a community. If no one is stepping forward to offer to *test* or *maintain* in an ongoing and serious way Jython on a particular platform, how can anyone really say it is supported or appropriate for that platform, even if it compiles on it? It seems to me, even given Jython compiling under Java 1.2, that Java 1.4.2 or later (or probably better yet now 1.5 or later as time has passed, and 1.4.2 is already on its way out) is the platform almost all Jython users who would adopt Jython 2.2 are using. Those are the Java platforms a community with limited resources can say, yes, the program has been compiled there and heavily tested here, and you are unlikely to be extremely dissatisfied if you use it on that platform. Even simple things like screen shots, install directions, dealing with bug fixes, and so on may differ across platforms. Is most of the community in a position to even just speculate on how to fix a bug that, say, only shows up in JVM 1.2 or 1.3 (but not in 1.4 or 1.5) if one should pop up? And, in a community with limited resources, does anyone really want to debug and make these fixes as a priority? Have enough things changes since then to make that "promise" to run under 1.2 obsolete relative to other priorities even for the people promised? Will such people really be significantly harmed if that "promise" is broken and they have to either stick with Jython 2.1 or compile and support Jython 2.2 themselves? Are there any real Jython users out there who say they really need a 1.2 version? If so, please raise your hands. On the other hand, I'd expect almost everyone here uses Java 1.4.2 or later (with support for Java ME being a different issue, as someone else raised). I think Frank made a good decision to keep later Java features out of Jython 2.2 so it could in theory run under Java 1.2 given how far things had advanced. Someone could now easily compile it under Java 1.2. and support it themselves, and that flexibility is a good thing. But as a general release which presumably is going to be supported and maintained by people on this list, is messing around with bugs from Java 1.2 or Java 1.3 going to receive any level of priority here -- or will they just become unhappy at an implicit unkept promise that they will get reasonable support if Jython 2.2. is said to support those versions of Java? Anyway, I know where people are coming from in terms of saying that Jython does not yet depend on JVM or Java features later than 1.2. But nonetheless, that dependency is only part of the whole release and maintenance cycle. Let me give you a concrete example -- for one project I had to be very careful to compile it only under Java 1.4.2 because the exact identical code would be compiled differently under 1.5 and then would not work under 1.4.2 (a class I used had added methods in 1.5, thus changing it's downwardly compatible signature I think). So, essentially, if Jython 2.2. is listed as being supported by Java 1.2, then really any released version needs to be compiled under Java 1.2, because the compatibility of compilation is more assured going forward then going backward. So, who here is going to always be willing to do every binary checkin for Jython 2.2 bug fixes under a JVM nobody can easily get nowadays? And if someone is willing here (I assume Frank must be doing development and compilation under 1.2 and plans to use that for the release?), how long will that last? So essentially, a "1.2" compatible Jython 2.2. is, essentially, just about already orphaned on release in that sense (unless, again, someone like Frank is going to keep Java 1.2 on his machine from now until whenever bug fixes for 2.2 are no longer accepted and new released are not made). So here is my proposal based on the needs for testing and maintenance, not development. Jython can in theory compile under JDK 1.2 or 1.3. Make a note of that in the documentation, but don't offer to support that (unless the person who needs that support is willing to do it themselves, etc.) Tell people if they want out of the box support for earlier JDKs use Jython 2.1. Compile and release Jython 2.2 as supported for JDK 1.5 and later (or if feeling generous, for JDK 1.4.2 forward). Anyway, I am sorry if I am steeping on the toes of JDK 1.2 users (if they are out there?), but I am ultimately just trying to make the life easier for the maintainers of Jython so they can focus on continuing to move it forward :-) --Paul Fernhout Leo User wrote: > Im not even sure where you'd get a 1.2 Java these > days. I went looking at Sun's pages and can only find > 1.3 onward. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: Leo User <leouser126@xxxxxxxxx>
In-reply-to:
<ae0cc0d80611290913p5c0a3d01o8448421d58c506d3@xxxxxxxxxxxxxx>
References:
<ae0cc0d80611290913p5c0a3d01o8448421d58c506d3@xxxxxxxxxxxxxx>
Im not even sure where you'd get a 1.2 Java these days. I went looking at Sun's pages and can only find 1.3 onward. leouser --- Brian Schlining <bschlining@xxxxxxxxx> wrote: > I agree with Leo. > > The big problem I see with targeting JDK 1.2 and JDK > 1.3 is that soon > developers will have trouble getting those JDK's. > Sun is > 'end-of-lifeing' JDK 1.3. If you have a requirement > that people > wishing to contribute to Jython write to a JDK they > can't get; well, > you're going to run out of developers pretty quick. > > It looks like this project still has a very small > pool of developers. > If you try to cover too many targets (JDK 1.2-6.0, > J2SE, J2ME) with a > few developers, forward progress will be > SLLLOOOOOOWWW. And really, > with folks on this list already arguing about > whether Jython should be > described as 'inactive' or 'active', do you really > want to slow > development further? In my mind this is the scenario > you want: > 1) Crank out a 2.2. release. > 2) People realize Jython isn't dead. They use it, > they like > (Personally, I love it). > 3) People notice the project...it gets some buzz > again!! > 4) More developers sign on > 5) With more developers on board, the team can start > thinking about > the smaller Java niches, like J2ME. > > > > On 11/28/06, Leo User <leouser126@xxxxxxxxx> wrote: > > allright, either the first response was sent to > Oti or > > its entered the ether... > > > > Ok, so Im not sure I see the connection between > 1.2 > > and smaller devices. Usually I associate these > with > > J2ME which to my understanding isn't constrained > by > > what was 1.2 but is a subset of your typical > > J2SE(someone can fill the missing details for me > if > > they want). > > > > As to being compatible with the 1.2 release, I > guess I > > don't see the romance/use for doing so. 1.2 was > > released 9-10(more?) years ago and is no longer > > supported. I can see this as being a negative > selling > > point to any Java developer who may be interested > in > > developing Jython. Why would he want to sharpen > his > > skills on an obsolete Java when there are projects > out > > there that will exercise them on a modern Java? > > > > leouser > > > > > > --- Oti <ohumbel@xxxxxxxxx> wrote: > > > > > Hi, > > > > > > the current discussion IMHO applies for desktop > an > > > server users. > > > > > > But there are users which struggle to get Jython > > > running on smaller > > > VM's (cell phones, handhelds and the like). And > if I > > > recall correctly, > > > we sort of promised them to still support JDK > 1.2. > > > in Jython 2.2. But > > > I might be wrong. > > > > > > I'd say: let's open things up for releases > > 2.2, > > > and do not change > > > target JDK for the upcoming release. > > > > > > best wishes, > > > Oti. > > > > > > On 11/28/06, Leo User <leouser126@xxxxxxxxx> > wrote: > > > > Ive tossed the question as to what Java > version > > > the > > > > JRuby folks require to the JRuby mailing list. > > > They > > > > currently require 1.4.2 but are considering > 1.5 > > > for > > > > 1.0 release. Interestingly, their responses > so > > > far as > > > > to why their considering 1.5 haven't been > centered > > > > around whose using what Java version but > focused > > > on > > > > new things that can be used in Java 1.5 that > will > > > make > > > > a better implementation. > > > > > > > > leouser > > > > > > > > > > > > --- Petr Gladkikh <petrglad@xxxxxxxxx> wrote: > > > > > > > > > Hello. > > > > > > > > > > I think it would be sensible to take a > survey on > > > the > > > > > Jython's website > > > > > asking which version of Java users are using > or > > > > > would like to use so > > > > > there are no more vague guesses on the > topic. > > > > > > > > > > In my case, we are using JDK 1.4 only due to > > > lack of > > > > > STABLE packages > > > > > for Debian Linux. Our admins usually prefer > to > > > stay > > > > > on safe side with > > > > > that (even considering that only remaining > bugs > > > > > there are small > > > > > intaller glitch and licence issue :). But > with > > > > > opening Sun JDK we will > > > > > be able to switch to JDK 1.5 or even 1.6. > > > > > > > > > > That said with fully opened JDK there are no > > > more > > > > > hard reasons to use > > > > > older versions. > > > > > > > > > > So. IMO it would be perfectly valid to use > 1.5 > > > for > > > > > future releases and > > > > > 1.4 for current development. > > > > > > > > > > -- > > > > > Petr Gladkikh > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > Take Surveys. Earn Cash. Influence the > Future of > > > IT > > > > > Join SourceForge.net's Techsay panel and > you'll > > > get > > > > > the chance to share your > > > > > opinions on IT & business topics through > brief > > > > > surveys - and earn cash > > > > > > > > > > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > _______________________________________________ > > > > > Jython-dev mailing list > > > > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > > > > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > > > > > > > > > > > > > > > > > > > > > > > === message truncated === ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: "Brian Schlining" <bschlining@xxxxxxxxx>
In-reply-to:
<917384.71499.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<ba90a0a90611281315m3ba5b621w17661c7753024208@xxxxxxxxxxxxxx> <917384.71499.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
I agree with Leo. The big problem I see with targeting JDK 1.2 and JDK 1.3 is that soon developers will have trouble getting those JDK's. Sun is 'end-of-lifeing' JDK 1.3. If you have a requirement that people wishing to contribute to Jython write to a JDK they can't get; well, you're going to run out of developers pretty quick. It looks like this project still has a very small pool of developers. If you try to cover too many targets (JDK 1.2-6.0, J2SE, J2ME) with a few developers, forward progress will be SLLLOOOOOOWWW. And really, with folks on this list already arguing about whether Jython should be described as 'inactive' or 'active', do you really want to slow development further? In my mind this is the scenario you want: 1) Crank out a 2.2. release. 2) People realize Jython isn't dead. They use it, they like (Personally, I love it). 3) People notice the project...it gets some buzz again!! 4) More developers sign on 5) With more developers on board, the team can start thinking about the smaller Java niches, like J2ME. On 11/28/06, Leo User <leouser126@xxxxxxxxx> wrote: > allright, either the first response was sent to Oti or > its entered the ether... > > Ok, so Im not sure I see the connection between 1.2 > and smaller devices. Usually I associate these with > J2ME which to my understanding isn't constrained by > what was 1.2 but is a subset of your typical > J2SE(someone can fill the missing details for me if > they want). > > As to being compatible with the 1.2 release, I guess I > don't see the romance/use for doing so. 1.2 was > released 9-10(more?) years ago and is no longer > supported. I can see this as being a negative selling > point to any Java developer who may be interested in > developing Jython. Why would he want to sharpen his > skills on an obsolete Java when there are projects out > there that will exercise them on a modern Java? > > leouser > > > --- Oti <ohumbel@xxxxxxxxx> wrote: > > > Hi, > > > > the current discussion IMHO applies for desktop an > > server users. > > > > But there are users which struggle to get Jython > > running on smaller > > VM's (cell phones, handhelds and the like). And if I > > recall correctly, > > we sort of promised them to still support JDK 1.2. > > in Jython 2.2. But > > I might be wrong. > > > > I'd say: let's open things up for releases > 2.2, > > and do not change > > target JDK for the upcoming release. > > > > best wishes, > > Oti. > > > > On 11/28/06, Leo User <leouser126@xxxxxxxxx> wrote: > > > Ive tossed the question as to what Java version > > the > > > JRuby folks require to the JRuby mailing list. > > They > > > currently require 1.4.2 but are considering 1.5 > > for > > > 1.0 release. Interestingly, their responses so > > far as > > > to why their considering 1.5 haven't been centered > > > around whose using what Java version but focused > > on > > > new things that can be used in Java 1.5 that will > > make > > > a better implementation. > > > > > > leouser > > > > > > > > > --- Petr Gladkikh <petrglad@xxxxxxxxx> wrote: > > > > > > > Hello. > > > > > > > > I think it would be sensible to take a survey on > > the > > > > Jython's website > > > > asking which version of Java users are using or > > > > would like to use so > > > > there are no more vague guesses on the topic. > > > > > > > > In my case, we are using JDK 1.4 only due to > > lack of > > > > STABLE packages > > > > for Debian Linux. Our admins usually prefer to > > stay > > > > on safe side with > > > > that (even considering that only remaining bugs > > > > there are small > > > > intaller glitch and licence issue :). But with > > > > opening Sun JDK we will > > > > be able to switch to JDK 1.5 or even 1.6. > > > > > > > > That said with fully opened JDK there are no > > more > > > > hard reasons to use > > > > older versions. > > > > > > > > So. IMO it would be perfectly valid to use 1.5 > > for > > > > future releases and > > > > 1.4 for current development. > > > > > > > > -- > > > > Petr Gladkikh > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of > > IT > > > > Join SourceForge.net's Techsay panel and you'll > > get > > > > the chance to share your > > > > opinions on IT & business topics through brief > > > > surveys - and earn cash > > > > > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > _______________________________________________ > > > > Jython-dev mailing list > > > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > Want to start your own business? > > > Learn how on Yahoo! Small Business. > > > http://smallbusiness.yahoo.com/r-index > > > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of > > IT > > > Join SourceForge.net's Techsay panel and you'll > > get the chance to share your > > > opinions on IT & business topics through brief > > surveys - and earn cash > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > Jython-dev mailing list > > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get > > the chance to share your > > opinions on IT & business topics through brief > > surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Jython-dev mailing list > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > ____________________________________________________________________________________ > Want to start your own business? > Learn how on Yahoo! Small Business. > http://smallbusiness.yahoo.com/r-index > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: Samuele Pedroni <pedronis@xxxxxxxxxx>
In-reply-to:
<456D6FE9.7010004@xxxxxxxxxx>
References:
<96c4692d0611282239s29618026j724d954dd64ed431@xxxxxxxxxxxxxx> <456D6FE9.7010004@xxxxxxxxxx>
Samuele Pedroni wrote: > Charlie Groves wrote: > >> A few of the failures don't make sense to me yet, especially in the >> rich comparison operators. The tests seem to expect the comparison >> method on the subclass to be called no matter what when compared to >> the base class. i.e. from rich_comparisions >> >> class ZZ(complex): >> def __eq__(self, other): >> try: >> return abs(self - other) <= 1e-6 >> except: >> return NotImplemented >> >> zz = ZZ(1.0000003) >> assert zz == 1+0j >> assert 1+0j == zz >> >> fails on the second assertion. Somehow __eq__ should always be called >> on the subclass but I haven't seen anything about that in what I've >> read about new style classes. What am I missing? >> >> > that we all forgot to change PyObject to implement the new style rules > for picking __xxx__ > vs. __rxxx__, I think I told Brian that this was still missing but this > bit of information has got lost. > > We are still simply trying __xxx__ and then __rxxx__ in this order. Now > if the right hand side > operand is an instance of a subclass __rxxx__ should be tried first, > for __eq__ it means > trying __eq__(other, self) before __eq__(self, other). > > The real rule is even more complex and subtle (although this version of > the rule was introduced only in 2.3 > if I recall correctly), and depends on where the methods are found in > the hierarchy exactly. > > This needs to be done for all binary methods. > Also this is not going to be particularly pleasant to implement in a sane way, I may try to think about it a bit during the weekend. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: Samuele Pedroni <pedronis@xxxxxxxxxx>
In-reply-to:
<96c4692d0611282239s29618026j724d954dd64ed431@xxxxxxxxxxxxxx>
References:
<96c4692d0611282239s29618026j724d954dd64ed431@xxxxxxxxxxxxxx>
Charlie Groves wrote: > A few of the failures don't make sense to me yet, especially in the > rich comparison operators. The tests seem to expect the comparison > method on the subclass to be called no matter what when compared to > the base class. i.e. from rich_comparisions > > class ZZ(complex): > def __eq__(self, other): > try: > return abs(self - other) <= 1e-6 > except: > return NotImplemented > > zz = ZZ(1.0000003) > assert zz == 1+0j > assert 1+0j == zz > > fails on the second assertion. Somehow __eq__ should always be called > on the subclass but I haven't seen anything about that in what I've > read about new style classes. What am I missing? > that we all forgot to change PyObject to implement the new style rules for picking __xxx__ vs. __rxxx__, I think I told Brian that this was still missing but this bit of information has got lost. We are still simply trying __xxx__ and then __rxxx__ in this order. Now if the right hand side operand is an instance of a subclass __rxxx__ should be tried first, for __eq__ it means trying __eq__(other, self) before __eq__(self, other). The real rule is even more complex and subtle (although this version of the rule was introduced only in 2.3 if I recall correctly), and depends on where the methods are found in the hierarchy exactly. This needs to be done for all binary methods. regards. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: "Gwyn Evans" <gwyn.evans@xxxxxxxxx>
In-reply-to:
<96c4692d0611282239s29618026j724d954dd64ed431@xxxxxxxxxxxxxx>
References:
<96c4692d0611282239s29618026j724d954dd64ed431@xxxxxxxxxxxxxx>
On 29/11/06, Charlie Groves <charlie.groves@xxxxxxxxx> wrote: > A few of the failures don't make sense to me yet, especially in the > rich comparison operators. The tests seem to expect the comparison > method on the subclass to be called no matter what when compared to > the base class. i.e. from rich_comparisions > > class ZZ(complex): > def __eq__(self, other): > try: > return abs(self - other) <= 1e-6 > except: > return NotImplemented > > zz = ZZ(1.0000003) > assert zz == 1+0j > assert 1+0j == zz > > fails on the second assertion. Somehow __eq__ should always be called > on the subclass but I haven't seen anything about that in what I've > read about new style classes. What am I missing? Hi - I did a little googling & found the following in PEP207 (http://www.python.org/dev/peps/pep-0207/) which looks as if it explains that... 2. Additions of special methods for classes Classes wishing to support the rich comparison mechanisms must add one or more of the following new special methods: def __lt__(self, other): ... def __le__(self, other): ... def __gt__(self, other): ... def __ge__(self, other): ... def __eq__(self, other): ... def __ne__(self, other): ... Each of these is called when the class instance is the on the left-hand-side of the corresponding operators (<, <=, >, >=, ==, and != or <>). The argument other is set to the object on the right side of the operator. The return value of these methods is up to the class implementor (after all, that's the entire point of the proposal). If the object on the left side of the operator does not define an appropriate rich comparison operator (either at the C level or with one of the special methods, then the comparison is reversed, and the right hand operator is called with the opposite operator, and the two objects are swapped. This assumes that a < b and b > a are equivalent, as are a <= b and b >= a, and that == and != are commutative (e.g. a == b if and only if b == a). For example, if obj1 is an object which supports the rich comparison protocol and x and y are objects which do not support the rich comparison protocol, then obj1 < x will call the __lt__ method of obj1 with x as the second argument. x < obj1 will call obj1's __gt__ method with x as a second argument, and x < y will just use the existing (non-rich) comparison mechanism. /Gwyn ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: Oti <ohumbel@xxxxxxxxx>
In-reply-to:
<96c4692d0611281950v7bca2a7bwa5cc9a893fa9c7a4@xxxxxxxxxxxxxx>
References:
<96c4692d0611271800u2d0fdf0dq4f7a89a0011d58ee@xxxxxxxxxxxxxx> <4dab5f760611271921o68e2ca2exe436047b25c0c502@xxxxxxxxxxxxxx> <ba90a0a90611280408p24b0fc4bn1d4ed6c0353b190@xxxxxxxxxxxxxx> <96c4692d0611281950v7bca2a7bwa5cc9a893fa9c7a4@xxxxxxxxxxxxxx>
Wow, what a hit :-) Oti. On 11/29/06, Charlie Groves <charlie.groves@xxxxxxxxx> wrote: > Done in svn revision 3000. Not quite as satisfying as watching an > odometer roll over, but close. > > Charlie ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: "Charlie Groves" <charlie.groves@xxxxxxxxx>
I've been going through the failures in test_descr.py over the past few days to try to figure out how much is left to do for new style classes. The current status is at http://wiki.python.org/jython/CharlieGroves/DescrFailures. I've still got a few to look through, but I've gone through enough that I'm going to start fixing a few of the problems. I opened a slew of bugs and assigned them to beta1, 2 or no groups depending on how severe they looked. I don't have a good feel for how much the more advanced bits of new style classes are used so my categorization may be off. I'm sure that as some of these are fixed they're going to reveal other bugs lurking underneath them; even if my priorities are spot on this won't be the final list for beta1. The ones I'm working on are assigned to me so the others are fair game. A few of the failures don't make sense to me yet, especially in the rich comparison operators. The tests seem to expect the comparison method on the subclass to be called no matter what when compared to the base class. i.e. from rich_comparisions class ZZ(complex): def __eq__(self, other): try: return abs(self - other) <= 1e-6 except: return NotImplemented zz = ZZ(1.0000003) assert zz == 1+0j assert 1+0j == zz fails on the second assertion. Somehow __eq__ should always be called on the subclass but I haven't seen anything about that in what I've read about new style classes. What am I missing? That's probably enough for now. It's going to be exciting to start fixing some things rather than just filing bugs. Charlie ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: "Charlie Groves" <charlie.groves@xxxxxxxxx>
In-reply-to:
<456C0683.9040703@xxxxxx>
References:
<456C0683.9040703@xxxxxx>
Hi Ueli, I'm afraid the PyDev parser has moved on pretty significantly since it was pulled out of Jython; I don't know if bugs and/or fixes would line up at all. We've talked a little about reuniting the parsers as Jython gets closer to modern Python, but we haven't done anything in that direction. I'd suggest asking the PyDev people if they've got any ideas. If you do find something interesting, we'd definitely like to hear about it here. Sorry I couldn't be of more help, Charlie On 11/28/06, Ueli Kistler <ukistler@xxxxxx> wrote: > Hi, > > short: we need some advice/help on the parser :) > Please reply if you have some answers to the following questions. > > We're working on a Eclipse IDE Python Refactoring plug-in (open-source, > LTK based) > and are using Jython for checking our AST rewriters generated code > (http://sifsstud2.hsr.ch/peptic/wiki/RewriterTest)! > Btw happy coding for Jython 2.2 Final! > > > We're facing 2 main *challenges* using the jython parser (working on > PyDev's jython parser provided for Python 2.4/2.5 grammars): > 1. BeginColumn provided are wrong sometimes (we really need correct > values here for correct indentation) > 2. Visitor pattern is not applied for all nodes as expected (sometimes > nodes just get traversed.. unnoticed by the visitor) > .. less important: > 3. Num-Node didn't provide enough information (fixed by providing numType). > 4. Comments may disappear > > BeginColumn: > We would really appreciate some advise/help on this issue! > ClassDef/FunctionDef e.g. have correct beginColumn values... but e.g. > Assign-Nodes usually not. > Can someone check this behaviour and confirm ... give some advice how to > fix it or even provide a fix? > > Visitor: > I wrote an AST rewriter visitor (AST -> source code, works quite well) > and noticed that *not* all AST nodes are "properly" handled by the > visitor pattern. > > 1. Is there any reason why some nodes shouldn't be noticed by the > visitor (accept(VisitorIF visitor) just traversing its "child" nodes, > not calling any visit...-method provided) > 2. We would like to contribute our change proposals later ... is the > Jython/PyDev project working together? Where should be post change > proposals? > > Currently certain nodes are handled differently, but it would be helpful > if the visitor would work like expected. > Please visit > http://sifsstud2.hsr.ch/peptic/wiki/Rewriter#Nodeswithoutvisitorcallback > for a more detailed description. > > Num: > see http://sifsstud2.hsr.ch/peptic/wiki/Parser > > Comments: > see http://sifsstud2.hsr.ch/peptic/wiki/Parser > > > Thanks, > Ueli Kistler, Dennis Hunziker > http://sifsstud2.hsr.ch > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 29, 2006
From: "Charlie Groves" <charlie.groves@xxxxxxxxx>
In-reply-to:
<ba90a0a90611280408p24b0fc4bn1d4ed6c0353b190@xxxxxxxxxxxxxx>
References:
<96c4692d0611271800u2d0fdf0dq4f7a89a0011d58ee@xxxxxxxxxxxxxx> <4dab5f760611271921o68e2ca2exe436047b25c0c502@xxxxxxxxxxxxxx> <ba90a0a90611280408p24b0fc4bn1d4ed6c0353b190@xxxxxxxxxxxxxx>
Done in svn revision 3000. Not quite as satisfying as watching an odometer roll over, but close. Charlie On 11/28/06, Oti <ohumbel@xxxxxxxxx> wrote: > No objections from my side. > > Oti. > > On 11/28/06, Frank Wierzbicki <fwierzbicki@xxxxxxxxx> wrote: > > On 11/27/06, Charlie Groves <charlie.groves@xxxxxxxxx> wrote: > > > Hi, > > > > > > Any objections to moving /trunk/sandbox/jt to > > > /trunk/jython/src/templates in svn? That'll make merging from trunk > > > to 2.3 easier and mean the templates can be regenerated from trunk > > > without a second checkout. > > It sounds like a good idea to me. I say go ahead. > > > > -Frank > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Jython-dev mailing list > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: Leo User <leouser126@xxxxxxxxx>
In-reply-to:
<ba90a0a90611281315m3ba5b621w17661c7753024208@xxxxxxxxxxxxxx>
References:
<ba90a0a90611281315m3ba5b621w17661c7753024208@xxxxxxxxxxxxxx>
allright, either the first response was sent to Oti or its entered the ether... Ok, so Im not sure I see the connection between 1.2 and smaller devices. Usually I associate these with J2ME which to my understanding isn't constrained by what was 1.2 but is a subset of your typical J2SE(someone can fill the missing details for me if they want). As to being compatible with the 1.2 release, I guess I don't see the romance/use for doing so. 1.2 was released 9-10(more?) years ago and is no longer supported. I can see this as being a negative selling point to any Java developer who may be interested in developing Jython. Why would he want to sharpen his skills on an obsolete Java when there are projects out there that will exercise them on a modern Java? leouser --- Oti <ohumbel@xxxxxxxxx> wrote: > Hi, > > the current discussion IMHO applies for desktop an > server users. > > But there are users which struggle to get Jython > running on smaller > VM's (cell phones, handhelds and the like). And if I > recall correctly, > we sort of promised them to still support JDK 1.2. > in Jython 2.2. But > I might be wrong. > > I'd say: let's open things up for releases > 2.2, > and do not change > target JDK for the upcoming release. > > best wishes, > Oti. > > On 11/28/06, Leo User <leouser126@xxxxxxxxx> wrote: > > Ive tossed the question as to what Java version > the > > JRuby folks require to the JRuby mailing list. > They > > currently require 1.4.2 but are considering 1.5 > for > > 1.0 release. Interestingly, their responses so > far as > > to why their considering 1.5 haven't been centered > > around whose using what Java version but focused > on > > new things that can be used in Java 1.5 that will > make > > a better implementation. > > > > leouser > > > > > > --- Petr Gladkikh <petrglad@xxxxxxxxx> wrote: > > > > > Hello. > > > > > > I think it would be sensible to take a survey on > the > > > Jython's website > > > asking which version of Java users are using or > > > would like to use so > > > there are no more vague guesses on the topic. > > > > > > In my case, we are using JDK 1.4 only due to > lack of > > > STABLE packages > > > for Debian Linux. Our admins usually prefer to > stay > > > on safe side with > > > that (even considering that only remaining bugs > > > there are small > > > intaller glitch and licence issue :). But with > > > opening Sun JDK we will > > > be able to switch to JDK 1.5 or even 1.6. > > > > > > That said with fully opened JDK there are no > more > > > hard reasons to use > > > older versions. > > > > > > So. IMO it would be perfectly valid to use 1.5 > for > > > future releases and > > > 1.4 for current development. > > > > > > -- > > > Petr Gladkikh > > > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of > IT > > > Join SourceForge.net's Techsay panel and you'll > get > > > the chance to share your > > > opinions on IT & business topics through brief > > > surveys - and earn cash > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > Jython-dev mailing list > > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > > > > > > > > ____________________________________________________________________________________ > > Want to start your own business? > > Learn how on Yahoo! Small Business. > > http://smallbusiness.yahoo.com/r-index > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of > IT > > Join SourceForge.net's Techsay panel and you'll > get the chance to share your > > opinions on IT & business topics through brief > surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Jython-dev mailing list > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get > the chance to share your > opinions on IT & business topics through brief > surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: j.juneau@xxxxxxxxx
If anyone has Jython content that they would like to have distributed with the December 2006 newsletter, please post it on the wiki at: http://wiki.python.org/jython/JythonMonthly/Articles/December2006 The December distribution of Jython Monthly is scheduled for 12/12. Thanks! Josh Juneau ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: Oti <ohumbel@xxxxxxxxx>
In-reply-to:
<20061128143326.98739.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References:
<590465ac0611272159g21b26690v98578cf8846ff71a@xxxxxxxxxxxxxx> <20061128143326.98739.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Hi, the current discussion IMHO applies for desktop an server users. But there are users which struggle to get Jython running on smaller VM's (cell phones, handhelds and the like). And if I recall correctly, we sort of promised them to still support JDK 1.2. in Jython 2.2. But I might be wrong. I'd say: let's open things up for releases > 2.2, and do not change target JDK for the upcoming release. best wishes, Oti. On 11/28/06, Leo User <leouser126@xxxxxxxxx> wrote: > Ive tossed the question as to what Java version the > JRuby folks require to the JRuby mailing list. They > currently require 1.4.2 but are considering 1.5 for > 1.0 release. Interestingly, their responses so far as > to why their considering 1.5 haven't been centered > around whose using what Java version but focused on > new things that can be used in Java 1.5 that will make > a better implementation. > > leouser > > > --- Petr Gladkikh <petrglad@xxxxxxxxx> wrote: > > > Hello. > > > > I think it would be sensible to take a survey on the > > Jython's website > > asking which version of Java users are using or > > would like to use so > > there are no more vague guesses on the topic. > > > > In my case, we are using JDK 1.4 only due to lack of > > STABLE packages > > for Debian Linux. Our admins usually prefer to stay > > on safe side with > > that (even considering that only remaining bugs > > there are small > > intaller glitch and licence issue :). But with > > opening Sun JDK we will > > be able to switch to JDK 1.5 or even 1.6. > > > > That said with fully opened JDK there are no more > > hard reasons to use > > older versions. > > > > So. IMO it would be perfectly valid to use 1.5 for > > future releases and > > 1.4 for current development. > > > > -- > > Petr Gladkikh > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get > > the chance to share your > > opinions on IT & business topics through brief > > surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Jython-dev mailing list > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > > ____________________________________________________________________________________ > Want to start your own business? > Learn how on Yahoo! Small Business. > http://smallbusiness.yahoo.com/r-index > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: Leo User <leouser126@xxxxxxxxx>
In-reply-to:
<c0312f5d0611281251k6953b4e1o716b2136357543fb@xxxxxxxxxxxxxx>
References:
<c0312f5d0611281251k6953b4e1o716b2136357543fb@xxxxxxxxxxxxxx>
That is kinda nice. I was browsing the HotSpot source with OpenGrok: http://opengrok.neojava.org/hotspot though, its pretty different(doesn't give you a sense of the pulse) from looking at FishEye I do like being able to quickly bounce around the source. leouser --- Gwyn Evans <gwyn.evans@xxxxxxxxx> wrote: > I'd suggest a link to the FishEye page - > http://fisheye3.cenqua.com/browse/jython > > /Gwyn > > On 28/11/06, Leo User <leouser126@xxxxxxxxx> wrote: > > Hi, > > > > Wouldn't it be a nice Jython front page feature to > > take you to a web browsable view of the SVN > > repository? One of the critiques of the Jython > > project is that it looks dead. If there was an > easy > > SVN link the user could poke around and see if > there > > was any activity and get a different impression. > > > > thoughts folks? > > leouser > > > > > > > > > ____________________________________________________________________________________ > > Do you Yahoo!? > > Everyone is raving about the all-new Yahoo! Mail > beta. > > http://new.mail.yahoo.com > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of > IT > > Join SourceForge.net's Techsay panel and you'll > get the chance to share your > > opinions on IT & business topics through brief > surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Jython-dev mailing list > > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > -- > Download Wicket 1.2.3 now! - > http://wicketframework.org > ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: Leo User <leouser126@xxxxxxxxx>
Hi, Wouldn't it be a nice Jython front page feature to take you to a web browsable view of the SVN repository? One of the critiques of the Jython project is that it looks dead. If there was an easy SVN link the user could poke around and see if there was any activity and get a different impression. thoughts folks? leouser ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: Leo User <leouser126@xxxxxxxxx>
In-reply-to:
<590465ac0611272159g21b26690v98578cf8846ff71a@xxxxxxxxxxxxxx>
References:
<590465ac0611272159g21b26690v98578cf8846ff71a@xxxxxxxxxxxxxx>
Ive tossed the question as to what Java version the JRuby folks require to the JRuby mailing list. They currently require 1.4.2 but are considering 1.5 for 1.0 release. Interestingly, their responses so far as to why their considering 1.5 haven't been centered around whose using what Java version but focused on new things that can be used in Java 1.5 that will make a better implementation. leouser --- Petr Gladkikh <petrglad@xxxxxxxxx> wrote: > Hello. > > I think it would be sensible to take a survey on the > Jython's website > asking which version of Java users are using or > would like to use so > there are no more vague guesses on the topic. > > In my case, we are using JDK 1.4 only due to lack of > STABLE packages > for Debian Linux. Our admins usually prefer to stay > on safe side with > that (even considering that only remaining bugs > there are small > intaller glitch and licence issue :). But with > opening Sun JDK we will > be able to switch to JDK 1.5 or even 1.6. > > That said with fully opened JDK there are no more > hard reasons to use > older versions. > > So. IMO it would be perfectly valid to use 1.5 for > future releases and > 1.4 for current development. > > -- > Petr Gladkikh > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get > the chance to share your > opinions on IT & business topics through brief > surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: Oti <ohumbel@xxxxxxxxx>
In-reply-to:
<4dab5f760611271921o68e2ca2exe436047b25c0c502@xxxxxxxxxxxxxx>
References:
<96c4692d0611271800u2d0fdf0dq4f7a89a0011d58ee@xxxxxxxxxxxxxx> <4dab5f760611271921o68e2ca2exe436047b25c0c502@xxxxxxxxxxxxxx>
No objections from my side. Oti. On 11/28/06, Frank Wierzbicki <fwierzbicki@xxxxxxxxx> wrote: > On 11/27/06, Charlie Groves <charlie.groves@xxxxxxxxx> wrote: > > Hi, > > > > Any objections to moving /trunk/sandbox/jt to > > /trunk/jython/src/templates in svn? That'll make merging from trunk > > to 2.3 easier and mean the templates can be regenerated from trunk > > without a second checkout. > It sounds like a good idea to me. I say go ahead. > > -Frank > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jython-dev mailing list > Jython-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/jython-dev > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Date: November 28, 2006
From: "A.M. Kuchling" <amk@xxxxxx>