#pyramid

hey guys, one more dummy question, what are factories? I see this pattern all the time in the docs

_rschalch: a factory is a callable which produces an object of a specific type/interface/etc

it's called that because it makes a thing, you see

ah thats it, thank you inklesspen

np

_rschalch tip to find definitions of terms: https://docs.pylonsproject.org/projects/pyramid...

and if you find a term that is not clear, please do submit an issue or pull request so we can amend the docs and Glossary

stevepie thanks ... I have to say that the docs could be simpler in some aspects, Ill try to contribute for that as soon I gain some experience with pyramid

Ive been playing with pyramid for two weeks and only now I started to realize how powerful it is

_rschalch agreed. they are dense for newbies to Pyramid, and much more so for Python newbs, and new web app devs fuggettabouddit

Pyramid, built upon the mistakes of mortals™

lol

one more question: I see that in pyramid imports are made inside methods as opposed to other frameworks ... I read the reason on the docs, but honestly didnt understand ... why it can be dangerous?

this sometimes leads to duplication

got link?

Ill try to find, but I think its in the get started session

right now Im writing tests for five views and asking myself i should put imports inside every test case

https://docs.pylonsproject.org/projects/pyramid... actually explains why

though i'd like to see an example of the breakage it's trying to prevent, tbh

yeah, I havent found a case which it breaks something, but Im sure the more experienced guys will come up with some cases

_rschalch I interpret the warning for imports within methods in the context of testing only, not your app

Yeah stevepie, it can make sense

in case if we test a single unit you mean?

correct

thanks so much guys, Im glad being part of this group

yw. the hugs are free

lol

[pyramid] mcdonc pushed 1 new commit to feature.append-slash-use-subrequest: https://git.io/fbpwQ

pyramid/feature.append-slash-use-subrequest 881bfd5 Chris McDonough: normalize to notfound

Pylons/pyramid#5664 (feature.append-slash-use-subrequest - 881bfd5 : Chris McDonough): The build passed.

Change view : https://github.com/Pylons/pyramid/compare/40d68...

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

hey o/ is there a way I can configure logging in ini so it uses style='{'

it's normally done using logging.Formatter('{asctime} {name} {levelname:8s} {message}',

... style='{')

so I guess my queston is can I pass the style to the formatter ia ini?

tomas what have you tried? also you might benefit from using translogger. See https://docs.pylonsproject.org/projects/pyramid...

stevepie_: just:

[formatter_generic]

format = %(asctime)s %(levelname)-5.5s %(message)s

style = {

but nogo

i don't understand the intent of `style = {`

stevepie_: this is so I do: log.debug('Message with {0} {name}', 2, name='placeholders')

*can do

ah, ok

oh, silly me, i meant structlog

and there is a pyramid_structlog add-on

Hey, if I want to always log every HTTP response for audit purposes, what's the best place to do that in Pyramid? In a tween? In a finished callback? Someplace else?

dropkick44: you could do it by logging configuration

just may take some playing

dega: Can you explain further or link to an example?

dega: There's already some logging hook for logging every request/response?

it depends on the subsystem, however if they have logging hooks you can configure them through the loggers handlers and formatters section in your ini

you can use your tweens if you want to

i.e. if you want to interact with the response

so yeah your idea would work but if the section that handles the response has a logger you can attach to that

i did some similar items with suds

I just don't understand what you're suggestion. You're just saying that if I already have `log.info()` calls throughout my code, I can attach handlers to those?

I just want to make sure that every request gets logged, and I was wondering the best place to put a log entry to do that. Obviously I could put separate entries in every view, but that seems a bit redundant