Re: Some thoughts about Pyramid
On 04/03/2011 20:03, Mike Orr wrote: I'll be at the Pyramid sprint but I don't know what I'll be doing. I would like to learn Git and Pyramid-at-Github if somebody would like to do a mini crash course. Me too please! I'm currently petrified of all things git and could use some hand holding. I'm eyeing up those two small venusian issues as training bait for this... cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: mod_wsgi mako - unable to find template
I should have said that the project works perfectly with paster either
with development.ini or production.ini but not when serving via
mod_wsgi.
I didn't change anything in the project and I didn't add any specific route.
I'm still stuck.
On Sat, Mar 5, 2011 at 1:27 AM, Mengu whalb...@gmail.com wrote:
for development, i recommend you using paster. you can just do paster
serve --reload development.ini.
- make sure you have mako.directories = appname:templates under
[app:appname] directive in your *.ini files.
- when you add a route or so, do not set the path like /templates/
index.html just set it like index.html. ie:
config.add_route('new_bookmark', '/bookmarks/new',
view='bookmarkapp.views.bookmarks.new', view_renderer='bookmarks/
index.html')
hope this helps.
On Mar 4, 1:02 pm, pgiraud pierre.gir...@gmail.com wrote:
Hi all,
I just created a new project using the pyramid_sqla template (which
includes mako template engine).
Then followed the run under mod_wsgi instructions [1], but I get the
following error:
TopLevelLookupException: Cant locate template for uri 'index.html'
Does anybody have an idea about what's wrong ?
Thanks,
Pierre
[1]http://docs.pylonsproject.org/projects/pyramid/1.0/tutorials/modwsgi/...
--
You received this message because you are subscribed to the Google Groups
pylons-devel group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
--
-
| Pierre GIRAUD
| 04.79.44.44.93
|
| http://pierrelebricoleur.blogspot.com
| http://www.flickr.com/photos/pierregiraud
-
--
You received this message because you are subscribed to the Google Groups
pylons-devel group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
Re: How do I combine paster templates?
You can't combine them but you can start out using paster create -t pyramid_routesalchemy myproject then change the result to use Jinja2 using the docs from pyramid_jinja2 at http://docs.pylonsproject.org/projects/pyramid_jinja2/dev/ - C On Sat, 2011-03-05 at 12:34 -0800, Sasker wrote: Hi I am new to Pyramid and currently going through the tutorials. I was wondering how can I combine pyramid_routesalchemy and pyramid_jinja_starter templates so I can get url_dispatch + sqlalchemy + jinja2 I tried searching docs and mailing list but couldn't find how to do this. I am a little confused. Also, I apologize if I am posting to the wrong group, I wasn't quite sure which group I should be posting to. Thanks. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: computing url for view registered by name
By leaving out the context you are effectively registering those views to *any* context, which is almost always undesirable. Regardless, my previous reply remains correct, if you want the path hanging off of /, simply use resource_url(request.root, request) and resource_url(request.root, request, 'history'). request.root is the root context, thus the context used for views hanging off of /. Michael On Fri, Mar 4, 2011 at 12:56 PM, Chris Withers ch...@simplistix.co.ukwrote: On 02/03/2011 00:48, Michael Merickel wrote: I noticed in your example you aren't specifying a context= or for_= in the view_config, implying you maybe intended to use route_name instead of name with url dispatch. Nope, no routes here, these are just views hanging off /, not registered against any context... cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
