From 426dd3312f31245622ec15c07824e406de9a76cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Tomulik?= Date: Wed, 7 May 2014 17:23:03 +0200 Subject: [PATCH] minor corrections to python documentation --- Doc/Manual/Python.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html index dcfd7427e..9b86652f4 100644 --- a/Doc/Manual/Python.html +++ b/Doc/Manual/Python.html @@ -5412,7 +5412,7 @@ class M3: pass

We edit pkg1/mod2.py and want to import module -pkg1/pkg2/pkg3.py in order to derive from class M3. We can +pkg1/pkg2/mod3.py in order to derive from class M3. We can write appropriate Python code in several ways, for example:

@@ -5570,8 +5570,8 @@ from __future__ import absolute_import

Imports in __init__.py are handy when you want to populate a package's namespace with names imported from other modules. In SWIG based projects this approach may also be used to split large pieces of code into -smaller modules, compile them in parallel and then re-assemble everything at another -level by importing submodules' contents in __init__.py, for +smaller modules, compile them in parallel and then re-assemble everything at +runtime by importing submodules' contents in __init__.py, for example.

Unfortunately import directives in __init__.py may cause problems,