Re: How does buildout determine paths needed? (for django-page-cms)
Bill Freeman wrote: Not buildout specific, but, if I recall correctly, the pages egg (among others) is not built in such a way that the media files get included (in setup.py the function that goes and discovers the .py files to install only does .py files, other files must be added more painfully, and a lot of package maintainers don't do it, and may not know, because they typically do a VCS checkout or install from a tar, rather than from the egg). Last time I installed pages, after using pip install, I had to get the tar and unpack it to get the media files. I don't recall if that involved templates, or just css, images, and js, but I wouldn't be surprised. The pages templates are examples, IIRC, and you make your own to stick in project_root/templates/pages/ . Hmmm the developer of django-page-cms does not use buildout, so I tried a buildout with django-page-cms as source and it behaved differently. I still needed project_root/media/ and subdirs, but it started finding templates. Thanks for the hints. John -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: How does buildout determine paths needed? (for django-page-cms)
Not buildout specific, but, if I recall correctly, the pages egg
(among others) is not
built in such a way that the media files get included (in setup.py the
function that
goes and discovers the .py files to install only does .py files, other
files must be
added more painfully, and a lot of package maintainers don't do it, and may not
know, because they typically do a VCS checkout or install from a tar,
rather than
from the egg). Last time I installed pages, after using pip install,
I had to get the
tar and unpack it to get the media files. I don't recall if that
involved templates, or
just css, images, and js, but I wouldn't be surprised. The pages templates are
examples, IIRC, and you make your own to stick in
project_root/templates/pages/ .
Bill
On Tue, Jun 29, 2010 at 8:56 AM, John Griessen wrote:
> I made a buildout with the config below that didn't work right and
> found it needed to have some extra paths added.
>
> Here is the extra path I needed:
>
> '/home/john/buildout/eggs/django_page_cms-1.1.3-py2.6.egg',
> '/home/john/buildout/eggs/django_page_cms-1.1.3-py2.6.egg/pages/templates/pages',
>
> pages was being found to not have the contents wanted. Is having a dir
> pages
> and pages/templates/pages a naming problem for buildout? If a search
> is being done for * in pages, it might stop short when the top level pages
> is found.
>
> Hints, suggestions how to resolve this appreciated.
> Meanwhile, every time I run buildout, I'll need to copy an paste that extra
> path...
>
> John
> -buildout.cfg
> [buildout]
> eggs-directory = /home/john/buildout/eggs
> extensions = mr.developer
>
> parts =
> django
>
> eggs =
> mock
> django-notification
> django-page-cms
> django-haystack
> django-staticfiles
> django-messages
> django-mptt-2
> whoosh
>
> [django]
> recipe = djangorecipe
> version = 1.2.1
> settings = development
> wsgi = true
> eggs = ${buildout:eggs}
> project = industromatic_com
> buildout.cfg--
>
> ___
> Distutils-SIG maillist - distutils-...@python.org
> http://mail.python.org/mailman/listinfo/distutils-sig
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
How does buildout determine paths needed? (for django-page-cms)
I made a buildout with the config below that didn't work right and
found it needed to have some extra paths added.
Here is the extra path I needed:
'/home/john/buildout/eggs/django_page_cms-1.1.3-py2.6.egg',
'/home/john/buildout/eggs/django_page_cms-1.1.3-py2.6.egg/pages/templates/pages',
pages was being found to not have the contents wanted. Is having a dir pages
and pages/templates/pages a naming problem for buildout? If a search
is being done for * in pages, it might stop short when the top level pages is
found.
Hints, suggestions how to resolve this appreciated.
Meanwhile, every time I run buildout, I'll need to copy an paste that extra
path...
John
-buildout.cfg
[buildout]
eggs-directory = /home/john/buildout/eggs
extensions = mr.developer
parts =
django
eggs =
mock
django-notification
django-page-cms
django-haystack
django-staticfiles
django-messages
django-mptt-2
whoosh
[django]
recipe = djangorecipe
version = 1.2.1
settings = development
wsgi = true
eggs = ${buildout:eggs}
project = industromatic_com
buildout.cfg--
___
Distutils-SIG maillist - distutils-...@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
