On Tue, Mar 8, 2011 at 12:28 AM, mjmein mjmeint...@gmail.com wrote:
I think the problem currently is that people start by going into the
main documentation, and then get overwhelmed.
Yes. I have mentioned this elsewhere, but a newcomer like me goes
through this process:
1. Google Pyramid
I got sick again this weekend so I won't be able to go to Pycon. It's
the same kind of severe cough I had for three weeks in February. I
just can't deal with a trip, especially a 5-hour plane ride. But I
will be sprinting from home on Monday and Tuesday, and will be on IRC
throughout the weekend
On Tue, Mar 8, 2011 at 20:07, Mike Orr sluggos...@gmail.com wrote:
I got sick again this weekend so I won't be able to go to Pycon. It's
the same kind of severe cough I had for three weeks in February. I
just can't deal with a trip, especially a 5-hour plane ride. But I
will be sprinting from
I'm sorry to read that Mike. I hope you get better soon. I retweeted Jorge's
message:
http://twitter.com/#!/elpargo/status/45192992025358336
2011/3/8 Mike Orr sluggos...@gmail.com
I got sick again this weekend so I won't be able to go to Pycon. It's
the same kind of severe cough I had for
Any ideas on that? I've re-read my code, and the documentation, but I
didn't see anything obvious. Should I ask pylons-devel instead? I'm
not sure if writing your own AuthenticationPolicy counts as pylons-
discuss or -devel material ;-)
oO
On Mar 4, 11:10 am, oO oliv...@ozoux.com wrote:
I seem
from pyramid import testing
from pyramid.security import remember
import pyramid.config
class TestingAuthenticationPolicy(object):
def authenticated_userid(self, request):
return 'larry'
def effective_principals(request):
return []
def remember(self, request,
The doctype goes to the top of your index.pt
Yes. That seems to be the only way. In a perfect world, one could write the
doctype that logically belongs to the outer template in the outer template,
not in the inner template. But which world is perfect... *sigh*
Btw, interesting project you
