#pyramid

/

      • cyphase joined the channel
      • mastokley joined the channel
      • zepolen has quit
      • zepolen joined the channel
      • davisagli has quit
      • supton joined the channel
      • mejymejy joined the channel
      • supton has quit
      • davisagli joined the channel
      • x58
        I use pyramid_mailer extensively, on my main site.
      • s/production/
      • Have had no issues.
      • marcidy joined the channel
      • hvelarde joined the channel
      • davisagli has quit
      • mejymejy has quit
      • davisagli joined the channel
      • mejymejy joined the channel
      • Method__ has quit
      • pdobrogost_home has quit
      • pdobrogost_home joined the channel
      • zepolen has quit
      • mejymejy has quit
      • mejymejy joined the channel
      • mejymejy has quit
      • mejymejy joined the channel
      • mejymejy has quit
      • npo joined the channel
      • rickmak_ joined the channel
      • zepolen joined the channel
      • davisagli has quit
      • davisagli joined the channel
      • hvelarde has quit
      • uralbash joined the channel
      • rickmak_ joined the channel
      • frispete joined the channel
      • c0le joined the channel
      • davisagli has quit
      • natim joined the channel
      • XeL64 joined the channel
      • Jonno_FTW has quit
      • Jonno_FTW joined the channel
      • yvl joined the channel
      • davisagli joined the channel
      • uralbash joined the channel
      • mastokley joined the channel
      • jhauser has quit
      • tokra100 joined the channel
      • tokra100 has left the channel
      • mejymejy joined the channel
      • romerocesar joined the channel
      • mejymejy has quit
      • disko has quit
      • davisagli has quit
      • brokencycle joined the channel
      • MatthewWilkes joined the channel
      • XeL64 has quit
      • XeL64 joined the channel
      • davisagli joined the channel
      • slav0nic joined the channel
      • mejymejy joined the channel
      • mejymejy has quit
      • amragaey has quit
      • rodfersou joined the channel
      • chrisw has quit
      • chrisw joined the channel
      • Pumukel joined the channel
      • yleclanche joined the channel
      • chrisw has quit
      • disko joined the channel
      • zepolen has quit
      • rickmak joined the channel
      • atomekk joined the channel
      • bochecha joined the channel
      • bochecha has quit
      • chrisw joined the channel
      • crooksey joined the channel
      • davisagli has quit
      • El_Rolando joined the channel
      • wiggy joined the channel
      • chrisw has quit
      • zepolen joined the channel
      • ronnix joined the channel
      • zepolen has quit
      • mejymejy joined the channel
      • mejymejy has quit
      • lothiraldan joined the channel
      • lothiraldan
        Hi
      • redir joined the channel
      • natim
        Hi lothiraldan
      • lothiraldan
        I’m looking for a list of LTS versions of pyramid
      • Is pyramid 1.7 still supported?
      • Sorry pyramid 1.6
      • wiggy
        there is LTS concept for pyramid
      • lothiraldan: your pyramid 1.6 using code will work without changes with pyramid 1.7
      • Charlie_X
        But 1.6 won't see any fixes.
      • lothiraldan
        Thank you, that’s what I wanted to know
      • Charlie_X
        Standard semantic versioning.
      • chrisw joined the channel
      • chrisw has quit
      • lothiraldan
        Unfortunately not all projects follow the semantic versioning
      • Charlie_X
        Well Pyramid does.
      • Anyway, massive changes are not to be expected.
      • There has been some refactoring and concentration on what has turned out to be the core.
      • Based on the upgrades I've done in the past I think Pyramid compares well with other libraries in not breaking compatibility needlessly and introducing bad ideas.
      • Most of the stuff where an LTS might be thought to make sense – security – is handled by external libraries. And with anything related to security you have to be prepared to update when necessary.
      • chrisw joined the channel
      • zepolen joined the channel
      • c0le has quit
      • chrisw: anyone offered to take over maintenance yet?
      • bochecha joined the channel
      • crooksey
        lothiraldan: When I upgrade from pyramid 1.34 to 1.6 (and moved to python3) I think I had about 10 things to change, and nearly all of those were python2/3 changes, the pyramid code I recall stayed the same
      • And I have some projects that are now 4 years old, views that were written 4 years ago, work unchanged with current pyramid code
      • Why I love pyramid, and moved away from django
      • But I now haven't used django in 4 years, so can't comment on djangos upgrade stance anymore
      • lothiraldan
        I will try with the 1.6 version because I will likely to have some subttle differences between pyramid versions because I need to get behind the public API
      • Charlie_X
        That doesn't make sense.
      • Go with 1.7 unless you already have an extensive project tied to 1.6
      • But you really, really, really ought to avoid using private APIs of any project.
      • zepolen has quit
      • betabug
        in pyramid that's totally unnecessary IMO
      • everything is there, and well documented
      • evilbungle joined the channel
      • c0le joined the channel
      • wiggy
        lothiraldan: I'm curious - can you explain what kind of behind-the-public-API things you had to do ?
      • Ergo joined the channel
      • RchrdB joined the channel
      • zepolen joined the channel
      • _user joined the channel
      • lothiraldan
        I’m working on a python agent for a web security product, we are like the newrelic of security
      • This agent hook into the app in order to intercept attacks / sanitize input or set security headers
      • wiggy
        can't that be done completely as a tween ?
      • lothiraldan
        I’m sorry I don’t understand what a tween is
      • Charlie_X
        I think 1.7 contains support for the more esoteric uses.
      • rickmak joined the channel
      • mejymejy joined the channel
      • lothiraldan: you should look them up.
      • Basically tweens can do things with the request/response headers.
      • lothiraldan
        Ok so a tween is only called on a exception ?
      • wiggy
        on, every time
      • Charlie_X
        No
      • wiggy
        a tween is like a more integrated WSGI middleware
      • they see all requests comining in, and responses going out
      • and can do all kinds of thigs: logging, modifying data, etc.
      • crooksey
        Do many attacks come directly to the app?
      • lothiraldan
        Ok could use a tween for the wsgi part but we also hook on the SQL driver to intercept SQL Injections, on the template framework to sanitize XSS attacks, etc…
      • So not everything could be done as a tween
      • wiggy
        pyramid does not have a "SQL driver"
      • stevepiercy
        1.6 might see fixes
      • wiggy
        I think you don't need any private APIs for pyramid itself