You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by bu...@apache.org on 2012/08/23 02:33:42 UTC

svn commit: r829814 - in /websites/staging/lucene/trunk/content: ./ pylucene/jcc/features.html

Author: buildbot
Date: Thu Aug 23 00:33:42 2012
New Revision: 829814

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/   (props changed)
    websites/staging/lucene/trunk/content/pylucene/jcc/features.html

Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 23 00:33:42 2012
@@ -1 +1 @@
-1376328
+1376331

Modified: websites/staging/lucene/trunk/content/pylucene/jcc/features.html
==============================================================================
--- websites/staging/lucene/trunk/content/pylucene/jcc/features.html (original)
+++ websites/staging/lucene/trunk/content/pylucene/jcc/features.html Thu Aug 23 00:33:42 2012
@@ -149,14 +149,14 @@ information and operating system specifi
 Python version used:</p>
 <ul>
 <li>python 2.7: <b>python -m jcc</b></li>
-<li>python 2.6: <b>python -m jcc.<strong>main</strong></b></li>
+<li>python 2.6: <b>python -m jcc.__main__</b></li>
 <li>python 2.5: <b>python -m jcc</b></li>
 <li>python 2.4:<ul>
-<li>no setuptools: <b>python <i>site-packages</i>/jcc/<strong>init</strong>.py</b></li>
-<li>with setuptools: <b>python <i>site-packages</i>/<i>jcc egg directory</i>/jcc/<strong>init</strong>.py</b></li>
+<li>no setuptools: <b>python <i>site-packages</i>/jcc/__init__.py</b></li>
+<li>with setuptools: <b>python <i>site-packages</i>/<i>jcc egg directory</i>/jcc/__init__.py</b></li>
 </ul>
 </li>
-<li>python 2.3: <b>python <i>site-packages</i>/<i>jcc egg directory</i>/jcc/<strong>init</strong>.py</b></li>
+<li>python 2.3: <b>python <i>site-packages</i>/<i>jcc egg directory</i>/jcc/__init__.py</b></li>
 </ul>
 <h2 id="generating-c-and-python-wrappers-with-jcc">Generating C++ and Python wrappers with JCC</h2>
 <p>JCC started as a C++ code generator for hiding the gory details of
@@ -304,7 +304,7 @@ via <i>--jar</i> are copied into the res
 egg as resources and added to the extension
 module's <i>CLASSPATH</i> variable. Classes or JAR files that
 are required by the classes contained in the argument JAR files need
-to be made findable via JCC's <i>--classpath</code> command line
+to be made findable via JCC's <i>--classpath</i> command line
 argument. At runtime, these need to be appended to the
 extension's <i>CLASSPATH</i> variable before starting the VM
 with <i>initVM(CLASSPATH)</i>.</p>
@@ -726,7 +726,7 @@ class _analyzer(PythonAnalyzer):
       return _tokenStream()
 </code></pre>
 
-<p>When an <i><strong>init</strong>()</i> is declared, <i>super()</i>
+<p>When an <i>__init__()</i> is declared, <i>super()</i>
 must be called or else the Java wrapper class will not know about
 the Python instance it needs to invoke.</p>
 <p>When a java extension class declares native methods for which there
@@ -803,7 +803,7 @@ extension class was defined in Java as d
 section by calling the <i>instantiate()</i> method on the 
 PythonVM instance. This method takes two string parameters, the
 name of the Python module and the name of the Python class to
-import and instantiate from it. The <i><strong>init</strong>()</i>
+import and instantiate from it. The <i>__init__()</i>
 constructor on this class must be callable without any parameters
 and, if defined, must call <i>super()</i> in order to
 initialize the Java side. The <i>instantiate()</i> method is