#pyramid

[pyramid] mmerickel pushed 1 new commit to master: https://git.io/vFLQZ

pyramid/master 87b7b7d Michael Merickel: fix lint

Damnit.

wat

raydeo: you beat me to it. I was about to push my branhc.

:-(

S'okay. I forgot to do it earlier today.

did you have any different fixes?

I renamed the O function.

But, I don't think it really matters.

I couldn't think of a better name, if you've got something we can use it

I liked the S and O for setting and override

I almost went with T for trump but then I didn't

lol

I was also surprised it didn't complain about S, but did about O.

it's just the font ambiguity

which is weird because of course zero is not a valid function name

I just renamed them to _setting and _override

ah

IMHO it doesn't make a bit of a difference.

yeah I'm fine just turning off the warning

Makes sense.

Pylons/pyramid#5389 (master - 87b7b7d : Michael Merickel): The build passed.

Change view : https://github.com/Pylons/pyramid/compare/a5d3d...

Build details : https://travis-ci.org/Pylons/pyramid/builds/294...

[webob] bertjwregeer pushed 1 new commit to master: https://git.io/vFL7F

webob/master 41f362b Steve Piercy: Update and fix links per `make linkcheck` (#334)...

[webob] bertjwregeer pushed 1 new commit to stevepiercy-patch-1: https://git.io/vFL7N

webob/stevepiercy-patch-1 31a3796 Bert JW Regeer: Merge branch 'master' into stevepiercy-patch-1

[webob] bertjwregeer pushed 1 new commit to master: https://git.io/vFL7x

webob/master 3e2238d Bert JW Regeer: Merge pull request #333 from Pylons/stevepiercy-patch-1...

raydeo x58 should I do anything on those three PRs? rebase the lint fix?

it's ok I'll do it

stevepiercy: the PR that is to master should be okay now.

the others may need some pushing.

I mean you can rebase the PR if you want sure

but I'll backport my lint fixes

ok, i'll just do master until you get to lint fixes

raydeo: Asking a potentially stupid question: Is there an accepted "Pyramid" canonical way to have pyramid extensions store extra data on the request object that should only be persisted for the duration of the request?

i'm curious if just restarting the build is all that is needed

x58: probably just add_request_method(..., reify=True)

raydeo: how do you make sure it won't conflict with something else?

you can attach a full object if you want

well request methods have a discriminator so they sort of handle it already

Basically I need to cache some information for the duration of the request, in my auth policy which is only created once for the lifetime of the app.

depending on how they are added

I still wish Pyramid had made those per request, alas, here we are.

I mean if you want the "safest" way to do it you could attach a WeakDictionary to the registry using a z.i interface utility

I already use pyramid_services, I was thinking of adding a "cache" service that just returned a dict like object...

Since that is per request.

and already disambiguated by interface.

I mean you can see pyramid_services doesn't worry so much, it just adds a key to the request

Some of us aren't Michael Merickel though... :P

what? why not?

suckers :(

I know you consider us figments of your imagination, but I swear we are not.

[pyramid] stevepiercy pushed 2 new commits to master: https://git.io/vFLAs

pyramid/master f9ae5ad Steve Piercy: Synch source files with cookiecutter

pyramid/master 0042089 Steve Piercy: Merge pull request #3192 from stevepiercy/master...

Pylons/pyramid#5390 (master - 0042089 : Steve Piercy): The build passed.

Change view : https://github.com/Pylons/pyramid/compare/87b7b...

Build details : https://travis-ci.org/Pylons/pyramid/builds/294...