home.social

#svcs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #svcs, aggregated by home.social.

  1. During my work hours, and with company resources, I made a simple but useful library to get logging very easily set up for FastAPI projects, using structlog and with integration with svcs.

    I think that would be quite useful for many folks, so I'm going to try to Open Source it. I expect resistance and a lot of red tape, but still I want to give it a try. Wish me luck!

    #FastAPI #structlog #svcs #OpenSource

  2. During my work hours, and with company resources, I made a simple but useful library to get logging very easily set up for FastAPI projects, using structlog and with integration with svcs.

    I think that would be quite useful for many folks, so I'm going to try to Open Source it. I expect resistance and a lot of red tape, but still I want to give it a try. Wish me luck!

    #FastAPI #structlog #svcs #OpenSource

  3. During my work hours, and with company resources, I made a simple but useful library to get logging very easily set up for FastAPI projects, using structlog and with integration with svcs.

    I think that would be quite useful for many folks, so I'm going to try to Open Source it. I expect resistance and a lot of red tape, but still I want to give it a try. Wish me luck!

    #FastAPI #structlog #svcs #OpenSource

  4. During my work hours, and with company resources, I made a simple but useful library to get logging very easily set up for FastAPI projects, using structlog and with integration with svcs.

    I think that would be quite useful for many folks, so I'm going to try to Open Source it. I expect resistance and a lot of red tape, but still I want to give it a try. Wish me luck!

    #FastAPI #structlog #svcs #OpenSource

  5. Anyone understand #ContextVars in #python ? I'm trying to add support to #svcs so that when there isn't a web framework with a context to glom onto, that you can use the thread/thread.local/ContextVars and an alternative to the Application/Request that a web framework would provide.

    So far, I can only get it to "work" if the ContextVars are globals.

    gist.github.com/matthewdeanmar

  6. Anyone understand #ContextVars in #python ? I'm trying to add support to #svcs so that when there isn't a web framework with a context to glom onto, that you can use the thread/thread.local/ContextVars and an alternative to the Application/Request that a web framework would provide.

    So far, I can only get it to "work" if the ContextVars are globals.

    gist.github.com/matthewdeanmar

  7. Anyone understand #ContextVars in #python ? I'm trying to add support to #svcs so that when there isn't a web framework with a context to glom onto, that you can use the thread/thread.local/ContextVars and an alternative to the Application/Request that a web framework would provide.

    So far, I can only get it to "work" if the ContextVars are globals.

    gist.github.com/matthewdeanmar

  8. Anyone understand #ContextVars in #python ? I'm trying to add support to #svcs so that when there isn't a web framework with a context to glom onto, that you can use the thread/thread.local/ContextVars and an alternative to the Application/Request that a web framework would provide.

    So far, I can only get it to "work" if the ContextVars are globals.

    gist.github.com/matthewdeanmar

  9. Anyone understand #ContextVars in #python ? I'm trying to add support to #svcs so that when there isn't a web framework with a context to glom onto, that you can use the thread/thread.local/ContextVars and an alternative to the Application/Request that a web framework would provide.

    So far, I can only get it to "work" if the ContextVars are globals.

    gist.github.com/matthewdeanmar

  10. Call it "first-mover advantage" -- or disadvantage, depending on your POV -- my #Django / #svcs integration apparently just barely beat @ubernostrum to the punch on the name on PyPi. Fortunately, they're a good sport and collaborative, and since my plugin is #FOSS, both of our works can coexist. #Python

  11. Call it "first-mover advantage" -- or disadvantage, depending on your POV -- my #Django / #svcs integration apparently just barely beat @ubernostrum to the punch on the name on PyPi. Fortunately, they're a good sport and collaborative, and since my plugin is #FOSS, both of our works can coexist. #Python

  12. Call it "first-mover advantage" -- or disadvantage, depending on your POV -- my #Django / #svcs integration apparently just barely beat @ubernostrum to the punch on the name on PyPi. Fortunately, they're a good sport and collaborative, and since my plugin is #FOSS, both of our works can coexist. #Python

  13. Call it "first-mover advantage" -- or disadvantage, depending on your POV -- my #Django / #svcs integration apparently just barely beat @ubernostrum to the punch on the name on PyPi. Fortunately, they're a good sport and collaborative, and since my plugin is #FOSS, both of our works can coexist. #Python

  14. Call it "first-mover advantage" -- or disadvantage, depending on your POV -- my #Django / #svcs integration apparently just barely beat @ubernostrum to the punch on the name on PyPi. Fortunately, they're a good sport and collaborative, and since my plugin is #FOSS, both of our works can coexist. #Python