django-page-cms - Project Hosting on Google Code

Yesterday 36 hours ago 3thPartyApps (a way to integrate 3th party apps into the CMS admin interfa...) Wiki page commented on by matburnham - This doesn't seem to work for me. Specifically I get 'Caught an exception while rendering: No module named urlconf_registry' if I try to use the admin after adding a call to register_urlconf. It seems that there is no pages.urlconf_registry module? This is with the 1.0.9 code. This doesn't seem to work for me. Specifically I get 'Caught an exception while rendering: No module named urlconf_registry' if I try to use the admin after adding a call to register_urlconf. It seems that there is no pages.urlconf_registry module? This is with the 1.0.9 code. 37 hours ago issue 185 (Pages failing appear in admin page list) commented on by roger.bumgarner - I'm hitting this exact bug in both the downloaded version and the latest svn but this fix doesnt work. ### URLS.PY from django.conf.urls.defaults import * # Uncomment the next two lines to enable the admin: from django.contrib import admin admin.autodiscover() urlpatterns = patterns('', (r'^admin/', include(admin.site.urls)), url(r'^pages/', include('pages.urls')), ) I get this error whenever I try and view admin/pages/pages: Template error: In template /var/lib/python-support/python2.5/pages/templates/admin/pages/page/change_list_table.html, error at line 28 I'm hitting this exact bug in both the downloaded version and the latest svn but this fix doesnt work. ### URLS.PY from django.conf.urls.defaults import * # Uncomment the next two lines to enable the admin: from django.contrib import admin admin.autodiscover() urlpatterns = patterns('', (r'^admin/', include(admin.site.urls)), url(r'^pages/', include('pages.urls')), ) I get this error whenever I try and view admin/pages/pages: Template error: In template /var/lib/python-support/python2.5/pages/templates/admin/pages/page/change_list_table.html, error at line 28 Last 7 days Dec 17, 2009 issue 191 (patch: Fix TinyMCE behavior) commented on by mkriheli - Ignore it, I'll create it as pull request on github Ignore it, I'll create it as pull request on github Dec 15, 2009 issue 188 (Hebrew translation) Status changed by batiste.bieler - I added you translation files: http://github.com/batiste/django-page- cms/commit/75d186c0c245aee743a97c50311b6a65672fcc3b Thanks again Status: Fixed I added you translation files: http://github.com/batiste/django-page- cms/commit/75d186c0c245aee743a97c50311b6a65672fcc3b Thanks again Status: Fixed Dec 15, 2009 issue 190 (pages ) commented on by bruno.felix - Seems nice to me :) (no conflict with django variable names) Seems nice to me :) (no conflict with django variable names) Dec 15, 2009 issue 189 (patch: RTL support for pages in admin) commented on by mkriheli - My full name is Meir Kriheli, 10x. BTW, I've made the patch against a svn checkout from google code, should I work with the git hub repo instead ? My full name is Meir Kriheli, 10x. BTW, I've made the patch against a svn checkout from google code, should I work with the git hub repo instead ? Dec 15, 2009 issue 189 (patch: RTL support for pages in admin) Status changed by batiste.bieler - Hey, thanks for the contribution! http://github.com/batiste/django-page- cms/commit/0e9ef67a6fb7c04396d51fdbf094b629abc13506 If you give me your full name I will include it to the AUTHORS file. Status: Fixed Hey, thanks for the contribution! http://github.com/batiste/django-page- cms/commit/0e9ef67a6fb7c04396d51fdbf094b629abc13506 If you give me your full name I will include it to the AUTHORS file. Status: Fixed Dec 15, 2009 issue 190 (pages ) commented on by batiste.bieler - We need to rename this variable pages. It far to generic. What about pages_navigation? We need to rename this variable pages. It far to generic. What about pages_navigation? Dec 15, 2009 issue 191 (patch: Fix TinyMCE behavior) reported by mkriheli - The following patch fixes the follwong problems with the TinyMCE widget: 1. Since it didn't accepts kwargs like other widgets' __init__, creating TinyMCE widgets from placeholders.py's get_widget() always raised a TypeError and `language` parameter never passed in except, since it passes `page` which TinyMCE's __init__ didn't expect. 2. Using mutable in a function declaration is a bad idea. Pass None and check for that in the function body. For more info see http://www.python.org/doc/current/reference/compound_stmts.html#function-definitions 3. The hard coded `mce_attrs` in TinyMCE's __init__ overwrites django-tinymce's TINYMCE_DEFAULT_CONFIG. One should be able to override hard coded behavior with custom settings, so take it into account. Cheers The following patch fixes the follwong problems with the TinyMCE widget: 1. Since it didn't accepts kwargs like other widgets' __init__, creating TinyMCE widgets from placeholders.py's get_widget() always raised a TypeError and `language` parameter never passed in except, since it passes `page` which TinyMCE's __init__ didn't expect. 2. Using mutable in a function declaration is a bad idea. Pass None and check for that in the function body. For more info see http://www.python.org/doc/current/reference/compound_stmts.html#function-definitions 3. The hard coded `mce_attrs` in TinyMCE's __init__ overwrites django-tinymce's TINYMCE_DEFAULT_CONFIG. One should be able to override hard coded behavior with custom settings, so take it into account. Cheers Dec 15, 2009 issue 190 (pages ) commented on by bruno.felix - oops, sorry for the title. "pages: load_pages <> Paginator conflict" would have been nice (but can't change) oops, sorry for the title. "pages: load_pages <> Paginator conflict" would have been nice (but can't change) Dec 14, 2009 issue 190 (pages ) reported by bruno.felix - What steps will reproduce the problem? 1. use {% load_pages %} {% for page in pages %} {% pages_menu page %} {% endfor %} in a site wide base template 2. create a view using pagination in an object_list generic view from django.conf.urls.defaults import * from django.contrib.auth.models import User urlpatterns = patterns('django.views.generic.list_detail', (r'userlist/$', 'object_list', { 'queryset': User.objects.all(), 'paginate_by': 10, 'template_name': 'test/user_list.html', } ), ) What is the expected output? What do you see instead? expect a list paginated TemplateDoesNotExist at /test/userlist/ test/user_list.html Request Method: GET Request URL: http://localhost:8000/test/userlist/?page=2 Exception Type: TemplateDoesNotExist Exception Value: test/user_list.html problem is: 'pages' is supposed to be an int for pagination can be fixed by modifiing LoadPagesNode in pages_tags Are you using the trunk version or a released version of this CMS? r781 If you can write a test that reproduce the problem, there is better chance it will be resolved quickly. What steps will reproduce the problem? 1. use {% load_pages %} {% for page in pages %} {% pages_menu page %} {% endfor %} in a site wide base template 2. create a view using pagination in an object_list generic view from django.conf.urls.defaults import * from django.contrib.auth.models import User urlpatterns = patterns('django.views.generic.list_detail', (r'userlist/$', 'object_list', { 'queryset': User.objects.all(), 'paginate_by': 10, 'template_name': 'test/user_list.html', } ), ) What is the expected output? What do you see instead? expect a list paginated TemplateDoesNotExist at /test/userlist/ test/user_list.html Request Method: GET Request URL: http://localhost:8000/test/userlist/?page=2 Exception Type: TemplateDoesNotExist Exception Value: test/user_list.html problem is: 'pages' is supposed to be an int for pagination can be fixed by modifiing LoadPagesNode in pages_tags Are you using the trunk version or a released version of this CMS? r781 If you can write a test that reproduce the problem, there is better chance it will be resolved quickly. Dec 14, 2009 issue 189 (patch: RTL support for pages in admin) reported by mkriheli - Right now django-page-cms looks bad when using the admin in RTL (right-to-left written) languages. Attached a patch which fixes most of the issues. See the attached screen shots for examples. Cheers -- Meir Right now django-page-cms looks bad when using the admin in RTL (right-to-left written) languages. Attached a patch which fixes most of the issues. See the attached screen shots for examples. Cheers -- Meir Last 30 days Dec 13, 2009 issue 188 (Hebrew translation) reported by mkriheli - Attached 'he' (Hebrew) translation (both .po and .mo). Cheers. Attached 'he' (Hebrew) translation (both .po and .mo). Cheers. Dec 06, 2009 r786 (Several fixes on the documentation) committed by batiste.bieler - Several fixes on the documentation Several fixes on the documentation Dec 06, 2009 r785 (Fix typo) committed by batiste.bieler - Fix typo Fix typo Dec 06, 2009 r784 (Some more documentation) committed by batiste.bieler - Some more documentation Some more documentation Dec 04, 2009 issue 187 (I need to use 2 or more templates in my project) Status changed by batiste.bieler - You can use has many templates you want, here is the documentation on how to use them: http://code.google.com/p/django-page-cms/source/browse/trunk/pages/settings.py#16 Just declare this variable in your settings.py: DEFAULT_PAGE_TEMPLATE = 'pages/default.html' PAGE_TEMPLATES = ( ('pages/nice.html', 'nice one'), ('pages/cool.html', 'cool one'), ) And just be sure that these templates exist at the right place in your template directory. Status: WontFix You can use has many templates you want, here is the documentation on how to use them: http://code.google.com/p/django-page-cms/source/browse/trunk/pages/settings.py#16 Just declare this variable in your settings.py: DEFAULT_PAGE_TEMPLATE = 'pages/default.html' PAGE_TEMPLATES = ( ('pages/nice.html', 'nice one'), ('pages/cool.html', 'cool one'), ) And just be sure that these templates exist at the right place in your template directory. Status: WontFix Dec 03, 2009 issue 187 (I need to use 2 or more templates in my project) reported by netovs - hi, this issue not is a trouble, is a doubt, i need use to many templates, but i can't declare it in a settings.py that is, my page 1 will use the template index.html, page 2 I used the template 2_column.html, I used the template page 3 forms.html i don't understand how is where is the template to use. The CMS it's no bad, but even is young. Please help me. hi, this issue not is a trouble, is a doubt, i need use to many templates, but i can't declare it in a settings.py that is, my page 1 will use the template index.html, page 2 I used the template 2_column.html, I used the template page 3 forms.html i don't understand how is where is the template to use. The CMS it's no bad, but even is young. Please help me. Dec 03, 2009 issue 186 (Installation fails) Status changed by batiste.bieler - Status: Fixed Status: Fixed Dec 03, 2009 issue 186 (Installation fails) commented on by koziel.arthur - Yep, 1.0.9 works fine. Yep, 1.0.9 works fine. Dec 03, 2009 r783 (Remove unecessary import) committed by batiste.bieler - Remove unecessary import Remove unecessary import Dec 03, 2009 r782 (Some precisions in the changelog) committed by batiste.bieler - Some precisions in the changelog Some precisions in the changelog Dec 03, 2009 issue 186 (Installation fails) commented on by batiste.bieler - I uploaded a new version of the package. And it install well with pip and easy_install for me. Can you confirm on your side? I uploaded a new version of the package. And it install well with pip and easy_install for me. Can you confirm on your side? Dec 03, 2009 django-page-cms-1.0.9.tar.gz (Django page CMS 1.0.9 release (Bugfix, new features)) file uploaded by batiste.bieler - Labels: Featured Type-Source OpSys-All Labels: Featured Type-Source OpSys-All Dec 03, 2009 r781 (New version) committed by batiste.bieler - New version New version Dec 03, 2009 issue 186 (Installation fails) commented on by koziel.arthur - Well, you get the same error: "warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python modules". Which means that setuptools doesn't install any Python modules. Are you sure the "pages" module wasn't already in the site-packages? Well, you get the same error: "warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python modules". Which means that setuptools doesn't install any Python modules. Are you sure the "pages" module wasn't already in the site-packages? Dec 03, 2009 issue 186 (Installation fails) commented on by batiste.bieler - It's definitely an error if the package doesn't install properly. This is what I get when I install : $ sudo easy_install django-page-cms /usr/lib/python2.6/dist-packages/setuptools/package_index.py:155: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) Environment.__init__(self,args,kw) /usr/lib/python2.6/dist-packages/setuptools/command/easy_install.py:191: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) self.local_index = Environment(self.shadow_path+sys.path) Searching for django-page-cms Reading http://pypi.python.org/simple/django-page-cms/ Reading http://code.google.com/p/django-page-cms/ Reading http://code.google.com/p/django-page-cms/downloads/list Best match: django-page-cms 1.0.8 Downloading http://django-page-cms.googlecode.com/files/django-page-cms-1.0.8.tar.gz Processing django-page-cms-1.0.8.tar.gz Running django-page-cms-1.0.8/setup.py -q bdist_egg --dist-dir /tmp/easy_install- YwFtt3/django-page-cms-1.0.8/egg-dist-tmp-uOvccq warning: no files found matching '' under directory 'docs' warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python modules to install Adding django-page-cms 1.0.8 to easy-install.pth file Installed /usr/local/lib/python2.6/dist-packages/django_page_cms-1.0.8-py2.6.egg Processing dependencies for django-page-cms Finished processing dependencies for django-page-cms It seems to work well for me. It's definitely an error if the package doesn't install properly. This is what I get when I install : $ sudo easy_install django-page-cms /usr/lib/python2.6/dist-packages/setuptools/package_index.py:155: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) Environment.__init__(self,args,kw) /usr/lib/python2.6/dist-packages/setuptools/command/easy_install.py:191: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) self.local_index = Environment(self.shadow_path+sys.path) Searching for django-page-cms Reading http://pypi.python.org/simple/django-page-cms/ Reading http://code.google.com/p/django-page-cms/ Reading http://code.google.com/p/django-page-cms/downloads/list Best match: django-page-cms 1.0.8 Downloading http://django-page-cms.googlecode.com/files/django-page-cms-1.0.8.tar.gz Processing django-page-cms-1.0.8.tar.gz Running django-page-cms-1.0.8/setup.py -q bdist_egg --dist-dir /tmp/easy_install- YwFtt3/django-page-cms-1.0.8/egg-dist-tmp-uOvccq warning: no files found matching '' under directory 'docs' warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python modules to install Adding django-page-cms 1.0.8 to easy-install.pth file Installed /usr/local/lib/python2.6/dist-packages/django_page_cms-1.0.8-py2.6.egg Processing dependencies for django-page-cms Finished processing dependencies for django-page-cms It seems to work well for me. Dec 03, 2009 r780 (Fix an install issue) committed by batiste.bieler - Fix an install issue Fix an install issue Dec 02, 2009 issue 186 (Installation fails) commented on by netovs - Hello i can solve that trouble: if you have the directory: django-page-cms-1.0.8/pages copy to the full path for django. In Ubuntu will need to also copy or make a link /usr/local/lib/python2.6/dist-packages/[here pages] /usr/lib/python2.6/dist-packages/[link here pages] python -c 'import pages' without ERROR Hello i can solve that trouble: if you have the directory: django-page-cms-1.0.8/pages copy to the full path for django. In Ubuntu will need to also copy or make a link /usr/local/lib/python2.6/dist-packages/[here pages] /usr/lib/python2.6/dist-packages/[link here pages] python -c 'import pages' without ERROR Dec 01, 2009 DisplayContentInTemplates (How to display page content in your templates) Wiki page edited by batiste.bieler - Revision r779 Edited wiki page through web user interface. Revision r779 Edited wiki page through web user interface. Dec 01, 2009 NavigationInTemplates (describes how the various menu tags are used) Wiki page edited by batiste.bieler - Revision r778 Edited wiki page through web user interface. Revision r778 Edited wiki page through web user interface. Dec 01, 2009 WriteYourOwnWidget (Example for creating and using a custom widget.) Wiki page edited by batiste.bieler - Revision r777 Edited wiki page through web user interface. Revision r777 Edited wiki page through web user interface. Dec 01, 2009 WriteYourOwnWidget (Example for creating and using a custom widget.) Wiki page edited by batiste.bieler - Revision r776 Edited wiki page through web user interface. Revision r776 Edited wiki page through web user interface. Nov 30, 2009 issue 186 (Installation fails) reported by koziel.arthur - django-page-cms cannot be installed with easy_install or pip. It will result in throwing a warning: warning: install_lib: 'build/lib' does not exist -- no Python modules to install Steps to reproduce: 1. easy_install django-page-cms 2. python -c 'import pages' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named pages This is due to line 23 in the setup.py that is commented out. Uncommenting the line fixes this problem. django-page-cms cannot be installed with easy_install or pip. It will result in throwing a warning: warning: install_lib: 'build/lib' does not exist -- no Python modules to install Steps to reproduce: 1. easy_install django-page-cms 2. python -c 'import pages' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named pages This is due to line 23 in the setup.py that is commented out. Uncommenting the line fixes this problem. Nov 24, 2009 r775 (Create a method that could be used for testing the frontend/...) committed by batiste.bieler - Create a method that could be used for testing the frontend/backend Create a method that could be used for testing the frontend/backend Nov 23, 2009 r774 (Fix the MANIFEST file) committed by batiste.bieler - Fix the MANIFEST file Fix the MANIFEST file Earlier this year Nov 20, 2009 r773 (Finish to convert all the doc in the REST format.) committed by batiste.bieler - Finish to convert all the doc in the REST format. Finish to convert all the doc in the REST format. Nov 20, 2009 r772 (Improve the documentation) committed by batiste.bieler - Improve the documentation Improve the documentation Nov 19, 2009 issue 185 (Pages failing appear in admin page list) commented on by intellinick - Fixed. If anyone else has the problem, make sure you're using the new-style admin URLs: (r'^admin/', include(admin.site.urls)), This version will cause the pages to disappear in admin list (even though the rest of admin works fine): (r'^admin/?(.)', admin.site.root), Fixed. If anyone else has the problem, make sure you're using the new-style admin URLs: (r'^admin/', include(admin.site.urls)), This version will cause the pages to disappear in admin list (even though the rest of admin works fine): (r'^admin/?(.)', admin.site.root), Nov 19, 2009 issue 185 (Pages failing appear in admin page list) reported by intellinick - One of my installations refuses to show any pages in the admin page list. You can still access the retail pages, as well as find the edit pages, and they both work fine. 'pages' appears to be None when change_list_table.html tries to render {% for page in pages %} Another one of my installations does not have this problem, and is running the exact same version of django-page-cms (both are symlinked). I can't find any discernible difference between the two installations, after researching both setups for a few hours. I'll be continuing to research the problem and will post here if I find anything out. One of my installations refuses to show any pages in the admin page list. You can still access the retail pages, as well as find the edit pages, and they both work fine. 'pages' appears to be None when change_list_table.html tries to render {% for page in pages %} Another one of my installations does not have this problem, and is running the exact same version of django-page-cms (both are symlinked). I can't find any discernible difference between the two installations, after researching both setups for a few hours. I'll be continuing to research the problem and will post here if I find anything out. Nov 18, 2009 r771 (Add Johannes Knutsen in AUTHORS file, add doc form image pla...) committed by batiste.bieler - Add Johannes Knutsen in AUTHORS file, add doc form image placeholder Add Johannes Knutsen in AUTHORS file, add doc form image placeholder Nov 18, 2009 r770 (Use staticfiles application for media file) committed by batiste.bieler - Use staticfiles application for media file Use staticfiles application for media file Nov 17, 2009 issue 184 (Child templates (maybe?) should lose data but don't; non-los...) commented on by Vader82 - Oh, I wasn't aware. The reason I posted an issue was because of the Javascript warning me I was going to lose data. Sorry! Oh, I wasn't aware. The reason I posted an issue was because of the Javascript warning me I was going to lose data. Sorry! Nov 17, 2009 issue 184 (Child templates (maybe?) should lose data but don't; non-los...) Status changed by batiste.bieler - It's in fact normal. The field/placeholders that have the same name considered the same in this CMS even if the template is different. You could use the language delete if you realy want to get ride of all the data. Status: WontFix It's in fact normal. The field/placeholders that have the same name considered the same in this CMS even if the template is different. You could use the language delete if you realy want to get ride of all the data. Status: WontFix Nov 17, 2009 issue 184 (Child templates (maybe?) should lose data but don't; non-los...) commented on by batiste.bieler - It's in fact normal. The field/placeholders that have the same are simply considered the same in this CMS. You could use the language delete if you realy want to get ride of all the data. It's in fact normal. The field/placeholders that have the same are simply considered the same in this CMS. You could use the language delete if you realy want to get ride of all the data. Nov 17, 2009 r769 (Fix a typo) committed by batiste.bieler - Fix a typo Fix a typo Nov 17, 2009 issue 184 (Child templates (maybe?) should lose data but don't; non-los...) reported by Vader82 - What steps will reproduce the problem? 1. Using the example site, create a page using basic template 2. Now change the page template for that page (nice one) and see a warning about losing data (misspelled "loose") 3. Hit save anyhow and load the page in the CMS What is the expected output? What do you see instead? I would expect to see all my old data gone and the new data replacing it. Instead I see both the old data which pertained to the old template, and the new data which pertains to the new template. Even though the old data still shows up when the page is rendered. Might this be because the template "nice one" extends the default template? Are you using the trunk version or a released version of this CMS? 1.0.8 release If you can write a test that reproduce the problem, there is better chance it will be resolved quickly. I'm afraid I can't successfully do that. What steps will reproduce the problem? 1. Using the example site, create a page using basic template 2. Now change the page template for that page (nice one) and see a warning about losing data (misspelled "loose") 3. Hit save anyhow and load the page in the CMS What is the expected output? What do you see instead? I would expect to see all my old data gone and the new data replacing it. Instead I see both the old data which pertained to the old template, and the new data which pertains to the new template. Even though the old data still shows up when the page is rendered. Might this be because the template "nice one" extends the default template? Are you using the trunk version or a released version of this CMS? 1.0.8 release If you can write a test that reproduce the problem, there is better chance it will be resolved quickly. I'm afraid I can't successfully do that. Nov 17, 2009 r768 (Remove unessecary image model) committed by batiste.bieler - Remove unessecary image model Remove unessecary image model Nov 17, 2009 r767 (Make the image placeholder tag to work properly. Refactor th...) committed by batiste.bieler - Make the image placeholder tag to work properly. Refactor the code at the same time so it's easier to create new placeholder template tags Make the image placeholder tag to work properly. Refactor the code at the same time so it's easier to create new placeholder template tags Nov 16, 2009 r766 (Went half way with the image placeholder) committed by batiste.bieler - Went half way with the image placeholder Went half way with the image placeholder

