#pyramid

Is it possible to make "request" available in jinja2 templates like flask? (it might be possible by setting it as global? ill re-search that, if not or if theres another way in pyramid pls tell me)

(i dont use class bases views)

evagelos: hmm why do you need the request

cdunklau: cause i need to put data from db depending on the user from request

actually i can just pass request to render

evagelos: sounds like that should happen in the view though

the thing is how should i do it in the end, i mean either add_request_method or..?

cdunklau: well this packages uses the "main" package to send emails and iv been asked the main should handle everything

i tried to do it like u said and iv been asked to revert it back

so i have to call a function inside the jinja2 template where this function depends on the request

evagelos: i don't really see it

evagelos: but there's gotta be a way to inject the request object into the template globals

so A is main package, B uses includeme to be included when A starts

B has views that need to send emails, A has the send_email function

B templates have a spot for an image(per user)

so, sorry, i don't know

:9

:(

ok ok np :)

so the solution i guess is hook up the function while B starts, I pass the request in the templates so B templates can call that function

i dont see any other solution so i will use add_request_method, im not expert whatsoever

it just goes through A(main package) where it shouldn't know anything specific from B package thats the problem i guess

evagelos: request is available in the jinja2 templates

are you using pyramid_jinja2?

heh is it really

i couldn't find a mention of that in the docs

i haven't gotten far enough in my pyramid project to need that

cdunklau: the default template projects set things up for you - you should be able to access request normally

neat

same with any other variable that you return from your views - you should not need to call render() directly unless you do something specific

(like rendering emails)

Ergo im not sure but anyway i can pass it in the render()

Well guys my problem was that i was creating a jinja2 environment in order to render etc etc i think i finally figure it out how to do it properly and seems that i have to call render

i just finally set it up correctly

one problem that i have now is;

package A(the main one) adds 1 jinja2 filter like: config.add_settings({'jinja2.filters': 'A.function'})

i need to do the same for the rest of the packages B, C,...

My question is, in pyramid, how can i add more settings in the same "namespace" 'jinja2.filters' ?

i want to update the 'jinja2.filters' dictionary

(also i think i might a smallish bug in pyramid_jinja2 but im not sure)

*i might found

hmm well i dont think im doing it right by adding a function that i want to be called inside the template as a filter :/

moo-_-: yep you can totally validate the data again on the server works great that way.

moo-_-: bad part is that json schema is kinda... not so great :\

evagelos: here https://github.com/websauna/websauna/blob/maste...

raydeo: https://github.com/Pylons/hupper/pull/8 should work correctly now