I need an opinion on the 'safety' of a potential approach...
Calls to `pyramid.paster.bootstrap` are definitely what is taking too long
( 2.5s on dev ! )
Looking at the path of execution and relevant bits...
`pyramid.paster` `bootstrap`
calls `paste.deploy` `get_app` ( which looks to be expensive )
calls `pyramid.scripting` `prepare` ( which may or may not be expensive
)
`pyramid.scripting` `prepare`
does a lot of stuff with threadlocals / etc. and that scares me.
my idea is to pull the app out of the env, then create a new env -
injecting that app into it.
the gist is below...
https://gist.github.com/jvanasco/5783417
i'm wondering if this is safe, or if much of it is needed :
- do i need to update the 'app' ? is that used on anything ?
- should i pull the `registry` out of the env and pass that into
`prepare_request` too ?
any ideas ?
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