issue 186 (Installation fails) commented on by batiste.bieler - It's definitely an error if the package doesn't install properly. This is what I get when I install : $ sudo easy_install django-page-cms /usr/lib/python2.6/dist-packages/setuptools/package_index.py:155: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) Environment.__init__(self,*args,**kw) /usr/lib/python2.6/dist-packages/setuptools/command/easy_install.py:191: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) self.local_index = Environment(self.shadow_path+sys.path) Searching for django-page-cms Reading http://pypi.python.org/simple/django-page-cms/ Reading http://code.google.com/p/django-page-cms/ Reading http://code.google.com/p/django-page-cms/downloads/list Best match: django-page-cms 1.0.8 Downloading http://django-page-cms.googlecode.com/files/django-page-cms-1.0.8.tar.gz Processing django-page-cms-1.0.8.tar.gz Running django-page-cms-1.0.8/setup.py -q bdist_egg --dist-dir /tmp/easy_install- YwFtt3/django-page-cms-1.0.8/egg-dist-tmp-uOvccq warning: no files found matching '*' under directory 'docs' warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python modules to install Adding django-page-cms 1.0.8 to easy-install.pth file Installed /usr/local/lib/python2.6/dist-packages/django_page_cms-1.0.8-py2.6.egg Processing dependencies for django-page-cms Finished processing dependencies for django-page-cms It seems to work well for me.

