#pyramid

Hey, do you guys usually declare all instance attributes in the init of a class?

Let's say your init only accepts one parameter, but you have other attributes you plan on using, would you say something like self.otherattribute = None to clarify?

yeah, that's a good thing to do

that's not necessarily the same thing as "declaring instance attributes"

and there's no technical benefit to doing this. but it's handy down the line when you look at the __init__ and wonder what is going on.

Hey there folks, quick question to help direct my reading. I'm trying to create a situation where I check some db state before a view is routed, and if the db is not ready I return a HTTPFound (or something) sending it somewhere else. Importantly this needs to be done for most of the views in the app so I kind of want it to happen in a single location.

There are two distinct, non user related states that I've got to do this for (effectively blocking the app until the state is resolved) and the obvious example of this is with user Auth. I've seen this done in a root factory with acls redirecting to a login page but I'm wondering if there is somewhere else thats better suited to non-user stuff-- or if I should keep following the root factory rabbit hole and see where it leads?

Any tips would be greatly appreciated :D

inklesspen: Yeah, I agree, just wanted to hear what the kind of consensus was, so thanks for the info

ash__: the ContextFound event might be appropriate

ash__: Why not put it in the __init__ of your main view class?

inklesspen: I was looking through the events at one stage. Will go back and re-read this now.

user___: "main view class"?

my pyramd apps have no such thing. :D

user__: Currently not using class based views but could look into this. Was thinking at one stage I could inherit from something that provided this overriding of the view for me, but then went off on the event tangent... :p. Might have a look again but it would require changing of a (small) chunk of code.

"db isnt ready" = no db connection at all?

I understand not everyone uses this approach, but it is a pattern I use, my fault for assuming that everybody does :D

I come from a java background so my python is tainted by many of the philosophies from java...

Zart: I think he is trying to resolve concurrent access or race conditions

ash__: http://docs.pylonsproject.org/projects/pyramid/...

user__: Yah. Have done this before. Just got out of the habit to keep things flat and simple in small apps.

Makes a lot of sense though-- thanks for the link :)

from now on, if someone asks me about pyramid ... I only can say ... "Pyramid? I wish I would have tried it earlier! :D"

bind: but what about Pyramid? :>

Well, for example that from the get go you are confronted with the "best practices" wrt python packaging

so yesterday I wanted to run my pyramid example app on our hosting thing

I just had to do pip install . within the source checkout from within the virtualenv

and created an upstart thing running gunicorn --paste production.ini

furthermore there is quite a lot of freedom and a lot of routing/view/renderer goodies which are quite handy ... but then again ... still being a bit new to pyramid :D

bind we're missing a gunicorn deployment recipe for the cookbook: http://docs.pylonsproject.org/projects/pyramid-...

it would be nice to have one