javaclass

Change of README.txt

161:b3d6020a2737
README.txt
     1.1 --- a/README.txt	Mon Jan 24 20:08:56 2005 +0100
     1.2 +++ b/README.txt	Mon Jan 24 20:42:23 2005 +0100
     1.3 @@ -12,8 +12,8 @@
     1.4  
     1.5    python setup.py install
     1.6  
     1.7 -I don't think distutils supports uninstall, but the installation just adds the
     1.8 -java and javaclass packages to your site-packages directory and the
     1.9 +I don't think distutils supports uninstall, but the installation just adds
    1.10 +the java and javaclass packages to your site-packages directory and the
    1.11  runclass.py program to the same bin directory that python resides in.
    1.12  
    1.13  Testing
    1.14 @@ -57,8 +57,8 @@
    1.15    import javaclass.classhook
    1.16  
    1.17  (Other modules reside in the javaclass package, so it is possible to access
    1.18 -them without changing Python's import mechanisms, should such modification be
    1.19 -undesirable or unnecessary.)
    1.20 +them without changing Python's import mechanisms, should such modification
    1.21 +be undesirable or unnecessary.)
    1.22  
    1.23  Importing Non-package Classes
    1.24  -----------------------------
    1.25 @@ -118,12 +118,13 @@
    1.26  
    1.27       python tools/wrap.py examples/Tkinter/tkjava Tkinter
    1.28  
    1.29 -     Since the Java class files, if left in the processed directory, would be
    1.30 -     detected and imported using the special import hook, and since this would
    1.31 -     result in two conflicting implementations being imported (with possibly the
    1.32 -     non-functional Java classes being made available instead of the generated
    1.33 -     wrapper classes), the wrap.py tool removes all processed class files,
    1.34 -     leaving only Python source files in the processed directory.
    1.35 +     Since the Java class files, if left in the processed directory, would
    1.36 +     be detected and imported using the special import hook, and since this
    1.37 +     would result in two conflicting implementations being imported (with
    1.38 +     possibly the non-functional Java classes being made available instead
    1.39 +     of the generated wrapper classes), the wrap.py tool removes all
    1.40 +     processed class files, leaving only Python source files in the
    1.41 +     processed directory.
    1.42  
    1.43    4. The Java classes which use the wrapped Python libraries can now be
    1.44       imported and used as described above. The wrapper package (tkjava in
    1.45 @@ -136,6 +137,9 @@
    1.46  Issues
    1.47  ------
    1.48  
    1.49 +The test program crashes, fairly quickly under Python 2.4, too. There seems
    1.50 +to be some kind of memory allocation problem.
    1.51 +
    1.52  Investigate better exception raising. Currently, exceptions have to be
    1.53  derived from object so that object.__new__ can be used upon them. However,
    1.54  this seems to prevent them from being raised, and they need to be wrapped
    1.55 @@ -150,7 +154,8 @@
    1.56  
    1.57  Update the javaclass/__init__.py __version__ attribute.
    1.58  Update the release notes (see above).
    1.59 -Check the setup.py file and ensure that all package directories are mentioned.
    1.60 +Check the setup.py file and ensure that all package directories are
    1.61 +mentioned.
    1.62  Tag, export.
    1.63  Rename ClassFile to javaclass (and add the release to the directory name).
    1.64  Archive, upload.