At 05:16 18.04.03 -0600, Kevin Butler wrote:
>License: Python license
>Used for building documentation
the templates that ships with it have the wrong color scheme and some
details. I have a fixed version to probably check under Tools but I should
change also the the build.xml to use them.
># if you ever do ant clean, you'll need to do
># cvs upd -APd # to get back the PythonGrammar* classes (clean removes them)
># unless you've installed javacc
># you'll need ~200 MB of RAM + swap for some of these tests
># If using a JRE, need to add a path to a JDK's tools.jar
># set JYTHON_JAVA_ARGS -Dtoolsjar=d:/pipeline/products/jdk/lib/tools.jar
># The javashell test is sensitive to other output from your jython script,
># and to multiple layers of script wrapping. Best to ensure that
># $JYTHONCVS/jython is the first 'jython' in yuor PATH.
>cd $JYTHON_CVS/Lib/test/ javatests
>javac -d .. *.java
general note: for a definitive release also an appropriate subset of
CPython test suite should be considered.
>- I just compiled it with whatever java compiler I had handy 1.4 something
>(will this be JDK1.1 compatible? no?)
if it is the sun one maybe not (up to 1.3.x -target 1.1 does the trick but
when I tried javac 1.4.0 even with -target 1.1,it produced classes
rejected by JDK 1.1.7/8, that's a bug on javac part, don't know if it is
solved with later releases)
>- On windows, so no readline library (how?)
>- just grabbing almost all the .py files from the PyXML distribution
general note not especially for 2.2a0: can we run their tests and be more
>- this has a mixed bag of all the Python 2.2 modules, except those
>with specific Jython counterparts. There will be library files that
>don't work. Let us know about them.
in some sense that will be spurious bugs/reports.
general note: the test suite should also tell that :)
>- The installer .class file built by this process doesn't work yet - it
>starts up, prompts for the OS (!),
>then fails to load os.properties
at worst given the nature of 2.2a0 you can simply zip the distribution.