home.social

#pythonflask — Public Fediverse posts

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

  1. Bwahahaha, enterprise-ify ALL THE THINGS! codeberg.org/Freedom-to-Write/

    Just trying to make sure #WritingMonth is something everyone can look forward to for years to come. :D

    #Python #PythonFlask

  2. A preview of the new Pallets Projects logos by @georgically in sticker form! Find me at the PyCon open spaces and sprints to get one before they run out. #PyCon #Python #Flask #PythonFlask

  3. Back at inbox zero for Flask 🎉 version 2.3 coming soon ™️
    #Python #Flask #PythonFlask

  4. Just finished a massive PR to deprecate bytes and charsets other than UTF-8 in Werkzeug 2.3. (You can still work with raw bytes in requests/responses, so it's still possible to use other charsets.) Surprisingly, very few tests failed due to it, which was a relief. Looking forward to making the PR removing all the deprecations 😈 github.com/pallets/werkzeug/pu #Python #Flask #Werkzeug #PythonFlask #PythonWerkzeug

  5. Last year at PyCon US 2022, @tonybaloney ran a basic benchmark of Flask. I finally got around to it, and achieved a ✨ 35% ✨ speedup to routing and environ processing.

    Due to Python 2/3, Werkzeug had its own modified copy of `urlparse`/`urllib.parse`, with a lot of unnecessary encoding/decoding due to str/bytes support. I finally replaced that with the standard library, and got a huge speed boost.

    github.com/pallets/werkzeug/pu

    #Python #Flask #PythonFlask #PythonWerkzeug

  6. Just documented the Flask application setup, serving, and request lifecycle. A pretty dense but important topic, one I was surprised wasn't documented already. I gave a talk on this at PyCon Canada 2018 then forgot to write it down 😅 flask.palletsprojects.com/en/2 #Python #PythonFlask

  7. My latest sample uses with Flask Blueprints, Flask-SQLAlchemy with PostgreSQL, pytest, ruff, black, pre-commit, Github actions, plus Docker for local dev and deployment to Azure Container Apps.

    Code @
    github.com/pamelafox/flask-sur

  8. Flask-SQLAlchemy 3.0.3 released pypi.org/project/Flask-SQLAlch with SLSA provenance for the build.

    It adds error messages around some common incorrect uses of the extension, which started failing more obviously (but mysteriously) with the 3.0 release.

    Now that I've got the publish workflow created, it's really easy to copy it to each project, and the automation is really nice.

    #Python #PythonFlask #SQLAlchemy #FlaskSQLAlchemy

  9. For me, one of the hardest parts about writing a app is deciding on my directory structure / overall project organization.

    For those of you who use Flask Blueprints, do you use this folder structure, /blueprints/<blueprintname> ?

  10. I gave a workshop today about containerizing web apps, both for local development and deployment.

    My first time teaching containers! As usual, teaching is helping me to understand better.

    pamelafox.github.io/my-py-talk

  11. Anyone familiar with Rust and PyO3 want to jump on Discord and help me improve MarkupSafe in Rust? My initial implementation is about 6 times slower than the native implementation on a basic benchmark. discord.gg/pallets #Python #Rust #PyO3 #PythonFlask

  12. developers: When you're developing locally, do you...

  13. Making a very lightweight surveys app as a demo and I don't want to require any user login.

    Should I check if someone has already answered based on cookie, localStorage, or sessionStorage?

  14. Flask and the other Pallets projects are all using `pyproject.toml` instead of `setup.py` and `setup.cfg`. Only MarkupSafe still has a `setup.py`, in order to configure the C speedups. #Python #PythonFlask #pyproject

  15. Flask and the other Pallets projects are all using `pyproject.toml` instead of `setup.py` and `setup.cfg`. Only MarkupSafe still has a `setup.py`, in order to configure the C speedups. #Python #PythonFlask #pyproject

  16. Flask and the other Pallets projects are all using `pyproject.toml` instead of `setup.py` and `setup.cfg`. Only MarkupSafe still has a `setup.py`, in order to configure the C speedups. #Python #PythonFlask #pyproject

  17. Flask and the other Pallets projects are all using `pyproject.toml` instead of `setup.py` and `setup.cfg`. Only MarkupSafe still has a `setup.py`, in order to configure the C speedups.

  18. Flask and the other Pallets projects are all using `pyproject.toml` instead of `setup.py` and `setup.cfg`. Only MarkupSafe still has a `setup.py`, in order to configure the C speedups. #Python #PythonFlask #pyproject

  19. Just released MarkupSafe 2.1.2. Aside from fixing a bug, it also provides Python 3.11 wheels, as well as SLSA provenance.

    This was the first automated release through GitHub workflows. Push a tag, and it automatically builds sdist and 49 platform wheels, generates SLSA provenance, creates a GitHub release with all the files, waits for review, then publishes them to PyPI.

    github.com/pallets/markupsafe/

    #Python #PythonFlask #PythonMarkupSafe #SLSA

  20. Flask and all Pallets projects now test against Python 3.12-dev, all tests passing. Didn't have to fix any code, only updated the CI config. #Python #PythonFlask