From: Brian Z. <bz...@zi...> - 2005-06-08 13:24:34
|
The majority of the changes have been committed to the head for new-style migration and a number of the collection classes have been integrated with the Java Collections so I think we're getting ready for a first run at a release. This release will certainly be alpha-quality since much of the code is new, not all the tests pass and the installer has not received widespread testing but we should really start getting some feedback on outstanding issues and such beyond our testing. I know there are components missing from the initial proposal, namely rewriting the Py[Java]Class|Instance stuff but I think that's going to have to wait. What other items are missing? Can we begin a quick catalog? Frank, Clark and Oti, do you have know of any missing features that would keep us from releasing soon? thanks, brian |
From: Frank W. <fwi...@gm...> - 2005-06-08 16:12:23
|
Brian, I don't know of any issues that should block an alpha release. Frank On 6/8/05, Brian Zimmer <bz...@zi...> wrote: >=20 > The majority of the changes have been committed to the head for > new-style migration and a number of the collection classes have been > integrated with the Java Collections so I think we're getting ready for > a first run at a release. >=20 > This release will certainly be alpha-quality since much of the code is > new, not all the tests pass and the installer has not received > widespread testing but we should really start getting some feedback on > outstanding issues and such beyond our testing. >=20 > I know there are components missing from the initial proposal, namely > rewriting the Py[Java]Class|Instance stuff but I think that's going to > have to wait. >=20 > What other items are missing? Can we begin a quick catalog? Frank, > Clark and Oti, do you have know of any missing features that would keep > us from releasing soon? >=20 > thanks, >=20 > brian >=20 >=20 > |
From: Oti <oh...@ya...> - 2005-06-08 21:43:28
|
[ Brian Zimmer ] > The majority of the changes have been committed to the head for > new-style migration and a number of the collection classes have been > integrated with the Java Collections so I think we're getting ready > for > a first run at a release. > > This release will certainly be alpha-quality since much of the code > is > new, not all the tests pass and the installer has not received > widespread testing but we should really start getting some feedback > on > outstanding issues and such beyond our testing. > > I know there are components missing from the initial proposal, namely > > rewriting the Py[Java]Class|Instance stuff but I think that's going > to > have to wait. > > What other items are missing? Can we begin a quick catalog? Frank, > Clark and Oti, do you have know of any missing features that would > keep > us from releasing soon? Hello Brian, agreeing with Frank, I don't see any blockers for an alpha. After browsing through todo's and mails, I found the following 'polishing' tasks: - documentation for build and install - build against informix jdbc driver, too - remove 1.1 support (in the code) - remove differences between generated and checked in parser classes - reorganize installer (move to /src folder) but none of them is required for an alpha, IMHO. Best wishes, Oti. |
From: brian z. <bz...@zi...> - 2005-06-09 11:15:54
|
> Hello Brian, > > agreeing with Frank, I don't see any blockers for an alpha. > After browsing through todo's and mails, I found the following > 'polishing' tasks: > > - documentation for build and install This we should start finishing up. > - build against informix jdbc driver, too I can look into this. > - remove 1.1 support (in the code) This would be good to remove soon. At least compiling with > JDK1.2 allows us to use the collections and other additions without all the runtime decision making forced by running only on JDK 1.1. > - remove differences between generated and checked in parser classes What do you mean by this? > - reorganize installer (move to /src folder) Yeah this isn't as important for the release as it is for maintenance. thanks, brian |
From: Samuele P. <ped...@st...> - 2005-06-12 13:14:37
|
Brian Zimmer wrote: > > The majority of the changes have been committed to the head for > new-style migration and a number of the collection classes have been > integrated with the Java Collections so I think we're getting ready for > a first run at a release. > > This release will certainly be alpha-quality since much of the code is > new, not all the tests pass and the installer has not received > widespread testing but we should really start getting some feedback on > outstanding issues and such beyond our testing. > this is a comparison between running tests on the head and the last time I did, there are some improvements but also some regressions, see the "failed were passed" tests. LOC /Users/pedronis/jy-ws/jython/Lib/test = jy-newstyle LOC /Users/pedronis/jy-ws/jython-head/Lib/test = jy-newstyle LOC /Users/pedronis/Py_22/python/dist/src/Lib/test = py22 LOC d:\wsjy\jython\Lib\test = jy-newstyle LOC d:\area22\python\dist\src\Lib\test = py22 217 test(s) (+2) 108 passed (-6) 11 failed, were passed [py22]test_atexit [py22]test_builtin [py22]test_cfgparser [py22]test_contains [py22]test_httplib [py22]test_re [py22]test_string [py22]test_userstring [jy-newstyle]test_javashell [jy-newstyle]test_string [jy-newstyle]test_types 4 passed, were failed [py22]test_hmac [py22]test_struct [py22]test_zlib [jy-newstyle]test_descrtut 1 passed, were skipped [py22]test_wave 52 skipped (-1) 51 skipped, were skipped [py22]test_al [py22]test_audioop [py22]test_bsddb [py22]test_capi [py22]test_cd [py22]test_cl [py22]test_cmath [py22]test_commands [py22]test_crypt [py22]test_curses [py22]test_dbm [py22]test_dl [py22]test_email_codecs [py22]test_fcntl [py22]test_fork1 [py22]test_gc [py22]test_gdbm [py22]test_gl [py22]test_grp [py22]test_hotshot [py22]test_imageop [py22]test_imgfile [py22]test_linuxaudiodev [py22]test_locale [py22]test_minidom [py22]test_mmap [py22]test_nis [py22]test_openpty [py22]test_parser [py22]test_poll [py22]test_pty [py22]test_pwd [py22]test_pyexpat [py22]test_regex [py22]test_rgbimg [py22]test_rotor [py22]test_sax [py22]test_select [py22]test_signal [py22]test_socket_ssl [py22]test_socketserver [py22]test_strop [py22]test_sunaudiodev [py22]test_sundry [py22]test_symtable [py22]test_timing [py22]test_ucn [py22]test_unicode_file [py22]test_unicodedata [py22]test_winreg [py22]test_winsound 1 new skipped [jy-newstyle]test_javalist 57 failed (+9) 44 failed, were failed [py22]test_asynchat [py22]test_binop [py22]test_class [py22]test_cpickle [py22]test_descr [py22]test_descrtut [py22]test_doctest2 [py22]test_extcall [py22]test_frozen [py22]test_funcattrs [py22]test_generators [py22]test_getargs [py22]test_gettext [py22]test_inspect [py22]test_iter [py22]test_largefile [py22]test_long_future [py22]test_longexp [py22]test_marshal [py22]test_mhlib [py22]test_mutants [py22]test_new [py22]test_operations [py22]test_os [py22]test_pickle [py22]test_pkgimport [py22]test_popen2 [py22]test_profile [py22]test_profilehooks [py22]test_pyclbr [py22]test_repr [py22]test_scope [py22]test_socket [py22]test_sre [py22]test_tempfile [py22]test_threaded_import [py22]test_threadedtempfile [py22]test_trace [py22]test_types [py22]test_unary [py22]test_unicode [py22]test_userlist [py22]test_uu [py22]test_weakref 1 new failed [jy-newstyle]test_array 1 failed, were skipped [py22]test_array 108 passed (-6) 101 passed, were passed [py22]test_MimeWriter [py22]test_StringIO [py22]test___all__ [py22]test___future__ [py22]test_augassign [py22]test_base64 [py22]test_bastion [py22]test_binascii [py22]test_binhex [py22]test_bisect [py22]test_bufio [py22]test_calendar [py22]test_call [py22]test_cgi [py22]test_charmapcodec [py22]test_codecs [py22]test_codeop [py22]test_coercion [py22]test_compare [py22]test_compile [py22]test_complex [py22]test_cookie [py22]test_copy_reg [py22]test_difflib [py22]test_dircache [py22]test_doctest [py22]test_dospath [py22]test_dumbdbm [py22]test_errno [py22]test_exceptions [py22]test_file [py22]test_fileinput [py22]test_fnmatch [py22]test_format [py22]test_fpformat [py22]test_future [py22]test_getopt [py22]test_glob [py22]test_global [py22]test_grammar [py22]test_gzip [py22]test_hash [py22]test_htmllib [py22]test_htmlparser [py22]test_import [py22]test_long [py22]test_mailbox [py22]test_math [py22]test_md5 [py22]test_mimetools [py22]test_mimetypes [py22]test_multifile [py22]test_netrc [py22]test_ntpath [py22]test_opcodes [py22]test_operator [py22]test_pep247 [py22]test_pkg [py22]test_posixpath [py22]test_pow [py22]test_pprint [py22]test_queue [py22]test_quopri [py22]test_random [py22]test_rfc822 [py22]test_richcmp [py22]test_sgmllib [py22]test_sha [py22]test_strftime [py22]test_structseq [py22]test_thread [py22]test_threading [py22]test_time [py22]test_tokenize [py22]test_traceback [py22]test_unpack [py22]test_urllib [py22]test_urllib2 [py22]test_urlparse [py22]test_userdict [py22]test_xmllib [py22]test_xmlrpc [py22]test_xreadline [py22]test_zipfile [jy-newstyle]test_janoninner [jy-newstyle]test_jbasic [jy-newstyle]test_joverload [jy-newstyle]test_jreload [jy-newstyle]test_jser [jy-newstyle]test_jsubclass [jy-newstyle]test_jy_compile [jy-newstyle]test_jy_internals [jy-newstyle]test_math [jy-newstyle]test_methods [jy-newstyle]test_opcodes [jy-newstyle]test_operations [jy-newstyle]test_pow [jy-newstyle]test_re [jy-newstyle]test_thread [jy-newstyle]test_time [jy-newstyle]test_unpack 2 new passed [jy-newstyle]test_enumerate [jy-newstyle]test_sets 2 vanished passed [jy-newstyle]test_jarray [jy-newstyle]test_runner |
From: Frank W. <fwi...@gm...> - 2005-06-12 15:05:54
|
> this is a comparison between running tests on the head and the last time= =20 > I did, there are some improvements but also some regressions, see > the "failed were passed" tests. The following (at least) [py22]test_cfgparser [py22]test_httplib [py22]test_userstring have a problem with calls like s.split(None, 1). The generated code does not handle skipped defaults well at this point. I'm thinking of extending gexpose.py to handle default values perhaps with a syntax like: expose_meth: :o split s?(" ") i? to insert a default value of " " which would result in code like this in exposed_split: public PyObject __call__(PyObject arg0,PyObject arg1) { //new part if (arg0 =3D=3D null) { arg0 =3D " "; } //end new part try { return self.str_split(arg0.asString(0),arg1.asInt(1)); } catch (PyObject.ConversionException e) { String msg; switch (e.index) { case 1: msg=3D"expected an integer"; break; case 0: msg=3D"expected a string"; break; default: msg=3D"xxx"; } throw Py.TypeError(msg); } } I'm just starting this, and I'm guessing the embedded space in this case will be a problem. Any syntax suggestions for gexpose.py? Frank |
From: Samuele P. <ped...@st...> - 2005-06-12 15:41:23
|
Frank Wierzbicki wrote: >>this is a comparison between running tests on the head and the last time >>I did, there are some improvements but also some regressions, see >>the "failed were passed" tests. > > > The following (at least) > [py22]test_cfgparser > [py22]test_httplib > [py22]test_userstring > > have a problem with calls like s.split(None, 1). The generated code > does not handle skipped defaults well at this point. I'm thinking of > extending gexpose.py to handle default values perhaps with a syntax > like: gexpose has already that syntax for default values. But I don't think it is that useful to think in terms of "skipped" defaults. > > expose_meth: :o split s?(" ") i? but None is equivalent to .split() which is not equivalent at all with .split(" "). map(None, is similar, also in that case expressing things in term of a default is not simple (well in that case the default would be the identity but still not a short and sweet thing to express) In this case I think it is easier to introduce a type specifier that means None or string, such that for None it produces null, .split() is already by passing null to the 2 arg version. > > to insert a default value of " " which would result in code like this > in exposed_split: > > public PyObject __call__(PyObject arg0,PyObject arg1) { > //new part > if (arg0 == null) { > arg0 = " "; > } None will not be converted into null, this receives a PyObject directly. > //end new part > try { > return self.str_split(arg0.asString(0),arg1.asInt(1)); > } catch (PyObject.ConversionException e) { > String msg; > switch (e.index) { > case 1: > msg="expected an integer"; > break; > case 0: > msg="expected a string"; > break; > default: > msg="xxx"; > } > throw Py.TypeError(msg); > } > } > > I'm just starting this, and I'm guessing the embedded space in this > case will be a problem. > Any syntax suggestions for gexpose.py? > > Frank > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
From: Frank W. <fwi...@gm...> - 2005-06-12 16:13:39
|
> In this case I think it is easier to introduce a type specifier that > means None or string, such that for None it produces null, .split() is > already by passing null to the 2 arg version. Let me make sure I understand. I would need to add a method to PyObject like "asStringOrNull" (which from PyObject should just return asString()) and subclass that in PyNone so that it returns null, and then add a new type (probably a symbol that will replace the ? in "s?", maybe "s!") to gexpose.py that will use asStringOrNull. Frank |
From: Samuele P. <ped...@st...> - 2005-06-12 16:25:40
|
Frank Wierzbicki wrote: >>In this case I think it is easier to introduce a type specifier that >>means None or string, such that for None it produces null, .split() is >>already by passing null to the 2 arg version. > > Let me make sure I understand. I would need to add a method to > PyObject like "asStringOrNull" (which from PyObject should just return > asString()) and subclass that in PyNone so that it returns null, and > then add a new type (probably a symbol that will replace the ? in > "s?", maybe "s!") to gexpose.py that will use asStringOrNull. yes, for the syntax you could simply introduce s = string S = string or None I would go fot that route for now unless you have other obvious examples where you may want a or None modification. |
From: Brian Z. <bz...@zi...> - 2005-06-12 20:47:45
|
Frank, Are you working on implementing these changes this weekend? It looks like Samuele and you have come to agreement on the implementation, true? thanks, brian On Jun 12, 2005, at 11:13 AM, Frank Wierzbicki wrote: >> In this case I think it is easier to introduce a type specifier that >> means None or string, such that for None it produces null, .split() is >> already by passing null to the 2 arg version. > Let me make sure I understand. I would need to add a method to > PyObject like "asStringOrNull" (which from PyObject should just return > asString()) and subclass that in PyNone so that it returns null, and > then add a new type (probably a symbol that will replace the ? in > "s?", maybe "s!") to gexpose.py that will use asStringOrNull. > > Frank > |
From: Frank W. <fwi...@gm...> - 2005-06-12 21:46:50
|
Yes I'm going to try to get the PyString problems fixed tonight in the manner that Samuele and I discussed. The PyFile stuff is still under discussion so I'll work on that next (not likely tonight). Frank On 6/12/05, Brian Zimmer <bz...@zi...> wrote: > Frank, >=20 > Are you working on implementing these changes this weekend? It looks > like Samuele and you have come to agreement on the implementation, > true? >=20 > thanks, >=20 > brian >=20 > On Jun 12, 2005, at 11:13 AM, Frank Wierzbicki wrote: >=20 > >> In this case I think it is easier to introduce a type specifier that > >> means None or string, such that for None it produces null, .split() is > >> already by passing null to the 2 arg version. > > Let me make sure I understand. I would need to add a method to > > PyObject like "asStringOrNull" (which from PyObject should just return > > asString()) and subclass that in PyNone so that it returns null, and > > then add a new type (probably a symbol that will replace the ? in > > "s?", maybe "s!") to gexpose.py that will use asStringOrNull. > > > > Frank > > >=20 > |
From: Brian Z. <bz...@zi...> - 2005-06-12 23:17:02
|
I applied the patch for PyFile locally and I'm in favor of it at this time. It provides the necessary mechanics for instantiating a PyFile without too much overhead of keywords (as I previously suggested) by deferring to the underlying constructors. The biggest issue I have with it is it's difficult to document as well as promoting the use of an internal class. Perhaps it would be better if only 'file' or 'open' supported this feature? In any event, it helps pass a number of the failing regrtests. I'm going to run the whole suite and then likely commit it. brian On Jun 12, 2005, at 04:46 PM, Frank Wierzbicki wrote: > Yes I'm going to try to get the PyString problems fixed tonight in the > manner that Samuele and I discussed. The PyFile stuff is still under > discussion so I'll work on that next (not likely tonight). > > Frank > > On 6/12/05, Brian Zimmer <bz...@zi...> wrote: >> Frank, >> >> Are you working on implementing these changes this weekend? It looks >> like Samuele and you have come to agreement on the implementation, >> true? >> >> thanks, >> >> brian >> >> On Jun 12, 2005, at 11:13 AM, Frank Wierzbicki wrote: >> >>>> In this case I think it is easier to introduce a type specifier that >>>> means None or string, such that for None it produces null, .split() >>>> is >>>> already by passing null to the 2 arg version. >>> Let me make sure I understand. I would need to add a method to >>> PyObject like "asStringOrNull" (which from PyObject should just >>> return >>> asString()) and subclass that in PyNone so that it returns null, and >>> then add a new type (probably a symbol that will replace the ? in >>> "s?", maybe "s!") to gexpose.py that will use asStringOrNull. >>> >>> Frank >>> >> >> > |
From: Brian Z. <bz...@zi...> - 2005-06-12 23:56:07
|
Frank and Clark, I assigned a couple of patches to you based on the work you've been doing recently (file and array). Apply them as you can. thanks, brian On Jun 12, 2005, at 04:46 PM, Frank Wierzbicki wrote: > Yes I'm going to try to get the PyString problems fixed tonight in the > manner that Samuele and I discussed. The PyFile stuff is still under > discussion so I'll work on that next (not likely tonight). > > Frank > > On 6/12/05, Brian Zimmer <bz...@zi...> wrote: >> Frank, >> >> Are you working on implementing these changes this weekend? It looks >> like Samuele and you have come to agreement on the implementation, >> true? >> >> thanks, >> >> brian >> >> On Jun 12, 2005, at 11:13 AM, Frank Wierzbicki wrote: >> >>>> In this case I think it is easier to introduce a type specifier that >>>> means None or string, such that for None it produces null, .split() >>>> is >>>> already by passing null to the 2 arg version. >>> Let me make sure I understand. I would need to add a method to >>> PyObject like "asStringOrNull" (which from PyObject should just >>> return >>> asString()) and subclass that in PyNone so that it returns null, and >>> then add a new type (probably a symbol that will replace the ? in >>> "s?", maybe "s!") to gexpose.py that will use asStringOrNull. >>> >>> Frank >>> >> >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office > luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
From: Frank W. <fwi...@gm...> - 2005-06-15 15:23:00
|
I have most of the work done to pass the Python 2.3 version of test_types.py (which also necessitates bringing in test_long.py from 2.3). I'll probably feel comfortable with over the weekend sometime.=20 But I have a couple of questions. Most importantly, should I hold off until the alpha release is out?=20 The code changes touch many classes in minor ways (mainly due to returning PyObject instead of PyInteger from __int__). Is there a way to specify classmethods in gexpose.py? dict has a classmethod "fromkeys". Thanks, Frank |
From: Brian Z. <bz...@zi...> - 2005-06-13 01:29:07
|
Frank, The bugtests tests are failing because PyString is missing isunicode. It looks like it was modified in the class but that the expose script doesn't have it? thanks, brian |
From: Frank W. <fwi...@gm...> - 2005-06-13 02:54:06
|
I'll look into it. I'm sure I just missed it. Thanks, Frank On 6/12/05, Brian Zimmer <bz...@zi...> wrote: > Frank, >=20 > The bugtests tests are failing because PyString is missing isunicode. > It looks like it was modified in the class but that the expose script > doesn't have it? >=20 > thanks, >=20 > brian >=20 > |
From: Brian Z. <bz...@zi...> - 2005-06-13 13:25:59
|
Thanks for patching it. brian Frank Wierzbicki wrote: > I'll look into it. I'm sure I just missed it. > > Thanks, > Frank > On 6/12/05, Brian Zimmer <bz...@zi...> wrote: > >>Frank, >> >>The bugtests tests are failing because PyString is missing isunicode. >>It looks like it was modified in the class but that the expose script >>doesn't have it? >> >>thanks, >> >>brian >> >> > > |
From: Brian Z. <bz...@zi...> - 2005-06-12 23:35:42
|
I'm upgrading the version of test_contains in the Jython test suite with the version from Python 2.3. I updated PyString to allow 'ab' in 'abc' to evaluate correctly (prior to 2.3 it would raise an exception if the left hand side was not a character). This will fix test_contains. brian On Jun 12, 2005, at 08:16 AM, Samuele Pedroni wrote: > Brian Zimmer wrote: >> The majority of the changes have been committed to the head for >> new-style migration and a number of the collection classes have been >> integrated with the Java Collections so I think we're getting ready >> for a first run at a release. >> This release will certainly be alpha-quality since much of the code >> is new, not all the tests pass and the installer has not received >> widespread testing but we should really start getting some feedback >> on outstanding issues and such beyond our testing. > > this is a comparison between running tests on the head and the last > time I did, there are some improvements but also some regressions, see > the "failed were passed" tests. > > LOC /Users/pedronis/jy-ws/jython/Lib/test = jy-newstyle > LOC /Users/pedronis/jy-ws/jython-head/Lib/test = jy-newstyle > LOC /Users/pedronis/Py_22/python/dist/src/Lib/test = py22 > LOC d:\wsjy\jython\Lib\test = jy-newstyle > LOC d:\area22\python\dist\src\Lib\test = py22 > 217 test(s) (+2) > 108 passed (-6) > 11 failed, were passed > [py22]test_atexit > [py22]test_builtin > [py22]test_cfgparser > [py22]test_contains > [py22]test_httplib > [py22]test_re > [py22]test_string > [py22]test_userstring > [jy-newstyle]test_javashell > [jy-newstyle]test_string > [jy-newstyle]test_types > 4 passed, were failed > [py22]test_hmac > [py22]test_struct > [py22]test_zlib > [jy-newstyle]test_descrtut > 1 passed, were skipped > [py22]test_wave > 52 skipped (-1) > 51 skipped, were skipped > [py22]test_al > [py22]test_audioop > [py22]test_bsddb > [py22]test_capi > [py22]test_cd > [py22]test_cl > [py22]test_cmath > [py22]test_commands > [py22]test_crypt > [py22]test_curses > [py22]test_dbm > [py22]test_dl > [py22]test_email_codecs > [py22]test_fcntl > [py22]test_fork1 > [py22]test_gc > [py22]test_gdbm > [py22]test_gl > [py22]test_grp > [py22]test_hotshot > [py22]test_imageop > [py22]test_imgfile > [py22]test_linuxaudiodev > [py22]test_locale > [py22]test_minidom > [py22]test_mmap > [py22]test_nis > [py22]test_openpty > [py22]test_parser > [py22]test_poll > [py22]test_pty > [py22]test_pwd > [py22]test_pyexpat > [py22]test_regex > [py22]test_rgbimg > [py22]test_rotor > [py22]test_sax > [py22]test_select > [py22]test_signal > [py22]test_socket_ssl > [py22]test_socketserver > [py22]test_strop > [py22]test_sunaudiodev > [py22]test_sundry > [py22]test_symtable > [py22]test_timing > [py22]test_ucn > [py22]test_unicode_file > [py22]test_unicodedata > [py22]test_winreg > [py22]test_winsound > 1 new skipped > [jy-newstyle]test_javalist > 57 failed (+9) > 44 failed, were failed > [py22]test_asynchat > [py22]test_binop > [py22]test_class > [py22]test_cpickle > [py22]test_descr > [py22]test_descrtut > [py22]test_doctest2 > [py22]test_extcall > [py22]test_frozen > [py22]test_funcattrs > [py22]test_generators > [py22]test_getargs > [py22]test_gettext > [py22]test_inspect > [py22]test_iter > [py22]test_largefile > [py22]test_long_future > [py22]test_longexp > [py22]test_marshal > [py22]test_mhlib > [py22]test_mutants > [py22]test_new > [py22]test_operations > [py22]test_os > [py22]test_pickle > [py22]test_pkgimport > [py22]test_popen2 > [py22]test_profile > [py22]test_profilehooks > [py22]test_pyclbr > [py22]test_repr > [py22]test_scope > [py22]test_socket > [py22]test_sre > [py22]test_tempfile > [py22]test_threaded_import > [py22]test_threadedtempfile > [py22]test_trace > [py22]test_types > [py22]test_unary > [py22]test_unicode > [py22]test_userlist > [py22]test_uu > [py22]test_weakref > 1 new failed > [jy-newstyle]test_array > 1 failed, were skipped > [py22]test_array > 108 passed (-6) > 101 passed, were passed > [py22]test_MimeWriter > [py22]test_StringIO > [py22]test___all__ > [py22]test___future__ > [py22]test_augassign > [py22]test_base64 > [py22]test_bastion > [py22]test_binascii > [py22]test_binhex > [py22]test_bisect > [py22]test_bufio > [py22]test_calendar > [py22]test_call > [py22]test_cgi > [py22]test_charmapcodec > [py22]test_codecs > [py22]test_codeop > [py22]test_coercion > [py22]test_compare > [py22]test_compile > [py22]test_complex > [py22]test_cookie > [py22]test_copy_reg > [py22]test_difflib > [py22]test_dircache > [py22]test_doctest > [py22]test_dospath > [py22]test_dumbdbm > [py22]test_errno > [py22]test_exceptions > [py22]test_file > [py22]test_fileinput > [py22]test_fnmatch > [py22]test_format > [py22]test_fpformat > [py22]test_future > [py22]test_getopt > [py22]test_glob > [py22]test_global > [py22]test_grammar > [py22]test_gzip > [py22]test_hash > [py22]test_htmllib > [py22]test_htmlparser > [py22]test_import > [py22]test_long > [py22]test_mailbox > [py22]test_math > [py22]test_md5 > [py22]test_mimetools > [py22]test_mimetypes > [py22]test_multifile > [py22]test_netrc > [py22]test_ntpath > [py22]test_opcodes > [py22]test_operator > [py22]test_pep247 > [py22]test_pkg > [py22]test_posixpath > [py22]test_pow > [py22]test_pprint > [py22]test_queue > [py22]test_quopri > [py22]test_random > [py22]test_rfc822 > [py22]test_richcmp > [py22]test_sgmllib > [py22]test_sha > [py22]test_strftime > [py22]test_structseq > [py22]test_thread > [py22]test_threading > [py22]test_time > [py22]test_tokenize > [py22]test_traceback > [py22]test_unpack > [py22]test_urllib > [py22]test_urllib2 > [py22]test_urlparse > [py22]test_userdict > [py22]test_xmllib > [py22]test_xmlrpc > [py22]test_xreadline > [py22]test_zipfile > [jy-newstyle]test_janoninner > [jy-newstyle]test_jbasic > [jy-newstyle]test_joverload > [jy-newstyle]test_jreload > [jy-newstyle]test_jser > [jy-newstyle]test_jsubclass > [jy-newstyle]test_jy_compile > [jy-newstyle]test_jy_internals > [jy-newstyle]test_math > [jy-newstyle]test_methods > [jy-newstyle]test_opcodes > [jy-newstyle]test_operations > [jy-newstyle]test_pow > [jy-newstyle]test_re > [jy-newstyle]test_thread > [jy-newstyle]test_time > [jy-newstyle]test_unpack > 2 new passed > [jy-newstyle]test_enumerate > [jy-newstyle]test_sets > 2 vanished passed > [jy-newstyle]test_jarray > [jy-newstyle]test_runner > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you > shotput > a projector? How fast can you ride your desk chair down the office > luge track? > If you want to score the big prize, get to know the little guy. Play > to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
From: Brian Z. <bz...@zi...> - 2005-06-16 02:03:23
|
Go ahead. I still want to commit the pep302 branch. I'll be out this weekend but I'm thinking the following weekend should be a good time to cut the alpha so you should have time to test. Please make sure to run the regrtest in Lib/test as it does a good job catching bugs. thanks, brian On Jun 15, 2005, at 10:22 AM, Frank Wierzbicki wrote: > I have most of the work done to pass the Python 2.3 version of > test_types.py (which also necessitates bringing in test_long.py from > 2.3). I'll probably feel comfortable with over the weekend sometime. > But I have a couple of questions. > > Most importantly, should I hold off until the alpha release is out? > The code changes touch many classes in minor ways (mainly due to > returning PyObject instead of PyInteger from __int__). > > Is there a way to specify classmethods in gexpose.py? dict has a > classmethod "fromkeys". > > Thanks, > Frank > |
From: Frank W. <fwi...@gm...> - 2005-06-16 12:46:15
|
I have been running them often. I've noticed that some recent changes (I believe yours) have fixed 15 or so testcases which is great -- leaving only :) 40some failers. We are really making some progress.=20 The 2.3 test_types only break py22 test_types and py22 test_long, which is expected since the 2.2 and 2.3 types have incompatibilities. Frank On 6/15/05, Brian Zimmer <bz...@zi...> wrote: > Go ahead. I still want to commit the pep302 branch. >=20 > I'll be out this weekend but I'm thinking the following weekend should > be a good time to cut the alpha so you should have time to test. > Please make sure to run the regrtest in Lib/test as it does a good job > catching bugs. >=20 > thanks, >=20 > brian |