I propose we make tg a namespace for 2.0:
benefits:
branding. Turbogears can now have tg.whateverTurbogearsRelatedProject
you want. such as:
tg.repoze.who
tg.silverplate
tg.dbmechanic !!?
Here is the required change:
begin patch:
````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Index: setup.py
===================================================================
--- setup.py (revision 4567)
+++ setup.py (working copy)
@@ -23,6 +23,7 @@
url=url,
license=license,
packages=find_packages(exclude=['ez_setup', 'examples',
'tests']),
+ namespace_packages = ['tg'],
include_package_data=True,
zip_safe=False,
install_requires=[
Index: tg/__init__.py
===================================================================
--- tg/__init__.py (revision 4567)
+++ tg/__init__.py (working copy)
@@ -50,6 +50,9 @@
they make it possible for a group of TurboGears components to share
assumptions
about how things will work.
"""
+#make the tg namespace work
+__import__('pkg_resources').declare_namespace(__name__)
+
from tg.controllers import TGController, redirect, url
from tg.decorators import validate, expose
from tg.flash import flash, get_flash, get_status
``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
end patch
Committers, give the go-ahead and I will svn ci.
cheers.
-chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
