svn commit: r1387102 - /subversion/site/publish/docs/release-notes/1.8.html

[st...@apache.org]

Author: stsp
Date: Tue Sep 18 11:58:10 2012
New Revision: 1387102

URL: http://svn.apache.org/viewvc?rev=1387102&view=rev
Log:
* publish/docs/release-notes/1.8.html
  (swig-py-star): Move to compatibility section since it describes an
    incompatible change. Also drop link to viewvc, we shouldn't be trying
    to link individual commits from here. If people are interested in
    that kind of stuff they'll know where to look.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1387102&r1=1387101&r2=1387102&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Tue Sep 18 11:58:10 2012
@@ -309,6 +309,29 @@ to "yes".</p>
 
 </div>  <!-- client-cert-prompt-suppression -->
 
+<div class="h4" id="swig-py-star">
+<h4>Star-imports in the SWIG-Python bindings
+  <a class="sectionlink" href="#swig-py-star"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>The swig-py bindings have been changed to make <tt>*</tt>-imports
+of submodules to do the right thing:
+<tt>from svn.client import *</tt> will now import only symbols beginning with
+<tt>svn_</tt> or <tt>SVN_</tt>.  (Most of these symbols will be
+<tt>svn_client_*</tt> symbols, of course.)  Star-imports of <tt>from svn</tt> have
+not changed (they import <a
+href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/python/svn/core.py"
+>just the bare submodule names</a>: 'fs', 'ra', etc), and
+star imports of <tt>from svn.core</tt> currently imports some select symbols
+(notably 'Pool').</p>
+
+<p>This change is incompatible: code that expected symbols such as 'commit_txn'
+(in 'fs') and 'apr_initialize' to be pulled by a star-import will have to change.</p>
+
+</div>  <!-- swig-py-star --> 
+
+
 </div>  <!-- compat-misc -->
 
 </div>  <!-- compatibility -->
@@ -642,30 +665,6 @@ rare, and we anticipate the actual impac
 <p>Language bindings have mostly been updated for the new APIs, though
 some may lag more than others.</p>
 
-<div class="h4" id="swig-py-star">
-<h4>Star-imports in the SWIG-Python bindings
-  <a class="sectionlink" href="#swig-py-star"
-    title="Link to this section">&para;</a>
-</h4>
-
-<p>The swig-py bindings have been
-<a href="http://svn.apache.org/viewvc/?view=rev&amp;revision=r1303375"
->patched</a> to make <tt>*</tt>-imports of submodules to do the right thing:
-<tt>from svn.client import *</tt> will now import only symbols beginning with
-<tt>svn_</tt> or <tt>SVN_</tt>.  (Most of these symbols will be
-<tt>svn_client_*</tt> symbols, of course.)  Star-imports of <tt>from svn</tt> have
-not changed (they import <a
-href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/python/svn/core.py"
->just the bare submodule names</a>: 'fs', 'ra', etc), and
-star imports of <tt>from svn.core</tt> currently imports some select symbols
-(notably 'Pool').</p>
-
-<p>This change is incompatible: code that expected symbols such as 'commit_txn'
-(in 'fs') and 'apr_initialize' to be pulled by a star-import will have to change.
-We will consider amending the list of symbols exported to a star-import as needed.</p>
-
-</div>  <!-- swig-py-star --> 
-
 </div>  <!-- apis -->
 
 <div class="h3" id="bug-fixes">