prepare readme and universal whee

Author: RonnyPfannschmidt

README.txt

@@ -5,11 +5,15 @@ With apipkg you can control the exported namespace of a
 python package and greatly reduce the number of imports for your users.
 It is a `small pure python module`_ that works on virtually all Python
 versions, including CPython2.3 to Python3.1, Jython and PyPy.  It co-operates
-well with Python's ``help()`` system, custom importers (PEP302) and common 
-command line completion tools.  
+well with Python's ``help()`` system, custom importers (PEP302) and common
+command line completion tools.
 
 Usage is very simple: you can require 'apipkg' as a dependency or you
-can copy paste the <100 Lines of code into your project.
+can copy paste the <200 Lines of code into your project.
+
+As extra it will automatically set package.__version__
+to your distribution version.
+
 
 Tutorial example
 -------------------
@@ -26,14 +30,14 @@ and exports two objects imported from different modules::
         }
     }
 
-The package is initialized with a dictionary as namespace. 
+The package is initialized with a dictionary as namespace.
 
-You need to create a ``_mypkg`` package with a ``somemodule.py`` 
+You need to create a ``_mypkg`` package with a ``somemodule.py``
 and ``othermodule.py`` containing the respective classes.
-The ``_mypkg`` is not special - it's a completely 
-regular python package. 
+The ``_mypkg`` is not special - it's a completely
+regular python package.
 
-Namespace dictionaries contain ``name: value`` mappings 
+Namespace dictionaries contain ``name: value`` mappings
 where the value may be another namespace dictionary or
 a string specifying an import location.  On accessing
 an namespace attribute an import will be performed::
@@ -62,23 +66,23 @@ loaded when they are accessed.   This means:
 Including apipkg in your package
 --------------------------------------
 
-If you don't want to add an ``apipkg`` dependency to your package you 
-can copy the `apipkg.py`_ file somewhere to your own package, 
+If you don't want to add an ``apipkg`` dependency to your package you
+can copy the `apipkg.py`_ file somewhere to your own package,
 for example ``_mypkg/apipkg.py`` in the above example.  You
 then import the ``initpkg`` function from that new place and
-are good to go. 
+are good to go.
 
 .. _`small pure python module`:
 .. _`apipkg.py`: http://bitbucket.org/hpk42/apipkg/src/tip/apipkg.py
 
-Feedback? 
+Feedback?
 -----------------------
 
-If you have questions you are welcome to 
+If you have questions you are welcome to
 
-* join the #pylib channel on irc.freenode.net 
-* subscribe to the http://codespeak.net/mailman/listinfo/py-dev list. 
+* join the #pylib channel on irc.freenode.net
+* subscribe to the http://codespeak.net/mailman/listinfo/py-dev list.
 * create an issue on http://bitbucket.org/hpk42/apipkg/issues
 
-have fun, 
+have fun,
 holger krekel

apipkg.py

@@ -9,8 +9,6 @@
 import sys
 from types import ModuleType
 
-__version__ = '1.3.dev'
-
 
 def _py_abspath(path):
     """
@@ -36,6 +34,10 @@ def distribution_version(name):
         return dist.version
 
 
+# this will yield wrong data for vendore versions
+__version__ = distribution_version(__name__)
+
+
 def initpkg(pkgname, exportdefs, attr=dict()):
     """ initialize given package from the export definitions. """
     oldmod = sys.modules.get(pkgname)