It's definitely an error if the package doesn't install properly. This is what I get when I install : $ sudo easy_install django-page-cms /usr/lib/python2.6/dist-packages/setuptools/package_index.py:155: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) Environment.__init__(self,*args,**kw) /usr/lib/python2.6/dist-packages/setuptools/command/easy_install.py:191: UserWarning: Unbuilt egg for setuptools [unknown version] (/usr/local/lib/python2.6/dist-packages) self.local_index = Environment(self.shadow_path+sys.path) Searching for django-page-cms Reading http://pypi.python.org/simple/django-page-cms/ Reading http://code.google.com/p/django-page-cms/ Reading http://code.google.com/p/django-page-cms/downloads/list Best match: django-page-cms 1.0.8 Downloading http://django-page-cms.googlecode.com/files/django-page-cms-1.0.8.tar.gz Processing django-page-cms-1.0.8.tar.gz Running django-page-cms-1.0.8/setup.py -q bdist_egg --dist-dir /tmp/easy_install- YwFtt3/django-page-cms-1.0.8/egg-dist-tmp-uOvccq warning: no files found matching '*' under directory 'docs' warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python modules to install Adding django-page-cms 1.0.8 to easy-install.pth file Installed /usr/local/lib/python2.6/dist-packages/django_page_cms-1.0.8-py2.6.egg Processing dependencies for django-page-cms Finished processing dependencies for django-page-cms It seems to work well for me.

Yesterday

Last 7 days

Last 30 days

Earlier this year