home.social

Search

1000 results for “djangocon”

  1. Today I am proud to announce that Phase One of my wildlife conservation project is complete.

    This project is personal. I come from a family of farmers and wildlife rangers. Conservation is not just a cause for me, it is my heritage. After losing my job, I spent months in the fields, mountains, and valleys of our beautiful land, Namibia, talking to my community, listening, and building.

    The road has not been easy. The project faces a serious challenge: funding. I have exhausted my budget. On top of that, my ideas are being taken by those in power, people who know that without their approval, the project cannot move forward. That is the biggest obstacle I face.

    And yet, at the end of it all, if this project never sees the light of day, I will still be proud that I tried. Proud that Django and Python were the tools I chose. Proud that the open-source community walked this road with me.

    I am also still open to job opportunities though.

    Thank you, Django community. Thank you, Python community, Thank you, Ubuntu community.. You gave me the tools and the encouragement. This is as much yours as it is mine.

    wildtrackcms.com/

    #Django #Python #OpenSource #WildlifeConservation #Africa

    @[email protected] @[email protected] @djangocon @ThePSF @CodenameTim

  2. Today I am proud to announce that Phase One of my wildlife conservation project is complete.

    This project is personal. I come from a family of farmers and wildlife rangers. Conservation is not just a cause for me, it is my heritage. After losing my job, I spent months in the fields, mountains, and valleys of our beautiful land, Namibia, talking to my community, listening, and building.

    The road has not been easy. The project faces a serious challenge: funding. I have exhausted my budget. On top of that, my ideas are being taken by those in power, people who know that without their approval, the project cannot move forward. That is the biggest obstacle I face.

    And yet, at the end of it all, if this project never sees the light of day, I will still be proud that I tried. Proud that Django and Python were the tools I chose. Proud that the open-source community walked this road with me.

    I am also still open to job opportunities though.

    Thank you, Django community. Thank you, Python community, Thank you, Ubuntu community.. You gave me the tools and the encouragement. This is as much yours as it is mine.

    wildtrackcms.com/

    #Django #Python #OpenSource #WildlifeConservation #Africa

    @[email protected] @[email protected] @djangocon @ThePSF @CodenameTim

  3. Today I am proud to announce that Phase One of my wildlife conservation project is complete.

    This project is personal. I come from a family of farmers and wildlife rangers. Conservation is not just a cause for me, it is my heritage. After losing my job, I spent months in the fields, mountains, and valleys of our beautiful land, Namibia, talking to my community, listening, and building.

    The road has not been easy. The project faces a serious challenge: funding. I have exhausted my budget. On top of that, my ideas are being taken by those in power, people who know that without their approval, the project cannot move forward. That is the biggest obstacle I face.

    And yet, at the end of it all, if this project never sees the light of day, I will still be proud that I tried. Proud that Django and Python were the tools I chose. Proud that the open-source community walked this road with me.

    I am also still open to job opportunities though.

    Thank you, Django community. Thank you, Python community, Thank you, Ubuntu community.. You gave me the tools and the encouragement. This is as much yours as it is mine.

    wildtrackcms.com/

    @[email protected] @[email protected] @djangocon @ThePSF @CodenameTim

  4. Today I am proud to announce that Phase One of my wildlife conservation project is complete.

    This project is personal. I come from a family of farmers and wildlife rangers. Conservation is not just a cause for me, it is my heritage. After losing my job, I spent months in the fields, mountains, and valleys of our beautiful land, Namibia, talking to my community, listening, and building.

    The road has not been easy. The project faces a serious challenge: funding. I have exhausted my budget. On top of that, my ideas are being taken by those in power, people who know that without their approval, the project cannot move forward. That is the biggest obstacle I face.

    And yet, at the end of it all, if this project never sees the light of day, I will still be proud that I tried. Proud that Django and Python were the tools I chose. Proud that the open-source community walked this road with me.

    I am also still open to job opportunities though.

    Thank you, Django community. Thank you, Python community, Thank you, Ubuntu community.. You gave me the tools and the encouragement. This is as much yours as it is mine.

    wildtrackcms.com/

    #Django #Python #OpenSource #WildlifeConservation #Africa

    @[email protected] @[email protected] @djangocon @ThePSF @CodenameTim

  5. Today I am proud to announce that Phase One of my wildlife conservation project is complete.

    This project is personal. I come from a family of farmers and wildlife rangers. Conservation is not just a cause for me, it is my heritage. After losing my job, I spent months in the fields, mountains, and valleys of our beautiful land, Namibia, talking to my community, listening, and building.

    The road has not been easy. The project faces a serious challenge: funding. I have exhausted my budget. On top of that, my ideas are being taken by those in power, people who know that without their approval, the project cannot move forward. That is the biggest obstacle I face.

    And yet, at the end of it all, if this project never sees the light of day, I will still be proud that I tried. Proud that Django and Python were the tools I chose. Proud that the open-source community walked this road with me.

    I am also still open to job opportunities though.

    Thank you, Django community. Thank you, Python community, Thank you, Ubuntu community.. You gave me the tools and the encouragement. This is as much yours as it is mine.

    wildtrackcms.com/

    #Django #Python #OpenSource #WildlifeConservation #Africa

    @[email protected] @[email protected] @djangocon @ThePSF @CodenameTim

  6. Just in time for my trip to DjangoCon 📰

  7. 🧵 Technical deep dive starting now!

    "Free Threaded Django"
    Breaking down the GIL barriers! Explore how Django is evolving for Python's free-threaded future and what this means for performance 🚀

  8. A chance to contribute to open source, collaborate with others in the community, and learn through hands-on work.

    Whether you’re new to contributing or experienced, there’s a place to get involved.

    2026.djangocon.us

  9. I'm planning to do a lightning ⚡ talk tonight - To JWT or not to JWT - why JSON Web Tokens might not be the one size that fits all (in my opinion)

    vote for me in the #DjangoCon Chat:
    chat.djangocon.eu/#narrow/chan

    #selfpromotion #django #jwt #security

  10. I'm planning to do a lightning ⚡ talk tonight - To JWT or not to JWT - why JSON Web Tokens might not be the one size that fits all (in my opinion)

    vote for me in the #DjangoCon Chat:
    chat.djangocon.eu/#narrow/chan

    #selfpromotion #django #jwt #security

  11. I'm planning to do a lightning ⚡ talk tonight - To JWT or not to JWT - why JSON Web Tokens might not be the one size that fits all (in my opinion)

    vote for me in the #DjangoCon Chat:
    chat.djangocon.eu/#narrow/chan

    #selfpromotion #django #jwt #security

  12. I'm planning to do a lightning ⚡ talk tonight - To JWT or not to JWT - why JSON Web Tokens might not be the one size that fits all (in my opinion)

    vote for me in the #DjangoCon Chat:
    chat.djangocon.eu/#narrow/chan

    #selfpromotion #django #jwt #security

  13. I'm planning to do a lightning ⚡ talk tonight - To JWT or not to JWT - why JSON Web Tokens might not be the one size that fits all (in my opinion)

    vote for me in the Chat:
    chat.djangocon.eu/#narrow/chan

  14. Parking an idea – WNDR, for Web Native Dynamic Rendering

    I realised today when writing a post into the Django Forum that I had a half formed idea in the new post form that I had totally forgot about out. I spent some chatting with Carlton about it, so it seemed worth dropping the ideas here before they’re lost to the ether.

    Background – Carlton’s DjangoCon Europe 2024 talk

    This post won’t make much sense without knowing about the talk I’m referring to, Carlton Gibson’s DjangoCon Europe talk – API Maybe: Bootstrapping a Web Application circa 2024.

    The link I’ve used points to the talk abstract and I’ve below on to the youtube recording of the talk too:

    https://www.youtube.com/watch?v=cLHVM31Rv6A

    The gist is that while we’ve had a few years of separate front and back end teams building projects of late, and that in 2024, it’s not really that necessary any more.

    For me there were a few takeaways relevant to this post, namely:

    • the tools for server side development are getting a lot better
    • a new paradigm has been emerging where we stop sending json back and forth over the wire with relatively ‘thick’ React/Ember/Vue clients that replicate logic client-side that we already implemented in the server
    • this paradigm instead relies on much less javascript in the browser, and sending html fragments that have been rendered server side instead
    • in the django ecosystem, we’re well served with htmx alphine.js and various django packages like django-htmx

    Naming this pattern

    Anyway, one thing we discussed is that while the pattern he described in his talk had been helpful to him, we didn’t know if there was a useful shortform name for it like we had in the mid 2000’s with the ‘AJAX’ term coined by Jesse James Garrett , for the new kind of interactivity that didn’t rely on entire page reloads all the time.

    In 2024, different frameworks now implement this process, but I’m unaware of the shared name for what is effectively the same kind of behaviour.

    In the Elixir community, there is one feature, LiveView that is similar. In the Rails community, I believe there is a related feature called TurboLinks.

    Anyway, names for stuff are useful, so we joked about wishing there was a pronouncable catchy acronym, for this pattern we could use in 2024. So over a drink, we started trying a few out.

    In the end, I think WNDR was one I remembered, standing for Web Native Dynamic Rendering, and pronounced wonder.

    Let’s unpack this:

    Web Native

    Web Native was a reference to where possible using the existing elements that the HTML language offers us, and all the functionality you get by default when you implement links and forms as the spec suggests.

    A common criticism of extremely heavy javascript front-ends is not only that they are slow, and resource hungry, but they also end up being a disaster accessibility wise. You lose many of the accessibility benefits from using proper hyperlinks and buttons for example, and in many cases, you lose the ability to hyperlink to views of the app too

    So Web Native is a response – to emphasis that we have loads of nice tools now, and where possible, we should invest the time to see what browsers now offer if you “go with the grain” as part of the approach to development, instead of immediately looking for a npm-installable library.

    Dynamic Rendering

    Was the reference to not needing a full page load to see updates, while avoiding the need explicitly name a technology.

    While back in the day AJAX explicitly referenced XMLHTTPRequest, HTMX isn’t the only game in town, so if you avoid naming specific technology, you can include not just Django-HTMX and Unicorn in the Django Ecosystem, but you could use this term to describe the patterns I linked to in other communities too.

    Big tents and all that.

    Anyway, it’s out of my head. I can move on with my life, and if I say WNDR in future, I now have a link I can refer to.

    Onwards!

    #django #webDevelopment #wndr

  15. Parking an idea – WNDR, for Web Native Dynamic Rendering

    I realised today when writing a post into the Django Forum that I had a half formed idea in the new post form that I had totally forgot about out. I spent some chatting with Carlton about it, so it seemed worth dropping the ideas here before they’re lost to the ether.

    Background – Carlton’s DjangoCon Europe 2024 talk

    This post won’t make much sense without knowing about the talk I’m referring to, Carlton Gibson’s DjangoCon Europe talk – API Maybe: Bootstrapping a Web Application circa 2024.

    The link I’ve used points to the talk abstract and I’ve below on to the youtube recording of the talk too:

    https://www.youtube.com/watch?v=cLHVM31Rv6A

    The gist is that while we’ve had a few years of separate front and back end teams building projects of late, and that in 2024, it’s not really that necessary any more.

    For me there were a few takeaways relevant to this post, namely:

    • the tools for server side development are getting a lot better
    • a new paradigm has been emerging where we stop sending json back and forth over the wire with relatively ‘thick’ React/Ember/Vue clients that replicate logic client-side that we already implemented in the server
    • this paradigm instead relies on much less javascript in the browser, and sending html fragments that have been rendered server side instead
    • in the django ecosystem, we’re well served with htmx alphine.js and various django packages like django-htmx

    Naming this pattern

    Anyway, one thing we discussed is that while the pattern he described in his talk had been helpful to him, we didn’t know if there was a useful shortform name for it like we had in the mid 2000’s with the ‘AJAX’ term coined by Jesse James Garrett , for the new kind of interactivity that didn’t rely on entire page reloads all the time.

    In 2024, different frameworks now implement this process, but I’m unaware of the shared name for what is effectively the same kind of behaviour.

    In the Elixir community, there is one feature, LiveView that is similar. In the Rails community, I believe there is a related feature called TurboLinks.

    Anyway, names for stuff are useful, so we joked about wishing there was a pronouncable catchy acronym, for this pattern we could use in 2024. So over a drink, we started trying a few out.

    In the end, I think WNDR was one I remembered, standing for Web Native Dynamic Rendering, and pronounced wonder.

    Let’s unpack this:

    Web Native

    Web Native was a reference to where possible using the existing elements that the HTML language offers us, and all the functionality you get by default when you implement links and forms as the spec suggests.

    A common criticism of extremely heavy javascript front-ends is not only that they are slow, and resource hungry, but they also end up being a disaster accessibility wise. You lose many of the accessibility benefits from using proper hyperlinks and buttons for example, and in many cases, you lose the ability to hyperlink to views of the app too

    So Web Native is a response – to emphasis that we have loads of nice tools now, and where possible, we should invest the time to see what browsers now offer if you “go with the grain” as part of the approach to development, instead of immediately looking for a npm-installable library.

    Dynamic Rendering

    Was the reference to not needing a full page load to see updates, while avoiding the need explicitly name a technology.

    While back in the day AJAX explicitly referenced XMLHTTPRequest, HTMX isn’t the only game in town, so if you avoid naming specific technology, you can include not just Django-HTMX and Unicorn in the Django Ecosystem, but you could use this term to describe the patterns I linked to in other communities too.

    Big tents and all that.

    Anyway, it’s out of my head. I can move on with my life, and if I say WNDR in future, I now have a link I can refer to.

    Onwards!

    #django #webDevelopment #wndr

  16. This morning we recorded half an hour of new content for the @foxleytalent YouTube channel.

    Watch, like and subscribe here: youtube.com/@foxleytalent

    With @JoshFoxleyTalent we covered some of the current hot topics in the Python/Django World at the moment.

    We'll record and release more of these over the coming months.

    Let us know if there's a topic you want us to talk about.

    AQA

    #Django #Python #DjangoCon #PyCon #DjangoDeveloper #PythonDeveloper #AQA

  17. This morning we recorded half an hour of new content for the @foxleytalent YouTube channel.

    Watch, like and subscribe here: youtube.com/@foxleytalent

    With @JoshFoxleyTalent we covered some of the current hot topics in the Python/Django World at the moment.

    We'll record and release more of these over the coming months.

    Let us know if there's a topic you want us to talk about.

    AQA

  18. This morning we recorded half an hour of new content for the @foxleytalent YouTube channel.

    Watch, like and subscribe here: youtube.com/@foxleytalent

    With @JoshFoxleyTalent we covered some of the current hot topics in the Python/Django World at the moment.

    We'll record and release more of these over the coming months.

    Let us know if there's a topic you want us to talk about.

    AQA

    #Django #Python #DjangoCon #PyCon #DjangoDeveloper #PythonDeveloper #AQA

  19. This morning we recorded half an hour of new content for the @foxleytalent YouTube channel.

    Watch, like and subscribe here: youtube.com/@foxleytalent

    With @JoshFoxleyTalent we covered some of the current hot topics in the Python/Django World at the moment.

    We'll record and release more of these over the coming months.

    Let us know if there's a topic you want us to talk about.

    AQA

    #Django #Python #DjangoCon #PyCon #DjangoDeveloper #PythonDeveloper #AQA

  20. This morning we recorded half an hour of new content for the @foxleytalent YouTube channel.

    Watch, like and subscribe here: youtube.com/@foxleytalent

    With @JoshFoxleyTalent we covered some of the current hot topics in the Python/Django World at the moment.

    We'll record and release more of these over the coming months.

    Let us know if there's a topic you want us to talk about.

    AQA

    #Django #Python #DjangoCon #PyCon #DjangoDeveloper #PythonDeveloper #AQA

  21. Đại hội 14 của Đảng là sự kết tinh trí tuệ, ý chí tự lực, tự cường của dân tộc, thể hiện quyết tâm phát triển đất nước phồn vinh, hạnh phúc. Trong các phiên thảo luận, Thủ tướng Phạm Minh Chính nhấn mạnh: Niềm tin của nhân dân, doanh nghiệp và bạn bè quốc tế là nền tảng quan trọng để Việt Nam đạt các mục tiêu kinh tế - xã hội. #DaiHoi14 #DangCongSan #VietNam #TuLucTuCuong #PhatTrien #KinhTeXaHoi #PoliticalCongress #VietnamDevelopment #SelfReliance #CommunistParty #EconomicGoals

    https://vietnamn

  22. Từ Lai Châu đến Sơn La, đồng bào các dân tộc cùng cán bộ, đảng viên gửi gắm niềm tin sâu sắc vào Đại hội XIV của Đảng – sự kiện chính trị trọng đại, thể hiện tinh thần đoàn kết, quyết tâm phát triển đất nước bền vững, công bằng và giàu bản sắc. #DaiHoiXIV #LaiChau #SonLa #DangCongSan #PhatTrien #DoanKet #Vietnam #CommunistParty #Congress2025 #NorthernVietnam

    vtcnews.vn/tu-lai-chau-den-son

  23. Từ Lai Châu đến Sơn La, đồng bào các dân tộc cùng cán bộ, đảng viên gửi gắm niềm tin sâu sắc vào Đại hội XIV của Đảng – sự kiện chính trị trọng đại, thể hiện tinh thần đoàn kết, quyết tâm phát triển đất nước bền vững, công bằng và giàu bản sắc. #DaiHoiXIV #LaiChau #SonLa #DangCongSan #PhatTrien #DoanKet #Vietnam #CommunistParty #Congress2025 #NorthernVietnam

    vtcnews.vn/tu-lai-chau-den-son

  24. 🎉 New Django OAuth2 AuthCodeFlow release version 1.4.1 🎊
    Authenticate with any OpenId Connect/Oauth2 provider through authorization code flow.
    PKCE is also supported

    pypi.org/project/django-oauth2

    📦 gitlab.com/snake_coders/django

    Feel free to give feedback 💬, open issues 📝 or merge requests 🎁.
    📢 Boost appreciated.

    gitlab.com/snake_coders/django
    #djangooauth2authcodeflow #oauth2 #oauth2client #openid #openidconnect #oidc #oidcclient #django

  25. 🎉 New Django OAuth2 AuthCodeFlow release version 1.4.1 🎊
    Authenticate with any OpenId Connect/Oauth2 provider through authorization code flow.
    PKCE is also supported

    pypi.org/project/django-oauth2

    📦 gitlab.com/snake_coders/django

    Feel free to give feedback 💬, open issues 📝 or merge requests 🎁.
    📢 Boost appreciated.

    gitlab.com/snake_coders/django
    #djangooauth2authcodeflow #oauth2 #oauth2client #openid #openidconnect #oidc #oidcclient #django

  26. 🎉 New Django OAuth2 AuthCodeFlow release version 1.4.0 🎊
    Authenticate with any OpenId Connect/Oauth2 provider through authorization code flow.
    PKCE is also supported

    pypi.org/project/django-oauth2

    📦 gitlab.com/snake_coders/django

    Feel free to give feedback 💬, open issues 📝 or merge requests 🎁.
    📢 Boost appreciated.

    gitlab.com/snake_coders/django
    #djangooauth2authcodeflow #oauth2 #oauth2client #openid #openidconnect #oidc #oidcclient #django

  27. 🎉 New Django OAuth2 AuthCodeFlow release version 1.4.0 🎊
    Authenticate with any OpenId Connect/Oauth2 provider through authorization code flow.
    PKCE is also supported

    pypi.org/project/django-oauth2

    📦 gitlab.com/snake_coders/django

    Feel free to give feedback 💬, open issues 📝 or merge requests 🎁.
    📢 Boost appreciated.

    gitlab.com/snake_coders/django
    #djangooauth2authcodeflow #oauth2 #oauth2client #openid #openidconnect #oidc #oidcclient #django

  28. Last year at #DjangoCon US, Lisa Dusseault showed off the data pipeline framework, Phaser. I enjoyed this talk because it made me realize I should revisit how data processing in my project should work.

    better-simple.com/lunch-talks/

    This talk is worth watching if you're interested in:
    - Contributing to Phaser
    - Data pipeline frameworks
    - Learning how to approach building your own framework

    #Python #Data #ETL

  29. 🚀 Day 1 on django-rls-tenants — bringing true PostgreSQL Row-Level Security to Django multitenancy!

    Instead of separate schemas or filtered querysets, this library leverages native RLS policies at the DB level to isolate tenant data automatically.

    ✅ Pros:
    • True DB-level isolation — tenants can't bleed into each other
    • Transparent to Django ORM — no custom managers needed
    • Leaner than schema-per-tenant approaches
    • Scales well for high tenant counts
    • Security enforced even outside the app layer

    ❌ Cons:
    • PostgreSQL-only (no MySQL/SQLite support)
    • RLS policies add complexity to migrations
    • Debugging cross-tenant issues can be tricky
    • Superuser connections bypass RLS — needs care
    • Less community tooling than shared-schema approaches

    Still very early, but the foundations are solid. Would love feedback from anyone who's tackled multitenancy in Django before! 🐘🐍

    #Django #PostgreSQL #Python #Multitenancy #RLS #RowLevelSecurity #OpenSource #WebDev #SaaS #DjangoORM #DevLife

  30. 🚀 Day 1 on django-rls-tenants — bringing true PostgreSQL Row-Level Security to Django multitenancy!

    Instead of separate schemas or filtered querysets, this library leverages native RLS policies at the DB level to isolate tenant data automatically.

    ✅ Pros:
    • True DB-level isolation — tenants can't bleed into each other
    • Transparent to Django ORM — no custom managers needed
    • Leaner than schema-per-tenant approaches
    • Scales well for high tenant counts
    • Security enforced even outside the app layer

    ❌ Cons:
    • PostgreSQL-only (no MySQL/SQLite support)
    • RLS policies add complexity to migrations
    • Debugging cross-tenant issues can be tricky
    • Superuser connections bypass RLS — needs care
    • Less community tooling than shared-schema approaches

    Still very early, but the foundations are solid. Would love feedback from anyone who's tackled multitenancy in Django before! 🐘🐍