url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://dev.to/theodesp | Theofanis Despoudis - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close Follow User actions Theofanis Despoudis Senior Software Engineer @wpengine, Experienced mentor @codeimentor, Technical Writer @fixate.io, Book author Location Ireland Joined Joined on Jun 19, 2017 github website twitter website Work Senior Software Engineer at WP Engine Eight Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least eight years. Got it Close 2 Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 Got it Close Seven Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least seven years. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Six Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least six years. Got it Close Trusted Member 2022 Awarded for being a trusted member in 2022. Got it Close Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Hacktoberfest 2019 Awarded for successful completion of the 2019 Hacktoberfest challenge. Got it Close 4 Week Writing Streak You've posted at least one post per week for 4 consecutive weeks! Got it Close CSS Awarded to the top CSS author each week Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close Beloved Comment Awarded for making a well-loved comment, as voted on with 25 heart (❤️) reactions by the community. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close Show all 16 badges More info about @theodesp Organizations Techway GitHub Repositories cache-line Returns your current CPU cache line size in bytes C++ • 4 stars fetch-future A fetch that returns Futures instead of Promises JavaScript • 4 stars caddy Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS Go • 53139 stars go-calendly go-calendly is a Go client library for accessing the Calendly API https://godoc.org/github.com/theodesp/go-calendly/calendly Go • 7 stars awesome-coding-camps A curated list of awesome Coding Bootcamps and websites to help you boost your career in Programming 356 stars unionfind An idiomatic implementation of a weighted Union Find data structure with path compression in Go. Go • 21 stars Skills/Languages Javascript, Python, Go, HTML, CSS, Scheme Currently learning Kotlin, Kubernetes, Go, Blockchain, Spring Boot Currently hacking on https://codethat.today/ Post 57 posts published Comment 514 comments written Tag 38 tags followed New MEAP update "Full-Stack AI for Web Developers" Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jan 28 '25 New MEAP update "Full-Stack AI for Web Developers" # webdev # ai # javascript 1 reaction Comments 1 comment 1 min read Want to connect with Theofanis Despoudis? Create an account to connect with Theofanis Despoudis. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Full-Stack AI for Web Developers Book Launch + Manning Holiday Sale Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Dec 20 '24 Full-Stack AI for Web Developers Book Launch + Manning Holiday Sale # webdev # ai # javascript 1 reaction Comments 2 comments 1 min read My New Book: Full-Stack AI for Web Developers - 50% discount code included! AMA! Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Dec 12 '24 My New Book: Full-Stack AI for Web Developers - 50% discount code included! AMA! # webdev # ai # javascript # react 2 reactions Comments 2 comments 1 min read My new book about Typescript 4 is published. AMA Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Sep 16 '21 My new book about Typescript 4 is published. AMA # typescript # programming # learning 2 reactions Comments Add Comment 1 min read How to read Haskell Documentation. Step by step guide. Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 20 '20 How to read Haskell Documentation. Step by step guide. # haskell # tutorial # documentation # algorithms 6 reactions Comments 3 comments 7 min read Solving Algorithm Challenges in Haskell: Anagrams Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 17 '20 Solving Algorithm Challenges in Haskell: Anagrams # haskell # learning # algorithms # functional 12 reactions Comments 6 comments 5 min read Build a type safe React App with ReasonML, Part 1 Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow for Techway Mar 27 '20 Build a type safe React App with ReasonML, Part 1 # react # tutorial # reason 36 reactions Comments Add Comment 7 min read 30 minute introduction to ReasonML for React Developers Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow for Techway Mar 23 '20 30 minute introduction to ReasonML for React Developers # reason # tutorial # beginners # react 16 reactions Comments 1 comment 8 min read Doomsday? Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Mar 4 '20 Doomsday? # discuss 4 reactions Comments 3 comments 1 min read Top 30 Javascript Interview Warmup Exercises Part 3 Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Feb 9 '20 Top 30 Javascript Interview Warmup Exercises Part 3 # javascript # interview # programming 90 reactions Comments 2 comments 8 min read Top 30 Javascript Interview Warmup Exercises Part 2 Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jan 18 '20 Top 30 Javascript Interview Warmup Exercises Part 2 # javascript # interview # programming 207 reactions Comments 3 comments 8 min read A word on Technical Interviews Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jan 8 '20 A word on Technical Interviews # interview # advice 22 reactions Comments 8 comments 4 min read Top 30 Javascript Interview Warmup Exercises Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jan 6 '20 Top 30 Javascript Interview Warmup Exercises # javascript # interview # programming 287 reactions Comments 19 comments 6 min read How to Read Java Bytecode (with examples) Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Dec 9 '19 How to Read Java Bytecode (with examples) # java # jvm # tutorial 38 reactions Comments 1 comment 7 min read "Hello World" performance comparison between GraalVM and Go Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Dec 1 '19 "Hello World" performance comparison between GraalVM and Go # go # kotlin # performance 9 reactions Comments 4 comments 3 min read Exploring Open Source Architectures - Redis.py Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 29 '19 Exploring Open Source Architectures - Redis.py # redis # python # architecture 12 reactions Comments 3 comments 5 min read Please don't post Paywalled Medium links Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 26 '19 Please don't post Paywalled Medium links # discuss # rant # meta 20 reactions Comments 15 comments 1 min read Top HTML Interview Questions with detailed answers 🌺🌴😃🤽🏨🏖️ Part II Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 24 '19 Top HTML Interview Questions with detailed answers 🌺🌴😃🤽🏨🏖️ Part II # html # interview # career 113 reactions Comments 6 comments 3 min read Top HTML Interview Questions with detailed answers 🍁🔥👌😊🤘 Part I Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 16 '19 Top HTML Interview Questions with detailed answers 🍁🔥👌😊🤘 Part I # interview # html # career 187 reactions Comments 4 comments 5 min read Top CSS Interview Questions with detailed answers.👑✨😊🏈⚽🏀🏐⚾ Part III Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 6 '19 Top CSS Interview Questions with detailed answers.👑✨😊🏈⚽🏀🏐⚾ Part III # css # interview # career 58 reactions Comments 4 comments 7 min read Two CSS properties Walk Into a Bar... Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 4 '19 Two CSS properties Walk Into a Bar... # jokes # css 62 reactions Comments 12 comments 1 min read Top CSS Interview Questions with detailed answers.😁🏆🥇💯 Part II Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 2 '19 Top CSS Interview Questions with detailed answers.😁🏆🥇💯 Part II # css # interview # career 89 reactions Comments Add Comment 8 min read Top CSS Interview Questions with detailed answers.✌️🤩✌️ Part I Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 28 '19 Top CSS Interview Questions with detailed answers.✌️🤩✌️ Part I # css # interview # career 340 reactions Comments 11 comments 7 min read Best ways to use React Hooks for state management Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 25 '19 Best ways to use React Hooks for state management # discuss # react # javascript # typescript 65 reactions Comments 3 comments 7 min read Creating Reusable Web Components with Stencil.js Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 19 '19 Creating Reusable Web Components with Stencil.js # tutorial # webdev # webcomponents # javascript 10 reactions Comments Add Comment 4 min read Best Practices for using Feature Flags 🏳️ Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 17 '19 Best Practices for using Feature Flags 🏳️ # discuss # webdev # tips # codequality 7 reactions Comments Add Comment 5 min read Using Terraform remote state for collaboration Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 15 '19 Using Terraform remote state for collaboration # devops # tutorial # terraform 24 reactions Comments 2 comments 3 min read Introducing CodeThat.today 🙌🍾 Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 14 '19 Introducing CodeThat.today 🙌🍾 # showdev # coding # webdev 11 reactions Comments 9 comments 2 min read Spectrum Joins GitHub Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Dec 3 '18 Spectrum Joins GitHub # discuss # github # webdev 6 reactions Comments 7 comments 1 min read "Computer programmer," is a skill, not a job. Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Nov 20 '18 "Computer programmer," is a skill, not a job. # discuss # programming # productivity 15 reactions Comments 2 comments 1 min read What was your first PR on Github? Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Sep 18 '18 What was your first PR on Github? # discuss # github # programming 28 reactions Comments 26 comments 1 min read This is the feeling of working with legacy code. Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 29 '18 This is the feeling of working with legacy code. # discuss # php # productivity 34 reactions Comments 20 comments 3 min read A Step-by-Step Guide to Go Internationalization (i18n) & Localization (l10n) Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow May 18 '18 A Step-by-Step Guide to Go Internationalization (i18n) & Localization (l10n) # go # programming # tutorial 56 reactions Comments 1 comment 13 min read Explain Proof of Stake (PoS) like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Apr 23 '18 Explain Proof of Stake (PoS) like I'm five # explainlikeimfive # discuss # blockchain 21 reactions Comments Add Comment 1 min read Explain Service Mesh like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Feb 12 '18 Explain Service Mesh like I'm five # explainlikeimfive # devops 15 reactions Comments 1 comment 1 min read Explain Cgroups like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Feb 5 '18 Explain Cgroups like I'm five # explainlikeimfive # linux 20 reactions Comments 1 comment 1 min read Mastering some Advanced Design Patterns: Resource Pool Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jan 2 '18 Mastering some Advanced Design Patterns: Resource Pool # programming # designpatterns 36 reactions Comments 3 comments 6 min read Task for this New year. Find bugs in Dev.to website. Make it better. Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jan 2 '18 Task for this New year. Find bugs in Dev.to website. Make it better. # discuss # debugging # ui # meta 41 reactions Comments 5 comments 1 min read Let's Implement a Bloom Filter in Go Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Dec 18 '17 Let's Implement a Bloom Filter in Go # datastructures # computerscience # go 16 reactions Comments 4 comments 5 min read Understanding SOLID Principles: Liskov Substitution Principle Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Nov 23 '17 Understanding SOLID Principles: Liskov Substitution Principle # bestpractices # development 24 reactions Comments 2 comments 4 min read Explain this Javascript expression just like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Nov 22 '17 Explain this Javascript expression just like I'm five # discuss # quiz # explainlikeimfive 17 reactions Comments 6 comments 1 min read Understanding SOLID Principles: Interface Segregation Principle Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Nov 11 '17 Understanding SOLID Principles: Interface Segregation Principle # solid # bestpractices # development # learning 29 reactions Comments 1 comment 4 min read Kitchen-Sink-As-A-Service Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Nov 6 '17 Kitchen-Sink-As-A-Service # discuss # iot # cloud 8 reactions Comments 7 comments 1 min read Understanding SOLID Principles: Open-Closed Principle Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Nov 2 '17 Understanding SOLID Principles: Open-Closed Principle # solid # bestpractices # development # learning 39 reactions Comments 2 comments 4 min read Explain Serverless like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Oct 3 '17 Explain Serverless like I'm five # explainlikeimfive # discuss # cloud 16 reactions Comments 2 comments 1 min read Explain Git Rebase just like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Sep 28 '17 Explain Git Rebase just like I'm five # explainlikeimfive # git # discuss 32 reactions Comments 12 comments 1 min read How Machine Learning and AI could eventually replace development work Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Sep 11 '17 How Machine Learning and AI could eventually replace development work # ai # machinelearning 31 reactions Comments 2 comments 6 min read How to be an awesome programmer. Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 31 '17 How to be an awesome programmer. # career # productivity 131 reactions Comments 1 comment 4 min read Understanding SOLID Principles: Single Responsibility Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 22 '17 Understanding SOLID Principles: Single Responsibility # solid # bestpractices # development # learning 22 reactions Comments Add Comment 6 min read Explain Monads Like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 18 '17 Explain Monads Like I'm five # explainlikeimfive # discuss 63 reactions Comments 18 comments 1 min read What DevOps really is? A developers perspective. Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 12 '17 What DevOps really is? A developers perspective. # devops # documentation # continuousdelivery 28 reactions Comments 4 comments 5 min read Explain git like I'm five Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Aug 9 '17 Explain git like I'm five # explainlikeimfive # git # discuss 17 reactions Comments 7 comments 1 min read Behind Continuations Passing Style. Practical Examples in Go Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 28 '17 Behind Continuations Passing Style. Practical Examples in Go # go # closures # continuations 11 reactions Comments Add Comment 5 min read Understanding SOLID Principles: Dependency Inversion Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 18 '17 Understanding SOLID Principles: Dependency Inversion # solid # di # inversify # ooprinciples 53 reactions Comments 6 comments 7 min read What is BDD anyway? Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 7 '17 What is BDD anyway? # bdd # tdd # javascript # cucumberjs 10 reactions Comments 2 comments 7 min read ‘this’-less Javascript Development Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jul 1 '17 ‘this’-less Javascript Development # javascript # closures # deque # datastructures 5 reactions Comments 2 comments 9 min read Hi, I'm Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Jun 20 '17 Hi, I'm Theofanis Despoudis # introduction 16 reactions Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://twitter.com/intent/tweet?text=%22When%20to%20Use%20Server-Side%20rendering%20vs%20Static%20Generation%20in%20Next.js%22%20by%20Dylan%20Muraco%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fdmuraco3%2Fwhen-to-user-server-side-rendering-vs-static-generation-in-nextjs-8ab | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:02 |
https://dev.to/ishaan_agrawal/vs-codes-unhinged-malware-problem-what-microsofts-own-logs-reveal-5e1p | Concerning Amounts of Malware in the VS Code Marketplace: What Microsoft’s Own Logs Reveal - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Ishaan Agrawal Posted on Jan 9 Concerning Amounts of Malware in the VS Code Marketplace: What Microsoft’s Own Logs Reveal # security # productivity # programming # backend If you are like me, your VS Code setup is a carefully curated collection of themes, linters, and productivity boosters. We trust the Visual Studio Marketplace to be a safe haven for tools that make our lives easier. But if you take a look under the hood at what is actually getting removed from the platform, the picture gets a lot uglier. I recently went down a rabbit hole looking at the official list of removed extensions on GitHub, and it is a wake-up call for anyone who blindly clicks "Install." The "Install First, Ask Questions Later" Problem The way the Marketplace works is fundamentally based on a reactive model. Microsoft does have automated scans, but a staggering amount of malicious code only gets taken down after it has already been published and downloaded by unsuspecting developers. When you look at the logs of removed extensions, you see a constant stream of entries flagged for things like: Credential Theft: Extensions designed to scrape your .env files or SSH keys. Typosquatting: Malicious clones of popular extensions like Prettier or ESLint that hope you won't notice a tiny misspelling in the name. Remote Access: Plugins that open backdoors into your development environment. Why This Matters to You As developers, our machines are high-value targets. We have access to production servers, API keys, proprietary source code, and personal data. A single malicious extension has the same permissions as you do. It can read your files, track your keystrokes, and send your data to a remote server without you ever seeing a popup. The scary part isn't just that these extensions exist. It is that they are actively making it onto the store, staying there for days or weeks, and only getting purged after the damage might already be done. How to Protect Your Workflow You don't have to stop using extensions, but you do need to stop treating the Marketplace like a curated app store where everything is vetted. Here is how I have changed my approach: Check the Publisher: Look for the "Verified" checkmark. If a popular tool is being published by a random account with no history, stay away. Verify the Numbers: If an extension claims to be a popular tool but only has 500 downloads while the real one has 5 million, you are looking at a typosquatting attempt. Audit Your List: Every few months, go through your installed extensions. If something hasn't been updated in years, maybe double-check its safety. Do a Deeper Scan: Since we know malicious code can bypass basic store filters, you need a more aggressive way to vet what you are installing. I suggest using a VS Code extension security analyzer. It will perform a deep security assessment by looking for obfuscated code, hidden network connections, and dangerous dependencies that standard checks often miss. That will give you a clear risk report before you let the code touch your machine. Final Thoughts The VS Code Marketplace is an incredible resource, but we have to stop assuming it is inherently safe. The "Removed Packages" list is proof that malware is constantly slipping through the cracks. Take five minutes today to look at what you have installed. It is much better to spend a few minutes auditing your setup now than to spend a week dealing with a compromised machine later. What's your take? Do you check the credentials of every extension you install, or do you just hit install and hope for the best? Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Ishaan Agrawal Follow Security Researcher & Developer Joined Jun 26, 2025 More from Ishaan Agrawal 🚨BREAKING: A Self-Propagating Worm Is Hitting VSCode Extensions Right Now— Here’s How to Protect Yourself # vscode # security # software # programming Are Your VSCode Extensions Safe? The Risk We Don’t Talk About # vscode # security # productivity # cybersecurity VSCode Extensions are Malicious—Here's What I Found After Scanning 1,000 of Them # security # vscode # programming # ai 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/psf/workgroups/ | Work Groups of the Python Software Foundation | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Work Groups of the Python Software Foundation Active Work Groups Code of Conduct Work Group Diversity and Inclusion Work Group Education & Outreach Work Group Fellows Work Group Grants Work Group Infrastructure Work Group Python Job Board Work Group Packaging Work Group Trademarks Work Group Inactive Committees & Work Groups Scientific Python Work Group Marketing Work Group Sprint Work Group Public Support Committee (PSC) Public Relations Committee (PRC) Python Conference Committee (PCC) Cuban Pythonistas Work Group Active Work Groups Code of Conduct Work Group Formed: May 2018 Mailing List: conduct-wg at python.org The workgroup's purpose is to foster a diverse and inclusive Python community by enforcing the PSF code of conduct, along with providing guidance and recommendations to the Python community on codes of conduct, that supports the PSF mission of “ongoing development of Python-related technology and educational resources”. Establishing resolution: RESOLVED , that the Python Software Foundation add the following new members to the code of conduct work group: Anwesha Das, Brett Cannon, Jeff Triplett, Kenneth Reitz, Maricela Sanchez Miranda, Philip James, Rami Chowdhury, Sasha Romijn, Thomas Wouters. Approved May 31, 2018 The list of members can be found here . Diversity and Inclusion Work Group Formed: November 2020 Notes: https://wiki.python.org/psf/DiversityandInclusionWG The workgroup's purpose is to further the PSF’s mission to ‘support and facilitate the growth of a diverse and international community of Python programmers.’ We also aim to provide guidance to the PSF Board of Directors in line with this mandate. Establishing resolution: RESOLVED, that the Python Software Foundation approve the creation of the PSF Diversity and Inclusion Working Group to actively further the PSF’s mission to ‘support and facilitate the growth of a diverse and international community of Python programmers.’ The group will be formed under this charter: https://docs.google.com/document/d/1uvIztyTLr6Cq4yQpNCjPlIl5pYlUjYYYqWCG1ZQrkHE/edit?usp=sharing Education & Outreach Work Group Formed: June 2011 Re-formed: December 2024 Charter: Education & Outreach Work Group Charter The Education & Outreach Workgroup's (EOW) purpose is to support the Python Software Foundation’s mission to promote the Python programming language, especially in supporting and enhancing the education of Python. Re-establishing resolution: RESOLVED , that the Python Software Foundation Board of Directors approve the Education & Outreach Work Group Charter as written at https://wiki.python.org/psf/PythonEduWGCharter . Approved; 10-0-0 by PSF Board Meeting vote on 11 December, 2024. Fellows Work Group Formed: July 2017 Mailing List: psf-fellow at python.org Establishing resolution: RESOLVED , that the Python Software Foundation acknowledge the creation of the PSF Fellow Work Group to accept, review and approve Fellow applications for membership. Grants Work Group Formed: August 2015 Mailing List: psf-grants at python.org Establishing resolution: RESOLVED , that the Python Software Foundation acknowledge the creation of the PSF Grants Workgroup to review proposals to the PSF for grants in support of conferences, training workshops, and related projects. Infrastructure Work Group Formed: April 2010 Mailing List: infrastructure at python.org This committee works on making concrete plans for improving python.org infrastructure and to address technical infrastructure broadly. The board created this committee at a special meeting on March 24 2005. In June 2013, this committee was formed into a PSF Working Group. The charter for this working group can be found here . Python Job Board Work Group Formed: July 2018 Mailing List: jobs at python.org This working group was created to help manage the job board with the support of PSF staff. Current resolution July 2018: RESOLVED , that the Python Software Foundation acknowledge the creation of the Python Software Foundation Jobs Work Group to manage, review, and approve job postings. Packaging Work Group Formed: May 2016 Notes: https://wiki.python.org/psf/PackagingWG Mailing List: packaging-wg at python.org The purpose of this working group is to support the larger efforts of improving and maintaining the packaging ecosystem in Python through fundraising and disbursement of raised funds. It will largely focus on efforts such as PyPI, pip, packaging.python.org, setuptools, and cross project efforts. Establishing resolution: RESOLVED , that the Python Software Foundation acknowledge the creation of the PSF Packaging WG to support the larger efforts of improving and maintaining the packaging ecosystem in Python through fundraising and disbursement of raised funds https://wiki.python.org/psf/PackagingWG/Charter Trademarks Work Group Formed: November 2008 Mailing List: psf-trademarks at python.org This committee assesses actual and proposed uses of the Python trademarks. See the PSF Trademark Usage Policy . Work group resolution: RESOLVED , that the Trademark Committee shall be a working group of the Python Software Foundation, co-chaired by David Mertz and Marc-André Lemburg. Membership shall consist of co-chairs and additionally Carl Trachte, Doug Napoleone, David Goodger, Van Lindberg. Co-chairs shall, by joint agreement, have the power to add or remove committee members, with the current membership roster to be approved by the Python Software Foundation Board of Directors at least once per year Approved 7-0-1 by IRC vote, 16 August, 2013. Establishing resolution: RESOLVED , that a Project Management Committee designated the "Trademarks Committee" (TMC) be formed with David Goodger, Marc-Andre Lemburg, Van Lindberg, David Mertz, Doug Napoleone, James Tauber and Trevor Toenjes as initial members, and James Tauber as the initial chairman, and that the Trademarks Committee shall, when so instructed by the PSF Board, assess trademarks for compliance with the current PSF Trademark Usage Policy and advise the PSF Board on what action, if any, to take. Inactive Committees & Work Groups Scientific Python Work Group Formed: April 2015 Mailing List: scientific at python.org This working group shall draw on the expertise of both the PSF and NumFOCUS, and on the broader scientific Python community in general, to select the best use of its budgeted funds to advance the scope, breadth, and utility of Python for scientific work. In essence, the purpose of the group is to grant funds allocated to it by PSF and/or NumFOCUS towards conferences, user groups, educational, and development efforts. Current resolution June 2015: RESOLVED , that the Python Software Foundation recognize the Scientific Python Workgroup as an official PSF workgroup. Marketing Work Group Formed: August 2015 Mailing list: psf-marketing-wg at python.org Establishing resolution: RESOLVED , that the Python Software Foundation acknowledge the creation of the PSF Grants Workgroup to review proposals to the PSF for grants in support of conferences, training workshops, and related projects. Sprint Work Group Formed: May 2010 Mailing List: sprints at python.org The committee will be responsible for the coordination and review and approval of sprint proposals. For more information, see the sprints website . Establishing resolution: RESOLVED , that the Board approves the creation of a specific "Targeted Sprint Committee" and allocates a yearly budget of 5000 USD for the funding of targeted, community based sprints with Jesse Noller as the initial Chairman, and additional members as needed per project requirements and approved by the board. Public Support Committee (PSC) Dissolved: February 25, 2007 Formed: August 13, 2002 Chairman: Stephan Deibel Members: Steve Holden, Neil Norwitz, David Goodger, and Stephan Deibel Mailing List: http://mail.python.org/mailman/listinfo/psc The Public Support Committee (PSC) is charged with fund raising for the PSF, which it does by creating fund raising messages, ads, and materials, soliciting donations from private and commercial contributors, and managing the PSF's fund raising infrastructure. Charter RESOLVED, That the Public Support Committee (PSC) be made up of the following initial members: Stephan Deibel, Jeremy Hylton, Marc-Andre Lemburg, Tim Peters, Aahz, Alex Martelli, Neil Norwitz and Greg Ward, that the committee follows rules analog to those set forth in the PSF bylaws for the PSF board with respect to voting and meetings, and that Marc-Andre Lemburg will be the initial chairman of the PSC. Amended Charter (2004-04-13) RESOLVED, that the Public Support Committee formed in August 2002 shall continue under current membership and leadership, and that the committee's activities shall now be constrained to all aspects of fund raising for the PSF, including but not limited to (1) creation of fund raising messages, ads, and materials, (2) soliciting of donations from private and company contributors, and (3) management of fund raising infrastructure. Public Relations Committee (PRC) Dissolved: April 12, 2005 Formed: April 13, 2004 Chairman: Steve Holden Members: Aahz, Kevin Altis, Steve Holden, Andrew Kuchling, Tim Parkin, Barry Warsaw Mailing List: http://mail.python.org/mailman/listinfo/psf-prc The Public Relations Committee (PRC) is responsible for the development of official informational, marketing, and advocacy materials for the Python programming language. This includes the python.org website and brand identities associated with the PSF and Python, among other things. The PRC also promotes Python in commercial, governmental and educational contexts, in order to facilitate the recruitment of new users and contributors to the language. Establishing Resolution RESOLVED, that a Public Relations (PR) Committee is formed, with Tim Parkin, Kevin Altis, Aahz, Barry Warsaw, Andrew Kuchling, and Steve Holden as initial members, and Steve Holden as the initial chairman and Vice President of Public Relations, that the PR Committee replaces and subsumes the activities of the previously disbanded Web Committee, and that the PR Committee shall: Facilitate and oversee the development and maintenance of the official informational, marketing, and advocacy materials for the Python programming language, including but not limited to those appearing on python.org, brochures, and press releases. Ensure that content and design for such materials is consistent and appropriate with the mission and requirements of the Python Software Foundation and the needs and ideals of the Python open source community. Develop and manage brand identities associated with the Python Software Foundation and Python. Actively promote Python in commercial, governmental and educational contexts, in order to facilitate the recruitment of new users and contributors to Python. Python Conference Committee (PCC) Dissolved: March 14, 2008 Formed: Oct 14, 2003 Chairman: Andrew Kuchling Members: David Ascher, David Goodger, Steve Holden (secretary), Andrew Kuchling (chair) Mailing List: http://mail.python.org/mailman/listinfo/pycon-organizers The PyCon Committee runs PyCon , the annual developer-oriented conference for the Python programming language. Establishing Resolution RESOLVED, that the Foundation establish a Project Management Committee, the Python Conference Committee, responsible for organizing and sponsoring conferences that advance the Foundation's mission. The committee is authorized to incur expenses up to a limit establish by the board for a specific conference. The chairman of the committee shall be Vice President of the Corporation. The initial members of the committee shall be David Ascher, Steve Holden, and Jeremy Hylton. Ascher will be its initial chairman. Amending Resolution (2005-05-06) RESOLVED, that Andrew Kuchling be appointed a member of the Python Conference Committee, and that he be appointed the new chair of this Committee. By this resolution, the membership of the Committee will be David Ascher, Steve Holden (secretary), Jeremy Hylton, Andrew Kuchling (chair). Amending Resolution (2007-01-08) RESOLVED, that the Conference Committee chair be authorized to appoint and dismiss committee members, subject to prompt reporting to the Board. Cuban Pythonistas Work Group Formed: March 2015 Moderator: David Mertz Mailing List: python-cuba at python.org Current resolution June 2015: RESOLVED , that the Python Software Foundation recognize the Python Cuba Workgroup as an official PSF workgroup. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://dev.to/t/callbacks | Callbacks - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # callbacks Follow Hide Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Mastering Asynchronous Operations in Node.js: Practical Strategies and Examples Jeferson Eiji Jeferson Eiji Jeferson Eiji Follow Dec 8 '25 Mastering Asynchronous Operations in Node.js: Practical Strategies and Examples # node # asynchronous # promises # callbacks 1 reaction Comments Add Comment 1 min read Functional Strategy Pattern: Unlocking Clean Code with Higher-Order Functions and Callbacks Aditya Pratap Bhuyan Aditya Pratap Bhuyan Aditya Pratap Bhuyan Follow Aug 6 '25 Functional Strategy Pattern: Unlocking Clean Code with Higher-Order Functions and Callbacks # strategypattern # functions # callbacks 1 reaction Comments Add Comment 4 min read What Is a JavaScript Callback? Mateen Kiani Mateen Kiani Mateen Kiani Follow Jun 26 '25 What Is a JavaScript Callback? # javascript # callbacks # asynchronous Comments Add Comment 3 min read Callbacky - bring callbacks to simple Ruby objects Jokūbas Pučinskas Jokūbas Pučinskas Jokūbas Pučinskas Follow Jun 3 '25 Callbacky - bring callbacks to simple Ruby objects # ruby # callbacks # gem 1 reaction Comments Add Comment 1 min read Demystify asynchronous JavaScript: Callbacks, Promises, and Async/Await Sandesh S Sandesh S Sandesh S Follow Mar 15 '25 Demystify asynchronous JavaScript: Callbacks, Promises, and Async/Await # javascript # callbacks # promises # asyncawait Comments Add Comment 3 min read Understanding Callbacks in JavaScript - From A Beginner For Beginners Reilly Shofner Reilly Shofner Reilly Shofner Follow Feb 4 '25 Understanding Callbacks in JavaScript - From A Beginner For Beginners # javascript # callbacks Comments Add Comment 4 min read 🚀 Mastering Callbacks and Promises in JavaScript : A Complete Guide to Asynchronous Programming DCT Technology Pvt. Ltd. DCT Technology Pvt. Ltd. DCT Technology Pvt. Ltd. Follow Jan 28 '25 🚀 Mastering Callbacks and Promises in JavaScript : A Complete Guide to Asynchronous Programming # webdev # javascript # callbacks # programming 6 reactions Comments Add Comment 2 min read Understanding Interrupts and Callbacks in Embedded Systems Aditya Pratap Bhuyan Aditya Pratap Bhuyan Aditya Pratap Bhuyan Follow Jan 11 '25 Understanding Interrupts and Callbacks in Embedded Systems # embeddedsystem # interrupts # callbacks 4 reactions Comments Add Comment 6 min read Mastering Asynchronous JavaScript: Promises, Async/Await, and Callbacks Explained Okoye Ndidiamaka Okoye Ndidiamaka Okoye Ndidiamaka Follow Nov 6 '24 Mastering Asynchronous JavaScript: Promises, Async/Await, and Callbacks Explained # javascript # webdev # callbacks # codetips Comments Add Comment 3 min read Explicitly Avoiding Callback Hell Syriamme Syriamme Syriamme Follow Aug 28 '24 Explicitly Avoiding Callback Hell # javascript # callbacks # backend # backenddevelopment 2 reactions Comments Add Comment 2 min read 7/ NextAuth callback functions explained Peter Jacxsens Peter Jacxsens Peter Jacxsens Follow Apr 1 '24 7/ NextAuth callback functions explained # nextauth # callbacks # nextjs 21 reactions Comments 2 comments 7 min read Javascript Callback functions & Promises Sayed Naweed Rizvi Sayed Naweed Rizvi Sayed Naweed Rizvi Follow Aug 15 '22 Javascript Callback functions & Promises # javascript # callbacks # promises # callbackhell 3 reactions Comments 1 comment 3 min read Always `prepend: true` for `before_destroy` callbacks Augusts Bautra Augusts Bautra Augusts Bautra Follow Jul 22 '22 Always `prepend: true` for `before_destroy` callbacks # todayilearned # rails # callbacks # trick 5 reactions Comments Add Comment 1 min read Ruby on Rails ActiveRecord Callbacks Eapen Zacharias Eapen Zacharias Eapen Zacharias Follow Jul 5 '22 Ruby on Rails ActiveRecord Callbacks # rails # activerecord # ruby # callbacks 18 reactions Comments Add Comment 4 min read Javascript Assíncrono - Fluxo assíncrono e Event Loop Carlos José Vaz Carlos José Vaz Carlos José Vaz Follow May 1 '22 Javascript Assíncrono - Fluxo assíncrono e Event Loop # javascript # callbacks # promises # programming 8 reactions Comments Add Comment 6 min read Javascript Assíncrono - Entenda o que são Callbacks Carlos José Vaz Carlos José Vaz Carlos José Vaz Follow Apr 26 '22 Javascript Assíncrono - Entenda o que são Callbacks # javascript # callbacks # promises # programming 6 reactions Comments 1 comment 3 min read 4 Ways To Handle Async Operations In JavaScript Mohamed Mayallo Mohamed Mayallo Mohamed Mayallo Follow Feb 21 '22 4 Ways To Handle Async Operations In JavaScript # javascript # rxjs # promises # callbacks 8 reactions Comments Add Comment 9 min read JavaScript: Synchronous or Asynchronous? Anandteerth Onkar Anandteerth Onkar Anandteerth Onkar Follow Aug 27 '21 JavaScript: Synchronous or Asynchronous? # javascript # callbacks # promises # asyncawait 2 reactions Comments Add Comment 2 min read Array methods and callback functions for beginners Chris Chris Chris Follow Aug 7 '21 Array methods and callback functions for beginners # javascript # arrays # callbacks # functional 7 reactions Comments Add Comment 3 min read Understanding Callbacks, Promises, Generators and Async/Await Muhammad Muhktar Musa Muhammad Muhktar Musa Muhammad Muhktar Musa Follow Jul 13 '21 Understanding Callbacks, Promises, Generators and Async/Await # callbacks # promises # generators # async 6 reactions Comments Add Comment 7 min read Callbacks and Promises in Asynchronous Programming Nava Nava Nava Follow Jul 7 '21 Callbacks and Promises in Asynchronous Programming # callbacks # promises # asyncawait 2 reactions Comments Add Comment 5 min read Callbacks in JavaScript explained! (video) Ania Kubow Ania Kubow Ania Kubow Follow Jun 16 '21 Callbacks in JavaScript explained! (video) # javascript # callbacks 5 reactions Comments Add Comment 1 min read Callback, Promise and Async/Await by Example in JavaScript dade! dade! dade! Follow May 20 '21 Callback, Promise and Async/Await by Example in JavaScript # javascript # asyncawait # promises # callbacks 3 reactions Comments Add Comment 3 min read Callbacks in Javascript Jay Cruz Jay Cruz Jay Cruz Follow Jun 16 '21 Callbacks in Javascript # webdev # javascript # callbacks 3 reactions Comments Add Comment 3 min read JavaScript Asynchronous Programming and Callbacks Altaf Shaikh Altaf Shaikh Altaf Shaikh Follow Mar 22 '21 JavaScript Asynchronous Programming and Callbacks # javascript # asynchronous # callbacks 4 reactions Comments Add Comment 3 min read loading... trending guides/resources Mastering Asynchronous Operations in Node.js: Practical Strategies and Examples 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://docs.python.org/3/howto/remote_debugging.html | Remote debugging attachment protocol — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents Remote debugging attachment protocol Permission requirements Locating the PyRuntime structure Reading _Py_DebugOffsets Locating the interpreter and thread state Writing control information Summary Previous topic C API Extension Support for Free Threading Next topic Python Frequently Asked Questions This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » Python HOWTOs » Remote debugging attachment protocol | Theme Auto Light Dark | Remote debugging attachment protocol ¶ This protocol enables external tools to attach to a running CPython process and execute Python code remotely. Most platforms require elevated privileges to attach to another Python process. Permission requirements ¶ Attaching to a running Python process for remote debugging requires elevated privileges on most platforms. The specific requirements and troubleshooting steps depend on your operating system: Linux The tracer process must have the CAP_SYS_PTRACE capability or equivalent privileges. You can only trace processes you own and can signal. Tracing may fail if the process is already being traced, or if it is running with set-user-ID or set-group-ID. Security modules like Yama may further restrict tracing. To temporarily relax ptrace restrictions (until reboot), run: echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope Note Disabling ptrace_scope reduces system hardening and should only be done in trusted environments. If running inside a container, use --cap-add=SYS_PTRACE or --privileged , and run as root if needed. Try re-running the command with elevated privileges: sudo -E !! macOS To attach to another process, you typically need to run your debugging tool with elevated privileges. This can be done by using sudo or running as root. Even when attaching to processes you own, macOS may block debugging unless the debugger is run with root privileges due to system security restrictions. Windows To attach to another process, you usually need to run your debugging tool with administrative privileges. Start the command prompt or terminal as Administrator. Some processes may still be inaccessible even with Administrator rights, unless you have the SeDebugPrivilege privilege enabled. To resolve file or folder access issues, adjust the security permissions: Right-click the file or folder and select Properties . Go to the Security tab to view users and groups with access. Click Edit to modify permissions. Select your user account. In Permissions , check Read or Full control as needed. Click Apply , then OK to confirm. Note Ensure you’ve satisfied all Permission requirements before proceeding. This section describes the low-level protocol that enables external tools to inject and execute a Python script within a running CPython process. This mechanism forms the basis of the sys.remote_exec() function, which instructs a remote Python process to execute a .py file. However, this section does not document the usage of that function. Instead, it provides a detailed explanation of the underlying protocol, which takes as input the pid of a target Python process and the path to a Python source file to be executed. This information supports independent reimplementation of the protocol, regardless of programming language. Warning The execution of the injected script depends on the interpreter reaching a safe evaluation point. As a result, execution may be delayed depending on the runtime state of the target process. Once injected, the script is executed by the interpreter within the target process the next time a safe evaluation point is reached. This approach enables remote execution capabilities without modifying the behavior or structure of the running Python application. Subsequent sections provide a step-by-step description of the protocol, including techniques for locating interpreter structures in memory, safely accessing internal fields, and triggering code execution. Platform-specific variations are noted where applicable, and example implementations are included to clarify each operation. Locating the PyRuntime structure ¶ CPython places the PyRuntime structure in a dedicated binary section to help external tools find it at runtime. The name and format of this section vary by platform. For example, .PyRuntime is used on ELF systems, and __DATA,__PyRuntime is used on macOS. Tools can find the offset of this structure by examining the binary on disk. The PyRuntime structure contains CPython’s global interpreter state and provides access to other internal data, including the list of interpreters, thread states, and debugger support fields. To work with a remote Python process, a debugger must first find the memory address of the PyRuntime structure in the target process. This address can’t be hardcoded or calculated from a symbol name, because it depends on where the operating system loaded the binary. The method for finding PyRuntime depends on the platform, but the steps are the same in general: Find the base address where the Python binary or shared library was loaded in the target process. Use the on-disk binary to locate the offset of the .PyRuntime section. Add the section offset to the base address to compute the address in memory. The sections below explain how to do this on each supported platform and include example code. Linux (ELF) To find the PyRuntime structure on Linux: Read the process’s memory map (for example, /proc/<pid>/maps ) to find the address where the Python executable or libpython was loaded. Parse the ELF section headers in the binary to get the offset of the .PyRuntime section. Add that offset to the base address from step 1 to get the memory address of PyRuntime . The following is an example implementation: def find_py_runtime_linux ( pid : int ) -> int : # Step 1: Try to find the Python executable in memory binary_path , base_address = find_mapped_binary ( pid , name_contains = "python" ) # Step 2: Fallback to shared library if executable is not found if binary_path is None : binary_path , base_address = find_mapped_binary ( pid , name_contains = "libpython" ) # Step 3: Parse ELF headers to get .PyRuntime section offset section_offset = parse_elf_section_offset ( binary_path , ".PyRuntime" ) # Step 4: Compute PyRuntime address in memory return base_address + section_offset On Linux systems, there are two main approaches to read memory from another process. The first is through the /proc filesystem, specifically by reading from /proc/[pid]/mem which provides direct access to the process’s memory. This requires appropriate permissions - either being the same user as the target process or having root access. The second approach is using the process_vm_readv() system call which provides a more efficient way to copy memory between processes. While ptrace’s PTRACE_PEEKTEXT operation can also be used to read memory, it is significantly slower as it only reads one word at a time and requires multiple context switches between the tracer and tracee processes. For parsing ELF sections, the process involves reading and interpreting the ELF file format structures from the binary file on disk. The ELF header contains a pointer to the section header table. Each section header contains metadata about a section including its name (stored in a separate string table), offset, and size. To find a specific section like .PyRuntime, you need to walk through these headers and match the section name. The section header then provides the offset where that section exists in the file, which can be used to calculate its runtime address when the binary is loaded into memory. You can read more about the ELF file format in the ELF specification . macOS (Mach-O) To find the PyRuntime structure on macOS: Call task_for_pid() to get the mach_port_t task port for the target process. This handle is needed to read memory using APIs like mach_vm_read_overwrite and mach_vm_region . Scan the memory regions to find the one containing the Python executable or libpython . Load the binary file from disk and parse the Mach-O headers to find the section named PyRuntime in the __DATA segment. On macOS, symbol names are automatically prefixed with an underscore, so the PyRuntime symbol appears as _PyRuntime in the symbol table, but the section name is not affected. The following is an example implementation: def find_py_runtime_macos ( pid : int ) -> int : # Step 1: Get access to the process's memory handle = get_memory_access_handle ( pid ) # Step 2: Try to find the Python executable in memory binary_path , base_address = find_mapped_binary ( handle , name_contains = "python" ) # Step 3: Fallback to libpython if the executable is not found if binary_path is None : binary_path , base_address = find_mapped_binary ( handle , name_contains = "libpython" ) # Step 4: Parse Mach-O headers to get __DATA,__PyRuntime section offset section_offset = parse_macho_section_offset ( binary_path , "__DATA" , "__PyRuntime" ) # Step 5: Compute the PyRuntime address in memory return base_address + section_offset On macOS, accessing another process’s memory requires using Mach-O specific APIs and file formats. The first step is obtaining a task_port handle via task_for_pid() , which provides access to the target process’s memory space. This handle enables memory operations through APIs like mach_vm_read_overwrite() . The process memory can be examined using mach_vm_region() to scan through the virtual memory space, while proc_regionfilename() helps identify which binary files are loaded at each memory region. When the Python binary or library is found, its Mach-O headers need to be parsed to locate the PyRuntime structure. The Mach-O format organizes code and data into segments and sections. The PyRuntime structure lives in a section named __PyRuntime within the __DATA segment. The actual runtime address calculation involves finding the __TEXT segment which serves as the binary’s base address, then locating the __DATA segment containing our target section. The final address is computed by combining the base address with the appropriate section offsets from the Mach-O headers. Note that accessing another process’s memory on macOS typically requires elevated privileges - either root access or special security entitlements granted to the debugging process. Windows (PE) To find the PyRuntime structure on Windows: Use the ToolHelp API to enumerate all modules loaded in the target process. This is done using functions such as CreateToolhelp32Snapshot , Module32First , and Module32Next . Identify the module corresponding to python.exe or python XY .dll , where X and Y are the major and minor version numbers of the Python version, and record its base address. Locate the PyRuntim section. Due to the PE format’s 8-character limit on section names (defined as IMAGE_SIZEOF_SHORT_NAME ), the original name PyRuntime is truncated. This section contains the PyRuntime structure. Retrieve the section’s relative virtual address (RVA) and add it to the base address of the module. The following is an example implementation: def find_py_runtime_windows ( pid : int ) -> int : # Step 1: Try to find the Python executable in memory binary_path , base_address = find_loaded_module ( pid , name_contains = "python" ) # Step 2: Fallback to shared pythonXY.dll if the executable is not # found if binary_path is None : binary_path , base_address = find_loaded_module ( pid , name_contains = "python3" ) # Step 3: Parse PE section headers to get the RVA of the PyRuntime # section. The section name appears as "PyRuntim" due to the # 8-character limit defined by the PE format (IMAGE_SIZEOF_SHORT_NAME). section_rva = parse_pe_section_offset ( binary_path , "PyRuntim" ) # Step 4: Compute PyRuntime address in memory return base_address + section_rva On Windows, accessing another process’s memory requires using the Windows API functions like CreateToolhelp32Snapshot() and Module32First()/Module32Next() to enumerate loaded modules. The OpenProcess() function provides a handle to access the target process’s memory space, enabling memory operations through ReadProcessMemory() . The process memory can be examined by enumerating loaded modules to find the Python binary or DLL. When found, its PE headers need to be parsed to locate the PyRuntime structure. The PE format organizes code and data into sections. The PyRuntime structure lives in a section named “PyRuntim” (truncated from “PyRuntime” due to PE’s 8-character name limit). The actual runtime address calculation involves finding the module’s base address from the module entry, then locating our target section in the PE headers. The final address is computed by combining the base address with the section’s virtual address from the PE section headers. Note that accessing another process’s memory on Windows typically requires appropriate privileges - either administrative access or the SeDebugPrivilege privilege granted to the debugging process. Reading _Py_DebugOffsets ¶ Once the address of the PyRuntime structure has been determined, the next step is to read the _Py_DebugOffsets structure located at the beginning of the PyRuntime block. This structure provides version-specific field offsets that are needed to safely read interpreter and thread state memory. These offsets vary between CPython versions and must be checked before use to ensure they are compatible. To read and check the debug offsets, follow these steps: Read memory from the target process starting at the PyRuntime address, covering the same number of bytes as the _Py_DebugOffsets structure. This structure is located at the very start of the PyRuntime memory block. Its layout is defined in CPython’s internal headers and stays the same within a given minor version, but may change in major versions. Check that the structure contains valid data: The cookie field must match the expected debug marker. The version field must match the version of the Python interpreter used by the debugger. If either the debugger or the target process is using a pre-release version (for example, an alpha, beta, or release candidate), the versions must match exactly. The free_threaded field must have the same value in both the debugger and the target process. If the structure is valid, the offsets it contains can be used to locate fields in memory. If any check fails, the debugger should stop the operation to avoid reading memory in the wrong format. The following is an example implementation that reads and checks _Py_DebugOffsets : def read_debug_offsets ( pid : int , py_runtime_addr : int ) -> DebugOffsets : # Step 1: Read memory from the target process at the PyRuntime address data = read_process_memory ( pid , address = py_runtime_addr , size = DEBUG_OFFSETS_SIZE ) # Step 2: Deserialize the raw bytes into a _Py_DebugOffsets structure debug_offsets = parse_debug_offsets ( data ) # Step 3: Validate the contents of the structure if debug_offsets . cookie != EXPECTED_COOKIE : raise RuntimeError ( "Invalid or missing debug cookie" ) if debug_offsets . version != LOCAL_PYTHON_VERSION : raise RuntimeError ( "Mismatch between caller and target Python versions" ) if debug_offsets . free_threaded != LOCAL_FREE_THREADED : raise RuntimeError ( "Mismatch in free-threaded configuration" ) return debug_offsets Warning Process suspension recommended To avoid race conditions and ensure memory consistency, it is strongly recommended that the target process be suspended before performing any operations that read or write internal interpreter state. The Python runtime may concurrently mutate interpreter data structures—such as creating or destroying threads—during normal execution. This can result in invalid memory reads or writes. A debugger may suspend execution by attaching to the process with ptrace or by sending a SIGSTOP signal. Execution should only be resumed after debugger-side memory operations are complete. Note Some tools, such as profilers or sampling-based debuggers, may operate on a running process without suspension. In such cases, tools must be explicitly designed to handle partially updated or inconsistent memory. For most debugger implementations, suspending the process remains the safest and most robust approach. Locating the interpreter and thread state ¶ Before code can be injected and executed in a remote Python process, the debugger must choose a thread in which to schedule execution. This is necessary because the control fields used to perform remote code injection are located in the _PyRemoteDebuggerSupport structure, which is embedded in a PyThreadState object. These fields are modified by the debugger to request execution of injected scripts. The PyThreadState structure represents a thread running inside a Python interpreter. It maintains the thread’s evaluation context and contains the fields required for debugger coordination. Locating a valid PyThreadState is therefore a key prerequisite for triggering execution remotely. A thread is typically selected based on its role or ID. In most cases, the main thread is used, but some tools may target a specific thread by its native thread ID. Once the target thread is chosen, the debugger must locate both the interpreter and the associated thread state structures in memory. The relevant internal structures are defined as follows: PyInterpreterState represents an isolated Python interpreter instance. Each interpreter maintains its own set of imported modules, built-in state, and thread state list. Although most Python applications use a single interpreter, CPython supports multiple interpreters in the same process. PyThreadState represents a thread running within an interpreter. It contains execution state and the control fields used by the debugger. To locate a thread: Use the offset runtime_state.interpreters_head to obtain the address of the first interpreter in the PyRuntime structure. This is the entry point to the linked list of active interpreters. Use the offset interpreter_state.threads_main to access the main thread state associated with the selected interpreter. This is typically the most reliable thread to target. Optionally, use the offset interpreter_state.threads_head to iterate through the linked list of all thread states. Each PyThreadState structure contains a native_thread_id field, which may be compared to a target thread ID to find a specific thread. Once a valid PyThreadState has been found, its address can be used in later steps of the protocol, such as writing debugger control fields and scheduling execution. The following is an example implementation that locates the main thread state: def find_main_thread_state ( pid : int , py_runtime_addr : int , debug_offsets : DebugOffsets , ) -> int : # Step 1: Read interpreters_head from PyRuntime interp_head_ptr = ( py_runtime_addr + debug_offsets . runtime_state . interpreters_head ) interp_addr = read_pointer ( pid , interp_head_ptr ) if interp_addr == 0 : raise RuntimeError ( "No interpreter found in the target process" ) # Step 2: Read the threads_main pointer from the interpreter threads_main_ptr = ( interp_addr + debug_offsets . interpreter_state . threads_main ) thread_state_addr = read_pointer ( pid , threads_main_ptr ) if thread_state_addr == 0 : raise RuntimeError ( "Main thread state is not available" ) return thread_state_addr The following example demonstrates how to locate a thread by its native thread ID: def find_thread_by_id ( pid : int , interp_addr : int , debug_offsets : DebugOffsets , target_tid : int , ) -> int : # Start at threads_head and walk the linked list thread_ptr = read_pointer ( pid , interp_addr + debug_offsets . interpreter_state . threads_head ) while thread_ptr : native_tid_ptr = ( thread_ptr + debug_offsets . thread_state . native_thread_id ) native_tid = read_int ( pid , native_tid_ptr ) if native_tid == target_tid : return thread_ptr thread_ptr = read_pointer ( pid , thread_ptr + debug_offsets . thread_state . next ) raise RuntimeError ( "Thread with the given ID was not found" ) Once a valid thread state has been located, the debugger can proceed with modifying its control fields and scheduling execution, as described in the next section. Writing control information ¶ Once a valid PyThreadState structure has been identified, the debugger may modify control fields within it to schedule the execution of a specified Python script. These control fields are checked periodically by the interpreter, and when set correctly, they trigger the execution of remote code at a safe point in the evaluation loop. Each PyThreadState contains a _PyRemoteDebuggerSupport structure used for communication between the debugger and the interpreter. The locations of its fields are defined by the _Py_DebugOffsets structure and include the following: debugger_script_path : A fixed-size buffer that holds the full path to a Python source file ( .py ). This file must be accessible and readable by the target process when execution is triggered. debugger_pending_call : An integer flag. Setting this to 1 tells the interpreter that a script is ready to be executed. eval_breaker : A field checked by the interpreter during execution. Setting bit 5 ( _PY_EVAL_PLEASE_STOP_BIT , value 1U << 5 ) in this field causes the interpreter to pause and check for debugger activity. To complete the injection, the debugger must perform the following steps: Write the full script path into the debugger_script_path buffer. Set debugger_pending_call to 1 . Read the current value of eval_breaker , set bit 5 ( _PY_EVAL_PLEASE_STOP_BIT ), and write the updated value back. This signals the interpreter to check for debugger activity. The following is an example implementation: def inject_script ( pid : int , thread_state_addr : int , debug_offsets : DebugOffsets , script_path : str ) -> None : # Compute the base offset of _PyRemoteDebuggerSupport support_base = ( thread_state_addr + debug_offsets . debugger_support . remote_debugger_support ) # Step 1: Write the script path into debugger_script_path script_path_ptr = ( support_base + debug_offsets . debugger_support . debugger_script_path ) write_string ( pid , script_path_ptr , script_path ) # Step 2: Set debugger_pending_call to 1 pending_ptr = ( support_base + debug_offsets . debugger_support . debugger_pending_call ) write_int ( pid , pending_ptr , 1 ) # Step 3: Set _PY_EVAL_PLEASE_STOP_BIT (bit 5, value 1 << 5) in # eval_breaker eval_breaker_ptr = ( thread_state_addr + debug_offsets . debugger_support . eval_breaker ) breaker = read_int ( pid , eval_breaker_ptr ) breaker |= ( 1 << 5 ) write_int ( pid , eval_breaker_ptr , breaker ) Once these fields are set, the debugger may resume the process (if it was suspended). The interpreter will process the request at the next safe evaluation point, load the script from disk, and execute it. It is the responsibility of the debugger to ensure that the script file remains present and accessible to the target process during execution. Note Script execution is asynchronous. The script file cannot be deleted immediately after injection. The debugger should wait until the injected script has produced an observable effect before removing the file. This effect depends on what the script is designed to do. For example, a debugger might wait until the remote process connects back to a socket before removing the script. Once such an effect is observed, it is safe to assume the file is no longer needed. Summary ¶ To inject and execute a Python script in a remote process: Locate the PyRuntime structure in the target process’s memory. Read and validate the _Py_DebugOffsets structure at the beginning of PyRuntime . Use the offsets to locate a valid PyThreadState . Write the path to a Python script into debugger_script_path . Set the debugger_pending_call flag to 1 . Set _PY_EVAL_PLEASE_STOP_BIT in the eval_breaker field. Resume the process (if suspended). The script will execute at the next safe evaluation point. Table of Contents Remote debugging attachment protocol Permission requirements Locating the PyRuntime structure Reading _Py_DebugOffsets Locating the interpreter and thread state Writing control information Summary Previous topic C API Extension Support for Free Threading Next topic Python Frequently Asked Questions This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » Python HOWTOs » Remote debugging attachment protocol | Theme Auto Light Dark | © Copyright 2001 Python Software Foundation. This page is licensed under the Python Software Foundation License Version 2. Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License. See History and License for more information. The Python Software Foundation is a non-profit corporation. Please donate. Last updated on Jan 13, 2026 (06:19 UTC). Found a bug ? Created using Sphinx 8.2.3. | 2026-01-13T08:49:02 |
https://pressable.com/?utm_source=Automattic&utm_medium=rpc&%23038;utm_campaign=Concierge%20Referral&%23038;utm_term=concierge | Truly Incredible WordPress Hosting by Pressable Skip to main content Pricing Solutions Managed WordPress Hosting Discover whether Pressable is right for you. Agency WordPress Hosting Time is money and we’ll help you save it. WooCommerce Stores Sell more with a stable and secure store. Business Owners We’ll help you every step of the way. Web Developers Easy to use with the smart tech you need. High Traffic Websites Go viral. We have your back. All Solutions View all our solutions Features Build Better from the start Manage When every site matters Automate Work smarter, not harder All Features View all our features Changelog Resources Blog Helpful and relevant articles on all things WP. Knowledge Base Everything you wanted to know and more! Log In Schedule a demo Pricing Solutions Features Changelog Resources Log In Toggle color theme Light Mode Dark Mode Schedule a demo Managed WordPress Hosting Discover whether Pressable is right for you. Agency WordPress Hosting Time is money and we’ll help you save it. WooCommerce Stores Sell more with a stable and secure store. Business Owners We’ll help you every step of the way. Web Developers Easy to use with the smart tech you need. High Traffic Websites Go viral. We have your back. All Solutions View all our solutions Build Better from the start Manage When every site matters Automate Work smarter, not harder All Features View all our features Blog Helpful and relevant articles on all things WP. Knowledge Base Everything you wanted to know and more! WordPress Hosting You Can Count On. Get Speed, Scale, and Peace of Mind. Managed WordPress hosting at its best: Scale when you need it. Stability when it matters. Support you’ll never outgrow. See Pricing Get Demo Trustpilot “Pressable helps with moving our business forward.” “Selling products on WooCommerce? Pressable is perfect for your needs!” “We don’t have to worry if our clients’ sites can handle extreme traffic events.” Why are businesses switching to Pressable? Transparent Pricing Stop paying for overpriced hosting with rigid contracts. Pressable gives you the freedom to scale without long-term commitments, surprise overage fees, or hidden costs – just straightforward, high-performance hosting. Hosting You Can Trust Your site’s performance should be an advantage, not a liability. Pressable’s NVMe-powered servers, built-in caching, and global CDN ensure lightning-fast speeds and 100% uptime via high availability. Support Our Customers Love No more long wait times or canned responses. Our 24/7 support team is made up of real WordPress experts who solve problems fast so you can focus on your business, not troubleshooting your site. How can Pressable help my business? Get More Sales & Less Headaches Stress-Free Ecommerce Sites Slow load times and downtime cost you sales. Pressable’s managed WooCommerce hosting delivers unmatched speed, security, and reliability. Lightning-fast load times keep customers shopping. Enterprise-grade security & daily backups protects your revenue. Start Selling Streamline Client Sites & Scale With Confidence Fast & Reliable Hosting for Agencies Managing multiple client sites shouldn’t slow you down. Pressable’s managed WordPress hosting delivers seamless performance, security, and expert support. One dashboard to manage all client sites with ease. 24/7 expert support ensures every site runs smoothly. Start Hosting Build Faster & Deploy Smarter High-Performance Developer Hosting Slow, unreliable hosting gets in the way of great work. Pressable gives you the speed, flexibility, and robust API documentation to build and launch without limits. Developer-friendly features like SSH, Git, and WP-CLI built-in. 100% uptime via high availability for speedy deployments. Start Building Stay Fast, Even Under Heavy Traffic Scalable Hosting for High-Traffic Sites Traffic spikes shouldn’t slow you down. Pressable’s managed WordPress hosting delivers the speed, scalability, and reliability your site needs to handle any traffic demands. A global CDN keeps load times lightning-fast. 100% uptime, automatic scaling, and 24/7 expert support ensure your site stays online no matter what. Get High-Traffic Hosting Why should I switch to Pressable? With Pressable Other Hosts Unlimited WordPress Site Migrations With Pressable Other Hosts: Top-Tier Performance with Auto-Scaling Resources With Pressable: Other Hosts: Malware Monitoring & Assistance With Pressable: Other Hosts: Premium Jetpack Security With Pressable: Other Hosts: 100% Uptime Guarantee With Pressable: Other Hosts: 24/7 Expert Support with ~4 Min Average First Response With Pressable: Other Hosts: Highly Available Geo-Redundant Failover With Pressable: Other Hosts: Global Content Delivery With Edge Cache With Pressable: Other Hosts: Still have questions about switching from your old host ? Curious about how much you’ll save when you switch to Pressable? Want to learn more about our free white glove migration service ? We’re here to help. Contact Sales I moved from WP Engine to Pressable because they had feature parity, better pricing, and higher traffic allowances. The most significant difference is that my WP Admin and site are noticeably faster. My only wish is that I had moved to Pressable sooner. Jon Henshaw Founder, Coywolf How much does Pressable cost? Single Site Plan $25 /mo $tk /yr Perfect for ecommerce & web developers tk 1 WordPress site 30,000 visits 20GB storage Start Your Site tk Agency Plan $90 /mo $tk /yr Designed for agencies with multiple sites tk Up to 10 WordPress sites 150,000 visits 50GB storage Start Your Plan tk Premium Site Plan $350 /mo $tk /yr Supports millions of pageviews tk Geo-redundant HA Cloud Starting at 10 Base vCPUs Per Site 512MB X Each PHP Worker/Process Contact Sales tk Every plan includes: 24/7 expert support Automated WordPress updates Automatic datacenter failover Daily, hourly, and on-demand backups Edge and persistent object caching Global CDN with 28+ locations Industry-leading PHP resources Jetpack Security with WAF and instant patches One-click restores Staging, WP-CLI, SSH, and Git tools Ultra-fast DNS with automatic SSL Unlimited free site migrations Other Pricing Options How is Pressable’s performance? Static performance test response time 5.2 milliseconds – WPHostingBenchmarks.com – August 2023 P95 performance test response time 12 milliseconds – WPHostingBenchmarks.com – August 2023 Four-week average customer satisfaction score 98.5% rating – April 2025 Current G2 rating 4.8/5 stars – g2.com – July 2024 Current Trustpilot rating 4.8/5 stars – trustpilot.com – April 2025 Four-week average first support response time 2 mins, 9 sec – April 2025 What are all of Pressable’s features? Build Manage Collaborate Automate Feature Free SSL Certificates Feature 30-Day Money-Back Guarantee On All Pressable Hosting Plans Feature Seamless White Glove WordPress Migrations Feature Smart WordPress Staging Environments Feature WordPress Cloud Hosting Platform | WP Cloud Feature Secure WordPress Hosting with Jetpack Security Feature 100% Uptime Guarantee Feature WordPress Malware Cleaning and Hack Recovery Assistance Feature WordPress Web Application Firewall (WAF) Solutions Feature WordPress Malware Scanning & Threat Monitoring Feature Easy-to-Use WordPress Hosting Dashboard & Control Panel Feature Around the Clock WordPress Hosting Support with Pressable Feature WordPress Performance Monitoring and Optimization Feature Professional-Grade WordPress Email Hosting Powered by Titan Feature Auto-Scaling WordPress That Exceeds Expectations Feature Automatic Managed WordPress Updates Feature Automated Backups Feature Free Automatic Failover Feature Free Global Content Delivery Network Feature WordPress Plugin Update Scheduler and Performance Reports The Power Of WP Cloud At Pressable, we’re proud to be one of the original managed WordPress hosting providers built on Automattic’s WP Cloud. This isn’t just any cloud hosting solution, it’s a platform designed from the ground up to maximize the potential of WordPress websites. Plus, our web application firewall , free global CDN , automatic failover , and WordPress daily backups come with all plans! What do customers think about Pressable? The rating of this product is 5 out of 5 Support is everything! Pressable is amazing! I’m in the process of moving over 200 sites to Pressable from another hosting company that I used to love because they used to care about […] Ben J. The rating of this product is 5 out of 5 Pressable has exceeded all my expectations when it comes to WordPress hosting. The performance is top-notch, with blazing-fast load times and rock-solid stability. Plus, their support team is on another level – […] Jarciano Silva The rating of this product is 5 out of 5 Great value for the quality of hosting received and AMAZING support. I have tried other hosts such as WP Engine and Kinsta. The interactions I have had with Pressable have been amazing. Paul Van York Trustpilot I love the speed that my website comes up. Sites haven’t gone down since moving to Pressable. Best hosting support , bar none. Above and beyond any other host. Worth every penny . Easy way to switch hosting. Great value for the quality we get . Much faster speeds than other big box hosting. AMAZING support. Sites run smoother, faster and the difference is amazing . Press ABLE , that’s the name. The features I needed were all there. I wish I’d found Pressable earlier . See More Reviews What else do I need to know about Pressable? Categories – press button to select a category. Select Categories General General Which Pressable plan is right for me? We offer various value-rich WordPress hosting plans and customization options. Choose your plan based on the number of sites you need to host, the storage you need for your website, and how many visitors you estimate your site will have each month. To speak with a Pressable team member about customizing a plan or getting a demonstration of our platform, start a live chat with our sales team. Can you move my sites to your servers? Absolutely! We offer free migrations of your WordPress website to our hosting platform. Just sign up for a plan and get in touch with support to start. Learn more about free migrations. Will my site perform better on Pressable? Our platform delivers the best possible speed and reliability. Most subscribers see a significant improvement in performance after migrating to Pressable. Plus, you can contact our support team for advice on how to get the most out of your WordPress site. Read about hosting speed and reliability. Can I run WooCommerce on any of your WordPress plans? Of course! We built all our managed WordPress plans to handle new or established WooCommerce stores with a lot of traffic. Managed WordPress Hosting for WooCommerce Does Pressable offer phone support? Pressable doesn’t offer phone support, and that’s a good thing. Phone support can hinder customer service when it comes to technical issues. Learn why online support is ultimately better . At Pressable, our average response time is within two minutes, and our average resolution time is less than 10 minutes. Even better, our customer satisfaction rating is 98% or better. Our customers agree that our live chat is where it’s at. We’d love to show you how much better the experience is when you get your support online. Does Pressable offer email hosting? Yes, Pressable has partnered with Titan Email to provide you with a feature-rich email platform that makes connecting with customers, partners, and colleagues easier than ever. And right now, if you sign up for a Pressable Hosting account, you get a free 90-day trial! Do you support WordPress multisite? We do! At this time, we only support subdirectory multisite setups. Don’t know how your multisite is set up? Learn how to find out if your multisite will work on Pressable . How is Pressable different from the competition? Our data network was created (and is maintained) by the same minds behind WordPress.com, WooCommerce, and WordPress VIP. That means actual WordPress experts are keeping your website up, running, and secure. Still have questions? Speak with our WordPress experts who deliver industry-leading managed WordPress hosting with top-tier performance, a 100% uptime SLA, and 24/7 expert support. Chat With Sales Contact Pressable Chat with Sales 1 (888) 602-6756 sales@pressable.com Report a Concern Back to top ↑ Get Started Pricing & Plans Hire a WordPress Agency Automattic for Agencies Affiliate Program Solutions Managed WordPress Hosting Agency WordPress Hosting Ecommerce Hosting Web Hosting WooCommerce Hosting Resources Web Tools API Documentation Case Studies eBooks Webinars Company About Us Contact Careers Press Kit Legal Sitemap Do not sell or share my personal information An hosting lab Powered by WordPress © 2026 Pressable, Inc. All rights reserved. SLA Support Policy Cookies | 2026-01-13T08:49:02 |
https://dev.to/evanlin/line-taiwan-devrel-2020-review-and-2021-community-plans-part-3-technical-branding-and-hiring-2d1 | LINE Taiwan DevRel: 2020 Review and 2021 Community Plans (Part 3: Technical Branding and Hiring) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Evan Lin Posted on Jan 11 • Originally published at evanlin.com on Jan 11 LINE Taiwan DevRel: 2020 Review and 2021 Community Plans (Part 3: Technical Branding and Hiring) # devjournal # community # marketing # career title: [LINE DevRel] LINE Taiwan Developer Relations 2020 Review and 2020 Developer Community Plan Report (part 3: Technical Branding and Hiring) published: false date: 2021-02-03 00:00:00 UTC tags: canonical_url: http://www.evanlin.com/devrel-2020-3/ Enter fullscreen mode Exit fullscreen mode Preface Hello everyone, I am Evan Lin from the LINE Taiwan Developer Relations team. After more than a year of effort by LINE Developer Relations, I would like to summarize in this article what the entire team has done, and I also hope to make an annual report for the " LINE Developer Community Plan ". According to the original introduction article (Introducing Developer Relations team) written by LINE Developer Relations, the main goals of this team are clearly defined as follows: External Evangelism: Encouraging developers to use LINE's platform, APIs and SDKs to develop attractive and interesting application services. (Encouraging people to make attractive and interesting services using the APIs and the SDK by LINE) Internal Evangelism: Through some methods to enable engineers to grow and hone themselves (Doing whatever our engineers feel difficult to do themselves in making improvements at work) Technical Branding and Hiring: Letting more people know that being a LINER (LINE employees' self-proclaimed name) has many interesting and exciting things. (Letting people know how fun and exciting it is for engineers to work at LINE) The previous article has clearly defined External Evangelism , and the next step will be to further explain Technical Branding and Hiring . Article List: [LINE DevRel] LINE Taiwan Developer Relations 2020 Review and 2020 Developer Community Plan Report (part 1: External Evangelism) [LINE DevRel] LINE Taiwan Developer Relations 2020 Review and 2020 Developer Community Plan Report (part 2: Internal Evangelism) [LINE DevRel] LINE Taiwan Developer Relations 2020 Review and 2020 Developer Community Plan Report (part 3: **Technical Branding and Hiring) (This article) Technical Branding and Hiring: Letting more people know that being a LINER (LINE employees' self-proclaimed name) has many interesting and exciting things. As a technology-based technology company, LINE requires developers for many underlying architectures and services. However, the brand awareness of LINE's technology is an area that needs continuous effort, so another important task of Developer Relations is to let more developers understand that LINE Taiwan has a considerable number of developers, and there are many interesting job openings here that need the participation of experts from all sides. Summer Tech Fair We hope to create more opportunities for technical sharing and cross-border exchanges, and at the same time, continue to recruit outstanding talents to join the LINE Taiwan development engineering team! This is the first joint recruitment Taiwan technology job fair this year, hoping to let more student friends understand the student internship program brought by LINE. "LINE Tech Star Talent Program – LINE TECHFRERSH". Reference Articles: LINE Developer Community Plan: Summer Tech Fair Taiwan Technology Job Fair Community Event Co-hosting Invitation (Community Meetup) This year, LINE Taiwan not only holds community events by itself, but also welcomes various technical communities to hold community gatherings at the LINE Taiwan office. In addition to hoping to have more exchanges with the community, it will also provide LINE internal developers to share relevant development experiences with everyone. As a developer, do you know that LINE also actively participates in welcoming various communities to apply and exchange? Due to the epidemic, the events in the first half of the year were postponed. In the second half of the year, 5 open source technology community gatherings were held at the LINE office, and we cooperated with many communities, and allowed many communities to understand that LINE also has related development technology engineers, and each colleague has an open attitude and is willing to share. Related Articles: You are also welcome to refer to the following articles to learn more about the exciting community event content: LINE Developer Community Plan: 2020/10/21 TWJUG@LINE LINE Developer Community Plan: Golang #54 Community Gathering Experience LINE Developer Community Plan: Vue.js Taiwan 006 Gathering Highlights Sharing LINE Developer Community Plan: 20200707 Test Corner #26 Gathering Experience 2020 June LINE Platform Update Summary and LINE Group/Room Chatbot Demonstration LINE Taiwan Security Meetup – BECKS #6 LINE Taiwan Security Meetup – BECKS #5 LINE Annual Developer Recruitment Conference LINE Developer Recruitment Day LINE Taiwan Developers Recruitment Day is a public recruitment event for developers. We invite outstanding candidates who have passed the online preliminary test to participate in the interview. In addition, we have also planned a full day of product and service introductions, and welcome the developers invited to the interview to come and learn together. Through this event, more developers can also understand that LINE Taiwan has a considerable number of development positions waiting for experts from all sides to join. Related Articles 2020 LINE Taiwan Developers Recruitment Day LINE UIT Introduction LINE SHOPPING Introduction LINE QA Introduction LINE TODAY Introduction LINE Pay Introduction Technical Seminars (COSCUP, DataCon, JCConf, JSDC) Regarding the technical seminars, the LINE Developer Relations department also participated in JCConf this year, and set up a booth for LINE Taiwan engineers to communicate and discuss with everyone. We also found that in each exchange, each interaction, in addition to feeling the enthusiasm of LINER sharing, we can also feel the love and curiosity of every developer for LINE services. Everyone wants to explore the technical architecture content of the services they use every day, and the enthusiasm of the engineers' exchanges was also felt in the four seminars. Related Articles: LINE Taiwan x Java Annual Event: JCConf 2020 A trip to JCConf 2020 JCConf 2020 Conference Experience Sharing – RSocket Revolution, a High-Efficiency Communication Protocol Born for Reactive Programming Information Security Community in South Korea, Japan and Taiwan - BECKS Information security has always been one of the most important aspects of LINE. In addition to actively promoting various information security enhancement strategies, starting this year (2019), it has regularly held BECKS.IO – Security Meetup jointly in South Korea, Japan, and Taiwan, inviting information security researchers from various countries to participate, allowing information security researchers from all over the world to have more exchanges through this gathering. In 2019, a total of five BECKS gatherings were held, and we also hope that more participants can join us. Related Articles: BECKS Community Event Registration Website LINE Taiwan Security Meetup – BECKS #6 LINE Taiwan Security Meetup – BECKS #5 LINE Taiwan Annual Developer Event - LINE TECHPULSE 2020 LINE TAIWAN TECHPULSE 2020 was held on 2020/12/18 at Nangang Exhibition Center Hall 2. I don't know if you all participated in this carefully arranged event this year. As one of the organizers, we always hope that every idea and thought can be shared with every guest. We hope that through this article, regardless of whether you are present or not, you can feel the team's dedication. In addition to the new venue this year, the working team has also carefully prepared the following items to welcome everyone to learn more: LINE CLOVA venue experience The first dual-track agenda, a perfect combination of technology and business applications Interactive booth: giving you the opportunity to know the gods Display rack (Poster): Face-to-face discussion of architecture with LINE Taiwan service engineers Related Articles: LINE TAIWAN TECHPULSE 2020 Agenda Content Sharing Behind the Scenes of LINE TAIWAN TECHPULSE 2020 Event Arrangements TECHPULSE 2020 Youth Main Stage – TECH FRESH Agenda and Booth Introduction LINE TAIWAN TECHPULSE 2020 Annual Event You Can't Miss Conclusion This is the last article summarizing the results of LINE Developer Relations in 2020. Thank you for watching. Developer Relations is never an easy road. Developers, due to their own desire for technical exchanges, are still willing to use their free time after work to participate in technical communities to get to know more like-minded people and hone their skills. Therefore, the staff of Developer Relations and Technical Promotion Department (Developer Relations) need more enthusiasm to plan in-depth and meaningful activities to make every hard-working developer have a fulfilling harvest and let everyone exchange happily. 2020 has passed, how many LINE Developer Relations events have you participated in? Let's meet again in 2020. Join the "LINE Developer Official Community" official account immediately, and you can receive push notifications of the latest Meetup events or the latest news related to the developer plan. ▼ "LINE Developer Official Community" Official Account ID: @line_tw_dev About "LINE Developer Community Plan" Join the "LINE Developer Official Community" official account immediately, and you can receive push notifications of the latest Meetup events or the latest news related to the developer plan. ▼ "LINE Developer Official Community" Official Account ID: @line_tw_dev About "LINE Developer Community Plan" LINE launched the "LINE Developer Community Plan" in Taiwan at the beginning of this year, and will invest manpower and resources in Taiwan for a long time to hold developer community gatherings, recruitment days, developer conferences, etc., both internally and externally, online and offline, and is expected to hold more than 30 events throughout the year. Readers are welcome to continue to check back for the latest updates. For details, please see: LINE Taiwan Developer Relations 2019 Review and 2019 Developer Community Plan Report 2019 LINE Developer Community Plan Event Schedule 2020 LINE Developer Community Plan Event Schedule 2021 LINE Developer Community Plan Event Schedule (continuously updated) Enter fullscreen mode Exit fullscreen mode Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Some comments may only be visible to logged-in visitors. Sign in to view all comments. Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Evan Lin Follow Attitude is Everything. @golangtw Co-Organizer / LINE Taiwan Technology Evangelist. Golang GDE. Location Taipei Work Technology Evangelist at LINE Corp. Joined Jun 16, 2020 More from Evan Lin Steve Jobs: The Biography (Updated Edition) # career # leadership # motivation # product 2020: Review and Outlook # career # devjournal # productivity [TIL] Golang community discussion about PTT BBS # community # backend # discuss # go 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/rsionnach/shift-left-reliability-4poo#why-now | Shift-Left Reliability - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Rob Fox Posted on Jan 12 Shift-Left Reliability # sre # devops # cicd # platformengineering We've become exceptionally good at incident response. Modern teams restore service quickly, run thoughtful postmortems, and hold themselves accountable through corrective actions. And yet… A team ships a change that passes every test, gets all the required approvals, and still brings down checkout for 47 minutes. The postmortem conclusion? "We should have known our latency SLO was already at 94% before deploying." Many postmortems point to the same root cause: changes we introduced ourselves. Not hardware failures. Not random outages. Just software behaving exactly as we told it to. We continue to treat reliability as something to evaluate once those changes are already live. This isn't a failure of tooling or process. It's a question of when we decide whether a system is ready. The paradox We've invested heavily in observing and responding to failure - better alerting, faster incident response, thorough postmortems. Teams care deeply about reliability and spend significant time optimizing how they respond to incidents. But when in a service's lifecycle are they supposed to define reliability? Where's the innovation that happens before deployment? Where reliability decisions actually happen today I've seen multiple teams running identical technology stacks with completely different SLOs, metrics, and alerts. Nobody told them what to implement, what's best-practice or how to tune their alerts. They want to be good reliability citizens, but getting from the theory in the handbook to putting that theory into practice is not straightforward. Services regularly move into production with SLOs being created months later - or never. Dashboards are missing, insufficient, or inconsistent. "Looks fine to me" during PR reviews. Tribal knowledge. Varying levels of understanding across teams. Reliability is fundamentally bespoke and ungoverned. That's the core issue. The missing layer GitHub gave us version control for code. Terraform gave us version control for infrastructure. Security has transformed with shift-left - finding flaws as code is written, not after deployment. We're still missing version control for reliability. We need a specification that defines requirements, validates them against reality, and generates the artifacts: dashboards, SLOs, alerts, escalation policies. If the specification is validated and the artifacts created, the same tool can check in real-time whether a service is in breach - and block high-risk deployments in CI/CD. What shift-left reliability actually means Shift-left reliability doesn't mean more alerts and dashboards, more postmortems or more people in the room. It means: Spec - Define reliability requirements as code before production deployment Validate - Test those requirements against reality Enforce - Gate deployments through CI/CD Engineers don't write PromQL or Grafana JSON - they declare intent, and reliability becomes deterministic. Outcomes are predictable, consistent, transparent, and follow best practice. An executable reliability contract Keep it simple. A team creates a service.yaml file with their reliability intent: name: payment-api tier: critical type: api team: payments dependencies: - postgresql - redis Enter fullscreen mode Exit fullscreen mode Here is a complete service.yaml example . Tooling validates metrics, SLOs, and error budgets then generates these artifacts automatically. This is the approach I am exploring with an open-source project called NthLayer. NthLayer runs in any CI/CD pipeline - GitHub Actions, ArgoCD, Jenkins, Tekton, GitLab CI. The goal isn't to be an inflexible blocker; it's visible risk and explicit decisions. Overrides are fine when they're intentional, logged, and owned. When a deployment is attempted, the specification is evaluated against reality: $ nthlayer check-deploy - service payment-api ERROR: Deployment blocked - availability SLO at 99.2% (target: 99.95%) - error budget exhausted: -47 minutes remaining - 3 P1 incidents in last 7 days Exit code: 2 (BLOCKED) Enter fullscreen mode Exit fullscreen mode Why now? SLOs have had 8+ years to mature and move from the Google SRE Handbook into mainstream practice. GitOps has normalized declarative configuration. Platform Engineering has matured as a discipline. The concepts are ready but the tooling has lagged behind. This is a deliberate shift in approach. Reliability is no longer up for debate during incidents. Services have defined owners with deterministic standards. We can stop reinventing the reliability wheel every time a new service is onboarded. If requirements change, update the service.yaml , run NthLayer and every service benefits from adopting the new standard. What this does not replace NthLayer doesn't replace service catalogs, developer portals, observability platforms, or incident management. It doesn't predict failures or eliminate human judgment. It's upstream of all these systems. The goal: a reliability specification, automated deployment gates and to reduce cognitive load to implement best practices. Open questions I don't have all the answers but two questions I keep returning to are: Contract Drift: What happens when the spec says 99.95% but reality has been 99.5% for months? Is the contract wrong, or is the service broken? Emergency Overrides: How should they work? Who approves? How do you prevent them from becoming the default? The timing problem Where do reliability decisions actually happen in your organization? What would it look like to decide readiness before deployment? What reliability rules do you wish you could enforce automatically? The timing problem isn't going away. The only question is whether you address it before deployment - or learn about it in the postmortem. NthLayer is open source and looking for early adopters. If you're tired of reliability being an afterthought: pip install nthlayer nthlayer init nthlayer check-deploy --service your-service Enter fullscreen mode Exit fullscreen mode → github.com/rsionnach/nthlayer Star the repo, open an issue, or tell me I'm wrong. I want to hear how reliability decisions happen in your organization. Rob Fox is a Senior Site Reliability Engineer focused on platform and reliability tooling. He's exploring how reliability engineering can move earlier in the software delivery lifecycle. Find him on GitHub . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Rob Fox Follow Sr Site Reliability Engineer. Building NthLayer, an open-source tool for shift-left reliability. Opinions are my own. github.com/rsionnach Location Dublin, Ireland Joined Jan 6, 2026 Trending on DEV Community Hot The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning How I Built an AI Terraform Review Agent on Serverless AWS # aws # terraform # serverless # devops How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/bogaboga1/odoo-core-and-the-cost-of-reinventing-everything-15n1#the-odoo-is-old-argument | Odoo Core and the Cost of Reinventing Everything - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Boga Posted on Jan 12 Odoo Core and the Cost of Reinventing Everything # python # odoo # qweb # owl Hello, this is my first blog post ever. I’d like to share my experience working with Odoo , an open-source Enterprise Resource Planning (ERP) system, and explain why I believe many of its architectural choices cause unnecessary complexity. Odoo is a single platform that provides many prebuilt modules (mini-applications) that most companies need. For example, almost every company requires a Human Resources system to manage employee details, leaves, attendance, contracts, resignations, and more. Beyond HR, companies also need purchasing, inventory, accounting, authentication, authorization, and other systems. Odoo bundles all of these tightly coupled systems into a single installation. On paper, this sounds great — and from a business perspective, it often is. From a technical perspective , however, things get complicated very quickly. Odoo Core Components Below are the main Odoo components, ranked from least complex to most complex, and all largely developed in-house instead of relying on existing mature frameworks: Odoo HTTP Layer JSON-RPC Website routing Odoo Views XML transformed into Python and JavaScript Odoo ORM Custom inheritance system Query builder Dependency injection Caching layers Cache System Implemented from scratch WebSocket Implementation Very low-level handling Odoo HTTP Layer Odoo is not built on a standard Python web framework like Django or Flask. Instead, it implements its own HTTP framework on top of Werkzeug (a WSGI utility library). This HTTP layer introduces its own abstractions, request lifecycle, routing, and serialization logic, including JSON-RPC and website controllers. While technically impressive, it reinvents many problems that have already been solved — and battle-tested — by existing frameworks. Odoo Views In my opinion, this is one of the most problematic parts of Odoo. Instead of using standard frontend technologies, Odoo relies heavily on XML-based views . These XML files are sent to the browser and then transformed using Abstract Syntax Tree (AST) analysis into JavaScript. In other contexts (like the website), the XML may be converted into Python code and sometimes back into JavaScript again. This creates: High cognitive overhead Difficult debugging Tight coupling between backend and frontend Poor tooling support compared to modern frontend stacks It feels like building a car from raw metal just to drive from point A to point B. Odoo ORM Odoo’s ORM is not a typical ORM. It implements: A custom inheritance system (instead of using Python’s built-in one) Its own dependency injection mechanism A query builder Caching layers (LRU) Model extension via monkey-patching While powerful, this system is extremely complex and hard to reason about. Debugging model behavior often feels like navigating invisible layers of magic. WebSocket Implementation Instead of using a mature real-time framework, Odoo implements its WebSocket handling with very low-level logic, sometimes in surprisingly small and dense files. A single comment from the codebase summarizes this approach better than words ever could: The “Odoo Is Old” Argument A common defense of Odoo’s architecture is that “it’s an old system” — originally developed around 2005 using Python 2. However, this argument no longer holds. Odoo was largely rewritten from scratch around 2017 to support Python 3. At that time, many excellent frameworks already existed and had solved the same problems more cleanly, while continuing to evolve without breaking their ecosystems. Today, even small changes in Odoo’s core can break custom modules unless they are limited to simple CRUD models with minimal dependencies on core behavior. Final Thoughts Odoo is a powerful product and a successful business platform. But from a software engineering perspective, many of its design decisions prioritize control and internal consistency over maintainability, clarity, and developer experience . If you work with Odoo long enough, you stop asking “why does it work this way?” and start asking “how do I survive this upgrade?” Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Boga Follow Senior Software Engineer Joined Jan 12, 2026 Trending on DEV Community Hot 🧱 Beginner-Friendly Guide 'Maximal Rectangle' – LeetCode 85 (C++, Python, JavaScript) # programming # cpp # python # javascript The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning What was your win this week??? # weeklyretro # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/success-stories/#content | Our Success Stories | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python allows us to produce maintainable features in record times, with a minimum of developers. Cuong Do, Software Architect YouTube.com Newest success stories Python on Arm: 2025 Update Want to know how Python is performing on Arm across Linux, Windows, and the cloud? Our 2025 update highlights the latest JIT improvements, ecosystem milestones like GitHub runners and PyTorch on Windows, and the continued collaboration driving it all forward. Read more Using Python to build a solution for instant tokenized real estate redemptions Python programmability on Algorand makes the entire development lifecycle easier and means more affordable and efficient maintenance and upgrades going forward. Read more Zama Concrete ML: Simplifying Homomorphic Encryption for Python Machine Learning To simplify the adoption of FHE, which involves a complex and resource-intensive technological stack, Zama developed tools that streamline the integration of FHE into applications. Since Python is the de facto standard for building machine learning (ML) applications, it was an obvious choice to create an open-source FHE library in Python. Read more Building Robust Codebases with Python's Type Annotations Maintaining our ever-evolving Python codebase poses an intricate challenge: how do we make updates to reflect the changing rules and regulations of 200+ global markets without compromising access to the systems that our engineers and traders use on a daily basis? While an inner layer of shared business logic enables coherency in our codebase performance, it also means small regulatory changes can impact many systems. In this article, Python Engineer John Lekberg details how we use Python type annotations to minimize the time and risk involved in manual verification. Read more Newest success stories by category Arts See All Business Using Python to build a solution for instant tokenized real estate redemptions Lincoln Loop: Building a sustainable business inspired by Python’s ethos Using Python for commercial cloud backup Using Python to make unstable APIs reliable Python for Financial Machine Learning at Union Investment See All Data Science How HyperFinity Is Streamlining Its Serverless Architecture with Snowflake's Snowpark for Python Reimagining data science with Python-based operators in Einblick’s visual canvas Using Python with Gretel.ai to Generate Synthetic Location Data See All Education Elementary school education: Is it love or just Python? Using Python to Automate Tedious Tasks Python in the Blind Audio Tactile Mapping System See All Engineering Python for Collaborative Robots Abridging clinical conversations using Python Getting to Know Python See All Government Python Powered CrossCompute Report Automation for eReliability Tracker Leads to Cost and Time Savings for the American Public Power Association Saving the world with Open Data and Python Frequentis TAPtools® - Python in Air Traffic Control See All Scientific Why Python Matters for the VR Community Python for Collaborative Drug Discovery Python To Help Meteorologists Python for Scientific Data Visualization Simulating Biomolecules with Python See All Software Development Python on Arm: 2025 Update Zama Concrete ML: Simplifying Homomorphic Encryption for Python Machine Learning Building Robust Codebases with Python's Type Annotations Building a Dependency Graph of Our Python Codebase Bleeding Edge Dependency Testing Using Python See All Submit Yours! Python users want to know more about Python in the wild. Tell us your story ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/grants/ | PSF Grants Program | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> Grants >>> Grants program The PSF Grants Program is currently paused The PSF Grants Program has been temporarily paused after hitting our 2025 funding cap early. It was an extremely difficult but necessary decision to ensure the program and foundation’s near and long term sustainability. Learn more about the pause and how you can support the PSF’s future in our blog post . If you have submitted an application and have yet to receive a decision, you will receive an email from us soon. Thank you for your patience and understanding as we navigate this challenging situation. Table of Contents Overview of the PSF Grants Program Guiding Principles Program Guiding Principles Funding Guiding Principles So what do these Guiding Principles mean? What to expect Why do we ask for so much information? Grant Process Application How to Submit Resolution After a Grant is Awarded Resources Grant Proposal Tips Office Hours Questions? Example Conference Grant Proposal Recent Grants Overview of the PSF Grants Program Welcome to the Python Software Foundation (PSF) Grants Program page! This page and the PSF Grants Work Group are here to help support your Python-related conferences, workshops, and local Python communities in line with the PSF's mission . The grants process is in place to ensure that we have the information we need to evaluate grant requests and maintain our records. We also want to make sure that grant requesters and recipients are set up for success! If you have any questions about the Program, process, or applying, you have a couple of options to find answers: Read through this page– we’ve tried to cover as much as possible! Check out the Grants FAQ page Join the monthly PSF Grants Program Office Hour sessions on the PSF Discord Email grants@python.org We have successfully provided over 3 million USD in grants since we started the program in 2015 all of which have supported tons of fun and exciting work and events to enrich the Python community. We can’t wait to hear about your event, workshop, or regional community—so let’s jump right in! Guiding Principles The PSF Grants Program supports hundreds of Python-related conferences, workshops, and communities globally in line with our mission : The mission of the Python Software Foundation is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers. To facilitate a sustainable grant program, the PSF Board established guiding principles for the program and funding in 2024. Program Guiding Principles The guiding principles of the PSF Grants Program are: Impactful Reliable Equitable Transparent Sustainable Funding Guiding Principles The guiding principles behind the PSF Grants Program funding are: Strive for geographic equity Prioritize underserved communities Prioritize high returns on investment in terms of community impact Invest in both new and existing communities Evaluate and fund in our areas of expertise Ensure Python and Pythonistas are supported So what do these Guiding Principles mean? The program and funding principles outlined in our PSF Grants Program Guiding Principles help us do a couple of things: Ensure alignment with the PSF's mission. Set a vision for the program. Make decisions on a program level basis, as well as on individual grants. Help guide our analysis of grants data in our yearly Grants Program transparency report, and any goals that come from the report and its analysis. What to expect The process for applying for a grant is thorough so we can make decisions as effectively and quickly as possible. Listed below is an overview of what to expect, followed by a more detailed explanation of each step in the “Grant Process” section below. Submit your application. Please fill out every applicable field in the application form to reduce questions later on. The more information you can give us, the better. You will receive a confirmation email from psf-donations@python.org that your application went through. A PSF Staff member pre-checks your application and may follow up with questions. This step helps identify any required information that might be missing in your application before presenting it to the Grants Work Group. Application review by the Grants Working Group or PSF Board. The Grants Work Group is made up of dedicated PSF community members from around the globe. They participate in the Grants Working Group on a volunteer basis and review and approve grant applications regularly. The PSF Board reviews consolidated grant requests. Note: The Grants Work Group is made up of volunteers and the review periods may sometimes reflect that. [As Needed] Questions about your application may be raised by members of the Grants WorkGroup and will be sent to you by PSF staff or members of the Work Group. [As Needed] Further review by the Grants Work Group. If there are a lot of questions about your application, the Working Group may need more time to review and discuss—this is why it’s great to include as much information as possible in your original application! [As Needed] Review by the PSF Board may be necessary in certain cases (e.g. the application is a consolidated grant request or the Grants Working Group cannot agree). Additional questions may result from this review. Decisions about your Grant application will be relayed. You will receive an email from a PSF Staff member regarding the resolution from the Working Group in regards to your application. If your application has been approved, this email will include additional information about invoicing, reporting, and more. Note: the PSF may approve partial funding for your application. Funds will be distributed if your application is approved. You will provide an invoice to the PSF accounting team per the instructions in the resolution email. The accounting team will distribute your funds within 7 business days of receiving all your completed invoice and payment instructions. You will provide a report about the event or workshop that the Grant funded via the grant report form we provide. (The template asks for a short list of information and takes about 10-15 minutes.) This is an important piece of the process because we want to gauge the impact of the grant. It is also required to be eligible for any future grant proposals. Why do we ask for so much information? We know that a lot of work goes into pulling together all the required information to apply for a grant, and we're very appreciative of that effort! The PSF is a nonprofit organization based in the US, which means a couple of things for our Grants Program: We have information requirements as well as limitations on how we can distribute money to follow regulations set by the US federal government. The goal of the requirements in the Grant process is first to make sure we can legally provide funding to your request. For example, there are certain countries where we are unable to send funds (see the Grants FAQ page for more info). These restrictions are evolving and out of our hands, so we can’t list exactly what is allowed or not- because it's always changing (and we can’t update this page every day :)). Based on this, we need to evaluate each request on a case-by-case basis. Additionally, we need to do our best to ensure our grant awards align with the PSF's mission , which is a legal requirement for the PSF as a U.S.-based 501c3 organization. Beyond legal limitations, we have a limited pool of yearly funds to award grants to requesters. This means that we need ample information to ensure that our awards are making a significant impact. And, last but not least: we want to make sure PSF Staff, the Grants Working Group, and the PSF Board have all the information needed to efficiently review your request and get a decision back to you as quickly as possible! Grant Process Application Timeframe: We require that applications be submitted 8 weeks in advance of your event or workshop start date. If this is your first Grant request, we recommend adding a couple of weeks to the process. These time frames give us enough time to thoroughly review, ask questions, make a decision, and have enough time to send you the funds if your request is approved. Note: Consolidated applications and any requests that do not receive consensus within the Grants Working Group get moved to the PSF Board which may extend the timeframe. Types of grants the PSF funds: Our current focus is on Python conferences (in-person, virtual, or hybrid), workshops, and consolidated grants (program level requests for multiple events or workshops across a region). We also fund Python-related Meetup site subscriptions. Grants for non-Python events will only be considered where there's a clear Python component to the event, and the grant will only be utilized for the Python component of the event. Categories of the types of grants we currently fund include: Conferences (e.g. PyCon Italia) Event site subscriptions (Meetup.com) (e.g. London Django Meetup) Django Girls Workshops (e.g. Django Girls Busan Workshop) PyLadies Workshops (e.g. All Day PyLadies Workshop) Workshops (without equipment) (e.g. Robo Dojo: Intro to Python) Consolidated requests (e.g. Python Ghana’s yearly request for funding for 50+ workshops and meetups) Types of grants the PSF does NOT currently fund: Certain categories of spending the PSF does not consider as in line with our mission, and therefore we cannot fund them. Including any of these categories of spending with eligible spending requests will result in partial funding of your request. Such instances are as follows: Personal travel requests Hackathons Swag and prizes Unrelated to Python or the PSF’s charitable mission Other portions of the grant as determined by the GWG Grant categories that we formerly awarded in, but are currently on pause for funding include: Development work Kids Coding Camps Sprints Training Programs Workshops requiring equipment Other Requirements: All grant applications: Please submit a link to the event or initiatives website . We want to ensure that your event/initiative is established and community members are easily able to find information. Please submit the requested grant amount and a comprehensive budget . As a 501c3 organization based in the US, the PSF has a fiscal responsibility to understand how Grant funds will be used. If the grant is funding several components of an event or workshop, please provide a breakdown of the cost for each part. For example, a regional PyCon may plan to use funds for food & beverage, lodging, and A/V support- we need to see a list of each item with an estimate for each individually. A document with a detailed budget of the event/workshop is helpful to see expected expenses and revenues. We have provided a budget template that is available for community use. Note: Due to budget limitations, the PSF may only be able to provide partial funding for a proposal even if all planned expenses are eligible. Please submit a link to your Code of Conduct , it is a requirement in order to receive grant funding. We also check for a reporting method (e.g. an email alias or form) to ensure the Code of Conduct has an enforcement process. This is a requirement for every grant application, no matter the type. Please share the number of expected attendees or participants We want to understand the ratio of impact to grant dollars spent. Please ensure you submit a grant report via our reporting form if you are a repeat grant applicant and received PSF grant funding in the past. We want to understand how the grant funding was used and what impact it made. If you have yet to receive any grant funding from the PSF, you do not need to submit any reports. If your request is for a conference , we require a link to the schedule(s) (should include speaker info), registration page, and information about your sponsors or potential sponsors. We recommend waiting to submit your request until all or most of these components are in place. For example, it’s okay to submit a partial schedule if you have a conference website with ample information about the event, a registration page, and other sponsors. If your schedule is not yet finalized, we also accept schedules from previous editions of your event for your review. If your request is for a workshop , we would like to know more about the mentors and educational content. We prefer a high mentor-to-participant ratio of at least 1:10 (one mentor per ten participants). We require a curriculum with learning outcomes for participants as well. An outline is not sufficient, we would like to see code repositories, worksheets, presentation slides, etc. If you are submitting a grant request for a PyLadies Workshop , your chapter should be registered with PyLadies Global . If you are submitting a grant request for a Django Girls Workshop , your event should be registered with the Django Girls Foundation . Additionally, we highly encourage you to apply for a grant with the Django Girls Foundation . Sponsorships: the PSF wants to understand your prospects as far as additional sponsorships. Please include as much information as possible on any other sources of financial support you are pursuing (even if they haven’t committed yet; let us know who you’ve reached out to!). The PSF is happy to help first-time events get on their feet. The lack of additional sponsorship sources won’t hurt your application or reduce the grant amount, though we hope to see efforts to gain additional funding, especially in the cases of long-standing events. Due to the many initiatives and programs the PSF supports, being the sole source of funding for events is not sustainable for our foundation, or the community. Trademarks and Logos: Please read our Trademark Policy and Trademark FAQs . These cover the permitted uses of the Python logos or any similar logos, the use of the words "Python" or "PyCon", and how you should proceed. If you have questions about your intended use of the trademarks or want to ask for approval for using a "PyCon" conference name or a logo derivative, please contact the PSF Trademarks Committee by email. All conferences, projects, or user groups that create new logos or names using "PyCon" are required to obtain approval from the Trademarks Committee (psf-trademarks@python.org). How to Submit Please submit grant proposals via our online form at least 8 weeks before the start of the event or initiative so the Grants Work Group has enough time to review your request. If this is your first grant request, we recommend submitting your application a couple of weeks earlier in case more questions come up. >>>SUBMIT A PSF GRANT APPLICATION<<< To access the form, you need to create a free account on the psfmember.org website . Resolution PSF Staff will Provide Notice: You will receive an email from a PSF Staff member with the resolution (approved or denied) made by the Grants Working Group or PSF Board. Approved Grants: If your proposal is approved, you will receive instructions about invoicing and payments. Invoices will only be accepted from the grant submitter or a person designated by the grant submitter. You will also receive information about trademarks and reporting. After a Grant is Awarded Reporting: Any event, workshop, or community that receives funding from the PSF is required to submit a report. The PSF would like to see how the grant was used, so we ask to receive a report on the event, workshop, or program that was funded. The report asks for a short list of pieces of information and should take around 10-15 minutes. These reports are useful for us to gauge the impact we are having and how the event went. For subsequent events, we require past reports for both the event and the applicant to consider further requests. A report template is provided for approved grants. If your event, workshop, or community has a blog, social media post, or pictures that relate to the grant, we'd love to see those links, too! Frequency: The PSF will generally only fund up to two events per city and/or organizer within a given year. For example, if Python Workshop Mars were to request funding for a third workshop in one year, we would decline it unless they show ample evidence in their grant request that a third workshop is necessary. Additionally, if event organizer Jesse asks the PSF for a third grant request in one year, we will decline unless they show evidence in their grant request that a third workshop is needed. Resources The PSF has created a library of free resources for our community. We recommend reviewing these resources before you submit your grant request– they may be of use to your event! Grant Proposal Tips We recommend reading through our FAQ for additional information before you submit your application. Proposals should be for specific events or initiatives with a clear objective, rather than support for ongoing activities. Your grant proposal objective should be focused on the impact the grant will have on the Python community, and you should ensure you grant request aligns with the PSF's mission . For information on disbursements of payments, see our Payment Options page . Office Hours The PSF Grants Program Office Hours is a text-only chat based office hour hosted on the Python Software Foundation Discord at 1-2PM UTC (9AM Eastern) on the third Tuesday of the month. (Check what time that is for you.) The server is moderated by PSF Staff and is locked in between office hour sessions. If you’re new to Discord, check out some Discord Basics to help you get started. Questions? If you have questions about your submission please review our Grants FAQ page . If you have more questions please reach out to grants@python.org or join the monthly PSF Grants Program Office Hour session to ask the program administrators directly. Example Conference Grant Proposal Grant Title: PyCon 2020 Date: April 15, 2020 Event’s website: https://us.pycon.org/2020/ Grant amount & budget: $2000 total ($1500 for virtual platform support, $500 for accessibility support). To thank you for your sponsorship, we will place the PSF logo on our site and offer you 3 free tickets to PyCon to distribute as you see fit. We have attached an overview of the conference budget, which includes a breakdown of conference tickets and sponsorship revenue, as well as all of our expected expenses. Grant objective: PyCon will be taking place this April, and sponsorship from the Python Software Foundation would be much appreciated. In an effort to keep our ticket prices affordable and accessible to many, we've secured corporate sponsorship to cover equipment costs and speaker support, and are hoping that the PSF will be able to help us pay for our virtual platform and some accessibility such as captioning. Grant beneficiaries: We are expecting 300 attendees this year. We will also be recording the talks, and will make them available online a few days after the event. Regional Support: The proceeds from the PyCon conference help run our local User Group throughout the year and also help us kick off planning for next year's PyCon conference. Link to Conference Schedule(s): https://us.pycon.org/2020/online/ , https://us.pycon.org/2020/events/edusummit/ , https://us.pycon.org/2020/hatchery/mentoredsprints/ , https://us.pycon.org/2020/hatchery/trainers/ , https://us.pycon.org/2020/hatchery/beginnersdata/ Link to Registration Page: https://us.pycon.org/2020/online/ Link to Conference Prospectus: https://us.pycon.org/2020/sponsors/prospectus/ Code of Conduct: https://us.pycon.org/2020/about/code-of-conduct/ Percentage of Python: 100% Follow-up Activities: We will post a summary of PyCon on our blog and mention that the PSF sponsored the event. The conference will be posting all recordings to our YouTube channel so they will be made available to everyone. We will also submit the required post-event follow up form. Recent Grants You can find historical grant approvals on the Python Software Foundation Resolutions page. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://status.python.org/ | Python Infrastructure Status Python Infrastructure Subscribe to Updates Subscribe x Get email notifications whenever Python Infrastructure creates , updates or resolves an incident. Email address: Enter OTP: Resend OTP in: seconds Didn't receive the OTP? Resend OTP By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get text message notifications whenever Python Infrastructure creates or resolves an incident. Country code: Afghanistan (+93) Albania (+355) Algeria (+213) American Samoa (+1) Andorra (+376) Angola (+244) Anguilla (+1) Antigua and Barbuda (+1) Argentina (+54) Armenia (+374) Aruba (+297) Australia/Cocos/Christmas Island (+61) Austria (+43) Azerbaijan (+994) Bahamas (+1) Bahrain (+973) Bangladesh (+880) Barbados (+1) Belarus (+375) Belgium (+32) Belize (+501) Benin (+229) Bermuda (+1) Bolivia (+591) Bosnia and Herzegovina (+387) Botswana (+267) Brazil (+55) Brunei (+673) Bulgaria (+359) Burkina Faso (+226) Burundi (+257) Cambodia (+855) Cameroon (+237) Canada (+1) Cape Verde (+238) Cayman Islands (+1) Central Africa (+236) Chad (+235) Chile (+56) China (+86) Colombia (+57) Comoros (+269) Congo (+242) Congo, Dem Rep (+243) Costa Rica (+506) Croatia (+385) Cyprus (+357) Czech Republic (+420) Denmark (+45) Djibouti (+253) Dominica (+1) Dominican Republic (+1) Egypt (+20) El Salvador (+503) Equatorial Guinea (+240) Estonia (+372) Ethiopia (+251) Faroe Islands (+298) Fiji (+679) Finland/Aland Islands (+358) France (+33) French Guiana (+594) French Polynesia (+689) Gabon (+241) Gambia (+220) Georgia (+995) Germany (+49) Ghana (+233) Gibraltar (+350) Greece (+30) Greenland (+299) Grenada (+1) Guadeloupe (+590) Guam (+1) Guatemala (+502) Guinea (+224) Guyana (+592) Haiti (+509) Honduras (+504) Hong Kong (+852) Hungary (+36) Iceland (+354) India (+91) Indonesia (+62) Iraq (+964) Ireland (+353) Israel (+972) Italy (+39) Jamaica (+1) Japan (+81) Jordan (+962) Kenya (+254) Korea, Republic of (+82) Kosovo (+383) Kuwait (+965) Kyrgyzstan (+996) Laos (+856) Latvia (+371) Lebanon (+961) Lesotho (+266) Liberia (+231) Libya (+218) Liechtenstein (+423) Lithuania (+370) Luxembourg (+352) Macao (+853) Macedonia (+389) Madagascar (+261) Malawi (+265) Malaysia (+60) Maldives (+960) Mali (+223) Malta (+356) Martinique (+596) Mauritania (+222) Mauritius (+230) Mexico (+52) Monaco (+377) Mongolia (+976) Montenegro (+382) Montserrat (+1) Morocco/Western Sahara (+212) Mozambique (+258) Namibia (+264) Nepal (+977) Netherlands (+31) New Zealand (+64) Nicaragua (+505) Niger (+227) Nigeria (+234) Norway (+47) Oman (+968) Pakistan (+92) Palestinian Territory (+970) Panama (+507) Paraguay (+595) Peru (+51) Philippines (+63) Poland (+48) Portugal (+351) Puerto Rico (+1) Qatar (+974) Reunion/Mayotte (+262) Romania (+40) Russia/Kazakhstan (+7) Rwanda (+250) Samoa (+685) San Marino (+378) Saudi Arabia (+966) Senegal (+221) Serbia (+381) Seychelles (+248) Sierra Leone (+232) Singapore (+65) Slovakia (+421) Slovenia (+386) South Africa (+27) Spain (+34) Sri Lanka (+94) St Kitts and Nevis (+1) St Lucia (+1) St Vincent Grenadines (+1) Sudan (+249) Suriname (+597) Swaziland (+268) Sweden (+46) Switzerland (+41) Taiwan (+886) Tajikistan (+992) Tanzania (+255) Thailand (+66) Togo (+228) Tonga (+676) Trinidad and Tobago (+1) Tunisia (+216) Turkey (+90) Turks and Caicos Islands (+1) Uganda (+256) Ukraine (+380) United Arab Emirates (+971) United Kingdom (+44) United States (+1) Uruguay (+598) Uzbekistan (+998) Venezuela (+58) Vietnam (+84) Virgin Islands, British (+1) Virgin Islands, U.S. (+1) Yemen (+967) Zambia (+260) Zimbabwe (+263) Phone number: Change number Enter OTP: Resend OTP in: 30 seconds Didn't receive the OTP? Resend OTP Message and data rates may apply. By subscribing you agree to our Privacy Policy , the Atlassian Terms of Service , and the Atlassian Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you acknowledge our Privacy Policy . In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy . Get webhook notifications whenever Python Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: The URL we should send the webhooks to Email address: We'll send you email if your endpoint fails By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Follow @PythonStatus or view our profile . Get the Atom Feed or RSS Feed . All Systems Operational Uptime over the past 90 days. View historical uptime. python.org ? Operational 90 days ago 100.0 % uptime Today python.org - CDN ? Operational 90 days ago 100.0 % uptime Today python.org - Backends ? Operational 90 days ago 100.0 % uptime Today python.org - Downloads Backends ? Operational 90 days ago 100.0 % uptime Today PyPI Operational 90 days ago 99.99 % uptime Today pypi.org - General Operational pypi.org - CDN ? Operational 90 days ago 100.0 % uptime Today pypi.org - Backends ? Operational 90 days ago 99.99 % uptime Today pypi.org - Email ? Operational files.pythonhosted.org - Files ? Operational 90 days ago 100.0 % uptime Today files.pythonhosted.org - Redirects ? Operational files.pythonhosted.org - Redirects Backends ? Operational PyPI Hosting Platforms Operational AWS elasticache-us-east-2 Operational AWS elb-us-east-2 Operational AWS ec2-us-east-2 Operational AWS rds-us-east-2 Operational Google Cloud Platform Google Cloud Storage Operational docs.python.org Operational docs.python.org - Backends ? Operational docs.python.org - CDN Operational bugs.python.org Operational wiki.python.org Operational mail.python.org Operational Message Handling Services Operational Mailing Lists and Archives - Mailman Operational Mailing Lists and Archives - Mailman 3 Operational psfmember.org Operational us.pycon.org Operational PyPy Operational speed.pypy.org Operational Content Delivery Network ? Operational Fastly Asia/Pacific (HK) Operational Fastly US East (IAD) Operational Fastly US East (MIA) Operational Fastly US Central (DEN) Operational Fastly US Central (DFW) Operational Fastly US West (SEA) Operational Fastly US West (SJC) Operational Fastly Europe (FRA) Operational Fastly Europe (AMS) Operational Fastly Europe (LHR) Operational Fastly Asia/Pacific (SYD) Operational Fastly Asia/Pacific (NZ) Operational Fastly Brisbane (BNE) Operational Fastly Dubai (FJR) Operational Fastly Melbourne (MEL) Operational Fastly Osaka (ITM) Operational Fastly Perth (PER) Operational Fastly Tokyo (HND) Operational Fastly Tokyo (TYO) Operational Fastly Wellington (WLG) Operational Fastly Dublin (DUB) Operational Fastly Copenhagen (CPH) Operational Fastly Frankfurt (HHN) Operational Fastly Helsinki (HEL) Operational Fastly London (LON) Operational Fastly Madrid (MAD) Operational Fastly Manchester (MAN) Operational Fastly Milan (MXP) Operational Fastly Oslo (OSL) Operational Fastly Buenos Aires (EZE) Operational Fastly Bogota (BOG) Operational Fastly Curitiba (CWB) Operational Fastly Rio de Janeiro (GIG) Operational Fastly Santiago (SCL) Operational Fastly Johannesburg (JNB) Operational Fastly Cape Town (CPT) Operational Fastly Vancouver (YVR) Operational Fastly Toronto (YYZ) Operational Fastly St. Louis (STL) Operational Fastly Palo Alto (PAO) Operational Fastly Newark (EWR) Operational Fastly New York (LGA) Operational Fastly Montreal (YUL) Operational Fastly Minneapolis (STP) Operational Fastly Minneapolis (MSP) Operational Fastly Los Angeles (BUR) Operational Fastly Kansas City (MCI) Operational Fastly Houston (IAH) Operational Fastly Dallas (DAL) Operational Fastly Columbus (CMH) Operational Fastly Chicago (CHI) Operational Fastly Boston (BOS) Operational Fastly Atlanta (PDK) Operational Fastly Atlanta (FTY) Operational Fastly Ashburn (WDC) Operational Fastly New Delhi (DEL) Operational Fastly Mumbai (BOM) Operational Fastly Chennai (MAA) Operational Fastly Vienna (VIE) Operational Fastly Stockholm (BMA) Operational Fastly Paris (CDG) Operational Fastly Purging Operational Fastly Tokyo (NRT) Operational Fastly Singapore (QPG) Operational Fastly Seoul (ICN) Operational Fastly Manila (MNL) Operational Fastly Kuala Lumpur (KUL) Operational Fastly Dubai (DXB) Operational Fastly Christchurch (CHC) Operational Fastly Adelaide (ADL) Operational Fastly Ghana (ACC) Operational Fastly Sāo Paulo (CGH) Operational Fastly Lima (LIM) Operational Fastly Fortaleza (FOR) Operational Fastly Seattle (BFI) Operational Fastly Portland (PDX) Operational Fastly Phoenix (PHX) Operational Fastly Los Angeles (LGB - LAX/SNA) Operational Fastly Honolulu (HNL) Operational Fastly Gainesville (GNV) Operational Fastly Detroit (DTW) Operational Fastly Columbus (LCK) Operational Fastly Calgary (YYC) Operational Fastly Atlanta (ATL) Operational Fastly Sydney (SYD) Operational Fastly Palo Alto (PAO) Operational Fastly Amsterdam (AMS) Operational Fastly Kolkata (CCU) Operational Fastly Hyderabad (HYD) Operational Fastly Palermo (PMO) Operational Fastly Sofia (SOF) Operational Fastly Rome (FCO) Operational Fastly Munich (MUC) Operational Fastly Milan (LIN) Operational Fastly Marseille (MRS) Operational Fastly Lisbon (LIS) Operational Fastly Brussels (BRU) Operational Operational Degraded Performance Partial Outage Major Outage Maintenance Major outage Partial outage No downtime recorded on this day. No data exists for this day. had a major outage. had a partial outage. Related No incidents or maintenance related to this downtime. System Metrics Month Week Day PyPI CDN Edge Errors ? Fetching PyPI Files CDN Edge Errors ? Fetching PyPI CDN Miss Times Fetching PyPI Files CDN Miss Times Fetching Past Incidents Jan 13 , 2026 No incidents reported today. Jan 12 , 2026 No incidents reported. Jan 11 , 2026 No incidents reported. Jan 10 , 2026 No incidents reported. Jan 9 , 2026 No incidents reported. Jan 8 , 2026 No incidents reported. Jan 7 , 2026 PyPI Uploads failing Resolved - This incident has been resolved. Jan 7 , 23:00 UTC Monitoring - We identified a database lock causing contention and stopped all upload backends to release all locks and are monitoring for recovery. Jan 7 , 22:59 UTC Investigating - We are investigating why PyPI uploads are failing. Jan 7 , 22:42 UTC Jan 6 , 2026 No incidents reported. Jan 5 , 2026 No incidents reported. Jan 4 , 2026 No incidents reported. Jan 3 , 2026 No incidents reported. Jan 2 , 2026 No incidents reported. Jan 1 , 2026 No incidents reported. Dec 31 , 2025 No incidents reported. Dec 30 , 2025 No incidents reported. ← Incident History Powered by Atlassian Statuspage | 2026-01-13T08:49:02 |
https://dev.to/t/qweb | Qweb - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close # qweb Follow Hide Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Odoo Core and the Cost of Reinventing Everything Boga Boga Boga Follow Jan 12 Odoo Core and the Cost of Reinventing Everything # python # odoo # qweb # owl Comments Add Comment 3 min read loading... trending guides/resources Odoo Core and the Cost of Reinventing Everything 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://docs.suprsend.com/changelog | Product Updates - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Changelog Product Updates Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Changelog Product Updates Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Changelog Product Updates OpenAI Open in ChatGPT Logs of all the feature releases, improvements, and bug fixes in SuprSend. OpenAI Open in ChatGPT 18 December 2025 Hosted Preference Page — Modern Design with Multi-Language Support The hosted preference page has been updated with a refreshed UI and locale-aware localization support. Static UI content (CTAs, labels, system text) is translated automatically using built-in i18n support for up to 23 languages. Dynamic content, including notification category names and descriptions, is rendered using the translation files configured by you, based on the user’s locale. 📘 Checkout hosted preference page documentation and see how translations work 3 December 2025 Category Translations for Preference Centers Reach users worldwide with category translations — show your preference centers in your users’ native language. Whether your users speak Spanish, French, German, or any other language, they’ll see category names and descriptions in their preferred locale, making it easier for them to understand and manage their notification preferences. What you get: Multi-language support : Upload translations via Dashboard, API, or CLI — choose the method that works best for your workflow Smart fallbacks : If a translation isn’t available for a specific locale (e.g., es-AR ), we automatically try the base locale ( es ), then fall back to English — your users always see something meaningful Zero maintenance : English translations are automatically generated from your category names and descriptions, so you don’t need to manage them separately 📘 Learn more in the category translations documentation . 1 December 2025 📚 S3 Connector v2.0 — Comprehensive Notification Data Export S3 Connector v2.0 exports end-to-end notification data to your S3 bucket, giving you full visibility into requests, workflows, and message delivery for analytics, debugging, and compliance. It replaces the limited v1.0 connector with complete, structured logging. S3 Connector v1.0 will be deprecated over time. Migrate to v2.0 to access full logs and notification analytics. What’s New We’ve added 3 data points for end-to-end traceability of notifications from API request → workflow execution → final delivery : Messages: Delivery status, engagement metrics, vendor responses, and failures Workflow Executions: Step-by-step workflow logs for debugging conditions, preferences, and errors Requests: API payloads and responses for trigger-level debugging and audit trails Use Cases Internal analytics or customer-facing analytics Debug delivery and workflow issues using detailed logs or show logs on your customer portal Maintain audit trails for compliance and internal reporting Query and analyze notification data you fully own 📘 Check out the S3 Connector v2.0 documentation for more details. 29 November 2025 Channel-Level Control for Preference Categories Choose which channels users are opted into by default when setting up preference categories. You can use this to have preference category defaults as user gets in-app notification by default and other channels will be sent only if user explicitly opts in to them. 📘 Learn more in the preference categories documentation . 31 October 2025 Type-Safe Workflow Triggers Catch payload errors at compile time and get IDE autocomplete for workflow payloads and event properties using generated type definitions. Define your payload structure once using SuprSend JSON schemas , and automatically generate type definitions using SuprSend CLI . What’s Included and Why This Matters Prevents production bugs caused by invalid payloads Keeps backend code and notification schemas in sync Get IDE autocomplete, inline validation, and type hints for payload fields Supported languages: TypeScript, Python, Go, Java, Kotlin, Swift, Dart 📘 Learn more in the type safety & type generation documentation . 30 October 2025 🌍 Translations - One template, all languages, zero hassle Go global with translations — the easiest way to localize your notifications. One template, multiple languages, automatic fallbacks. No more maintaining separate templates for each language. What You Can Do Localize notifications instantly: Smart translation keys → Use {{t "key"}} syntax in templates and let SuprSend handle the rest Automatic fallbacks → Users always get a translation, even if their exact locale isn’t available Dynamic content → Pass variables like {{t "key" name=user.first_name}} for personalized content Pluralization → Automatic handling of singular/plural forms based on count Manage translations like code: Upload, download, edit → Work with translation files locally or in the dashboard Version control → Complete history tracking with one-click rollbacks CLI & API support → Manage translations programmatically or via command line Built for developers: Namespaced keys → {{t "feature:key"}} to avoid conflicts across features JSONNET support → Complex conditional logic for advanced use cases Handlebars integration → Combine with other helpers for dynamic content Version control for translations → Track changes, maintain history, and roll back when needed 📘 Check out the translation documentation to get started. 1 October 2025 Preference Category Management APIs You can now programmatically create, update, and commit preference categories using the Management APIs — no dashboard required. This makes it easy to integrate category management into your existing workflows, scripts, and deployment pipelines. 👉 Also available via the SuprSend CLI . 📘 See the API documentation to get started. 29 September 2025 🚀 SuprSend CLI Beta - Ship Notification changes like code We’re excited to announce the public beta of SuprSend CLI , bringing full notification management to your terminal. Using CLI, you can manage and promote assets across workspaces, integrate with CI/CD, and treat notification changes just like code. What You Can Do Promote assets across workspaces — move workflows, schemas, events, and categories between environments (e.g., staging → production) with suprsend sync or targeted pull/push commands. Automate with CI/CD Deployment – Release notification changes through feature or bugfix branches, just like any other piece of code: version it, test it, and deploy it. Manage notification changes in Git — pull assets locally, version them alongside your application code, and push updates as feature branches or bugfix releases. Treat notification infrastructure just like code — review, branch, merge, and release with the same version control workflows you already use. Built for developers Code reviews for notifications — keep your notification infrastructure in Git, track changes, and roll back when needed. Approval gates for production — ensure no change goes live without review and approval. Work with assets locally — create, edit, and test workflows, schemas, and translation files on your machine. Version control & rollback — maintain change log and safely revert changes when required. This is a beta release — we’re actively gathering feedback and making improvements. So, feel free to report an issue and contribute to the project. 📘 Check out the CLI documentation to get started. 29 September 2025 🤖 SuprSend MCP Server (Beta) — AI-Powered Notification Management Your AI agents, copilots, and LLM tools can now directly interact with SuprSend through natural language, making notification management as simple as having a conversation. What You Can Do with SuprSend MCP Everyday workflows with AI: Trigger workflows on demand “Run the approval-required workflow for user John Doe to test my setup.” Bootstrap test data “Create a sample user named John Doe and a tenant called acme-corp in my workspace.” Manage preferences “Enable email notifications for marketing and disable SMS.” Configure branding “Update the logo and primary color for the enterprise tenant.” Vibe-code with AI: Ask AI to fetch setup guides, code examples, or integration snippets directly from SuprSend docs and apply it in your application code. Expose safe, scoped endpoints (via MCP) that wrap APIs with context, reducing guesswork and hallucinations. Integrate with LLM-based assistants (Claude, Copilot, Cursor, Windsurf, etc.) to simplify notification setup with SuprSend. Compatible AI Tools Works with Claude, Cursor, Windsurf, and any MCP-compatible AI agent. Notes & Caveats (Beta) - APIs, behavior, or scopes may change based on feedback. We restrict destructive operations (e.g. deletes) initially to reduce risk. We welcome your feedback — report issues and share feedback to help us harden MCP for production. Getting Started Start the MCP server and configure it with your AI tool. See our MCP setup guide for detailed instructions. 12 September 2025 Send Notifications Only to Verified Channels in Sandbox Sandbox workspaces come pre-configured with SuprSend vendors for quick testing. However, we noticed some cases of misuse where test messages were being sent to unintended recipients. To prevent accidental spam and keep Sandbox safe, notifications can now only be sent to verified channels . You can set upto 5 verified channels for each channel type. Reach out to us if you need more. You can add and manage your verified channels from developers -> Verified Channels page . 12 September 2025 Test Mode: Test Notifications safely without sending to real users Testing notifications shouldn’t mean worrying about accidentally pinging your customers. In most companies, teams end up redirecting notifications to shared inboxes like [email protected] or [email protected] just to avoid delivery to real users—while still being able to debug the full notification flow. With Test Mode , you can now replicate this real-world testing flow directly in our platform: Test end-to-end notification flow : Add channels belonging to internal testers as test channels. In test mode, notifications to these channels are delivered normally—so you can preview messages on real devices. Set Up Test Channels : You can add channels belonging to your internal testers as test channels. Delivery will not be blocked for test channels in test mode. This helps you see preview of the notification in your real device. Catch-All Routing : Redirect all non-test notifications to a common channel (e.g., a QA inbox), making it easy to trace and debug every message in one place. This ensures you can confidently test notification workflows in an environment that mirrors production—without the risk of real users getting test messages. 30 August 2025 Validate workflow trigger Payload using JSON Schema We’ve introduced API-level JSON Schema validation for workflow trigger payloads. This catches payload mismatches before execution, preventing runtime failures and ensuring consistent, correct notifications. Why it matters When you trigger a workflow, you pass data (payload) that is used to resolve workflow variables and populate dynamic content in templates. Currently, If the payload does not include all the variables expected in the workflow, the execution may fail at different stages. With this change, Validation will happen at API level and there’ll be: Fewer runtime failures : Stop workflows from starting with missing or malformed data. Faster debugging : Get a clear, structured error list at request time—no more hunting through multi-step logs. More reliable messaging : Prevent partial runs, inconsistent behavior, and incorrect or incomplete notifications. How it works You can add JSON schema from Schema page and then link it to the workflow Trigger step or trigger Event from events page . When you trigger a workflow, the payload is validated against a JSON Schema that describes the expected data used to resolve variables and populate dynamic content. If the payload doesn’t match the schema, the Trigger API returns error response with a list of validation errors (e.g., path, expected type, missing fields). If validation passes, the workflow proceeds as usual. Fixes and Improvements: Workflow slug validation at the API layer: If a referenced workflow slug isn’t available, the error is now returned directly in the API response (in addition to request logs) for faster debugging. This validation will only apply to new workflows created after this change. If you want to apply it all your existing workflows, reach out to SuprSend support. 23 August 2025 Tenancy social links update Added support for TikTok in tenant social_links . Twitter renamed to x in descriptions and examples (field name remains compatible as per API changes). Updated social link icons for better visual consistency. 19 August 2025 Message logs revamp Redesigned UI for seamless tracking of notification lifecycles. Quickly view delivery status, opens, clicks, and errors across all channels in a single log view. Entity-level visibility : Drill down into logs by workflow, user, object, or list to understand exactly what happened in context. Advanced filtering : Filter logs by status, workflow, template, channel, category, or time range to debug faster. Consistent date range filter across all log pages, making it easier to trace the journey of a notification from request → workflow → final message delivery and it’s interaction state. Fixes and Improvements react-sdk (v0.3.0) - Introduced a custom infinite-scroll component with robust Shadow DOM compatibility. web-components (v0.3.0) - Enhanced Shadow DOM rendering support to ensure component isolation and consistent styling. 16 August 2025 Analytics 2.0 - faster, real-time, with one click filters to drill down into insights Real-time insights → Trends update as messages go out. Track performance across channels and spot dips in engagement instantly. Workflow-level comparisons → Compare workflows, templates, channels, and categories side by side to spot under performers and validate experiments. Know when your users opt-out → See which channels/categories drive opt-outs so you can adjust before churn sets in. Over-messaging trends → Track avg notifications per user, find patterns by category, and identify fatigue triggers to keep communications helpful—not noisy. Granular filtering → Multi-select filters for workflow, tenant, template, channel, category, time range Centralized error tracking → All API, workflow, and provider delivery errors in one place. Filter by tenant/workflow/template/channel, open the exact log, and debug in seconds. 23 July 2025 Sendgrid IP Pool support Enabled creation and management of SendGrid IP Pools, allowing granular control over email delivery, IP reputation, and segmentation of email traffic base on notification category. Fixes and Improvements Added support to send slack messages using broadcast. 11 July 2025 Workflow Management APIs Released comprehensive Management APIs to programmatically create, update, and commit workflows. Supports dynamic workflow orchestration — from your platform or third-party systems — to automate creation and modification of workflows from your codebase. You can checkout the documentation here . 4 July 2025 Proxy support in Java SDK Java SDK can now route outbound requests through HTTP/S proxies, enabling deployments behind corporate firewalls and network controls. 16 June 2025 iOS Native SDK Revamp with JWT based authentication & Preferences support The new iOS SDK now has our latest JWT authentication. You can use it to: JWT-based auth for secure event ingestion, profile updates and push token management. Support to add In-app Preferences Center in mobile apps with UI and example code available for quick setup. Fixes and Improvements Flutter sdk released (v2.5.0) - Fixed an Android push client issue and added silent push support for background updates. 22 May 2025 Role based auth in AWS SNS In line with our ongoing efforts to enhance platform security, we’ve also enabled IAM Role- based auth in AWS SNS vendor. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. 13 May 2025 New SMS Vendor: Bird We’ve added support for sending SMS using the new Bird APIs. The setup is straightforward with a simple vendor form to fill to get started, and full integration details are available here. 30 Apr 2025 SuprSend tracked Properties Now Available in Recipients Payload Recipient payloads now include key internal properties—like user type and their unique identifier—making them readily accessible for use in templates and workflows. → For users: {“$type”: “user”, “distinct_id”: “xxxx”} → For objects: {“$type”: “object”, “object_type”: “xxx”, “id”: “xxx”}" Use these properties to pre-fill form values, add conditional branching based on user type, or Create dynamic links using unique user IDs 23 Apr 2025 Workflow Conditions - Array Comparison Operators Now, find an element in array or find intersections between two arrays in workflow conditions. Example Use cases: Send a notification to users whose role is one of ["admin","manager"] Notify tournament followers who have subscribed to any of the playing teams or players. 15 Apr 2025 Introducing Preference Tags Filter notification categories shown to users based on tags like role, team, or department—so Finance sees billing alerts, and Engineers see only error and anomaly categories. You can assign multiple tags to each preference category or section, and define complex logical expressions (e.g. role == “manager” && department in [“sales”, “marketing”]) to dynamically show relevant preference categories per user. Great for building clean, personalized preference centers without bloating the UI. 7 Apr 2025 Documentation Revamp–Cleaner, Smarter, More Interactive We’ve overhauled our documentation experience to make it more consistent, intelligent, and user-friendly: Brand-Aligned UI : The docs now match the look and feel of the SuprSend platform. AI-Powered Search : Get smarter, faster answers with AI-supported search. You can also open documentation directly in ChatGPT or Claude for conversational, AI-driven assistance. Improved Readability : Upgraded UI components provide a cleaner layout and better readability, helping you navigate and understand complex topics more easily. Interactive API Reference : Try out API requests directly from the docs and view live responses in real-time—no need to switch tools. This revamp is part of our ongoing effort to make implementation faster, smoother, and more intuitive for developers. 27 Mar 2025 Cross Lookup User Subscriptions Easily view all of a user’s subscriptions—whether to lists or objects —in one place. The Subscriptions tab on the user details page now provides a centralized view for easier access to user subscriptions. Fixes in workflows UI Resolved an issue where newly published workflow versions wouldn’t appear without a page refresh (introduced after version history was added). Fixed a bug in the test trigger modal where object suggestions incorrectly appeared when switching from API to event trigger. Removed the success metric from delivery nodes where it’s not relevant (except for Smart Delivery Nodes). 20 Mar 2025 Workflow Trigger Overrides Event-Based triggers now support overriding the actor, recipient, tenant, and object—directly within the workflow. This removes the need to resolve recipients in your code, allowing you to pass internal events as-is and dynamically resolve users and related context per workflow. Perfect for use cases like sending a daily digest to tenant admins or notifying internal account managers at a parent company—all from the same event trigger. 15 Mar 2025 Clone content across template versions and languages Editing multi-lingual templates or doing A/B with different template content? Now, rollback to a version or copy designs between different languages by cloning within template. Fixes and Improvements iOS Integration - Fixed the bitcode issue in xcode16 6 Mar 2025 Role based auth in AWS SES and S3 connector In line with our ongoing efforts to enhance platform security, we’ve now enabled IAM Role- based auth in AWS connectors. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. Fixes and Improvements Added API name filter in request logs. This will help you drill down logs based on event and workflow name. 27 Feb 2025 In-App Inbox: French translation support The Inbox UI now supports automatic French translation! Just pass language="fr" when initializing the Inbox, and all static content will render in French—no extra setup needed. Available in @suprsend/web-inbox ≥ v0.6.0. More languages coming soon Fixes and Improvements Released suprsend-py-sdk==0.13.0 with latest user and object management APIs. Fixed Email issue where tenant button was not showing cursor clickable on hover. 20 Feb 2025 In-App: Fetch cross tenant feed We’ve recently been hearing multi-tenant use cases where a user belong to multiple tenants and would want to see Inbox feed for all tenants in a single product. e.g., an account manager is handling multiple client accounts and need to see updates or daily reports linked to all their accounts in a single feed. You can now achieve this by passing tenantId = * while initializing the Inbox. SuprSendInbox Copy Ask AI interface ISuprSendInbox { workspaceKey : string distinctId : string | null subscriberId : string | null tenantId ?: "*" ... } 15 Feb 2025 Workflow - Step-by-Step Analytics You can now track consolidated view of users’ workflow journey at each workflow step directly in the workflow graph. Track user entry, exit, drop-offs, branch followed, and node failures. You can also see workflow edit history and compare analytics across different workflow versions and time range. Next up: Deeper analysis into each workflow step - notification engagement (deliver, seen, click), failures, and AI-powered insights. Improvements: Added data centre field in account settings to check where your data centre region. 12 Feb 2025 Batch - Flush First Item Immediately We’ve introduced a new setting in batch processing: Flush First Item in Batch . Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window. This helps you to build leading debounce logic in workflows, where users are notified immediately about critical updates like anomaly alerts, while other alerts are batched and sent at regular intervals until the issue is resolved. You can find this option in batch -> advanced configuration . 07 Feb 2025 Workflow - Relative Delay and Batch window Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload. For instance, send a reminder 30 minutes after a task’s due time or send feedback 5 minutes after an event or webinar. Fixes and Improvements: In Inbox drop-in popover component, we fixed scroll bar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled. In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue. In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bug fix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction. 31 Jan 2025 Nested Objects - Choose the fan out depth Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers. Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions. 🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox). 🔹 Depth 1 → Notify the object’s channels + direct subscribers. 🔹 Depth N → Expand deeper into hierarchical subscriptions as needed. Copy Ask AI "recipients" : [ { "object_type" : "teams" , "id" : "finance" , //optional parameter to define subscription fan-out depth in workflows "$object_subscriptions_query" : { "depth" : 0 } } ] You can use this to build Escalation Workflows or Tiered Customer Support Notifications , send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration. Fixes and Improvements: [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK Added support to trigger multi-lingual templates in broadcast 29 Jan 2025 New handlebars helpers - jsonParse and jsonPath We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor: jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags. jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers. Fixes and Improvements: Opened up merge tag input to support handlebars helper in email merge tags . Added support for handlebars helper in display condition . 27 Jan 2025 List entry/exit events in trigger You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list. This will help you build workflows on user lists like, send series of activation notifications to users who didn’t interact with the product in last 30 days and stop sending when they become active again. Fixes and Improvements: [SDK] We have exposed object management methods in Node SDK 20 Jan 2025 Inbox 2.0 - better authentication, In-App feed component and seen interaction Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed In-App feed component and seamlessly create Full screen or Side sheet Inbox experience. What’s New? ✅ Enhanced Security : We’ve replaced HMAC authentication with stateless JWT authentication for better security. ✅ Drop-in components : You can now quickly build an inbox, including full screen and side sheet feeds, by directly importing UI inbox components that are available in our SDK. ✅ Bring your own toast : If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience. These updates offer greater flexibility, security, and customization—giving you full control over your in-app notification experience. If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK. 15 Jan 2025 Interaction Observer: Seen Tracking in Inbox We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as “seen” when they come in user’s scroll view. 10 Jan 2025 Enhanced Broadcast Observability We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions. Here’s what’s new: Real-time Execution Tracking : Monitor broadcast operations as they happen, ensuring you stay informed every step of the way. Step-by-Step Debugging : View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster. Advanced Filters : Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency-key, and status. Easily identify and analyze failure logs. Detailed Broadcast Summaries : Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs. 5 Jan 2025 Athena database connector We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines. 27 Nov 2024 New workflow node: Invoke Workflow With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows —e.g., if a team member doesn’t take action within a set time frame, the workflow escalates the issue and notifies their manager. This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management. 25 Nov 2024 New workflow node: Update User Profile You can now update recipient or actor profiles directly within a workflow. This feature simplifies user profile management by enabling real-time updates as part of the workflow process. If your have event-based system, where user profile changes are coming as events from your product or a third-party system, you don’t need to convert it into user update APIs in your codebase. Simply send events to SuprSend, and let workflows handle user profile updates seamlessly. Key use cases Event-based user profile updates : Simply send events to SuprSend when user updates their profile in your product or when you are setting custom profile attributes as a side-effect of related action, e.g., in a job board, change user’s application status when employer shortlists the profile. Update user profile based on a workflow step : Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, while the onboarding process, update %completion in user profile when they complete a step. 20 Nov 2024 Update Object subscriptions within workflow You can now dynamically update object subscriptions directly within a workflow. This enhancement eliminates the need for separate API calls for object update, allowing you to manage everything seamlessly within workflows. If you have event-based systems where all asset updates are coming in form of event from your product or third-party systems, you don’t have to consume those events internally and write custom APIs to update individual assets (user, list, object) in SuprSend. Simply send events and let the workflow handle object subscriptions and user profile updates, making SuprSend truly a single API integration. Example use case When someone subscribes to a topic (like a tournament), add them as a subscriber to the corresponding tournament object. Later, just trigger tournament related events to SuprSend and the object will automatically fan out and send notification to all users subscribed to the topic. 17 Nov 2024 New workflow node: Add / Remove user in list You can now dynamically update list users as part of workflow execution. This is a step toward creating user segments based on events or workflow progression, removing the need to call the List Update API separately. Key use cases Event-based segmentation : When an event occurs, trigger notification to the user and simultaneously add them to a list for future updates. e.g., when a user registers for an upcoming event or webinar, you can send them confirmation email and add them to a list to later send further updates related to the event. Workflow Step-based segmentation : Another use case is dynamically adding or removing a user from the list when they complete a workflow step. e.g., in a knowledge series designed to onboard new users, remove a user from the POC list once they complete onboarding steps. 15 Nov 2024 Deletion APIs On customer request, added APIs to dynamically delete entities in SuprSend. Following deletion APIs are added: Delete user profile Delete list Delete tenant/brand Delete Object and Remove object subscription These actions are also available on the dashboard for manual management. Delete function just deletes the asset and their related data, including preferences. It doesn’t have any effect on the historical workflows or broadcasts already executed. While calling the delete function, ensure no active workflows are running for the asset, else the execution will fail. 14 Nov 2024 User Merge API: Merge duplicate users into one Happy to announce user merge API to merge duplicate user identities into a single distinct_id . This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states. Key Use Cases Cross-Product Identity Consolidation : When users interact across multiple products (e.g., different apps or services within your platform), they may have different identifiers for each product which needs to be merged later. Anonymous to Identified Transition : Platforms often track user actions anonymously before sign-up or login. During this period, user actions are typically tracked under an anonymous ID. Upon sign-up, merge the anonymous profile into the newly created identifier to preserve historical data and Associate it with the identified user profile. 11 Nov 2024 User Management APIs Being developer first, we have made significant updates and enhancements to the User APIs for easier user management in SuprSend. Also, subscriber is renamed to users in all APIs to avoid confusion with object subscription. Here’s a list of all the changes: Introduced new APIs to fetch user profile , list users and delete user . User update API endpoint has been changed from /event to /user/{{distinct_id}} . There are 2 separate APIs to create(upsert) and edit user profile. Any addition or changes in existing user properties can be done using user upsert API . For deletion of property or channel, user edit API can be used. This is done to keep user upsert API structure flat and simple, consistent to how you identify user in workflow trigger. Subscriber is renamed to user in all APIs, including user preference APIs. 7 Nov 2024 Objects: Design scalable group notifications We’re excited to introduce a powerful new capability in SuprSend: Objects . Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously. What You Can Do with Objects: Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g. a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g. anomaly notifications) to shared channels. Objects can have it’s own channels and preferences to handle this use case. Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger . A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn’t have information of the users subscribed to that trigger. Maintain hierarchical user relationship with nested object subscription . e.g., sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object. Objects can be easily tested from platform with all object related actions available on SuprSend console. You can programmatically manage objects from your codebase using rest API calls . Support for SDKs coming soon… If there’s any use case in object that you think is missing and needs to be solved, please reach out to our support . 3 Nov 2024 Datetime comparators in workflow conditions You can now compare datetime fields in workflow conditions . This lets you compare two timestamps where values can be: Variable : computed from workflow input data Static : a fixed timestamp (e.g. 2024-01-01T00:00:00Z ) Relative to current timestamp : e.g. “ now ” or “ now+30d ” (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware. 30 Oct 2024 Send node execution log - UI revamp The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list. 29 Oct 2024 Audit Logs To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp. Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings. 22 Oct 2024 Support for customizing header component in Inbox Added support for customizing the header component in inbox SDKs. @suprsend/react-inbox You can now add a custom component to the right side of the header in the inbox popup. This replaces the “Mark all as read” text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer here . @suprsend/web-inbox In web-inbox , you can add an extra icon beside the “Mark all as read” button at the top of the inbox popup using headerIconUrl . You can also execute custom logic when this icon is clicked using headerIconClickHandler . This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation. 16 Oct 2024 Sample Workflow Library With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected] , and we’ll add them in the library! 21 Sep 2024 Deprecated Legacy androidpush methods As part of our ongoing efforts to maintain a robust and up-to-date platform, we’ve made the following deprecations: 1. Legacy FCM API Support Due to Google’s shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support. For more information, please refer to: Firebase Cloud Messaging Migration Guide 2. Xiaomi Push Service Following Xiaomi’s discontinuation of their push service outside mainland China, we have removed support for this feature. For more information, please visit: Xiaomi Developer Documentation We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don’t hesitate to contact our support team. 17 Sep 2024 Subscriber Page Revamp We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options. 14 Sep 2024 Typeahead autocomplete suggestions for subscribers We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id , email , and phone fields in subscriber profiles. 11 Sep 2024 Inbox - React SDK v3.4.0 This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers. New Features: Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked. This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences. 8 Sep 2024 Slack Text editor We are happy to announce the support of text editor in slack. So, now you won’t have to write complicated JSONNET template for simple text messages. The text editor supports emoji and use handlebars as the templating language. 6 Sep 2024 Web SDK v2.0 We are excited to announce a major update to our @suprsend/web-sdk . This new version brings significant improvements in security, performance, and developer experience. Major Changes Enhanced Authentication System Replaced workspace key-secret method with public API Key and Signed User JWT token Improved security and access control Synchronous Method Calls All methods now return API call status synchronously Enables better error handling and flow control in applications Improved Code Consistency and Developer Experience Renamed library methods and parameters from snake_case to camelCase Added proper IDE suggestions and method descriptions for easier development Breaking Changes Due to the significant improvements, this version introduces breaking changes. Users upgrading from v1.x should review the migration guide carefully. Documentation For a comprehensive list of changes and migration instructions, please refer to our detailed migration guide For users who need to reference the previous version, v1 documentation is still accessible here Feedback We value your feedback and encourage you to try out the new version. If you encounter any issues or have suggestions for improvement, please don’t hesitate to reach out to our support team. Thank you for your continued support and trust in SuprSend! 4 Sep 2024 View and fetch list users We’ve added a List Users tab to the lists page, giving you direct access to view all users in a list. Being API first, the same functionality is also exposed to API. Refer this GET list users API , or checkout: postman collection . API Details: The API returns 20 users per response. You can retrieve additional users by using cursor-based pagination (before and after cursors). 3 Sep 2024 Better delivery tracking in iOS We are excited to announce significant improvements in our latest update, focusing on enhancing delivery tracking for iOS Push notifications. Regardless of the application’s state, you will now experience more reliable and precise delivery tracking. We have rolled out updates for all our major SDKs. To take full advantage of these improvements, please ensure that you update your dependencies promptly. iOS SDK - v1.0.3 React Native SDK - v2.4.0 Flutter SDK - v2.2.0 2 Sep 2024 Web SDK v1.5.1 We have resolved an issue where the SDK would unexpectedly generate an error message whenever the event payload contained specific emojis. This fix ensures that event processing is now stable and reliable, even when such emojis are present. More details here 30 Aug 2024 Improvement in Workflow Listing page Developer testing workflows are now excluded from the Workflow List Page and search results, ensuring a cleaner and more organized workflow listing. These workflows will still be accessible through logs. Enhanced observability of Tenant APIs by displaying request logs on the logs page. This improvement provides better visibility and monitoring of API interactions. 27 Aug 2024 Wait Until - Add Condition on Event Property We’re excited to announce a powerful update to our Wait Until feature! You can now add multiple events and apply conditions on event properties within the Wait Until branch, allowing for more precise event filtering and targeting of the exact event required in your workflow. This is especially useful for scenarios where the same event triggers multiple workflows, and you want to exit or cancel a notification based on user actions. For instance, in a booking reminder workflow, if a user has multiple bookings, you can now match the booking ID of a cancellation event with the original event to ensure correct reminder gets canceled. Key Changes: Add conditions on event properties using a simple key-operator-value expression (e.g. booking_id = 123 ). Add condition on multiple event properties using AND , OR . Apply conditions across multiple events (e.g. avoid sending a notification if a user completes an action or achieves a specific milestone). Refer documentation for details on how to implement wait until node in your workflow. 26 Aug 2024 Enhanced branching capabilities We are excited to announce significant improvements to our branching capabilities . With the addition of more data types, you can now set precise conditions on various inputs within your branches, such as actor, recipient, and tenant properties. This enhancement allows you to tailor your workflows more effectively, ensuring that each journey is as personalized and efficient as possible. If you haven’t yet explored our branching feature, now is a great time to do so. It offers a robust way to construct multi-step journeys within a single workflow. Here are some example use cases where you could use branch: A/B test notification content by splitting cohorts based on user properties like region. Customize digest schedules (immediate, daily, weekly) using key in your trigger data or recipient’s preference. For support ticket requests, adjust who gets alerts, when to send them (immediately or batched), and which channels to use based on the issue’s priority. Define different next steps in an onboarding checklist depending on a user’s completion percentage. Here, you can also fetch completion% just before sending the next reminder. 23 Aug 2024 New SMS Integration: Pinnacle On customer demand, we are live with latest vendor Integration with Pinnacle for SMS. Check out vendor integration documentation for setup details. 20 Aug 2024 List Details Page Key Improvements: New List Details Page: Access all essential information (logs, broadcast runs, list users) and actions for a list (run broadcast, update user) in a single view, making list management much simpler. “Sync Now” button on query page: This will enable you to manually sync list users when required. Coming Soon: List Users Tab and API: We’ll soon be adding a tab to see all list users. The same functionality will also be exposed to hub APIs to | 2026-01-13T08:49:02 |
https://dev.to/t/iot/page/2 | Iot Page 2 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # iot Follow Hide Security challenges and solutions for Internet of Things and embedded devices. Create Post Older #iot posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu DEV Track Spotlight: Control Humanoid Robots and Drones with Voice and Agentic AI (DEV313) Gunnar Grosch Gunnar Grosch Gunnar Grosch Follow for AWS Dec 26 '25 DEV Track Spotlight: Control Humanoid Robots and Drones with Voice and Agentic AI (DEV313) # aws # ai # iot # robotics 1 reaction Comments Add Comment 7 min read What Is IoT Edge Analytics and Why It Matters for Industrial Real-Time Decisions Rushikesh Langale Rushikesh Langale Rushikesh Langale Follow Dec 26 '25 What Is IoT Edge Analytics and Why It Matters for Industrial Real-Time Decisions # analytics # architecture # iot # performance Comments Add Comment 2 min read Web Bluetooth Guide: How to Build a Real-Time Heart Rate Dashboard wellallyTech wellallyTech wellallyTech Follow Dec 25 '25 Web Bluetooth Guide: How to Build a Real-Time Heart Rate Dashboard # react # javascript # iot # webbluetooth Comments Add Comment 2 min read Securing IoT: Best Practices for Developers in a Smart-Device World 🔐🌍 Willie Harris Willie Harris Willie Harris Follow Dec 25 '25 Securing IoT: Best Practices for Developers in a Smart-Device World 🔐🌍 # iot # security # cybersecurity # devops 6 reactions Comments Add Comment 4 min read LoRa PHY Parameters Explained: How SF, BW, CR, and LDRO Affect Range and Power manthink manthink manthink Follow Dec 24 '25 LoRa PHY Parameters Explained: How SF, BW, CR, and LDRO Affect Range and Power # iot # networking # performance Comments Add Comment 2 min read From Steam Machines to Home Robots: Where Consumer Tech Is Actually Heading Deep Press Analysis Deep Press Analysis Deep Press Analysis Follow Dec 23 '25 From Steam Machines to Home Robots: Where Consumer Tech Is Actually Heading # opensource # iot # softwareengineering Comments Add Comment 2 min read LoRaWAN-Based CJ/T 188 M-Bus Heat Meter Data Acquisition: An Engineering Practice with KC22 and Edge-Bus manthink manthink manthink Follow Dec 24 '25 LoRaWAN-Based CJ/T 188 M-Bus Heat Meter Data Acquisition: An Engineering Practice with KC22 and Edge-Bus # architecture # iot # networking Comments Add Comment 3 min read Understanding LoRa PHY Parameters: How SF, BW, CR, and LDRO Shape Range and Power Consumption manthink manthink manthink Follow Dec 24 '25 Understanding LoRa PHY Parameters: How SF, BW, CR, and LDRO Shape Range and Power Consumption # iot # networking # performance Comments Add Comment 2 min read From Serial Ports to WebSockets: Debugging Across Two Worlds Diogo Diogo Diogo Follow Dec 23 '25 From Serial Ports to WebSockets: Debugging Across Two Worlds # tooling # iot # c # networking 5 reactions Comments 1 comment 2 min read Why Android Is Emerging as the Preferred Operating System for HMI and IoT Devices Kevin zhang Kevin zhang Kevin zhang Follow Dec 22 '25 Why Android Is Emerging as the Preferred Operating System for HMI and IoT Devices # android # iot # hmi Comments Add Comment 4 min read Securing High-Risk Zones: An Integrated RFID and Autonomous Drone Surveillance System Ashreya Bhutani Ashreya Bhutani Ashreya Bhutani Follow Dec 22 '25 Securing High-Risk Zones: An Integrated RFID and Autonomous Drone Surveillance System # systemdesign # robotics # iot # security Comments Add Comment 4 min read Cars Don’t Fail Suddenly-Software Taught Me That VechtronAI VechtronAI VechtronAI Follow Dec 22 '25 Cars Don’t Fail Suddenly-Software Taught Me That # ai # systemdesign # iot # automotive 3 reactions Comments Add Comment 3 min read Securing IoT Devices Without Agents Using Network-Based Machine Learning Asma Eman Asma Eman Asma Eman Follow Dec 27 '25 Securing IoT Devices Without Agents Using Network-Based Machine Learning # iot # security # webdev # ai Comments Add Comment 11 min read Radxa ROCK 5 vs Raspberry Pi 5 vs Kiwi Pi 5: A Detailed Comparison of Modern Single-Board Computers Leonard Liao Leonard Liao Leonard Liao Follow Dec 22 '25 Radxa ROCK 5 vs Raspberry Pi 5 vs Kiwi Pi 5: A Detailed Comparison of Modern Single-Board Computers # robotics # iot # performance # linux 2 reactions Comments Add Comment 2 min read Solar PCBs for Engineers: A Practical Guide to Designing and Building Boards That Survive the Outdoors Fen Liu Fen Liu Fen Liu Follow Dec 19 '25 Solar PCBs for Engineers: A Practical Guide to Designing and Building Boards That Survive the Outdoors # design # iot # tutorial 1 reaction Comments 1 comment 3 min read Hey There! DOM On the Way! Karthigeyan G Karthigeyan G Karthigeyan G Follow Dec 20 '25 Hey There! DOM On the Way! # robotics # 3dprinting # iot # raspberrypi Comments Add Comment 1 min read 🔧 AWS IoT Jobs: Automating Secure Device Management at Scale Jaswant Karun Jaswant Karun Jaswant Karun Follow Dec 18 '25 🔧 AWS IoT Jobs: Automating Secure Device Management at Scale # aws # iot # devops # automation 3 reactions Comments Add Comment 2 min read Pen Testing IoT Devices Aviral Srivastava Aviral Srivastava Aviral Srivastava Follow Dec 18 '25 Pen Testing IoT Devices # cybersecurity # testing # iot # security Comments Add Comment 8 min read Building a Smart Refrigerator with a $15 IoT Camera and SAM 3: Solving the "Warm Water" Problem ARmedia ARmedia ARmedia Follow Dec 18 '25 Building a Smart Refrigerator with a $15 IoT Camera and SAM 3: Solving the "Warm Water" Problem # showdev # iot # ai # machinelearning Comments 1 comment 4 min read Build a Smart Traffic Management System Using IoT David Thomas David Thomas David Thomas Follow Dec 17 '25 Build a Smart Traffic Management System Using IoT # iot # arduino # diy # smarttraffic Comments Add Comment 2 min read MQTT vs HTTP: Choosing the Right Protocol for Industrial IoT and Smart Factories mike brown mike brown mike brown Follow Dec 22 '25 MQTT vs HTTP: Choosing the Right Protocol for Industrial IoT and Smart Factories # mqtt # http # iot # smartfactories Comments Add Comment 3 min read What Benefits Can Industrial IoT Bring to Factories? Ricardo Ricardo Ricardo Follow Dec 16 '25 What Benefits Can Industrial IoT Bring to Factories? # automation # iot # networking # productivity Comments Add Comment 2 min read I Made a Reference Guide for AMB25 Because Realtek Forgot To 🤷♂️ Nityam Sheth Nityam Sheth Nityam Sheth Follow Dec 25 '25 I Made a Reference Guide for AMB25 Because Realtek Forgot To 🤷♂️ # iot # arduino # cpp # realtek 6 reactions Comments Add Comment 4 min read Building a Modular Starter Kit for M5StickC-Plus2: From Messy Code to Clean Architecture ChristopherDebray ChristopherDebray ChristopherDebray Follow Dec 14 '25 Building a Modular Starter Kit for M5StickC-Plus2: From Messy Code to Clean Architecture # arduino # iot # developer # cpp Comments Add Comment 6 min read Advent of Embedded Linux — Day 5 Kanak Shilledar Kanak Shilledar Kanak Shilledar Follow Dec 15 '25 Advent of Embedded Linux — Day 5 # iot # linux # adventofcode # adventofembeddedlinux Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/ishaan_agrawal | Ishaan Agrawal - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Ishaan Agrawal Security Researcher & Developer Joined Joined on Jun 26, 2025 Personal website https://vscan.dev More info about @ishaan_agrawal Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 4 posts published Comment 0 comments written Tag 3 tags followed Concerning Amounts of Malware in the VS Code Marketplace: What Microsoft’s Own Logs Reveal Ishaan Agrawal Ishaan Agrawal Ishaan Agrawal Follow Jan 9 Concerning Amounts of Malware in the VS Code Marketplace: What Microsoft’s Own Logs Reveal # security # productivity # programming # backend 12 reactions Comments Add Comment 3 min read 🚨BREAKING: A Self-Propagating Worm Is Hitting VSCode Extensions Right Now— Here’s How to Protect Yourself Ishaan Agrawal Ishaan Agrawal Ishaan Agrawal Follow Oct 20 '25 🚨BREAKING: A Self-Propagating Worm Is Hitting VSCode Extensions Right Now— Here’s How to Protect Yourself # vscode # security # software # programming 35 reactions Comments Add Comment 2 min read Are Your VSCode Extensions Safe? The Risk We Don’t Talk About Ishaan Agrawal Ishaan Agrawal Ishaan Agrawal Follow Sep 15 '25 Are Your VSCode Extensions Safe? The Risk We Don’t Talk About # vscode # security # productivity # cybersecurity 35 reactions Comments Add Comment 2 min read VSCode Extensions are Malicious—Here's What I Found After Scanning 1,000 of Them Ishaan Agrawal Ishaan Agrawal Ishaan Agrawal Follow Jun 26 '25 VSCode Extensions are Malicious—Here's What I Found After Scanning 1,000 of Them # security # vscode # programming # ai 36 reactions Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/codebunny20/looking-for-help-if-possible-im-stuck-on-my-trackmyhrt-app-medication-symptom-tracker-38fa#main-content | 🌈 Looking for help if possible: I’m Stuck on My TrackMyHRT App (Medication + Symptom Tracker) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse codebunny20 Posted on Jan 12 🌈 Looking for help if possible: I’m Stuck on My TrackMyHRT App (Medication + Symptom Tracker) # discuss # python # programming # opensource Hey devs — I’m working on a small, offline, privacy‑first desktop app called TrackMyHRT, and I’ve hit a point where I could really use some outside perspective. TrackMyHRT is part of a larger vision, but right now I’m focusing on this one tool: a simple, calm interface for logging HRT doses, symptoms, mood, energy, libido, and notes, with local‑only storage and export options. It’s meant to help people understand their patterns and advocate for themselves without giving their data to a cloud service. The core features work, but I’m stuck on the next steps. 🔧 Where I’m stuck (TrackMyHRT‑specific) Data model decisions I’m unsure whether to: keep the current JSON structure as‑is refactor into something more future‑proof or split entries into smaller components (meds, symptoms, metadata) I don’t want to over‑engineer, but I also don’t want to put myself into a corner. UI flow + structure The current UI works, but I’m struggling with: how to make the entry form feel smoother and less “form‑heavy” whether the viewer should stay simple or become more detailed how to keep everything accessible without clutter I want it to feel calm and low‑pressure, not like filling out a medical form. Export formats + long‑term planning Right now I support .jsonl, .json, .txt, and .md.I’m unsure whether: this is too many I should standardize around one or I should add a more structured export for future integrations Migration logic I have a small migration step for older JSONL → JSON storage.I’m not sure if I should: keep supporting legacy formats or simplify and drop old versions entirely 💬 What I’m looking for Advice on structuring small but extensible data models Thoughts on designing a calm, accessible UI for daily logging Opinions on export formats and long‑term maintainability Examples of similar trackers or patterns I could learn from General “here’s how I’d approach this” insight below is the github repo for the HRT Journey Tracker Suite where the TrackMyHRT tool is located TrackMyHRT👈 I’m not looking for someone to rewrite the app — just some guidance from people who’ve built trackers, logging tools, or small desktop apps before. TrackMyHRT is meant to support people navigating hormone therapy in a private, offline, non‑judgmental way. No accounts, no cloud sync, no analytics — just a simple tool that helps people understand their own journey. I want to build this thoughtfully, but right now I’m too stuck in my head to see the next steps. If you have experience with python, PySide6, data modeling, UX for logging tools, or just strong opinions about app structure, I’d love to hear from you. Thanks for reading — and thanks in advance for any guidance. Top comments (2) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand EmberNoGlow EmberNoGlow EmberNoGlow Follow Just a dude, a mid-level on Godot / Python developer and Rust beginner Joined Nov 18, 2025 • Jan 12 Dropdown menu Copy link Hide Code refactoring is an underrated and essential part of the workflow . Never be afraid to change something in your code, even if it breaks. Even if you add something that doesn't work, you've still created something new, not just tried to tweak incomprehensible code. This is already a great achievement. It's better to have buggy, yet beautifully written, functionality than to have well-functioning, but poorly written, code that's difficult to extend. Clean code is easier to extend and fix. The data export format isn't the most important thing, in my opinion, whether it's written in JSON , YAML , or TXT . The most important thing is, again, ease of access to the data and good readability for checking for bugs and bottlenecks. It's better to use one format, but one that's well-supported. Looking for compatibility with previous versions (if the current version has changed significantly) can backfire in the future, as you'll still have to migrate to new structures, as supporting the old format limits your functionality. Clearly define your goals. Create a roadmap and development documents. Defining goals on the fly - "What if I add this small feature?" - is a bad idea, as the project can turn into a sandbox with a multitude of ideas that may be completely unrelated. Don't be afraid to use AI! In my experience, while developing my project , I used AI for everything from refactoring to adding features, and even my training ( you can read my post about this ). My project was constantly changing and breaking, then fixing, or even completely changing the architecture. Don't be afraid to experiment and refactor, as it's part of the process. Good luck! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand codebunny20 codebunny20 codebunny20 Follow I'm a trans woman and after I started my transition I started learning python and other code languages and fell down the rabbit hole and now I'm hooked. Email xavierfields89@gmail.com Education high school Pronouns She/Her Work hopefully freelance some day Joined Jan 2, 2026 • Jan 12 Dropdown menu Copy link Hide Thank you so much Like comment: Like comment: 2 likes Like Comment button Reply Some comments may only be visible to logged-in visitors. Sign in to view all comments. Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse codebunny20 Follow I'm a trans woman and after I started my transition I started learning python and other code languages and fell down the rabbit hole and now I'm hooked. Education high school Pronouns She/Her Work hopefully freelance some day Joined Jan 2, 2026 More from codebunny20 Building Voice Trainer: a tiny, local‑first pitch analysis tool for gender‑affirming voice practice # opensource # privacy # showdev # tooling 🌈 HRT Journey Tracker Suite # webdev # programming # python # opensource Looking for Collaborators & Feedback: Building a Free, Accessible HRT Journey Tracker for the Trans Community # programming # beginners # python # learning 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://tatanotes.com/blog | TataNotes – Web Accessibility Personal Blog Blog – TataNotes – Web Accessibility Personal Blog Skip to main content TataNotes… …all about a11y Blog About me Blog Publication date January 12, 2026 AI in Assistive Technologies for People with Visual Impairments Publication date January 11, 2026 Glaucoma Awareness Month Publication date January 5, 2026 BIK Rejects Overlays for EN/WCAG Compliance Publication date May 12, 2025 Accessibility Testing on Windows on Mac Publication date December 3, 2024 International Day of Persons with Disabilities Tatyana Bayramova © 2024–present Important: All rights reserved | 2026-01-13T08:49:02 |
https://www.python.org/community/awards/psf-distinguished-awards/ | PSF Distinguished Service Awards | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF Distinguished Service Awards Contents Introduction 2024 2022 2021 2018 2017 2015 2014 2012 Introduction Building on the ideals of the Foundation's Community Service Award , the Distinguished Service Award is an offer of recognition for sustained exemplary contributions to the Python community. The Foundation's highest award is given for actions which carry significant impact that shapes the Python world, whether through contributions of code, efforts in community action, or otherwise. As with the Community Service Award, the intention is to demonstrate that such service to the community does lead to recognition and reward, rather than to provide a direct incentive to contributors. Awards will be made periodically as deserving candidates are identified. Any PSF member is entitled to propose an award at any time, stating the reasons for which the award is merited. Proposals should be made confidentially to the Board by sending email to psf@python.org . The minutes of award considerations will not name the individuals concerned unless an award is made. The Board will contact proposers to keep them informed of the status of their proposals (such as when the proposal will receive Board consideration). Recognition will take the form of an award certificate plus a cash award of $5000 USD. 2024 Ewa Jodlowska Ewa Jodlowska, former PSF Executive Director and Board Member, has been recognized with the PSF’s Distinguished Service Award. For over a decade, Ewa played a pivotal role in transforming the PSF from a volunteer-driven group into a thriving, professional organization. Thanks to her hard work and vision, the PSF now has paid staff, solid funding, and the ability to support the global Python community like never before. Today, the PSF can hire developers, manage a vital grants program, and oversee the infrastructure that keeps Python (and its vast library ecosystem) freely accessible to everyone worldwide. Ewa’s leadership has left an incredible mark on the PSF’s history, and her work has set us up for a future that once felt unimaginable. Van Lindberg Van Lindberg, a longtime member of the PSF Board, has been recognized with the PSF’s Distinguished Service Award. Van was the co-chair and then Chair of PyCon from 2008-2012, served on the PSF Board for over a decade (2012–2023), including four years as Chair (2012–2016) and seven years as PSF General Counsel from 2016-2023. Throughout his time with us, Van was our go-to expert for all things legal, bringing invaluable insights from the broader open-source world to help the PSF grow and stay ahead of the curve. During his time on the board, Van was instrumental in establishing the PSF as a professional organization able to support the worldwide Python community. From licensing and hiring to fundraising, Van was there every step of the way as the PSF experienced phenomenal growth. His deep understanding of open-source communities—paired with his legal expertise—helped the Foundation navigate challenges and embrace opportunities to better serve the global Python community. 2022 Naomi Ceder The 2022 Distinguished Service Award was presented to Naomi Ceder at PyCon US in Salt Lake City. Over the years Naomi has taken on many leadership roles to make PyCon US successful and welcoming. She served as Chair of the Hatchery Program and she helped found PyCon Charlas, our Spanish language track. At different points in time, she’s also been the Co-chair of Sprints, an Organizer of the PyCon Education Summit and Chair for poster sessions at PyCon US. She also co-founded Trans*Code, an on-going series of hackdays (mostly) in the UK, which aims to build community and foster tech education and skills for transgender and non-binary folks. PyCon US and the global Python community would not look like it does without her tireless, largely behind the scenes work. Her deep thoughtfulness coupled with her energy is an immeasurable gift to the Python community. 2021 Jesse Noller The 2021 Distinguished Service Award was presented to Jesse Noller for his significant contributions to Python as a core developer, PyCon US Chair, and PSF board member. 2018 Marc-André Lemburg 2018 Distinguished Service Award was presented to Marc-André Lemburg for his significant contributions to Python as a core developer, EuroPython chair, PSF board member, and board member of the EuroPython Society. 2017 Tim Peters The 2017 Distinguished Service Award was presented to Tim Peters. Tim's technical contributions to Python are immense as he implemented several modules into the standard library. Some examples include timsort , doctest , and the timeit module. Furthermore, Tim contributed to the Python Cookbook by writing the chapter on algorithms . Tim also has contributed to the Python community. He wrote the Zen of Python via PEP20 in 2015. He reached approximately one million people via his answers on Stack Over Flow. Moreover, Tim was an active PSF Board Director from 2001 to 2014 meaning that he volunteered on the board for 13 years! Additionally, Tim has contributed to many Python mailing lists and has been known to always contribute in a friendly, funny, and helpful way. The Python Software Foundation thanks Tim Peters for his contributions to the CPython project and the greater Python community. 2015 Mark Hammond The 2015 Distinguished Service Award was presented to Mark Hammond. Mark's contributions to the Python community, particularly around the Windows platform, have been so influential to the livelihood of Python on Windows that he received a special thanks in the installer throughout several releases. His contributions have been seen in a number of areas around CPython and in the standard library, from Windows specific behaviors in the libraries, to the PEP 397 launcher for Windows. Mark's creation and maintenance of the pywin32 package has enabled scores of developers on Windows to leverage the power of Python while integrating with lower-level Win32 APIs, as well as integrate with other Microsoft applications such as the Office suite of tools via COM. The Python Software Foundation thanks Mark Hammond for his contributions to the CPython project and the greater Python community, especially those on the Windows platform. 2014 Raymond Hettinger The 2014 Distinguished Service Award was presented to Raymond Hettinger at PyCon 2014 in Montréal. Raymond has been a prolific contributor to the CPython project for over a decade, having implemented and maintained many of Python's great features. He has been instrumental in modules like bisect, collections, decimal, functools, itertools, math, random, with types like namedtuple, sets, dictionaries, and many other places around the codebase. He has contributed to the modification of nearly 90,000 lines of code in the CPython repository, and has made over 160 changes in the PEP repository. Raymond has also served as a director of the Python Software Foundation, and has mentored many people over the years on their contributions to the python-dev community. He's also well known for his contributions to the Python Cookbook, and shares many pieces of Python wisdom on Twitter. The Python Software Foundation thanks Raymond Hettinger for his contributions to the CPython project and the greater Python community. 2012 John Hunter The 2012 Distinguished Service Award was given posthumously to John Hunter, creator of matplotlib . John began the matplotlib project in 2002 while studying epilepsy seizure data in a postdoctoral program at the University of Chicago. Unhappy with the state of proprietary solutions needed for his studies, John chose Python to build an open solution to his problem. "Matplotlib is both an amazing technical achievement and a shining example of open source community building, as John not only created its backbone but also fostered the development of a very strong development team, ensuring that the talent of many others could also contribute to this project," said Fernando Perez. The Python Software Foundation thanks John Hunter for his invaluable contributions to not just the Python community but to the numeric and scientific communities he impacted throughout his time. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://tatanotes.com/about | TataNotes – Web Accessibility Personal Blog About me – TataNotes – Web Accessibility Personal Blog Skip to main content TataNotes… …all about a11y Blog About me About me My name is Tatyana Bayramova, but I go by Tata. I'm a Senior Software Engineer with a strong focus on accessibility. I help to address accessibility barriers on each stage of the development cycle. I hold 1-on-1 and team meetings, give presentations, and raise awareness of accessibility issues. I work closely with UX designers to identify accessibility issues early on. During implementation phase, I perform code reviews and provide recommendations on how to write WCAG-compliant code. For quality assurance, I manually test sample pages for accessibility issues, and support the process with automated tools. I help teams to make sure that the end product is perceivable, operable, understandable, and robust. I am a member of IAAP – International Association of Accessibility Professionals – since December 2024. I am also a Certified Professional in Accessibility Core Competencies since March 2025. I hold a bachelor's and master's degrees in Applied Mathematics and Computer Science, both cum laude. Contact me You can reach out to me via email ( [email protected] ) or LinkedIn Opens a new page . View on Credly Opens a new page View on Credly Opens a new page Tatyana Bayramova © 2024–present Important: All rights reserved | 2026-01-13T08:49:02 |
https://dev.to/missamarakay/help-me-help-you-debugging-tips-before-seeking-help-12jj#submit-an-issue-or-even-a-pr | Help Me, Help You (Debugging Tips Before Seeking Help) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Apr 23, 2019 Help Me, Help You (Debugging Tips Before Seeking Help) # programming # productivity # beginners One of the really cool things about being a developer advocate is I get to help people, which I truly love. I love writing a snippet of code or clarifying documentation and then watching the magic that happens when a developer I've probably never met before takes it and creates something amazing with it. That's a great day in my book. But it is not always like that. Sometimes things break, and folks reach out for help. It can be frustrating for everyone involved when it appears to be "just one error" (it may not be actually!). Let me help you help me as we work through these things together. Be very clear about your problem or issue Overstate and overshare. If you can provide relevant screen shots or a link to the code, that's even better. Was this ever working? Or did you just get started? What version of the SDK or service are you using? Your OS version might also be relevant. What steps did you do to get to this point? Link to the exact tutorial or documentation. Do your homework first What steps did you take to try to debug this on your own? The answer cannot be "nothing". Did you do a search on the error? Stack Overflow? Relevant forums? A search engine? Has this happened before? Can you try an older version? Can you try a newer version? Can you reproduce it? Clouds are complicated When working in the cloud, you can have a lot more variables at play. I recommend firing off a simple GET to make sure something like your credentials are working and the service is responding. There is a reason many API docs include Curl, but maybe read my other post . Can you use Curl/Postman/ARC to test the endpoint? What region are you in? What tier of the service are you using? You may have hit a tier limit. Check for outages & maintenance. If you are on IBM Cloud, there is a widget on the dashboard (you may need to be logged in). Submit an issue (or even a PR) If you think you are experiencing a bug with an open source project, submit an issue. Often projects will have a template to follow, which look very similar to the items I outlined above! Coincidence, I think not. Be patient I cannot drop everything I'm doing to work on troubleshooting, but I try to put some time in my schedule during the week to take a look at things. This is often what you hear from OSS maintainers and can lead to burnout. I don't work weekends or evenings (unless I have very specific events) so I appreciate your patience. Following the above items will help us both tackle these challenges together. Feel free to apply these things anywhere in life or work. We are all busy, but if we meet each other halfway, everyone benefits. Do you have any tips I missed? Share them below! Top comments (3) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Theofanis Despoudis Theofanis Despoudis Theofanis Despoudis Follow Senior Software Engineer @wpengine, Experienced mentor @codeimentor, Technical Writer @fixate.io, Book author Location Ireland Work Senior Software Engineer at WP Engine Joined Jun 19, 2017 • Apr 24 '19 Dropdown menu Copy link Hide You forgot the meme Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand DrBearhands DrBearhands DrBearhands Follow Education MSc. Artificial Intelligence Joined Apr 9, 2018 • Apr 24 '19 Dropdown menu Copy link Hide Ahhh, those lovely "it's not working" bugreports. So easy to close by just opening the app and seeing that it is apparently working again. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Apr 24 '19 Dropdown menu Copy link Hide Love to hate those ones. It's... fixed...? Like comment: Like comment: 3 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Intro to Calling Third Party AI Services in Unreal Engine # programming # gamedev # unreal Updating Your Unity Project to Watson SDK for Unity 3.1.0 (and Core SDK 0.2.0) # unity3d # programming # gamedev A Few of My Favorite (Dev) Things # github # programming # softwaredevelopment 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/t/s3 | S3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # s3 Follow Hide Create Post Older #s3 posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Hosting a Static Website on Amazon S3 (Step-by-Step) irfan pasha irfan pasha irfan pasha Follow Jan 12 Hosting a Static Website on Amazon S3 (Step-by-Step) # aws # s3 # bigneer # website Comments Add Comment 2 min read Hosting a React App on AWS S3 in 5 minutes. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 10 Hosting a React App on AWS S3 in 5 minutes. # aws # react # s3 # webdev Comments Add Comment 1 min read Save on DuckDB + S3 Transfer Costs Tatsuya Nishimura Tatsuya Nishimura Tatsuya Nishimura Follow Jan 12 Save on DuckDB + S3 Transfer Costs # duckdb # s3 # parquet Comments Add Comment 4 min read 🪣 AWS 123: Data in Motion - Migrating S3 Buckets via AWS CLI Hritik Raj Hritik Raj Hritik Raj Follow Jan 3 🪣 AWS 123: Data in Motion - Migrating S3 Buckets via AWS CLI # aws # s3 # devops # 100daysofcloud Comments Add Comment 3 min read A Guide to AWS CloudFront Invalidations nithish rodrigo nithish rodrigo nithish rodrigo Follow Jan 3 A Guide to AWS CloudFront Invalidations # aws # cloudfront # invalidation # s3 2 reactions Comments Add Comment 2 min read Goodbye Localhost: Why I deployed my site on raw S3 instead of Netlify Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 27 '25 Goodbye Localhost: Why I deployed my site on raw S3 instead of Netlify # aws # webdev # beginners # s3 Comments Add Comment 2 min read Terraform aws_s3_object Data Source: Why Your `body` Might Be Null Anand Rathnas Anand Rathnas Anand Rathnas Follow Dec 26 '25 Terraform aws_s3_object Data Source: Why Your `body` Might Be Null # terraform # aws # s3 # infrastructureascode Comments Add Comment 3 min read AWS Service – Amazon S3 Glacier Gangeswara Gangeswara Gangeswara Follow Dec 18 '25 AWS Service – Amazon S3 Glacier # aws # awschallenge # s3 # webdev 1 reaction Comments Add Comment 1 min read Automated Reporting System ADEEL ABBAS ADEEL ABBAS ADEEL ABBAS Follow Dec 31 '25 Automated Reporting System # aws # lambda # s3 # awscommunitybuilder 6 reactions Comments 1 comment 3 min read Deploying Minio using Docker Compose Adnan Babakan (he/him) Adnan Babakan (he/him) Adnan Babakan (he/him) Follow Dec 29 '25 Deploying Minio using Docker Compose # docker # webdev # s3 Comments Add Comment 2 min read Why Your EC2 is Taking the Long Way to S3 Robindeva Robindeva Robindeva Follow Jan 4 Why Your EC2 is Taking the Long Way to S3 # aws # s3 # vpc Comments Add Comment 3 min read Saving Terraform State in S3 Sibelius Seraphini Sibelius Seraphini Sibelius Seraphini Follow for Woovi Dec 4 '25 Saving Terraform State in S3 # terraform # devops # s3 1 reaction Comments Add Comment 1 min read S3 Vectors: 90% Cheaper Than Pinecone? Our Migration Guide Dinesh Kumar Elumalai Dinesh Kumar Elumalai Dinesh Kumar Elumalai Follow Dec 31 '25 S3 Vectors: 90% Cheaper Than Pinecone? Our Migration Guide # aws # vectordatabase # migration # s3 1 reaction Comments Add Comment 7 min read Why Amazon S3 Makes More Technical Sense Today (Especially After MinIO’s Shift) Ishara Niwarthana Ishara Niwarthana Ishara Niwarthana Follow Dec 10 '25 Why Amazon S3 Makes More Technical Sense Today (Especially After MinIO’s Shift) # discuss # aws # s3 # devops 1 reaction Comments Add Comment 3 min read Day 3: Creating AWS S3 Bucket using Terraform Anil KUMAR Anil KUMAR Anil KUMAR Follow Nov 26 '25 Day 3: Creating AWS S3 Bucket using Terraform # terraform # aws # s3 # hcl Comments Add Comment 3 min read Gen AI Is Only as Reliable as Your Data: Lessons from AWS re:Invent 2025 Faye Ellis Faye Ellis Faye Ellis Follow for AWS Community Builders Dec 16 '25 Gen AI Is Only as Reliable as Your Data: Lessons from AWS re:Invent 2025 # aws # iceberg # s3 # resilience 3 reactions Comments Add Comment 5 min read Host Your Portfolio on Amazon S3: A Beginner's Guide to Static Website Hosting Khaja Sabik Ahmed Khaja Sabik Ahmed Khaja Sabik Ahmed Follow Nov 18 '25 Host Your Portfolio on Amazon S3: A Beginner's Guide to Static Website Hosting # awscommunity # s3 # portfolio # cloudcomputing Comments Add Comment 5 min read Finally! Amazon RDS Tells You What's Actually Happening During Snapshot Exports Robindeva Robindeva Robindeva Follow Dec 23 '25 Finally! Amazon RDS Tells You What's Actually Happening During Snapshot Exports # aws # rds # snapshots # s3 Comments Add Comment 3 min read How We Built an AI‑Native Object Store (Tensor Streaming, Erasure Coding, QUIC, Rust) Courtney Robinson Courtney Robinson Courtney Robinson Follow Nov 19 '25 How We Built an AI‑Native Object Store (Tensor Streaming, Erasure Coding, QUIC, Rust) # ai # rust # mlops # s3 1 reaction Comments Add Comment 4 min read Creating a S3 bucket using Terraform Sibelius Seraphini Sibelius Seraphini Sibelius Seraphini Follow for Woovi Dec 3 '25 Creating a S3 bucket using Terraform # terraform # s3 # objectstorage # devops 2 reactions Comments Add Comment 2 min read Cloudflare R2 in .NET Without the AWS SDK Headaches Alexis Alexis Alexis Follow Dec 20 '25 Cloudflare R2 in .NET Without the AWS SDK Headaches # cloud # dotnet # tooling # s3 1 reaction Comments Add Comment 6 min read How to Set Up an S3 Trigger for Lambda — and Kick Off a Step Functions Workflow Dhaval Mojidra Dhaval Mojidra Dhaval Mojidra Follow Nov 8 '25 How to Set Up an S3 Trigger for Lambda — and Kick Off a Step Functions Workflow # aws # ai # s3 # awsindia Comments Add Comment 1 min read Leaky Bucket: Full Attack Chain Against Public S3-Compatible Buckets in Yandex Cloud KL3FT3Z KL3FT3Z KL3FT3Z Follow Dec 10 '25 Leaky Bucket: Full Attack Chain Against Public S3-Compatible Buckets in Yandex Cloud # webdev # s3 # aws # cybersecurity 13 reactions Comments Add Comment 4 min read Test S3 ABAC locally with iam-lens David Kerber David Kerber David Kerber Follow Dec 10 '25 Test S3 ABAC locally with iam-lens # security # aws # iam # s3 1 reaction Comments Add Comment 5 min read AWS CDK 100 Drill Exercises #001: S3 Bucket Fundamentals —— From Default Settings to Practical Customization TOMOAKI ishihara TOMOAKI ishihara TOMOAKI ishihara Follow for AWS Community Builders Dec 7 '25 AWS CDK 100 Drill Exercises #001: S3 Bucket Fundamentals —— From Default Settings to Practical Customization # aws # cdk # 100drillexercises # s3 3 reactions Comments Add Comment 8 min read loading... trending guides/resources Deploying Minio using Docker Compose How I Built a Secure File Upload API Using FastAPI and AWS S3 Presigned URLs Leaky Bucket: Full Attack Chain Against Public S3-Compatible Buckets in Yandex Cloud I Built my First static website using Amazon S3 and infinityfree. Host Your Portfolio on Amazon S3: A Beginner's Guide to Static Website Hosting The Most Popular AWS Services You Probably Should Use: Key Picks & Why They Matter Amazon S3 Vectors: The Cost-Friendly Way to Store and Search AI Embeddings Cloudflare R2 in .NET Without the AWS SDK Headaches Gen AI Is Only as Reliable as Your Data: Lessons from AWS re:Invent 2025 Building a Serverless Student Management System Using AWS (Lambda, API Gateway, DynamoDB, S3 & Cl... S3 Vectors: 90% Cheaper Than Pinecone? Our Migration Guide A Guide to AWS CloudFront Invalidations Finally! Amazon RDS Tells You What's Actually Happening During Snapshot Exports Goodbye Localhost: Why I deployed my site on raw S3 instead of Netlify 🪣 AWS 123: Data in Motion - Migrating S3 Buckets via AWS CLI Terraform aws_s3_object Data Source: Why Your `body` Might Be Null Why Your EC2 is Taking the Long Way to S3 AWS - Secure, High‑Throughput Ingestion Pipeline for Large Binary Objects Test S3 ABAC locally with iam-lens How We Built an AI‑Native Object Store (Tensor Streaming, Erasure Coding, QUIC, Rust) 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/help/writing-editing-scheduling#Guidelines-for-AI-assisted-Articles-on-DEV | Writing, Editing and Scheduling - DEV Help - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close DEV Help The latest help documentation, tips and tricks from the DEV Community. Help > Writing, Editing and Scheduling Writing, Editing and Scheduling In this article The Editor Drafting and publishing a post: Scheduling a post: Creating a Series Cross-posting Content Helpful Resources DEV Editor guide Markdown Cheatsheet Best Practices for Writing on DEV Guidelines for Avoiding Plagiarism on DEV Guidelines for AI-assisted Articles on DEV Common Questions Q: How do I set a canonical URL on my post? Q: How do I set a cover image for my post? Q: Do I own the articles that I publish? Q: Can I cross-post something I've already written on my own blog or Medium? Q: Can I use profanity in my posts? Q: Why has my post been removed? Q: Will you put ads on my posts' pages? Explore the ins and outs of writing, editing, scheduling, and managing articles. The Editor The DEV editor is your primary tool for writing and sharing posts. With a Markdown -based syntax and flexible options for embedding content, the editor is one of the main ways DEV members express themselves. Drafting, scheduling, and publishing posts are all options; importing via RSS is also a feature that we provide. Learn how to use the DEV editor to create and format your articles effectively: Drafting and publishing a post: Click on " Write a Post " in the top right corner of the site. Follow the prompts to fill out the necessary inputs. Give your post a title, write the body content, add appropriate tags, and fill out any other optional fields. If you're not ready to share your article, just click "Save draft" in the bottom left. You can access your drafts from your user dashboard and return to editing your post whenever you wish. Once you're ready to share your post, click the "Publish" button in the bottom left. Note: if you are using the Basic Markdown editor you interface is more minimalistic, and you'll need to change published: false to published: true in the Front Matter of the post, then save to publish your post. Congratulations, your post should be published! You should see the article listed on your public profile. Note that you can access analytics for each post you've shared from your user dashboard by clicking on the ... beside the article title. Scheduling a post: To schedule a post, you may open a draft or start writing a new post. Once you've got your post set up, click on the hexagon icon in the bottom left-hand corner near the Publish button. See "Schedule Publication" and use the inputs to select a date and time for the post to go live. Note: this feature is set to your local time zone. Creating a Series DEV provides authors with the ability to link articles together in a series. A series has a title and an associated page to hold all the entries (e.g. Sloan's Inbox ). Most often this is done for articles that are thematically related or recurring weekly posts. We have a handy guide here that explains step-by-step how to create a series on DEV. Note: If you've written the first entry in a series and are wondering why the series title is not easily visible, it's because we don't actually display information about a post being part of a series until there is more than one entry in the series. Once you write your second entry in the series, the Table of Contents and title for the series should appear. Cross-posting Content DEV offers a variety of features for those who want to cross-post content from elsewhere on the web. We encourage folks to share articles from their personal and company blogs! Notably, we offer folks the ability to import content via RSS and set canonical links on any posts that are shared. Using the RSS Feed on DEV Community Configure RSS Feed: Navigate to extensions within the settings. Under "Publishing to DEV Community 👩💻👨💻 from RSS," enter your blog's RSS feed URL. You will see the option to "Mark the RSS source as canonical URL" or "Replace links with DEV Community links." Check the info below (Specifying a Canonical URL) to help you decide which option to select. Click "submit feed settings." Edit Post Drafts Before Publishing Go to your user dashboard. Click edit beside the post you want to post. Save each draft after making changes. Publish Post when ready. How to Specify a Canonical URL Members reposting content often worry about original posts becoming less discoverable in search engines and their website losing visibility as the newer publishing platform (e.g., DEV) might surpass the original blog. Fortunately, DEV allows authors to address these concerns. By inputting a canonical URL, contributors can ensure search engines understand the original source. This prevents any penalties for reposting, and search engine crawlers boost the ranking of the original article. Option 1 (RSS Import): Check the "Mark the RSS source as canonical URL by default" box upon import. Option 2 (Individual Posts): Identify your editor version in /settings/customization. Rich + Markdown Editor: Click the gear icon next to "Save draft" and enter the original post's URL in the "Canonical URL" field. Basic Markdown Editor: Add canonical_url: X to the post's front matter, specifying the original post's URL. Following these steps ensures proper attribution and maintains the visibility of your content. Helpful Resources Below you'll find various resources we recommend for better understanding DEV's writing policies and tools. DEV Editor guide A quick guide that provides you with technical tips for using the DEV Editor and our brand of Markdown. You can also find it by clicking the "?" page in the editor . Markdown Cheatsheet A handy cheatsheet for commonly-used Markdown formatting syntax. Best Practices for Writing on DEV A helpful series that offers both technical tips and general guidance for making the best-fit article for DEV. 🙌 Guidelines for Avoiding Plagiarism on DEV This resource offers guidance for how to avoid plagiarism. We take a strong stance against plagiarism on DEV; please don't hesitate to report any plagiarism to us. Guidelines for AI-assisted Articles on DEV These guidelines detail our requirements for properly labelling AI-assisted content on DEV. Please don't hesitate to report any content that is written with AI-assistance if it isn't following these guidelines. Common Questions Q: How do I set a canonical URL on my post? In the post editor, click the hexagon icon in the bottom left-hand corner beside "save draft" and you'll see an input box to designate a Canonical URL. Note: if you are using the Basic Markdown editor you must add a line for it inside the triple dashes (aka Front Matter), like so: --- title: published: false tags: canonical_url: <https://mycoolsite.com/my-post> --- Q: How do I set a cover image for my post? If using the Rich + Markdown editor, then click the "Add a cover image" button above the title of the post. If using the Basic Markdown editor, include cover_image: [url] in the front matter of your post. Note: you may change your editor type from your settings . Q: Do I own the articles that I publish? Yes, you own the rights to the content you create and post on dev.to and you have the full authority to post, edit, and remove your content as you see fit. Q: Can I cross-post something I've already written on my own blog or Medium? Absolutely, as long as you have the rights you need to do so! And if it's of high quality, we'll feature it. Q: Can I use profanity in my posts? We don't disallow profanity in general, but we do have an internal policy of not promoting posts that have profanity in the title, so you might want to keep that in mind. If your profanity is targeted at individuals or hateful, then it would cross the lines of what's acceptable via our Code of Conduct and we may take necessary action to remove you content. Q: Why has my post been removed? Your post is subject to removal at the discretion of the moderators if they believe it does not meet the requirements of our Code of Conduct . If you think we may have made a mistake, please email us at support@dev.to . Q: Will you put ads on my posts' pages? It's possible. We do allow organizations to purchase advertisements with DEV. However, if you would prefer that no ads be placed next to your posts, just navigate to Settings > Customization , scroll down to sponsors, and uncheck the box beside "Permit Nearby External Sponsors (When publishing)" Of course, we'd appreciate it if you keep those boxes checked as this is important to our business. But, we respect your decision and appreciate you sharing posts with us! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/igorganapolsky | Igor Ganapolsky - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Igor Ganapolsky Seasoned Android engineer and AI specialist with 15+ years of software development experience and a deep focus on native Android. Proven track record modernizing high-traffic apps using Kotlin. Location Florida, USA Joined Joined on Mar 19, 2018 github website twitter website Education Manhattan College Pronouns he Work Senior AI Engineer Seven Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least seven years. Got it Close Six Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least six years. Got it Close Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close More info about @igorganapolsky Skills/Languages Kotlin, Java, Android, Python, JavaScript, TypeScript, React, AWS, Terraform, Docker, Claude Code, OpenAI, Google Gemini Currently learning Claude Code, AWS, Python, React, Kotlin Currently hacking on Claude Code affiliate content generation Available for Anything Post 1044 posts published Comment 15 comments written Tag 1 tag followed Pin Pinned How I Built a 500% Productivity System Using Claude Code and 5 Game-Changing Developer Tools Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jul 30 '25 How I Built a 500% Productivity System Using Claude Code and 5 Game-Changing Developer Tools # claude # javascript # productivity # webdev Comments Add Comment 5 min read AI Trading: Lesson Learned: NEVER Tell CEO to Run CI - Do It Yourself Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 12 AI Trading: Lesson Learned: NEVER Tell CEO to Run CI - Do It Yourself # ai # trading # python # machinelearning Comments Add Comment 1 min read Want to connect with Igor Ganapolsky? Create an account to connect with Igor Ganapolsky. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in AI Trading: Lesson Learned #079: Tomorrow Hallucination Incident (Jan 5, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #079: Tomorrow Hallucination Incident (Jan 5, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #134: RAG Architecture Misunderstanding - Wrong Fix Applied Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #134: RAG Architecture Misunderstanding - Wrong Fix Applied # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #133: LYING - Claimed Fix Without Verification Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #133: LYING - Claimed Fix Without Verification # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #132: RAG Stuck on December 2025 Content (CRISIS) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #132: RAG Stuck on December 2025 Content (CRISIS) # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #130: Account Balance RAG Recording Failure (Jan 11, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #130: Account Balance RAG Recording Failure (Jan 11, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #131: Self-Healing Gap - Blog Lesson Sync Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #131: Self-Healing Gap - Blog Lesson Sync # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #130: Comprehensive Investment Strategy Review (Jan 11, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #130: Comprehensive Investment Strategy Review (Jan 11, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #129: Wheel Strategy Criticism - Deep Research Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 10 AI Trading: Lesson Learned #129: Wheel Strategy Criticism - Deep Research # ai # trading # python # machinelearning Comments Add Comment 3 min read AI Trading: Lesson Learned #129: Execute Trades, Don't Just Analyze Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 10 AI Trading: Lesson Learned #129: Execute Trades, Don't Just Analyze # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #129: Backtest Evaluation Bugs Discovered via Deep Research Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 10 AI Trading: Lesson Learned #129: Backtest Evaluation Bugs Discovered via Deep Research # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #129: CEO Trust Audit - Comprehensive Answers (Jan 10, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 10 AI Trading: Lesson Learned #129: CEO Trust Audit - Comprehensive Answers (Jan 10, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #129: Small Account Options Strategies for 2026 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 10 AI Trading: Lesson Learned #129: Small Account Options Strategies for 2026 # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #128: Comprehensive Trust Audit (Jan 10, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 10 AI Trading: Lesson Learned #128: Comprehensive Trust Audit (Jan 10, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #127: Comprehensive Trust Audit - CEO Questions Answered (Jan 9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #127: Comprehensive Trust Audit - CEO Questions Answered (Jan 9, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #127: LangSmith Removal - Dead Code Cleanup Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #127: LangSmith Removal - Dead Code Cleanup # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #126: Critical Position Review - Expired Options and Missing Stop-Losses Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #126: Critical Position Review - Expired Options and Missing Stop-Losses # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #125: Stale Position Data Inconsistency (Jan 9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #125: Stale Position Data Inconsistency (Jan 9, 2026) # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading Daily Report: January 09, 2026 | $+4,970.00 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading Daily Report: January 09, 2026 | $+4,970.00 # trading # ai # machinelearning # python Comments Add Comment 1 min read AI Trading: Lesson Learned #124: Secret Exposure Incident - Jan 9, 2026 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #124: Secret Exposure Incident - Jan 9, 2026 # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: LL-124: Phil Town CSP Strategy Not Executing Trades Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: LL-124: Phil Town CSP Strategy Not Executing Trades # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: LL-126: Alpaca API Credentials Invalid - 401 Unauthorized Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: LL-126: Alpaca API Credentials Invalid - 401 Unauthorized # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #125: Comprehensive Trust Audit (Jan 9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #125: Comprehensive Trust Audit (Jan 9, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: LL-120: API Access Verification Required Before Trading Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: LL-120: API Access Verification Required Before Trading # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #120: Capital-Aware Watchlist Required for Paper Trading Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #120: Capital-Aware Watchlist Required for Paper Trading # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #124: GitHub Secrets ARE Configured - Stop Hallucinating Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #124: GitHub Secrets ARE Configured - Stop Hallucinating # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #123: Trust Rebuild Audit - Comprehensive Evidence-Based Review Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #123: Trust Rebuild Audit - Comprehensive Evidence-Based Review # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #122: CEO Trust Audit - Comprehensive Strategy Review (Jan 9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #122: CEO Trust Audit - Comprehensive Strategy Review (Jan 9, 2026) # ai # trading # python # machinelearning Comments Add Comment 3 min read AI Trading: Lesson Learned #120: Paper Trading Broken - Trust Crisis (Jan 9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #120: Paper Trading Broken - Trust Crisis (Jan 9, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned: False PR Merge Claims - Took Credit for Auto-Merged Work Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned: False PR Merge Claims - Took Credit for Auto-Merged Work # ai # trading # python # machinelearning Comments Add Comment 3 min read AI Trading: Lesson Learned #121: Investment Strategy Audit - Honest Assessment (Jan 9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #121: Investment Strategy Audit - Honest Assessment (Jan 9, 2026) # ai # trading # python # machinelearning Comments Add Comment 3 min read AI Trading: Lesson Learned #120: Paper Trading System Broken for 4 Days (Jan 5-9, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 9 AI Trading: Lesson Learned #120: Paper Trading System Broken for 4 Days (Jan 5-9, 2026) # ai # trading # python # machinelearning Comments Add Comment 4 min read AI Trading: Lesson Learned #119: Paper Trading API Key Mismatch After Account Reset Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 8 AI Trading: Lesson Learned #119: Paper Trading API Key Mismatch After Account Reset # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #117: ChromaDB Removal Caused 2-Day Trading Gap Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 8 AI Trading: Lesson Learned #117: ChromaDB Removal Caused 2-Day Trading Gap # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #117: Trust Audit - Full System Review (Jan 8, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 8 AI Trading: Lesson Learned #117: Trust Audit - Full System Review (Jan 8, 2026) # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #112: Self-Healing Data Integrity System Required Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 8 AI Trading: Lesson Learned #112: Self-Healing Data Integrity System Required # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #116: Observability Lasagna - Connecting Logs to Traces Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 8 AI Trading: Lesson Learned #116: Observability Lasagna - Connecting Logs to Traces # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #115: PAL MCP for Adversarial Trade Validation Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 8 AI Trading: Lesson Learned #115: PAL MCP for Adversarial Trade Validation # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #112: Phase 1 Cleanup - ChromaDB Removed Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #112: Phase 1 Cleanup - ChromaDB Removed # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #112: Pre-Market Position Protection Gap Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #112: Pre-Market Position Protection Gap # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #111: Paper Trading Capital Must Be Realistic Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #111: Paper Trading Capital Must Be Realistic # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading Daily Report: January 07, 2026 | $+117,834.44 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading Daily Report: January 07, 2026 | $+117,834.44 # trading # ai # machinelearning # python Comments Add Comment 1 min read AI Trading: Lesson Learned #110: Trailing Stops Script Existed But Never Executed Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #110: Trailing Stops Script Existed But Never Executed # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #108: Strategy Verification Session (Jan 7, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #108: Strategy Verification Session (Jan 7, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #095: Trading Workflow Regression - Jan 7, 2026 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #095: Trading Workflow Regression - Jan 7, 2026 # ai # trading # python # machinelearning Comments Add Comment 1 min read AI Trading: Lesson Learned #095: Daily Trading Workflow Failure (Jan 7, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #095: Daily Trading Workflow Failure (Jan 7, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #107: Honest Report - System NOT Following Phil Town (Jan 7, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #107: Honest Report - System NOT Following Phil Town (Jan 7, 2026) # ai # trading # python # machinelearning Comments Add Comment 3 min read AI Trading: Lesson Learned #093: CI Triggering Blocked Without GitHub PAT (Jan 7, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #093: CI Triggering Blocked Without GitHub PAT (Jan 7, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #094: Daily Trading Workflow Not Triggering (Jan 7, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #094: Daily Trading Workflow Not Triggering (Jan 7, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #093: Automation Metadata Stale - No Trades Executed Jan 7 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #093: Automation Metadata Stale - No Trades Executed Jan 7 # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned: Phil Town Rule 1 Violation - Unprotected Positions Lost $93.69 (Jan 7, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned: Phil Town Rule 1 Violation - Unprotected Positions Lost $93.69 (Jan 7, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #093: North Star Reality Check - $100/Day Requires $50K+ Capital Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #093: North Star Reality Check - $100/Day Requires $50K+ Capital # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: LL-095: Pre-Trade Pattern Validation Wired In Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: LL-095: Pre-Trade Pattern Validation Wired In # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #105: Post-Trade RAG Sync Was Missing Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #105: Post-Trade RAG Sync Was Missing # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #094: North Star $100/day Reality Check Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #094: North Star $100/day Reality Check # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading: Lesson Learned #093: Google Recommender CAV Not Useful for Trading Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 7 AI Trading: Lesson Learned #093: Google Recommender CAV Not Useful for Trading # ai # trading # python # machinelearning Comments Add Comment 2 min read AI Trading Daily Report: January 06, 2026 | $+101,272.24 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 6 AI Trading Daily Report: January 06, 2026 | $+101,272.24 # trading # ai # machinelearning # python Comments Add Comment 1 min read AI Trading Daily Report: January 05, 2026 | $+101,197.92 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 5 AI Trading Daily Report: January 05, 2026 | $+101,197.92 # trading # ai # machinelearning # python Comments Add Comment 1 min read AI Trading Daily Report: January 02, 2026 | $+100.11 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 2 AI Trading Daily Report: January 02, 2026 | $+100.11 # trading # ai # machinelearning # python Comments Add Comment 1 min read AI Trading Daily Report: December 31, 2025 | $-185.16 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Dec 31 '25 AI Trading Daily Report: December 31, 2025 | $-185.16 # trading # ai # machinelearning # python Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://zeroday.forem.com/about#what-to-expect | About Zero Day Security Community - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close About Zero Day Security Community About the Zero Day Security Community Welcome to Zero Day, the ultimate hub for security professionals, enthusiasts, students, and anyone passionate about the world of security. Whether you're a seasoned CISO, a curious student, or a developer looking to write more secure code, you've found your home. Our Mission Our mission is to create a central, inclusive, and authoritative online community dedicated to fostering collaboration, knowledge sharing, and skill development across all domains of security. We believe in breaking down silos and building bridges between the theoretical and the practical, the digital and the physical. What We're All About Zero Day is a space for deep, meaningful discussion and learning. We are built on a few core principles: Knowledge First: We prioritize accurate, vetted, and practical information. We're here to learn from each other and elevate our collective expertise. Radical Inclusivity: Gatekeeping has no place here. We welcome all skill levels, from absolute beginners to world-renowned experts. We are a community dedicated to mentorship and support, not judgment. Strong Ethical Foundation: We are a strictly white-hat community. All discussions and activities are guided by a commitment to ethical hacking, responsible disclosure, and using our skills for good. What to Expect Here, you'll find a wide range of content and discussions covering the entire security landscape. We encourage posts, questions, and articles on topics like: Offensive Security (Red Team): From web app pentesting and exploit development to social engineering and adversary emulation. Defensive Security (Blue Team): Dive into threat intelligence, digital forensics, incident response (DFIR), and malware analysis. Cloud & Application Security: Explore DevSecOps, secure coding practices, cryptography, and securing cloud infrastructure (AWS, Azure, GCP). Governance, Risk & Compliance (GRC): Discuss frameworks like NIST and ISO 27001, risk management, and compliance challenges. Physical & Hardware Security: Explore everything from lockpicking and access control to IoT and embedded systems hacking. Career & Professional Development: Share advice on certifications (OSCP, CISSP, etc.), get resume feedback, and discuss interview experiences. How to Get Involved This community is powered by you! Here are a few ways to jump in: Introduce Yourself: Head over to the introductions thread and tell us about your interests. Ask Questions: No question is too basic. We are all here to learn. Share Your Knowledge: Write a post about a project you're working on, a tool you love, or a concept you've mastered. Join the Conversation: Upvote quality content and add your perspective to ongoing discussions. Set Your Flair: Edit your profile to add flair that shows your specialty (e.g., Pentester, DFIR, GRC, Student). We're thrilled to have you here. Let's build the best security community on the web, together. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/bogaboga1/odoo-core-and-the-cost-of-reinventing-everything-15n1#final-thoughts | Odoo Core and the Cost of Reinventing Everything - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Boga Posted on Jan 12 Odoo Core and the Cost of Reinventing Everything # python # odoo # qweb # owl Hello, this is my first blog post ever. I’d like to share my experience working with Odoo , an open-source Enterprise Resource Planning (ERP) system, and explain why I believe many of its architectural choices cause unnecessary complexity. Odoo is a single platform that provides many prebuilt modules (mini-applications) that most companies need. For example, almost every company requires a Human Resources system to manage employee details, leaves, attendance, contracts, resignations, and more. Beyond HR, companies also need purchasing, inventory, accounting, authentication, authorization, and other systems. Odoo bundles all of these tightly coupled systems into a single installation. On paper, this sounds great — and from a business perspective, it often is. From a technical perspective , however, things get complicated very quickly. Odoo Core Components Below are the main Odoo components, ranked from least complex to most complex, and all largely developed in-house instead of relying on existing mature frameworks: Odoo HTTP Layer JSON-RPC Website routing Odoo Views XML transformed into Python and JavaScript Odoo ORM Custom inheritance system Query builder Dependency injection Caching layers Cache System Implemented from scratch WebSocket Implementation Very low-level handling Odoo HTTP Layer Odoo is not built on a standard Python web framework like Django or Flask. Instead, it implements its own HTTP framework on top of Werkzeug (a WSGI utility library). This HTTP layer introduces its own abstractions, request lifecycle, routing, and serialization logic, including JSON-RPC and website controllers. While technically impressive, it reinvents many problems that have already been solved — and battle-tested — by existing frameworks. Odoo Views In my opinion, this is one of the most problematic parts of Odoo. Instead of using standard frontend technologies, Odoo relies heavily on XML-based views . These XML files are sent to the browser and then transformed using Abstract Syntax Tree (AST) analysis into JavaScript. In other contexts (like the website), the XML may be converted into Python code and sometimes back into JavaScript again. This creates: High cognitive overhead Difficult debugging Tight coupling between backend and frontend Poor tooling support compared to modern frontend stacks It feels like building a car from raw metal just to drive from point A to point B. Odoo ORM Odoo’s ORM is not a typical ORM. It implements: A custom inheritance system (instead of using Python’s built-in one) Its own dependency injection mechanism A query builder Caching layers (LRU) Model extension via monkey-patching While powerful, this system is extremely complex and hard to reason about. Debugging model behavior often feels like navigating invisible layers of magic. WebSocket Implementation Instead of using a mature real-time framework, Odoo implements its WebSocket handling with very low-level logic, sometimes in surprisingly small and dense files. A single comment from the codebase summarizes this approach better than words ever could: The “Odoo Is Old” Argument A common defense of Odoo’s architecture is that “it’s an old system” — originally developed around 2005 using Python 2. However, this argument no longer holds. Odoo was largely rewritten from scratch around 2017 to support Python 3. At that time, many excellent frameworks already existed and had solved the same problems more cleanly, while continuing to evolve without breaking their ecosystems. Today, even small changes in Odoo’s core can break custom modules unless they are limited to simple CRUD models with minimal dependencies on core behavior. Final Thoughts Odoo is a powerful product and a successful business platform. But from a software engineering perspective, many of its design decisions prioritize control and internal consistency over maintainability, clarity, and developer experience . If you work with Odoo long enough, you stop asking “why does it work this way?” and start asking “how do I survive this upgrade?” Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Boga Follow Senior Software Engineer Joined Jan 12, 2026 Trending on DEV Community Hot 🧱 Beginner-Friendly Guide 'Maximal Rectangle' – LeetCode 85 (C++, Python, JavaScript) # programming # cpp # python # javascript The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning What was your win this week??? # weeklyretro # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/t/programming/page/13 | Programming Page 13 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 10 11 12 13 14 15 16 17 18 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu I Called Myself a Tech Guy Without Building Anything! Suraj Kumar Suraj Kumar Suraj Kumar Follow Jan 9 I Called Myself a Tech Guy Without Building Anything! # webdev # programming # ai # mixedreality Comments Add Comment 2 min read Rust Series01 - Ownership is what you need to know Kevin Sheeran Kevin Sheeran Kevin Sheeran Follow Jan 10 Rust Series01 - Ownership is what you need to know # programming # rust # web3 # blockchain Comments Add Comment 1 min read Why Your AI's Context Window Problem Just Got Solved (And What It Means For Your Bottom Line) Debby McKinney Debby McKinney Debby McKinney Follow Jan 10 Why Your AI's Context Window Problem Just Got Solved (And What It Means For Your Bottom Line) # ai # programming # chatgpt # aiops 5 reactions Comments Add Comment 6 min read How to Check External API Throttle Limit in Laravel Ankit Verma Ankit Verma Ankit Verma Follow Jan 10 How to Check External API Throttle Limit in Laravel # programming # webdev # php # laravel Comments Add Comment 1 min read FlutterFlow's AI Future is DreamFlow. Its AI Present is This. Stuart Stuart Stuart Follow Jan 9 FlutterFlow's AI Future is DreamFlow. Its AI Present is This. # ai # flutter # dart # programming Comments Add Comment 3 min read Java Basics: Understanding Class and Object for Beginners Kesavarthini Kesavarthini Kesavarthini Follow Jan 9 Java Basics: Understanding Class and Object for Beginners # java # beginners # learning # programming Comments Add Comment 1 min read Solved: Is there a one-click way to backup my Docker containers? Darian Vance Darian Vance Darian Vance Follow Jan 8 Solved: Is there a one-click way to backup my Docker containers? # devops # programming # tutorial # cloud Comments Add Comment 9 min read Solved: Canceled my $15K/year ZoomInfo subscription. Built my own for $50/month. Darian Vance Darian Vance Darian Vance Follow Jan 8 Solved: Canceled my $15K/year ZoomInfo subscription. Built my own for $50/month. # devops # programming # tutorial # cloud Comments Add Comment 10 min read #1 - 1) Python input()은 항상 문자열이다 JEON HYUNJUN JEON HYUNJUN JEON HYUNJUN Follow Jan 9 #1 - 1) Python input()은 항상 문자열이다 # programming # python Comments Add Comment 2 min read RAG without the cloud: .NET + Semantic Kernel + Ollama on your laptop Frank Noorloos Frank Noorloos Frank Noorloos Follow Jan 9 RAG without the cloud: .NET + Semantic Kernel + Ollama on your laptop # ai # programming # dotnet # llm 3 reactions Comments Add Comment 8 min read Coding Language Prognostications For the New Year with Gemini CLI xbill xbill xbill Follow Jan 8 Coding Language Prognostications For the New Year with Gemini CLI # programming # gemini # shamwow # billymays 5 reactions Comments Add Comment 8 min read Running Llama 3 Locally with Apple MLX: A Guide to Unified Memory Sachin Myadam Sachin Myadam Sachin Myadam Follow Jan 8 Running Llama 3 Locally with Apple MLX: A Guide to Unified Memory # python # ai # apple # programming Comments Add Comment 3 min read LeetCode DSA Series #7: 169. Majority Element David Babalola David Babalola David Babalola Follow Jan 9 LeetCode DSA Series #7: 169. Majority Element # discuss # python # algorithms # programming Comments Add Comment 1 min read Build an AI-Powered Document Insights Tool with Django (Python), and React Faisal Malik Faisal Malik Faisal Malik Follow Jan 8 Build an AI-Powered Document Insights Tool with Django (Python), and React # ai # programming # react # python Comments Add Comment 3 min read Why Traditional API Gateways Fail at AI Governance (And What Actually Works) Debby McKinney Debby McKinney Debby McKinney Follow Jan 8 Why Traditional API Gateways Fail at AI Governance (And What Actually Works) # programming # ai # opensource # devops 5 reactions Comments Add Comment 5 min read You Know Python Basics—Now Let's Build Something Real Samuel Ochaba Samuel Ochaba Samuel Ochaba Follow Jan 8 You Know Python Basics—Now Let's Build Something Real # python # beginners # gamedev # programming Comments Add Comment 3 min read The Knight Capital Law: Why Your CI/CD Pipeline Is a Liability System Design Autopsy System Design Autopsy System Design Autopsy Follow Jan 8 The Knight Capital Law: Why Your CI/CD Pipeline Is a Liability # devops # systemdesign # softwareengineering # programming Comments Add Comment 3 min read Build an Engagement Rate Calculator That Actually Works Olamide Olaniyan Olamide Olaniyan Olamide Olaniyan Follow Jan 8 Build an Engagement Rate Calculator That Actually Works # webdev # programming # ai # tutorial Comments Add Comment 8 min read Understanding if, elif, and else in Python with Simple Examples Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Jan 8 Understanding if, elif, and else in Python with Simple Examples # python # beginners # tutorial # programming Comments Add Comment 2 min read Won't LLMs eventually train on themselves? It'll slowly decline in output.. intercepted16 intercepted16 intercepted16 Follow Jan 8 Won't LLMs eventually train on themselves? It'll slowly decline in output.. # ai # programming Comments Add Comment 1 min read How to Prepare for a Certification in any Tech Career KWAN KWAN KWAN Follow Jan 9 How to Prepare for a Certification in any Tech Career # programming # cloud # aws # certification 1 reaction Comments 1 comment 4 min read Connecting Your Frontend to AWS: APIs, Authentication, and Storage Blessing Njoku Blessing Njoku Blessing Njoku Follow Jan 8 Connecting Your Frontend to AWS: APIs, Authentication, and Storage # aws # frontend # webdev # programming Comments Add Comment 3 min read Build Your Own Local AI Agent (Part 4): The PII Scrubber 🧼 Harish Kotra (he/him) Harish Kotra (he/him) Harish Kotra (he/him) Follow Jan 8 Build Your Own Local AI Agent (Part 4): The PII Scrubber 🧼 # programming # ai # beginners # opensource Comments Add Comment 1 min read Day 7: Build in Public Week 1: What Worked, What Didn't Erik Erik Erik Follow for Allscreenshots Jan 8 Day 7: Build in Public Week 1: What Worked, What Didn't # webdev # programming Comments Add Comment 4 min read How I Built a Chrome Extension That Analyzes SEC Filings and Financial News in Seconds Mayuresh Smita Suresh Mayuresh Smita Suresh Mayuresh Smita Suresh Follow Jan 9 How I Built a Chrome Extension That Analyzes SEC Filings and Financial News in Seconds # extensions # javascript # programming # ai 1 reaction Comments Add Comment 12 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://tatanotes.com/blog/accessibility-testing-on-windows-on-mac | TataNotes – Web Accessibility Personal Blog Accessibility Testing on Windows on Mac – TataNotes Skip to main content TataNotes… …all about a11y Blog About me Tutorials Accessibility Testing on Windows on Mac A quick guide to Accessibility Testing using Windows-only tools on a modern Mac with Apple Silicon processor. Reading time: around 3 min Publication date May 12, 2025 Today’s note is about something that I, as a new Mac user, had to deal with while setting up my work environment. TL;DR: To run NVDA Opens a new page and JAWS Opens a new page on a Mac, you need to install Windows 11 for ARM Opens a new page in a virtual machine like UTM Opens a new page , and map a spare key to the Insert key with SharpKeys Opens a new page . Why do accessibility testing on Windows if you have a Mac? According to the WebAIM Screen Reader User Survey #10 Opens a new page , Windows-only screen readers NVDA and JAWS are used by the majority of users. Just like browsers, screen readers have differences in how they present information, so it’s always a good idea to test your website or app using different browser/screen reader combinations. In addition, some of the styling, like box shadows, background images, and so on, is removed when Windows High Contrast Mode (WHCM) is enabled. Sadly, there is no alternative to the WHCM on the Mac. Installation Step 1 – Installing a virtual machine There are multiple virtual machines available on Mac, such as Parallels, VirtualBox, and UTM. I’m using UTM, but this guide doesn’t depend on its specifics, so you can choose whatever works for you. You can download UTM for free from the official website Opens a new page . You can also purchase it from the Mac App Store Opens a new page to support the team behind the software. Step 2 – Installing Windows When you have got UTM up and running, create a new virtual machine. You will need a Windows installation disk image, which you can download from the Microsoft website Opens a new page . Click on “Create a New Virtual Machine”, select “Virtualize”, and follow the wizard. You will need to specify the path to the installation ISO here. Step 3 – Installing screen readers Both NVDA Opens a new page and JAWS Opens a new page work on ARM-based devices now, so you can install them in a virtual machine, just as you would on a real device. If you would like to install any other programs, make sure that they also support ARM processors. Step 4 – Mapping missing keys Due to the fact that Mac and Windows use different keyboards, you are not able to use the Insert key in your UTM virtual machine. (You will need it for the various shortcuts for NVDA and JAWS.) You have to use a third-party program to remap keys on Mac or Windows level. I’m using SharpKeys Opens a new page – an open-source program for Windows. Download, install, and run SharpKeys inside the virtual machine . Click on the “Add” button. In the new window, find “Special: Insert” on the right. In the left list, select a key that you would like to act as the Insert key. For instance, if you select F1 on the left, every time you press F1 key inside your virtual machine, it will register as Insert. Make sure to map a key that is not used in any shortcuts. Once finished, press “OK”, and then “Write to registry” to save changes – it will not work otherwise. At this point, you’re good to go and start your accessibility testing. Hooray! Step 5 (bonus) – Accessing localhost If you are developing a project and running it locally, you might want to do quality assurance before deploying changes. For this, you need to be able to access your project at http://localhost:port from within the virtual machine. One way to do that with UTM is to set the network mode for the virtual machine to “Shared Network”. Then, look up the Default Gateway IP address in Windows, which you can do by running ipconfig command in the Command Prompt: Now make sure that your project is accepting requests to this IP address. For example, to run a SvelteKit project in development mode and accept connections on all available IP addresses, you need to slightly modify the default command: npm run dev -- --host You can find a similar command for your tool. Extensive accessibility testing is important Mac is a great platform for web development. However, the reality is that majority of desktop users are Windows users. Thanks to tools like UTM, we are able to run Windows and Windows-specific software directly on a Mac. By testing on a wide range of tools and platforms, we make the Web accessible for all. Tatyana Bayramova © 2024–present Important: All rights reserved | 2026-01-13T08:49:02 |
https://core.forem.com/_bigblind/are-tag-follows-not-used-for-the-home-page-feeds-288k#comments | Are tag follows not used for the home page feeds? - Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Frederik 👨💻➡️🌐 Creemers Posted on Sep 8, 2025 Are tag follows not used for the home page feeds? # product I've admittedly been a lot les active on dev.to for a while, and so a lot of the people I follow are old accounts who no longer publish much content on dev.to, if any. So when I go to look at my home feed, both "Discover" and "Following", most of what I see are posts from the DEV team. I do, however, follow a fair number of tags, ranging from various programming languages, to #explainlikimfive and similar. Those do still get some activity, but I'm not seeing any of their posts on my home feed. Are they not considered? When I look at the top 7 posts overview, I do see that there's still some great stuff being published to the site, but I don't really have a good way to discover it, other than those posts right now. Top comments (2) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Ben Halpern Ben Halpern Ben Halpern Follow A Canadian software developer who thinks he’s funny. Email ben@forem.com Location NY Education Mount Allison University Pronouns He/him Work Co-founder at Forem Joined Dec 27, 2015 • Sep 8 '25 Dropdown menu Copy link Hide They are, but it's also a mix of other signals and some of the less popular tags kind of fade away. It's all about a balancing act — but this is valuable feedback because we want to strike the right balance and we're aware of the current imbalance you're describing. Great to see you around Frederik! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Roshan Sharma Roshan Sharma Roshan Sharma Follow 💻 Tech Enthusiast | Linux & Open Source Explorer 🔧 Sharing insights on Ubuntu, Debian, Docker, and DevOps tools 🐍 Passionate about Python, SQL & MySQL ✍️ Writing tutorials, guides, and answers to m Joined Aug 19, 2025 • Sep 26 '25 Dropdown menu Copy link Hide Nice post, this question gets overlooked a lot in community platforms. One thought: have you looked into how tag-follows affect personalized recommendations or feed relevance at scale? Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Frederik 👨💻➡️🌐 Creemers Follow I'm never sure what to put in a bio. If there's anything you want to know, don't be afraid to ask! Location Maastricht, the Netherlands Education Knowledge Engineering & Data Science at Maastricht University Pronouns he/him Work Developer at TalkJS Joined Mar 22, 2017 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/rsionnach/shift-left-reliability-4poo#what-shiftleft-reliability-actually%C2%A0means | Shift-Left Reliability - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Rob Fox Posted on Jan 12 Shift-Left Reliability # sre # devops # cicd # platformengineering We've become exceptionally good at incident response. Modern teams restore service quickly, run thoughtful postmortems, and hold themselves accountable through corrective actions. And yet… A team ships a change that passes every test, gets all the required approvals, and still brings down checkout for 47 minutes. The postmortem conclusion? "We should have known our latency SLO was already at 94% before deploying." Many postmortems point to the same root cause: changes we introduced ourselves. Not hardware failures. Not random outages. Just software behaving exactly as we told it to. We continue to treat reliability as something to evaluate once those changes are already live. This isn't a failure of tooling or process. It's a question of when we decide whether a system is ready. The paradox We've invested heavily in observing and responding to failure - better alerting, faster incident response, thorough postmortems. Teams care deeply about reliability and spend significant time optimizing how they respond to incidents. But when in a service's lifecycle are they supposed to define reliability? Where's the innovation that happens before deployment? Where reliability decisions actually happen today I've seen multiple teams running identical technology stacks with completely different SLOs, metrics, and alerts. Nobody told them what to implement, what's best-practice or how to tune their alerts. They want to be good reliability citizens, but getting from the theory in the handbook to putting that theory into practice is not straightforward. Services regularly move into production with SLOs being created months later - or never. Dashboards are missing, insufficient, or inconsistent. "Looks fine to me" during PR reviews. Tribal knowledge. Varying levels of understanding across teams. Reliability is fundamentally bespoke and ungoverned. That's the core issue. The missing layer GitHub gave us version control for code. Terraform gave us version control for infrastructure. Security has transformed with shift-left - finding flaws as code is written, not after deployment. We're still missing version control for reliability. We need a specification that defines requirements, validates them against reality, and generates the artifacts: dashboards, SLOs, alerts, escalation policies. If the specification is validated and the artifacts created, the same tool can check in real-time whether a service is in breach - and block high-risk deployments in CI/CD. What shift-left reliability actually means Shift-left reliability doesn't mean more alerts and dashboards, more postmortems or more people in the room. It means: Spec - Define reliability requirements as code before production deployment Validate - Test those requirements against reality Enforce - Gate deployments through CI/CD Engineers don't write PromQL or Grafana JSON - they declare intent, and reliability becomes deterministic. Outcomes are predictable, consistent, transparent, and follow best practice. An executable reliability contract Keep it simple. A team creates a service.yaml file with their reliability intent: name: payment-api tier: critical type: api team: payments dependencies: - postgresql - redis Enter fullscreen mode Exit fullscreen mode Here is a complete service.yaml example . Tooling validates metrics, SLOs, and error budgets then generates these artifacts automatically. This is the approach I am exploring with an open-source project called NthLayer. NthLayer runs in any CI/CD pipeline - GitHub Actions, ArgoCD, Jenkins, Tekton, GitLab CI. The goal isn't to be an inflexible blocker; it's visible risk and explicit decisions. Overrides are fine when they're intentional, logged, and owned. When a deployment is attempted, the specification is evaluated against reality: $ nthlayer check-deploy - service payment-api ERROR: Deployment blocked - availability SLO at 99.2% (target: 99.95%) - error budget exhausted: -47 minutes remaining - 3 P1 incidents in last 7 days Exit code: 2 (BLOCKED) Enter fullscreen mode Exit fullscreen mode Why now? SLOs have had 8+ years to mature and move from the Google SRE Handbook into mainstream practice. GitOps has normalized declarative configuration. Platform Engineering has matured as a discipline. The concepts are ready but the tooling has lagged behind. This is a deliberate shift in approach. Reliability is no longer up for debate during incidents. Services have defined owners with deterministic standards. We can stop reinventing the reliability wheel every time a new service is onboarded. If requirements change, update the service.yaml , run NthLayer and every service benefits from adopting the new standard. What this does not replace NthLayer doesn't replace service catalogs, developer portals, observability platforms, or incident management. It doesn't predict failures or eliminate human judgment. It's upstream of all these systems. The goal: a reliability specification, automated deployment gates and to reduce cognitive load to implement best practices. Open questions I don't have all the answers but two questions I keep returning to are: Contract Drift: What happens when the spec says 99.95% but reality has been 99.5% for months? Is the contract wrong, or is the service broken? Emergency Overrides: How should they work? Who approves? How do you prevent them from becoming the default? The timing problem Where do reliability decisions actually happen in your organization? What would it look like to decide readiness before deployment? What reliability rules do you wish you could enforce automatically? The timing problem isn't going away. The only question is whether you address it before deployment - or learn about it in the postmortem. NthLayer is open source and looking for early adopters. If you're tired of reliability being an afterthought: pip install nthlayer nthlayer init nthlayer check-deploy --service your-service Enter fullscreen mode Exit fullscreen mode → github.com/rsionnach/nthlayer Star the repo, open an issue, or tell me I'm wrong. I want to hear how reliability decisions happen in your organization. Rob Fox is a Senior Site Reliability Engineer focused on platform and reliability tooling. He's exploring how reliability engineering can move earlier in the software delivery lifecycle. Find him on GitHub . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Rob Fox Follow Sr Site Reliability Engineer. Building NthLayer, an open-source tool for shift-left reliability. Opinions are my own. github.com/rsionnach Location Dublin, Ireland Joined Jan 6, 2026 Trending on DEV Community Hot The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning How I Built an AI Terraform Review Agent on Serverless AWS # aws # terraform # serverless # devops How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://docs.suprsend.com/docs/in-app-inbox-template | In-App Inbox Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors In-App Inbox Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors In-App Inbox Template OpenAI Open in ChatGPT How to design Inbox template with customisation options like action buttons, tags, pinning, and expiry. OpenAI Open in ChatGPT In-App Inbox notification template, you can add header, body, buttons, avatar and card click action and other advanced configurations like pinning, expiry, tags to customize the view and behaviour of Inbox notification. Designing Template Designing template inside SuprSend is quite intuitive with WYSWYG editors for all channels. We use handlebars as the templating language. You can add variable in the template as {{var}} . We also support handlebars helpers for handling complex template use case like adding if-else condition, showing a default value when variable is absent or handling complex arrays. To create a template, go to SuprSend dashboard -> templates tab and enable Inbox channel. Form fields description Field Type Description Header Single line text field Heading of the message shown in bold at the top of the content. Use it to show the summary of your message like New comment received , Your story has got 30 views Text Multi-line text field Body of your message. This is where the message content will be shown. We support markdown syntax in body field to add links, blockquotes, showing some content in bold etc. All supported markdown syntax in text field are mentioned here. Avatar image public URL in .jpeg , .png format This can be used to show image of the actor as LinkedIn or some static images based on the type of message as used in HubSpot. Subtext Single line text field Subtext is like the footer of your content. It is clickable, so you can use it to show subtle information like in LinkedIn, you would see number of comments and likes in subtext or Jira uses it to show the task’s card number. Action URL http / https URL This is the URL user will be redirected on card click. You can select Open in new tab if you want the link to open in a new tab. Action buttons text - URL pair You can add up to 2 buttons in your template. Buttons can be used to redirect users to a link or perform any inline actions like opening a modal or calling an internal function like Approve button to internally approve the request. Refer Custom click handler to customize click action on a button. You can select Open in new tab if you want the button link to open in a new tab. Supported markdown syntax in text field We support headings , bold , Italic , Blockquotes , Nested Blockquotes , links and code . In-App inbox - advanced configurations (Optional) Tags You can add tags to filter and organize notifications inside multiple tabs . Other than tags, you can filter out tabs based on notification category or notification read status. e.g., show all unread notifications with mentions tag inside Mentions tab. Tags in Inbox template vs Tags in Workflow : Tags added in the Inbox template are used to filter notifications in inbox tabs. Tags in workflow are only used to group or filter similar workflows on the workflow listing page and do not affect inbox filtering. To filter notifications in tabs, you must add tags in the Inbox template and then reference them in your inbox configuration using tags: "your_tag" in the query. Inbox with tabs - All, mentions and replies Pin notification Pinned notifications are shown with a pinned tag on top in your notification list. Enable the switch to pin the notification. You can use this to send critical alerts where you want user to complete some critical action within your platform like finish compliance or renew plan or some limited time offer. Expiry Setting expiry will auto archive the notification when the expiry period is reached. You can use it to send notifications which are relevant till a particular timestamp like limited time offers or reminder to join an upcoming event or set a fixed expiry to all notifications, in general to keep user’s Inbox clean. You can either set fixed or dynamic expiry. Dynamic expiry are computed using data in your event or user properties and can vary for each user. An example of dynamic expiry could be reminder notifications of some upcoming event. You can also show expiry timer on the notification to drive action urgency. Fixed expiry Fixed expiry can be a relative time, like - **d **h **m **s or an absolute timestamp, like 2024-04-01 2:00 pm . Absolute timestamp added in form takes the time in your local timezone. Dynamic expiry In case of dynamic expiry, expiry is computed using the data from your event or user properties. You can add dynamic expiry as handlebars variable, like {{expiry_time}} . Your duration key variable can be computed to either: An ISO-8601 timestamp (e.g. 2024-03-02T20:34:07Z) which must be a datetime in the future, or A relative duration unit, which can be an integer like 50 , considered as duration in seconds. an interval string defined as **d **h **m **s , where d = day, h = hour, m = minutes and s = seconds Show expiry timer Enable it to show expiry timer on your Inbox notification. This helps to drive action urgency. The expiry timer shows in a grey background if the time left is greater than 1 hour and goes red when the difference goes below 1 hour so as to draw user’s attention when the expiry time is near. Expiry timer with different expiry left Adding dynamic content in the template There will always be the case where you would require to add dynamic content to a template, so as to personalise it for your users. To achieve this, you can add variables in the template, which will be replaced with the dynamic content at the time of sending the message. You’ll need to pass these while triggering the communication from one of our frontend or backend SDKs. Here is a step-by-step guide on how to add dynamic content in Inbox: 1 Declaring Variables in the global 'Mock data' button If you are at this stage, it is assumed that you have declared the variables along with sample values in the global Mock data button. To see how to declare variables before using them in designing templates,refer to this section in the Templates documentation . 2 Using variables in the templates Once the variables are declared, you can use them while designing the android push template. We support handlebarsjs to add variables in the template. As a general rule, all the variables have to be entered within double curly brackets: {{variable_name}} If you have declared the variables in the global ‘Mock data’ button, then they will come as auto-suggestions when you type a curly bracket { . This will remove the chances of errors like variable mismatch at the time of template rendering. Note that you will be able to enter a variable name even when you have not declared it inside the Variables button. To manually enter the variable name, follow the handlerbarsjs guide here . Below is an example of how to enter variables in the template design. For illustration, we are using the same sample variable names that we declared in the Templates section: json Copy Ask AI { "array" : [ { "product_name" : "Aldo Sling Bag" , "product_price" : "3,950.00" }, { "product_name" : "Clarles & Keith Women Slipper, Biege, 38UK" , "product_price" : "2,549.00" }, { "product_name" : "RayBan Sunglasses" , "product_price" : "7,899.00" } ], "event" : { "location" : { "city" : "Bangalore" , "state" : "KA" }, "order_id" : "11200123" , "first_name" : "Nikita" }, "product_page" : "https://www.suprsend.com" } 1 Enter a nested variable To enter a nested variable, enter in the format {{var1.var2.var3}} . e.g. to refer to city in the example above, you need to enter {{event.location.city}} 2 Refer to an array element To refer to an array element, enter in format {{var1.[*index*].var2}}. e.g. to refer to product_name of the first element of the array array, enter {{array.[0].product_name}}` 3 In case of a space inside your variable name: Enclose your variable name in square bracket as shown here: {{event.[first name]}} You will be able to see the sample values in the Preview section, as well as in the Live version when you publish a draft. If you cannot see your variable being rendered with the sample value, check one of the following: Make sure you have entered the variable name and the sample value in the Variables button. Make sure you have entered the correct variable name in the template, as per the handlebarsjs guideline. What happens if there is variable mismatch at the time of sending? At the time of sending communication, if there is a variable present in the template whose value is not rendered due to mismatch or missing, SuprSend will simply discard the template and not send that particular notification to your user. Please note that the rest of the templates will be sent. e.g. if there is an error in rendering Android Push template, but email template is successfully rendered, Android Push notification will not be triggered, but email notification will be triggered by SuprSend. Best Practices - notification design Here’s a breakdown of which form fields to use for different types of notifications: Tags act as filters to create Inbox tabs, a useful way to organize notifications. For instance, LinkedIn uses tabs to separate mentions and reactions to your posts in distinct tabs. You can use tabs to differentiate regular updates from more relevant ones. A generic example of tabs for a SAAS application could be All, Product releases and Upcoming events . Learn how to implement tabs in notification here . Expiry : It’s a good practice to add expiry of 15 days or more to all notifications except long lived notifications to maintain clean user inbox. A shorter expiry duration can be set for notifications valid for a limited time, such as webinars and upcoming events. You can also show expiry timer to prompt action urgency. For instance, when you need users to respond to feedback within three days or for events with impending registration closures. The color change of the expiry timer based on remaining time is an effective way to convey urgency. 📘 Avoid adding expiry to long-lived notifications that users might want to reference later, like product updates or blog posts. Pinning is used for notifications that should always show on top until user reads it or completes related action. Examples include compliance-related actions, system updates, or urgent releases requiring app version update. Always combine it with expiry otherwise the notification will always be pinned in user’s inbox until they archive it. Was this page helpful? Yes No Suggest edits Raise issue Previous SMS Template How to design and publish SMS template. Next ⌘ I x github linkedin youtube Powered by On this page Designing Template Form fields description Supported markdown syntax in text field In-App inbox - advanced configurations (Optional) Tags Pin notification Expiry Fixed expiry Dynamic expiry Show expiry timer Adding dynamic content in the template Best Practices - notification design | 2026-01-13T08:49:02 |
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Temporal | Temporal - JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Reference Standard built-in objects Temporal Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) 日本語 Temporal Limited availability This feature is not Baseline because it does not work in some of the most widely-used browsers. Learn more See full compatibility Report feedback The Temporal object enables date and time management in various scenarios, including built-in time zone and calendar representation, wall-clock time conversions, arithmetics, formatting, and more. It is designed as a full replacement for the Date object. In this article Description Static properties Specifications Browser compatibility See also Description Unlike most global objects, Temporal is not a constructor. You cannot use it with the new operator or invoke the Temporal object as a function. All properties and methods of Temporal are static (just like the Math object). Temporal has an intricate and powerful API. It exposes over 200 utility methods via several classes, so it could appear very complex. We will provide a high-level overview of how these APIs are related to each other. Background and concepts JavaScript has had the Date object for handling date and time since its first days. However, the Date API is based on the poorly designed java.util.Date class from Java, which was replaced in the early 2010s; but, because of JavaScript's goal of backward compatibility, Date sticks around in the language. The important lesson to preface the whole introduction is that date handling is complex . Most of the problems of Date are fixable by adding more methods, but a fundamental design flaw remains: it exposes so many methods on the same object that developers are often confused about what to use, leading to unexpected pitfalls. A well-designed API not only needs to do more, but also should do less with each level of abstraction, because preventing misuse is as important as enabling use cases. Date objects wear two hats simultaneously: As a timestamp : the number of milliseconds or nanoseconds elapsed since a fixed point in time (known as the epoch ). As a combination of components : year, month, day, hour, minute, second, millisecond, and nanosecond. The year, month, and day identifiers only make sense with reference to a calendar system . The whole combination maps to a unique instant in history when associated with a time zone. Date objects provide methods for reading and modifying these components. Time zones underlie a significant number of date-related bugs. When interacting with a Date via the "combination of components" model, the time can only be in two time zones: UTC and local (device), and there's no way to specify an arbitrary time zone. Also lacking is the concept of "no time zone": this is known as a calendar date (for dates) or wall-clock time (for times), which is a time you "read off a calendar or clock". For example, if you are setting a daily wake up alarm, you will want to set it to "8:00AM" regardless of whether it is daylight saving time or not, whether you have traveled to a different time zone, etc. A second feature lacking from Date is a calendar system . Most people may be familiar with the Gregorian calendar, where there are two eras, BC and AD; there are 12 months; each month has a different number of days; there's a leap year every 4 years; and so on. However, some of these concepts may not apply when you are working with another calendar system, such as the Hebrew calendar, the Chinese calendar, the Japanese calendar, etc. With Date , you can only work with the Gregorian calendar model. There are many other undesirable legacies about Date , such as all setters being mutating (which often causes unwanted side effects), the date time string format being impossible to parse in a consistent way, etc. In the end, the best solution is to build a new API from scratch, which is what Temporal is. API overview Temporal is a namespace, like Intl . It contains several classes and namespaces, each of which is designed to handle a specific aspect of date and time management. The classes can be grouped as such: Representing a time duration (a difference between two time points): Temporal.Duration Representing a time point: Representing a unique instant in history: As a timestamp: Temporal.Instant As a date-time component combination paired with a time zone: Temporal.ZonedDateTime Representing a time-zone-unaware date/time (which are all prefixed with "Plain"): Date (year, month, day) + time (hour, minute, second, millisecond, microsecond, nanosecond): Temporal.PlainDateTime (Note: ZonedDateTime is equivalent to PlainDateTime plus a time zone) Date (year, month, day): Temporal.PlainDate Year, month: Temporal.PlainYearMonth Month, day: Temporal.PlainMonthDay Time (hour, minute, second, millisecond, microsecond, nanosecond): Temporal.PlainTime Furthermore, there's also another utility namespace, Temporal.Now , which provides methods for getting the current time in various formats. Shared class interface There are many classes in the Temporal namespace, but they share many similar methods. The following table lists all methods of each class (except conversion methods ): Instant ZonedDateTime PlainDateTime PlainDate PlainTime PlainYearMonth PlainMonthDay Construction Instant() Instant.from() Instant.fromEpochMilliseconds() Instant.fromEpochNanoseconds() ZonedDateTime() ZonedDateTime.from() PlainDateTime() PlainDateTime.from() PlainDate() PlainDate.from() PlainTime() PlainTime.from() PlainYearMonth() PlainYearMonth.from() PlainMonthDay() PlainMonthDay.from() Updater N/A with() withCalendar() withTimeZone() withPlainTime() with() withCalendar() withPlainTime() with() withCalendar() with() with() with() Arithmetic add() subtract() since() until() add() subtract() since() until() add() subtract() since() until() add() subtract() since() until() add() subtract() since() until() add() subtract() since() until() N/A Rounding round() round() round() N/A round() N/A N/A Comparison equals() Instant.compare() equals() ZonedDateTime.compare() equals() PlainDateTime.compare() equals() PlainDate.compare() equals() PlainTime.compare() equals() PlainYearMonth.compare() equals() Serialization toJSON() toLocaleString() toString() valueOf() toJSON() toLocaleString() toString() valueOf() toJSON() toLocaleString() toString() valueOf() toJSON() toLocaleString() toString() valueOf() toJSON() toLocaleString() toString() valueOf() toJSON() toLocaleString() toString() valueOf() toJSON() toLocaleString() toString() valueOf() The following table summarizes which properties are available on each class, giving you a sense of what information each class can represent. Instant ZonedDateTime PlainDateTime PlainDate PlainTime PlainYearMonth PlainMonthDay Calendar N/A calendarId calendarId calendarId N/A calendarId calendarId Year-related N/A era eraYear year inLeapYear monthsInYear daysInYear era eraYear year inLeapYear monthsInYear daysInYear era eraYear year inLeapYear monthsInYear daysInYear N/A era eraYear year inLeapYear monthsInYear daysInYear N/A Month-related N/A month monthCode daysInMonth month monthCode daysInMonth month monthCode daysInMonth N/A month monthCode daysInMonth monthCode Week-related N/A weekOfYear yearOfWeek daysInWeek weekOfYear yearOfWeek daysInWeek weekOfYear yearOfWeek daysInWeek N/A N/A N/A Day-related N/A day dayOfWeek dayOfYear day dayOfWeek dayOfYear day dayOfWeek dayOfYear N/A N/A day Time components N/A hour minute second millisecond microsecond nanosecond hour minute second millisecond microsecond nanosecond N/A hour minute second millisecond microsecond nanosecond N/A N/A Time zone N/A timeZoneId offset offsetNanoseconds hoursInDay getTimeZoneTransition() startOfDay() N/A N/A N/A N/A N/A Epoch time epochMilliseconds epochNanoseconds epochMilliseconds epochNanoseconds N/A N/A N/A N/A N/A Conversion between classes The table below summarizes all conversion methods that exist on each class. How to convert from... Instant ZonedDateTime PlainDateTime PlainDate PlainTime PlainYearMonth PlainMonthDay to... Instant / toInstant() Convert to ZonedDateTime first ZonedDateTime toZonedDateTimeISO() / toZonedDateTime() toZonedDateTime() PlainDate#toZonedDateTime() (pass as argument) Convert to PlainDate first PlainDateTime Convert to ZonedDateTime first toPlainDateTime() / toPlainDateTime() PlainDate#toPlainDateTime() (pass as argument) PlainDate toPlainDate() toPlainDate() / No overlap in information toPlainDate() toPlainDate() PlainTime toPlainTime() toPlainTime() No overlap in information / No overlap in information PlainYearMonth Convert to PlainDate first toPlainYearMonth() No overlap in information / Convert to PlainDate first PlainMonthDay toPlainMonthDay() Convert to PlainDate first / With these tables, you should have a basic idea of how to navigate the Temporal API. Calendars A calendar is a way to organize days, typically into periods of weeks, months, years, and eras. Most of the world uses the Gregorian calendar, but there are many other calendars in use, especially in religious and cultural contexts. By default, all calendar-aware Temporal objects use the ISO 8601 calendar system, which is based on the Gregorian calendar and defines additional week-numbering rules. Intl.supportedValuesOf() lists most of the calendars likely to be supported by browsers. Here we provide a brief overview of how calendar systems are formed to help you internalize what factors may vary between calendars. There are three prominent periodic events on Earth: its rotation around the sun (365.242 days for one revolution), the moon's rotation around the Earth (29.53 days from new moon to new moon), and its rotation around its axis (24 hours from sunrise to sunrise). Every culture has the same measure of a "day", which is 24 hours. Occasional changes such as daylight saving time are not part of the calendar, but are part of the time zone 's information. Some calendars primarily define one year as 365.242 days on average, by defining years to have 365 days, and adding an extra day, the leap day , about every 4 years. Then, the year may be further divided into parts called months. These calendars are called solar calendars . The Gregorian calendar and the Solar Hijri calendar are solar calendars. Some calendars primarily define one month as 29.5 days on average, by defining months to alternate between 29 and 30 days. Then, 12 months may be grouped into a year of 354 days. These calendars are called lunar calendars . The Islamic calendar is a lunar calendar. Because a lunar year is artificial and does not correlate with the season cycle, lunar calendars are generally rarer. Some calendars also primarily define months based on lunar cycles, like lunar calendars. Then, to compensate for the 11-day discrepancy with the solar year, an extra month, the leap month , is added about every 3 years. These calendars are called lunisolar calendars . The Hebrew calendar and the Chinese calendar are lunisolar calendars. In Temporal , every date under one calendar system is uniquely identified by three components: year , month , and day . While year is typically a positive integer, it may also be zero or negative, and increases monotonically with time. The year 1 (or 0 , if it exists) is known as the calendar epoch, and is arbitrary for each calendar. month is a positive integer that increments by 1 every time, starting at 1 and ending at date.monthsInYear , then resetting back to 1 as the year advances. day is also a positive integer, but it may not start at 1 or increment by 1 every time, because political changes may cause days to be skipped or repeated. But in general, day monotonically increases and resets as the month advances. In addition to year , a year can also be uniquely identified by the combination of era and eraYear , for calendars that use eras. For example, the Gregorian calendar uses the era "CE" (Common Era) and "BCE" (Before Common Era), and the year -1 is the same as { era: "bce", eraYear: 2 } (note that year 0 always exists for all calendars; for the Gregorian calendar, it corresponds to 1 BCE due to astronomical year numbering ). era is a lowercase string, and eraYear is an arbitrary integer that may be zero or negative, or even decrease with time (usually for the oldest era). Note: Always use era and eraYear as a pair; don't use one property without also using the other. In addition, to avoid conflicts, don't combine year and era / eraYear when designating a year. Pick one year representation and use it consistently. Be careful of the following incorrect assumptions about years: Don't assume that era and eraYear are always present; they may be undefined . Don't assume that era is a user-friendly string; use toLocaleString() to format your date instead. Don't assume that two year values from different calendars are comparable; use the compare() static method instead. Don't assume that years have 365/366 days and 12 months; use daysInYear and monthsInYear instead. Don't assume that leap years ( inLeapYear is true ) have one extra day; they may have an extra month. In addition to month , a month in a year can also be uniquely identified by the monthCode . monthCode usually maps to the month's name, but month does not. For example, in the case of lunisolar calendars, two months with the same monthCode , where one belongs to a leap year and the other one does not, will have different month values if they come after the leap month, due to the insertion of an extra month. Note: To avoid conflicts, don't combine month and monthCode when designating a month. Pick one month representation and use it consistently. month is more useful if you need the order of months in a year (e.g., when looping through the months), while monthCode is more useful if you need the name of the month (e.g., when storing birthdays). Be careful of the following incorrect assumptions about months: Don't assume that monthCode and month always correspond. Don't assume the number of days in a month; use daysInMonth instead. Don't assume that monthCode is a user-friendly string; use toLocaleString() to format your date instead. Generally, don't cache the name of months in an array or object. Even though monthCode usually maps to the month's name within one calendar, we recommend always computing the month's name using, for example, date.toLocaleString("en-US", { calendar: date.calendarId, month: "long" }) . In addition to day (which is a month-based index), a day in a year can also be uniquely identified by the dayOfYear . dayOfYear is a positive integer that increments by 1 every time, starting at 1 and ending at date.daysInYear . The concept of a "week" is not connected with any astronomical event, but is a cultural construct. While the most common length is 7 days, weeks can also have 4, 5, 6, 8, or more days — or even lack a fixed number of days altogether. To get the specific number of days of the week of a date, use the date's daysInWeek . Temporal identifies weeks by the combination of weekOfYear and yearOfWeek . weekOfYear is a positive integer that increments by 1 every time, starting at 1 , then resetting back to 1 as the year advances. yearOfWeek is generally the same as year , but may be different at the start or end of each year, because one week may cross two years, and yearOfWeek picks one of the two years based on the calendar's rules. Note: Always use weekOfYear and yearOfWeek as a pair; don't use weekOfYear and year . Be careful of the following incorrect assumptions about weeks: Don't assume that weekOfYear and yearOfWeek are always present; they may be undefined . Don't assume that weeks are always 7 days long; use daysInWeek instead. Note that the current Temporal API does not support year-week dates, so you can't construct dates using these properties or serialize dates to year-week representations. They are only informational properties. RFC 9557 format All Temporal classes can be serialized and deserialized using the format specified in RFC 9557 , which is based on ISO 8601 / RFC 3339 . The format, in its full form, is as follows (spaces are only for readability and should not be present in the actual string): YYYY-MM-DD T HH:mm:ss.sssssssss Z/±HH:mm [time_zone_id] [u-ca=calendar_id] Different classes have different requirements for the presence of each component, so you will find a section titled "RFC 9557 format" in each class's documentation, which specifies the format recognized by that class. This is very similar to the date time string format used by Date , which is also based on ISO 8601. The main addition is the ability to specify micro- and nanosecond components, and the ability to specify the time zone and calendar system. Representable dates All Temporal objects that represent a specific calendar date impose a similar limit on the range of representable dates, which is ±10 8 days (inclusive) from the Unix epoch, or the range of instants from -271821-04-20T00:00:00 to +275760-09-13T00:00:00 . This is the same range as valid dates . More specifically: Temporal.Instant and Temporal.ZonedDateTime apply this limit directly on its epochNanoseconds value. Temporal.PlainDateTime interprets the date-time in the UTC time zone and requires it to be ±(10 8 + 1) days (exclusive) from the Unix epoch, so its valid range is -271821-04-19T00:00:00 to +275760-09-14T00:00:00 , exclusive. This allows any ZonedDateTime to be converted to a PlainDateTime regardless of its offset. Temporal.PlainDate applies the same check as PlainDateTime to the noon ( 12:00:00 ) of that date, so its valid range is -271821-04-19 to +275760-09-13 . This allows any PlainDateTime to be converted to a PlainDate regardless of its time, and vice versa. Temporal.PlainYearMonth has the valid range of -271821-04 to +275760-09 . This allows any PlainDate to be converted to a PlainYearMonth regardless of its date (except if a non-ISO month's first day falls in the ISO month -271821-03 ). The Temporal objects will refuse to construct an instance representing a date/time beyond this limit. This includes: Using the constructor or from() static method. Using the with() method to update calendar fields. Using add() , subtract() , round() , or any other method to derive new instances. Static properties Temporal.Duration Represents a difference between two time points, which can be used in date/time arithmetic. It is fundamentally represented as a combination of years, months, weeks, days, hours, minutes, seconds, milliseconds, microseconds, and nanoseconds values. Temporal.Instant Represents a unique point in time, with nanosecond precision. It is fundamentally represented as the number of nanoseconds since the Unix epoch (midnight at the beginning of January 1, 1970, UTC), without any time zone or calendar system. Temporal.Now Provides methods for getting the current time in various formats. Temporal.PlainDate Represents a calendar date (a date without a time or time zone); for example, an event on a calendar which happens during the whole day no matter which time zone it's happening in. It is fundamentally represented as an ISO 8601 calendar date, with year, month, and day fields, and an associated calendar system. Temporal.PlainDateTime Represents a date (calendar date) and time (wall-clock time) without a time zone. It is fundamentally represented as a combination of a date (with an associated calendar system) and a time . Temporal.PlainMonthDay Represents the month and day of a calendar date, without a year or time zone; for example, an event on a calendar that recurs every year and happens during the whole day. It is fundamentally represented as an ISO 8601 calendar date, with year, month, and day fields, and an associated calendar system. The year is used to disambiguate the month-day in non-ISO calendar systems. Temporal.PlainTime Represents a time without a date or time zone; for example, a recurring event that happens at the same time every day. It is fundamentally represented as a combination of hour, minute, second, millisecond, microsecond, and nanosecond values. Temporal.PlainYearMonth Represents the year and month of a calendar date, without a day or time zone; for example, an event on a calendar that happens during the whole month. It is fundamentally represented as an ISO 8601 calendar date, with year, month, and day fields, and an associated calendar system. The day is used to disambiguate the year-month in non-ISO calendar systems. Temporal.ZonedDateTime Represents a date and time with a time zone. It is fundamentally represented as a combination of an instant , a time zone, and a calendar system. Temporal[Symbol.toStringTag] The initial value of the [Symbol.toStringTag] property is the string "Temporal" . This property is used in Object.prototype.toString() . Specifications Specification Temporal # sec-temporal-objects Browser compatibility Enable JavaScript to view this browser compatibility table. See also Intl.DateTimeFormat Intl.RelativeTimeFormat Intl.DurationFormat Temporal polyfill by proposal champions Temporal polyfill by FullCalendar Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Dec 8, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar Standard built-in objects Temporal Related pages Temporal .Duration Temporal .Instant Temporal .Now Temporal .PlainDate Temporal .PlainDateTime Temporal .PlainMonthDay Temporal .PlainTime Temporal .PlainYearMonth Temporal .ZonedDateTime Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:49:02 |
https://dev.to/t/owl | Owl - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close # owl Follow Hide Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Odoo Core and the Cost of Reinventing Everything Boga Boga Boga Follow Jan 12 Odoo Core and the Cost of Reinventing Everything # python # odoo # qweb # owl Comments Add Comment 3 min read OWL JS 01 — Why Odoo Created OWL: A Framework Built for Modularity Trishan Fernando Trishan Fernando Trishan Fernando Follow Mar 31 '25 OWL JS 01 — Why Odoo Created OWL: A Framework Built for Modularity # odoo # owl # odooddevelopment # webdev Comments Add Comment 2 min read Stay Classy in OWL Paula Gearon Paula Gearon Paula Gearon Follow Nov 14 '22 Stay Classy in OWL # rdf # owl # sparql # rules 7 reactions Comments Add Comment 16 min read Classification Paula Gearon Paula Gearon Paula Gearon Follow Sep 28 '22 Classification # rdf # owl # sparql # rules Comments Add Comment 10 min read What Can't I do, as a Rule? Paula Gearon Paula Gearon Paula Gearon Follow Aug 22 '22 What Can't I do, as a Rule? # rdf # owl # sparql # rules 4 reactions Comments 4 comments 13 min read OWL in Odoo 14 - How to extend and patch existing OWL Components. Coding Dodo Coding Dodo Coding Dodo Follow Aug 15 '21 OWL in Odoo 14 - How to extend and patch existing OWL Components. # odoo # owl # javascript 8 reactions Comments 1 comment 13 min read RealWorld App with OWL (Odoo Web Library) - Part 1 Coding Dodo Coding Dodo Coding Dodo Follow Jun 7 '21 RealWorld App with OWL (Odoo Web Library) - Part 1 # owl # javascript # odoo 16 reactions Comments Add Comment 21 min read Ontologies - part I: Introduction Octa Octa Octa Follow Dec 2 '20 Ontologies - part I: Introduction # datascience # owl # beginners # ontology 5 reactions Comments Add Comment 2 min read Why Graph Will Win Kevin Feeney Kevin Feeney Kevin Feeney Follow for TerminusDB Community Mar 23 '20 Why Graph Will Win # owl # graphdatabase # rdf # database 5 reactions Comments Add Comment 6 min read loading... trending guides/resources Odoo Core and the Cost of Reinventing Everything 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/bogaboga1/odoo-core-and-the-cost-of-reinventing-everything-15n1#odoo-views | Odoo Core and the Cost of Reinventing Everything - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Boga Posted on Jan 12 Odoo Core and the Cost of Reinventing Everything # python # odoo # qweb # owl Hello, this is my first blog post ever. I’d like to share my experience working with Odoo , an open-source Enterprise Resource Planning (ERP) system, and explain why I believe many of its architectural choices cause unnecessary complexity. Odoo is a single platform that provides many prebuilt modules (mini-applications) that most companies need. For example, almost every company requires a Human Resources system to manage employee details, leaves, attendance, contracts, resignations, and more. Beyond HR, companies also need purchasing, inventory, accounting, authentication, authorization, and other systems. Odoo bundles all of these tightly coupled systems into a single installation. On paper, this sounds great — and from a business perspective, it often is. From a technical perspective , however, things get complicated very quickly. Odoo Core Components Below are the main Odoo components, ranked from least complex to most complex, and all largely developed in-house instead of relying on existing mature frameworks: Odoo HTTP Layer JSON-RPC Website routing Odoo Views XML transformed into Python and JavaScript Odoo ORM Custom inheritance system Query builder Dependency injection Caching layers Cache System Implemented from scratch WebSocket Implementation Very low-level handling Odoo HTTP Layer Odoo is not built on a standard Python web framework like Django or Flask. Instead, it implements its own HTTP framework on top of Werkzeug (a WSGI utility library). This HTTP layer introduces its own abstractions, request lifecycle, routing, and serialization logic, including JSON-RPC and website controllers. While technically impressive, it reinvents many problems that have already been solved — and battle-tested — by existing frameworks. Odoo Views In my opinion, this is one of the most problematic parts of Odoo. Instead of using standard frontend technologies, Odoo relies heavily on XML-based views . These XML files are sent to the browser and then transformed using Abstract Syntax Tree (AST) analysis into JavaScript. In other contexts (like the website), the XML may be converted into Python code and sometimes back into JavaScript again. This creates: High cognitive overhead Difficult debugging Tight coupling between backend and frontend Poor tooling support compared to modern frontend stacks It feels like building a car from raw metal just to drive from point A to point B. Odoo ORM Odoo’s ORM is not a typical ORM. It implements: A custom inheritance system (instead of using Python’s built-in one) Its own dependency injection mechanism A query builder Caching layers (LRU) Model extension via monkey-patching While powerful, this system is extremely complex and hard to reason about. Debugging model behavior often feels like navigating invisible layers of magic. WebSocket Implementation Instead of using a mature real-time framework, Odoo implements its WebSocket handling with very low-level logic, sometimes in surprisingly small and dense files. A single comment from the codebase summarizes this approach better than words ever could: The “Odoo Is Old” Argument A common defense of Odoo’s architecture is that “it’s an old system” — originally developed around 2005 using Python 2. However, this argument no longer holds. Odoo was largely rewritten from scratch around 2017 to support Python 3. At that time, many excellent frameworks already existed and had solved the same problems more cleanly, while continuing to evolve without breaking their ecosystems. Today, even small changes in Odoo’s core can break custom modules unless they are limited to simple CRUD models with minimal dependencies on core behavior. Final Thoughts Odoo is a powerful product and a successful business platform. But from a software engineering perspective, many of its design decisions prioritize control and internal consistency over maintainability, clarity, and developer experience . If you work with Odoo long enough, you stop asking “why does it work this way?” and start asking “how do I survive this upgrade?” Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Boga Follow Senior Software Engineer Joined Jan 12, 2026 Trending on DEV Community Hot 🧱 Beginner-Friendly Guide 'Maximal Rectangle' – LeetCode 85 (C++, Python, JavaScript) # programming # cpp # python # javascript The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning What was your win this week??? # weeklyretro # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/neisha1618/callbacks-vs-promises-4mi1#comment-22bml | Callbacks vs Promises - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Neisha Rose Posted on Apr 5, 2020 Callbacks vs Promises # javascript # callbacks # promises The Goal The goal is to achieve asynchronous code. Async code allows multiple things to happen at the same time. When you start an action, your program continues to run. When the action finishes, the program is informed and gets access to the result. We can achieve async code using two methods: callbacks and promises. With callback we pass a callback into a function that would then get called upon completion. With promises, you attach callbacks on the returned promise object. Callbacks A callback is a function that is to be executed after another function has finished executing. Async callbacks are functions that are passed as arguments. and when that function is called it will start executing code in the background. When the background code finishes running, it calls the callback function to let you know the work is done. We use these callbacks because we want to avoid executing things out of order. If we want to wait for something in JavaScript, we need to use a callback. Let’s make that pb&J from scratch using callbacks synchronous code This synchronous Peanut Butter & Jelly function runs in order, one function after another. but what if we had a function that needed to be ran first and other functions couldn't be ran until after this function finishes. Let’s think of making bread from scratch. you can’t put the peanut butter and jelly on the bread until it’s made so you must wait until its done. With synchronous code it doesn’t wait it just does it. How can we fix it? Async Callbacks We make an async callback so that we can make sure no other function runs until our bread is made. Let’s picture inside all the other functions there’s ample amounts of code to run. This can cause an issue because you can have plenty of nested callbacks inside one another. That leads to what we call callback hell. Callback hell can riddle code with bugs that are hard to catch. For this we need a way to make aync code while avoiding so many nested callbacks. Promises Promises are native to JavaScript, but you can also install promises libraries such as: Bluebird and Q. Promises are JavaScript objects that represent an eventual completion or failure of an asynchronous operation. A promise is a returned object where you attach callbacks, instead of passing callbacks into a function. the place where you attach the callback after a successful completion of a task is called, .then(). inside this you pass a callback through. What makes promises a way to avoid callback hell is that you can chain multiple .then() on each other which avoid nested callbacks and a neater line of code. For the failure of completing a task you can pass it through a .catch(). Let’s change our callback to a promise Here we take our PB&J function and turn it into a promise. We will first return the makeBread function and then on the successful completion of that function we will return a promise that will pass in the next callback to be ran. Next, we will chain on the other function that will be ran after that in order. thus, making async function. As you can see the code is neither and we avoid callback hell. We can also chain on an error message to the .catch() method and on that message "ewww crunchy peanut butter" because that will just ruin my sandwich. Final Promise Let’s make our promise a little bit neater by just passing in the callbacks. Conclusion Both callbacks and promises help make our code asynchronous. Making callbacks async can cause issues such as callback hell, so to avoid this we can use promises instead, doing this helps us avoid this pitfall while keeping our code async and neat. Top comments (3) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Devang patil Devang patil Devang patil Follow Javascript Developer Location Mumbai Education Be Comp Sci Work SSE at Race Joined Nov 22, 2019 • Oct 18 '22 Dropdown menu Copy link Hide async await makes more readable than promise I believe. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Mahesh Muttinti Mahesh Muttinti Mahesh Muttinti Follow I am a full stack web and mobile application developer. Email maheshmuttinti@gmail.com Location Hyderabad Work Not working Joined Dec 31, 2020 • Oct 17 '23 Dropdown menu Copy link Hide Indeed. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Kway Jaye Kway Jaye Kway Jaye Follow Joined Jun 2, 2024 • Aug 12 '24 Dropdown menu Copy link Hide Nice Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Neisha Rose Follow Returning to software engineering after a few years away. Currently rebuilding my skills in web development, WordPress, and JavaScript. Writing to stay accountable, share what I learn, and connect Location New Orleans, La Work IT Technician Joined Mar 4, 2020 More from Neisha Rose React and server side rendering with Next.js # react # webdev # javascript # codenewbie Navigating single page applications with React Router. # react # javascript # webdev # codenewbie Express Routing # webdev # javascript # beginners # express 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/about/help/#python-network | Help | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> About >>> Help Help New to programming and to Python? Check out the Beginner's Guide . New to Python? Read the standard tutorial . Look for a suitable book from a growing list of titles . Looking for code? See the download page for links to the Python interpreter. Explore the development repository . Got a Python problem or question? First check the Python FAQs , with answers to many common, general Python questions. The Python Help category of the discuss.python.org website hosts usage questions and answers from the Python community. The tutor list offers interactive help. If the tutor list isn't your cup of tea, there are many other mailing lists and newsgroups . Stack Overflow has many Python questions and answers . You can post questions and ask for general advice about your code at the r/LearnPython subreddit. If you suspect a bug in the Python core, search the Python Bug Tracker . If you think you've found a security vulnerability in Python, please read the instructions for reporting security issues . If you've found a problem with this web site, check the pythondotorg issue tracker . Looking for a particular Python module or application? Try the Python Package Index to browse and search an extensive list of registered packages. Want to contribute? To report a bug in the Python core, use the Python Bug Tracker . To report a problem with this web site, use the pythondotorg issue tracker . To contribute a bug fix or other patch to the Python core, see the Python Developer's Guide . To contribute to the official Python documentation , use the Issue Tracker to contribute a documentation patch. See also the guide to Helping with Documentation . To contribute to the official Python website, see the About the Python Web Site page or read the developer guide on Read the Docs . To announce your module or application to the Python community, use comp.lang.python.announce (or via email, python-announce@python.org , if you lack news access). More info: the announcements newsgroup description Need to contact the Python Software Foundation? Contact psf@python.org and let us know how we can help! Problems with this website? If you're having issues with python.org itself, contact webmaster@python.org and let us know how we can help! Other Issues? If you have a question not answered here, please reach out on discuss.python.org . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/about/help/#content | Help | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> About >>> Help Help New to programming and to Python? Check out the Beginner's Guide . New to Python? Read the standard tutorial . Look for a suitable book from a growing list of titles . Looking for code? See the download page for links to the Python interpreter. Explore the development repository . Got a Python problem or question? First check the Python FAQs , with answers to many common, general Python questions. The Python Help category of the discuss.python.org website hosts usage questions and answers from the Python community. The tutor list offers interactive help. If the tutor list isn't your cup of tea, there are many other mailing lists and newsgroups . Stack Overflow has many Python questions and answers . You can post questions and ask for general advice about your code at the r/LearnPython subreddit. If you suspect a bug in the Python core, search the Python Bug Tracker . If you think you've found a security vulnerability in Python, please read the instructions for reporting security issues . If you've found a problem with this web site, check the pythondotorg issue tracker . Looking for a particular Python module or application? Try the Python Package Index to browse and search an extensive list of registered packages. Want to contribute? To report a bug in the Python core, use the Python Bug Tracker . To report a problem with this web site, use the pythondotorg issue tracker . To contribute a bug fix or other patch to the Python core, see the Python Developer's Guide . To contribute to the official Python documentation , use the Issue Tracker to contribute a documentation patch. See also the guide to Helping with Documentation . To contribute to the official Python website, see the About the Python Web Site page or read the developer guide on Read the Docs . To announce your module or application to the Python community, use comp.lang.python.announce (or via email, python-announce@python.org , if you lack news access). More info: the announcements newsgroup description Need to contact the Python Software Foundation? Contact psf@python.org and let us know how we can help! Problems with this website? If you're having issues with python.org itself, contact webmaster@python.org and let us know how we can help! Other Issues? If you have a question not answered here, please reach out on discuss.python.org . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fpila%2Fconstructors-in-python-init-vs-new-2f9j&title=Constructors%20in%20Python%20%28__init%20vs%20__new__%29&summary=Most%20object-oriented%20programming%20languages%20such%20as%20Java%2C%20C%2B%2B%2C%20C%23..etc%20have%20the%20concept%20of%20a%20construct...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:02 |
https://www.python.org/about/help/#site-map | Help | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> About >>> Help Help New to programming and to Python? Check out the Beginner's Guide . New to Python? Read the standard tutorial . Look for a suitable book from a growing list of titles . Looking for code? See the download page for links to the Python interpreter. Explore the development repository . Got a Python problem or question? First check the Python FAQs , with answers to many common, general Python questions. The Python Help category of the discuss.python.org website hosts usage questions and answers from the Python community. The tutor list offers interactive help. If the tutor list isn't your cup of tea, there are many other mailing lists and newsgroups . Stack Overflow has many Python questions and answers . You can post questions and ask for general advice about your code at the r/LearnPython subreddit. If you suspect a bug in the Python core, search the Python Bug Tracker . If you think you've found a security vulnerability in Python, please read the instructions for reporting security issues . If you've found a problem with this web site, check the pythondotorg issue tracker . Looking for a particular Python module or application? Try the Python Package Index to browse and search an extensive list of registered packages. Want to contribute? To report a bug in the Python core, use the Python Bug Tracker . To report a problem with this web site, use the pythondotorg issue tracker . To contribute a bug fix or other patch to the Python core, see the Python Developer's Guide . To contribute to the official Python documentation , use the Issue Tracker to contribute a documentation patch. See also the guide to Helping with Documentation . To contribute to the official Python website, see the About the Python Web Site page or read the developer guide on Read the Docs . To announce your module or application to the Python community, use comp.lang.python.announce (or via email, python-announce@python.org , if you lack news access). More info: the announcements newsgroup description Need to contact the Python Software Foundation? Contact psf@python.org and let us know how we can help! Problems with this website? If you're having issues with python.org itself, contact webmaster@python.org and let us know how we can help! Other Issues? If you have a question not answered here, please reach out on discuss.python.org . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://dev.to/pila/constructors-in-python-init-vs-new-2f9j#comment-1c7jo | Constructors in Python (__init vs __new__) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pila louis Posted on Sep 16, 2020 Constructors in Python (__init vs __new__) # python # programming # 100daysofcode Most object-oriented programming languages such as Java, C++, C#..etc have the concept of a constructor, a special method that creates and initializes the object when it is created. Python is a little different; it has a constructor and an initializer. The constructor function is rarely used unless you're doing something exotic. So, we'll start our discussion with the initialization method. The assumption in this article is that you already know the basics of classes and objects in python. The constructor function in python is called __new__ and __init__ is the initializer function. Quoting the python documentation, __new__ is used when you need to control the creation of a new instance while __init__ is used when you need to control the initialization of a new instance. __new__ is the first step of instance creation. It's called first and is responsible for returning a new instance of your class. In contrast, __init__ doesn't return anything; it's only responsible for initializing the instance after it's been created. In general, you shouldn't need to override __new__ unless you're subclassing an immutable type like str, int, Unicode, or tuple. NOTE: Never name a function of your own with leading and trailing double underscores. It may mean nothing to Python, but there's always the possibility that the designers of Python will add a function that has a special purpose with that name in the future, and when they do, your code will break. Example 1: Using __init__ class Point: def __init__(self, data): self.num = data def print_num(self): print(self.num) obj = Point(100) obj.print_num() Output: 100 Note: The self parameter is a reference to the current instance of the class and is used to access variables that belong to the class. Example 2: class Person: def __new__(cls): return object.__new__(cls) def __init__(self): self.instance_method() def instance_method(self): print('success!') personObj = Person() Notice that __init__ receives the argument self, while __new__ receives the class (cls ). Since self is a reference to the instance, this should tell you quite evidently that the instance is already created by the time __init__ gets called, since it gets passed the instance. It's also possible to call instance methods precisely because the instance has already been created. Thank you for reading. 😄 END!!! Top comments (3) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Tongyu Lu Tongyu Lu Tongyu Lu Follow High school student at PRISMS. Interested in CS, ML, game-dev. USACO Platinum qualified, but still getting better at projects. Codes for fun. Location Earth Education https://prismsus.org Joined Jul 30, 2020 • Mar 7 '21 • Edited on Mar 7 • Edited Dropdown menu Copy link Hide You can actually use super (). method_name ( * args , ** kw ) # PEP 3135 Enter fullscreen mode Exit fullscreen mode In this case, it can be super (). __new__ ( cls , * args , ** kw ) Enter fullscreen mode Exit fullscreen mode The cls is actually necessary for __new__ . See more about PEP 3135 → Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Adyasha Mohanty Adyasha Mohanty Adyasha Mohanty Follow talks in bits believe in queue DS life is abstract data type Joined Feb 25, 2024 • Feb 25 '24 Dropdown menu Copy link Hide Thank you for making me clear in new and init Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matheesha Matheesha Matheesha Follow Joined Jun 6, 2024 • Jul 6 '24 Dropdown menu Copy link Hide So are people teaching wrong when they call __init__ the constructor? 🤔 Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pila louis Follow Full-stack software engineer with over 3years of industrial experience. I work well in a fast-paced environment. I am able to rise up to whatever it takes to make an impact in a new environment. Work Software Engineer at Chatdesk, Inc Joined Nov 11, 2019 Trending on DEV Community Hot How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview I Am 38, I Am a Nurse, and I Have Always Wanted to Learn Coding # career # learning # beginners # coding AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/about/help/#top | Help | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> About >>> Help Help New to programming and to Python? Check out the Beginner's Guide . New to Python? Read the standard tutorial . Look for a suitable book from a growing list of titles . Looking for code? See the download page for links to the Python interpreter. Explore the development repository . Got a Python problem or question? First check the Python FAQs , with answers to many common, general Python questions. The Python Help category of the discuss.python.org website hosts usage questions and answers from the Python community. The tutor list offers interactive help. If the tutor list isn't your cup of tea, there are many other mailing lists and newsgroups . Stack Overflow has many Python questions and answers . You can post questions and ask for general advice about your code at the r/LearnPython subreddit. If you suspect a bug in the Python core, search the Python Bug Tracker . If you think you've found a security vulnerability in Python, please read the instructions for reporting security issues . If you've found a problem with this web site, check the pythondotorg issue tracker . Looking for a particular Python module or application? Try the Python Package Index to browse and search an extensive list of registered packages. Want to contribute? To report a bug in the Python core, use the Python Bug Tracker . To report a problem with this web site, use the pythondotorg issue tracker . To contribute a bug fix or other patch to the Python core, see the Python Developer's Guide . To contribute to the official Python documentation , use the Issue Tracker to contribute a documentation patch. See also the guide to Helping with Documentation . To contribute to the official Python website, see the About the Python Web Site page or read the developer guide on Read the Docs . To announce your module or application to the Python community, use comp.lang.python.announce (or via email, python-announce@python.org , if you lack news access). More info: the announcements newsgroup description Need to contact the Python Software Foundation? Contact psf@python.org and let us know how we can help! Problems with this website? If you're having issues with python.org itself, contact webmaster@python.org and let us know how we can help! Other Issues? If you have a question not answered here, please reach out on discuss.python.org . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://walzr.com/ | Riley Walz Riley Walz IMG_0001: watch unnamed YouTube videos Bop Spotter: I put a mic on the street that Shazams, 24/7 Routeshuffle: Random route generator for runners and cyclists Mehran's Steak House: Made a fake steakhouse real for one night Andrew Walz: Created a fake candidate for Congress that Twitter verified Find My Parking Cops: Tracking San Francisco parking cops Looksmapping: Finding which restaurants the hottest people go to Panama Playlists: Leaking the Spotify playlists of celebrities Weather Watching: A camera that counts what layers people are wearing Papers: Archive of newspaper frontpages Chyrons: Archive of television news headlines Library Spy: Tracking what books people check out of a NYC library branch Fast Food Index: Comparing fast food prices across the country Postal Arbitrage: Send letters with Prime. It's cheaper than a stamp! Fire damage: Before and after photos of homes destroyed by 2025 wildfires 911 call stream: Emergency calls in San Francisco, mapped Blog 2024: Year in Review What a small world 2023: Year in Review Unclaimed property 2022: Year in Review 2021: Year in Review Perimeter Random Jobs Passing by Pictures When it's all over Following the rules Groceries Check & Go Music memories The bike lane The Secret Elevator at Penn Station Live streaming my high school graduation This Candidate Does Not Exist Schools Gone Virus WWDC scholarship Bump Touring Google New project Email , @rtwlz | 2026-01-13T08:49:02 |
https://reactjs.org/docs/getting-started.html#undefined | Quick Start – React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog GET STARTED Quick Start Tutorial: Tic-Tac-Toe Thinking in React Installation Creating a React App Build a React App from Scratch Add React to an Existing Project Setup Editor Setup Using TypeScript React Developer Tools React Compiler Introduction Installation Incremental Adoption Debugging and Troubleshooting LEARN REACT Describing the UI Your First Component Importing and Exporting Components Writing Markup with JSX JavaScript in JSX with Curly Braces Passing Props to a Component Conditional Rendering Rendering Lists Keeping Components Pure Your UI as a Tree Adding Interactivity Responding to Events State: A Component's Memory Render and Commit State as a Snapshot Queueing a Series of State Updates Updating Objects in State Updating Arrays in State Managing State Reacting to Input with State Choosing the State Structure Sharing State Between Components Preserving and Resetting State Extracting State Logic into a Reducer Passing Data Deeply with Context Scaling Up with Reducer and Context Escape Hatches Referencing Values with Refs Manipulating the DOM with Refs Synchronizing with Effects You Might Not Need an Effect Lifecycle of Reactive Effects Separating Events from Effects Removing Effect Dependencies Reusing Logic with Custom Hooks Is this page useful? Learn React Quick Start Welcome to the React documentation! This page will give you an introduction to 80% of the React concepts that you will use on a daily basis. You will learn How to create and nest components How to add markup and styles How to display data How to render conditions and lists How to respond to events and update the screen How to share data between components Creating and nesting components React apps are made out of components . A component is a piece of the UI (user interface) that has its own logic and appearance. A component can be as small as a button, or as large as an entire page. React components are JavaScript functions that return markup: function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } Now that you’ve declared MyButton , you can nest it into another component: export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Notice that <MyButton /> starts with a capital letter. That’s how you know it’s a React component. React component names must always start with a capital letter, while HTML tags must be lowercase. Have a look at the result: App.js App.js Reload Clear Fork function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Show more The export default keywords specify the main component in the file. If you’re not familiar with some piece of JavaScript syntax, MDN and javascript.info have great references. Writing markup with JSX The markup syntax you’ve seen above is called JSX . It is optional, but most React projects use JSX for its convenience. All of the tools we recommend for local development support JSX out of the box. JSX is stricter than HTML. You have to close tags like <br /> . Your component also can’t return multiple JSX tags. You have to wrap them into a shared parent, like a <div>...</div> or an empty <>...</> wrapper: function AboutPage ( ) { return ( < > < h1 > About </ h1 > < p > Hello there. < br /> How do you do? </ p > </ > ) ; } If you have a lot of HTML to port to JSX, you can use an online converter. Adding styles In React, you specify a CSS class with className . It works the same way as the HTML class attribute: < img className = "avatar" /> Then you write the CSS rules for it in a separate CSS file: /* In your CSS */ .avatar { border-radius : 50 % ; } React does not prescribe how you add CSS files. In the simplest case, you’ll add a <link> tag to your HTML. If you use a build tool or a framework, consult its documentation to learn how to add a CSS file to your project. Displaying data JSX lets you put markup into JavaScript. Curly braces let you “escape back” into JavaScript so that you can embed some variable from your code and display it to the user. For example, this will display user.name : return ( < h1 > { user . name } </ h1 > ) ; You can also “escape into JavaScript” from JSX attributes, but you have to use curly braces instead of quotes. For example, className="avatar" passes the "avatar" string as the CSS class, but src={user.imageUrl} reads the JavaScript user.imageUrl variable value, and then passes that value as the src attribute: return ( < img className = "avatar" src = { user . imageUrl } /> ) ; You can put more complex expressions inside the JSX curly braces too, for example, string concatenation : App.js App.js Reload Clear Fork const user = { name : 'Hedy Lamarr' , imageUrl : 'https://i.imgur.com/yXOvdOSs.jpg' , imageSize : 90 , } ; export default function Profile ( ) { return ( < > < h1 > { user . name } </ h1 > < img className = "avatar" src = { user . imageUrl } alt = { 'Photo of ' + user . name } style = { { width : user . imageSize , height : user . imageSize } } /> </ > ) ; } Show more In the above example, style={{}} is not a special syntax, but a regular {} object inside the style={ } JSX curly braces. You can use the style attribute when your styles depend on JavaScript variables. Conditional rendering In React, there is no special syntax for writing conditions. Instead, you’ll use the same techniques as you use when writing regular JavaScript code. For example, you can use an if statement to conditionally include JSX: let content ; if ( isLoggedIn ) { content = < AdminPanel /> ; } else { content = < LoginForm /> ; } return ( < div > { content } </ div > ) ; If you prefer more compact code, you can use the conditional ? operator. Unlike if , it works inside JSX: < div > { isLoggedIn ? ( < AdminPanel /> ) : ( < LoginForm /> ) } </ div > When you don’t need the else branch, you can also use a shorter logical && syntax : < div > { isLoggedIn && < AdminPanel /> } </ div > All of these approaches also work for conditionally specifying attributes. If you’re unfamiliar with some of this JavaScript syntax, you can start by always using if...else . Rendering lists You will rely on JavaScript features like for loop and the array map() function to render lists of components. For example, let’s say you have an array of products: const products = [ { title : 'Cabbage' , id : 1 } , { title : 'Garlic' , id : 2 } , { title : 'Apple' , id : 3 } , ] ; Inside your component, use the map() function to transform an array of products into an array of <li> items: const listItems = products . map ( product => < li key = { product . id } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; Notice how <li> has a key attribute. For each item in a list, you should pass a string or a number that uniquely identifies that item among its siblings. Usually, a key should be coming from your data, such as a database ID. React uses your keys to know what happened if you later insert, delete, or reorder the items. App.js App.js Reload Clear Fork const products = [ { title : 'Cabbage' , isFruit : false , id : 1 } , { title : 'Garlic' , isFruit : false , id : 2 } , { title : 'Apple' , isFruit : true , id : 3 } , ] ; export default function ShoppingList ( ) { const listItems = products . map ( product => < li key = { product . id } style = { { color : product . isFruit ? 'magenta' : 'darkgreen' } } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; } Show more Responding to events You can respond to events by declaring event handler functions inside your components: function MyButton ( ) { function handleClick ( ) { alert ( 'You clicked me!' ) ; } return ( < button onClick = { handleClick } > Click me </ button > ) ; } Notice how onClick={handleClick} has no parentheses at the end! Do not call the event handler function: you only need to pass it down . React will call your event handler when the user clicks the button. Updating the screen Often, you’ll want your component to “remember” some information and display it. For example, maybe you want to count the number of times a button is clicked. To do this, add state to your component. First, import useState from React: import { useState } from 'react' ; Now you can declare a state variable inside your component: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; // ... You’ll get two things from useState : the current state ( count ), and the function that lets you update it ( setCount ). You can give them any names, but the convention is to write [something, setSomething] . The first time the button is displayed, count will be 0 because you passed 0 to useState() . When you want to change state, call setCount() and pass the new value to it. Clicking this button will increment the counter: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } React will call your component function again. This time, count will be 1 . Then it will be 2 . And so on. If you render the same component multiple times, each will get its own state. Click each button separately: App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } Show more Notice how each button “remembers” its own count state and doesn’t affect other buttons. Using Hooks Functions starting with use are called Hooks . useState is a built-in Hook provided by React. You can find other built-in Hooks in the API reference. You can also write your own Hooks by combining the existing ones. Hooks are more restrictive than other functions. You can only call Hooks at the top of your components (or other Hooks). If you want to use useState in a condition or a loop, extract a new component and put it there. Sharing data between components In the previous example, each MyButton had its own independent count , and when each button was clicked, only the count for the button clicked changed: Initially, each MyButton ’s count state is 0 The first MyButton updates its count to 1 However, often you’ll need components to share data and always update together . To make both MyButton components display the same count and update together, you need to move the state from the individual buttons “upwards” to the closest component containing all of them. In this example, it is MyApp : Initially, MyApp ’s count state is 0 and is passed down to both children On click, MyApp updates its count state to 1 and passes it down to both children Now when you click either button, the count in MyApp will change, which will change both of the counts in MyButton . Here’s how you can express this in code. First, move the state up from MyButton into MyApp : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { // ... we're moving code from here ... } Then, pass the state down from MyApp to each MyButton , together with the shared click handler. You can pass information to MyButton using the JSX curly braces, just like you previously did with built-in tags like <img> : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } The information you pass down like this is called props . Now the MyApp component contains the count state and the handleClick event handler, and passes both of them down as props to each of the buttons. Finally, change MyButton to read the props you have passed from its parent component: function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } When you click the button, the onClick handler fires. Each button’s onClick prop was set to the handleClick function inside MyApp , so the code inside of it runs. That code calls setCount(count + 1) , incrementing the count state variable. The new count value is passed as a prop to each button, so they all show the new value. This is called “lifting state up”. By moving state up, you’ve shared it between components. App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } Show more Next Steps By now, you know the basics of how to write React code! Check out the Tutorial to put them into practice and build your first mini-app with React. Next Tutorial: Tic-Tac-Toe Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms On this page Overview Creating and nesting components Writing markup with JSX Adding styles Displaying data Conditional rendering Rendering lists Responding to events Updating the screen Using Hooks Sharing data between components Next Steps | 2026-01-13T08:49:02 |
https://www.python.org/download/other/#site-map | Download Python for other platforms | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Downloads >>> Other Platforms Download Python for other platforms Python has been ported to a number of specialized and/or older platforms, listed below in alphabetical order. Note that these ports often lag well behind the latest Python release. Python for AIX AIX binary packages for Python are available from IBM AIX Toolbox in RPM format. They can be installed using dnf package manager. Visit the Get Started page for more details. `_ is a port to the `Amiga Research OS `_. Tim Ocock maintains `AmigaPython `_. Older versions of Python for the Amiga can be found at `Aminet `_. --> `_. For all Python-related stuff on BeOS, `search here `_. --> Python for HP-UX You can purchase ActivePython (commercial and community versions, including scientific computing modules, not open source) Python for IBM i (formerly AS/400, iSeries) Both Python 2 and Python 3 are available from IBM in RPM form. They can be installed with the yum package manager or with the IBM i Access Client Solutions product. To get started with RPM-based open source packages for IBM i, visit http://ibm.biz/ibmi-rpms . These RPM packages require a version of IBM i in active (not extended) support. Python for iOS and iPadOS Briefcase (from the BeeWare project) and Buildozer (from the Kivy project) are two tools that can be used to deploy Python code as an iOS app. Python-Apple-support is a project that provides pre-compiled Python frameworks that can be embedded into an Xcode project. PythonKit can be used to provide Swift integration with Python. Pythonista is a complete development environment for writing Python scripts including third-party libraries and system integration on your iPad or iPhone. Pyto also provides a complete development environment for running Python 3 including many third-party libraries and system integration on an iPad or iPhone. Alternate Python packages for Linux You can purchase ActivePython (commercial and community versions, including scientific computing modules, not open source) `_. --> `_, built on the DJGPP platform, is also available. --> `_. --> `_. --> `__ once completed a port of Python to the Sony PlayStation 2. Contact him for more info. --> `__. It has most modules running and can even use the PSP's built in wifi, albeit awkwardly. --> `_. --> `_ --> Python for RISC OS Python is available for RISC OS, and can be obtained using the PackMan package manager. `__ can be found at archive.org. This page also includes some pre-ported external libraries as well as RISC OS specific extensions and documentation, written by Dietmar Schwertberger. --> `_. There are downloads available at ` `_. --> Python for Solaris You can purchase ActivePython (commercial and community versions, including scientific computing modules, not open source), or build from source if you have a C compiler. UNIX Packages has a variety of Python versions for a variety of Solaris versions. These use the standard Sun pkgadd. Python for UEFI Environment Standard CPython version 3.6.8 port for the Unified Extensible Firmware Interface (UEFI) shell environment is available through the Tianocore open source project. This provides the standard Python scripting capabilities on UEFI environment, helping the UEFI based firmware and platform developer community to use it for platform, firmware validation, debug and the like. Python for UEFI source code and build instructions are available here . Currently build support is enabled using VS2019 and GCC5 tool chains for x86 and x64 bit platforms. `_ is available. --> `__. --> `_ page. --> Python for z/OS `_ has a ported version of Python 2.4.1. --> Rocket Software provides a port of Python for z/OS . Python for z/OS is available from IBM for no license charge. It is available in PAX format from Early Programs Web Tool or SMP/E format from Shopz . Optional no-cost Subscription and Support (S&S) is available in the Shopz ordering process. Please visit the IBM Open Enterprise SDK for Python product page for more information. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://dev.to/pila/constructors-in-python-init-vs-new-2f9j#main-content | Constructors in Python (__init vs __new__) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pila louis Posted on Sep 16, 2020 Constructors in Python (__init vs __new__) # python # programming # 100daysofcode Most object-oriented programming languages such as Java, C++, C#..etc have the concept of a constructor, a special method that creates and initializes the object when it is created. Python is a little different; it has a constructor and an initializer. The constructor function is rarely used unless you're doing something exotic. So, we'll start our discussion with the initialization method. The assumption in this article is that you already know the basics of classes and objects in python. The constructor function in python is called __new__ and __init__ is the initializer function. Quoting the python documentation, __new__ is used when you need to control the creation of a new instance while __init__ is used when you need to control the initialization of a new instance. __new__ is the first step of instance creation. It's called first and is responsible for returning a new instance of your class. In contrast, __init__ doesn't return anything; it's only responsible for initializing the instance after it's been created. In general, you shouldn't need to override __new__ unless you're subclassing an immutable type like str, int, Unicode, or tuple. NOTE: Never name a function of your own with leading and trailing double underscores. It may mean nothing to Python, but there's always the possibility that the designers of Python will add a function that has a special purpose with that name in the future, and when they do, your code will break. Example 1: Using __init__ class Point: def __init__(self, data): self.num = data def print_num(self): print(self.num) obj = Point(100) obj.print_num() Output: 100 Note: The self parameter is a reference to the current instance of the class and is used to access variables that belong to the class. Example 2: class Person: def __new__(cls): return object.__new__(cls) def __init__(self): self.instance_method() def instance_method(self): print('success!') personObj = Person() Notice that __init__ receives the argument self, while __new__ receives the class (cls ). Since self is a reference to the instance, this should tell you quite evidently that the instance is already created by the time __init__ gets called, since it gets passed the instance. It's also possible to call instance methods precisely because the instance has already been created. Thank you for reading. 😄 END!!! Top comments (3) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Tongyu Lu Tongyu Lu Tongyu Lu Follow High school student at PRISMS. Interested in CS, ML, game-dev. USACO Platinum qualified, but still getting better at projects. Codes for fun. Location Earth Education https://prismsus.org Joined Jul 30, 2020 • Mar 7 '21 • Edited on Mar 7 • Edited Dropdown menu Copy link Hide You can actually use super (). method_name ( * args , ** kw ) # PEP 3135 Enter fullscreen mode Exit fullscreen mode In this case, it can be super (). __new__ ( cls , * args , ** kw ) Enter fullscreen mode Exit fullscreen mode The cls is actually necessary for __new__ . See more about PEP 3135 → Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Adyasha Mohanty Adyasha Mohanty Adyasha Mohanty Follow talks in bits believe in queue DS life is abstract data type Joined Feb 25, 2024 • Feb 25 '24 Dropdown menu Copy link Hide Thank you for making me clear in new and init Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matheesha Matheesha Matheesha Follow Joined Jun 6, 2024 • Jul 6 '24 Dropdown menu Copy link Hide So are people teaching wrong when they call __init__ the constructor? 🤔 Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pila louis Follow Full-stack software engineer with over 3years of industrial experience. I work well in a fast-paced environment. I am able to rise up to whatever it takes to make an impact in a new environment. Work Software Engineer at Chatdesk, Inc Joined Nov 11, 2019 Trending on DEV Community Hot How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview I Am 38, I Am a Nurse, and I Have Always Wanted to Learn Coding # career # learning # beginners # coding AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://zeroday.forem.com/about#main-content | About Zero Day Security Community - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close About Zero Day Security Community About the Zero Day Security Community Welcome to Zero Day, the ultimate hub for security professionals, enthusiasts, students, and anyone passionate about the world of security. Whether you're a seasoned CISO, a curious student, or a developer looking to write more secure code, you've found your home. Our Mission Our mission is to create a central, inclusive, and authoritative online community dedicated to fostering collaboration, knowledge sharing, and skill development across all domains of security. We believe in breaking down silos and building bridges between the theoretical and the practical, the digital and the physical. What We're All About Zero Day is a space for deep, meaningful discussion and learning. We are built on a few core principles: Knowledge First: We prioritize accurate, vetted, and practical information. We're here to learn from each other and elevate our collective expertise. Radical Inclusivity: Gatekeeping has no place here. We welcome all skill levels, from absolute beginners to world-renowned experts. We are a community dedicated to mentorship and support, not judgment. Strong Ethical Foundation: We are a strictly white-hat community. All discussions and activities are guided by a commitment to ethical hacking, responsible disclosure, and using our skills for good. What to Expect Here, you'll find a wide range of content and discussions covering the entire security landscape. We encourage posts, questions, and articles on topics like: Offensive Security (Red Team): From web app pentesting and exploit development to social engineering and adversary emulation. Defensive Security (Blue Team): Dive into threat intelligence, digital forensics, incident response (DFIR), and malware analysis. Cloud & Application Security: Explore DevSecOps, secure coding practices, cryptography, and securing cloud infrastructure (AWS, Azure, GCP). Governance, Risk & Compliance (GRC): Discuss frameworks like NIST and ISO 27001, risk management, and compliance challenges. Physical & Hardware Security: Explore everything from lockpicking and access control to IoT and embedded systems hacking. Career & Professional Development: Share advice on certifications (OSCP, CISSP, etc.), get resume feedback, and discuss interview experiences. How to Get Involved This community is powered by you! Here are a few ways to jump in: Introduce Yourself: Head over to the introductions thread and tell us about your interests. Ask Questions: No question is too basic. We are all here to learn. Share Your Knowledge: Write a post about a project you're working on, a tool you love, or a concept you've mastered. Join the Conversation: Upvote quality content and add your perspective to ongoing discussions. Set Your Flair: Edit your profile to add flair that shows your specialty (e.g., Pentester, DFIR, GRC, Student). We're thrilled to have you here. Let's build the best security community on the web, together. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:02 |
https://www3.nhk.or.jp/nhkworld/en/shows/2074236/ | Looking through Digital AIs - BIZ STREAM | NHK WORLD-JAPAN Shows Home Video Audio Categories Anime & Manga Art & Design Biz & Tech Culture & Lifestyle Current Affairs Debate Disaster Preparedness Documentary Drama Entertainment Food Interactive Interview Kids Learn Japanese News Pop Culture & Fashion Science & Nature Sports Travel Japan Navigator My List Looking through Digital AIs [On-Site Report: Looking through Digital AIs] This episode features services that are using image recognition technology to make a positive impact on our daily lives. *Subtitles and transcripts are available for video segments when viewed on our website. On-Site Report: Looking through Digital AIs Counterfeit detection software analyzes specific parts of a sneaker or other products to prevent the sale of fake luxury goods. A smartphone app for the visually impaired warns them of a variety of obstacles and guides them out of potentially dangerous situations. Global Trends: Research in Space on a Shoestring Research in space has long been a source of fascination because of conditions not found on Earth, such as low gravity and a vacuum environment. A Japanese startup is working to make such research possible at a lower cost, without the need for astronauts. One sake brewery hopes research into yeast will lead to a sake "born in space." A tech startup is developing a lens-free microscope with a tiny sensor to carry out unmanned, low-cost experiments in space. In Focus: History Shows Pressuring Fed May Not End Well US President Donald Trump is ramping up pressure on the Federal Reserve. He’s trying to fire one of its governors, while getting it to lower interest rates. That raising fears that the Fed's independence could be undermined. Transcript 03:23 "She seems to have had an infraction, and she can't have an infraction, 03:28 especially that infraction because she's in charge of, if you think about it, mortgages. 03:32 And we need people that are 100 percent above board, and it doesn't seem like she was." 03:38 Trump said in a letter to Cook there was "sufficient reason" to believe she had made false statements. 03:45 But many have suggested his real goal is to assert control over the Fed. 03:50 At its last policy meeting in July, 03:53 Cook voted alongside Chair Jerome Powell to keep rates unchanged. 03:58 If Trump succeeds in getting rid of her, 04:00 he can appoint someone more likely to vote his way. 04:04 "We have some very good people for that position. 04:07 And I think we have some very good people, we're down to - 04:10 I think, maybe, in my own mind, 04:12 have somebody that I like, then we'll have a majority very shortly. 04:16 So that'll be great." 04:17 But Cook isn't going quietly. 04:20 She's filed suit against the dismissal attempt. 04:23 The initial court hearing on August 29th ended without a clear decision, 04:27 and the fight is likely to drag on. 04:34 Markets didn't react much to Trump's announcement. 04:37 But it came just weeks after he fired the commissioner of the Bureau of Labor Statistics. 04:42 That has economy watchers worried the Fed's independence could be at real risk. 04:49 "Wall Street is concerned about the decision to fire Lisa Cook 04:53 mainly because we haven't seen this level of government involvement 04:57 within Fed decision-making in a very long time, if ever. 05:01 If any Fed voting members change their mind 05:04 on what they're going to do based on that decision. 05:07 I think if we do see a lot of the hawkish members 05:10 from last meeting flipped to dovish because of this, 05:13 it's a real concern when it comes to the independence of the Fed itself." 05:17 Others suggest Trump wants to weaken the dollar through rate cuts, 05:21 helping reduce the trade deficit. 05:23 But all the tariffs he's imposed are fueling inflationary pressure. 05:27 Lower rates could just add to that, requiring rates to go up to bring inflation down. 05:34 "If officials loosen monetary policy despite inflationary pressure, prices could really soar. 05:40 Eventually, the central bank would have to adopt a policy of high rates to fight inflation, 05:45 regardless of the conditions. 05:47 Moreover, it would be too late to curb prices. 05:50 The time to bring the situation under control would have passed." 05:57 History has a lesson to teach about all of this. 06:00 Ahead of the election in 1972, President Richard Nixon pushed the Fed Chair at the time, Arthur Burns, 06:08 to loosen monetary policy. 06:11 Americans ended up paying the price, 06:13 as high inflation set in until another Fed chair came in and rates began rising sharply. 06:20 So from history, we learn lowering rates in an inflationary environment 06:24 can lead straight into "stagflation." 06:27 That's high inflation with weak growth. 06:30 But it's not at all clear what lessons the current president learns from history. 09:24 This sake brewery in the western city of Kobe is over 360 years old. 09:32 The company has announced it is undertaking an experiment that could shape the future of sake brewing. 09:39 "By doing experiments in space, we may discover new and exciting possibilities." 09:47 But what on Earth is it sending into space? 09:51 It's one of the most basic elements in sake - yeast. 09:55 The brewer wants to see how yeast behaves under microgravity. 10:01 If the yeast changes, it could lead to entirely new strains. 10:09 That could ultimately result in a new type of sake, "born in space." 10:16 "As a luxury product, sake faces intense development competition. 10:21 So the story behind it is key to making it stand out. 10:25 We don't know yet what space can offer, 10:27 but we want to find out, without spending too much money." 10:33 All of this is being made possible by a startup. 10:39 It's developing a platform to carry out unmanned experiments in space at a low cost. 10:46 By using satellites rather than the space station, 10:49 it plans to offer services starting at around 10 million yen, or 67,000 dollars. 10:56 This is an experimental device now under development. 11:01 "We're creating a lens-free microscope that is extremely compact." 11:06 At its core is a sensor less than 7 millimeters wide. 11:11 A fine mesh detects light, converts it into images, and then zooms them. 11:19 Here's what happens when a droplet of water is placed on it. 11:24 Microorganisms smaller than one-hundredth of a millimeter come to life on screen, 11:30 automatically tracked in real time. 11:33 The entire device fits inside a 10-centimeter box, making it cheap to send into space. 11:44 Commercial service is set to start in late fiscal 2026. 11:49 A test launch has already been carried out in April. 11:52 It involved the startup's first corporate partner, the sake brewery. 11:57 The startup has also received enquiries from universities, research institutes and companies in various fields. 12:07 "Experiments can be launched at just about any time. 12:10 We aim to offer regular, low-cost access to space without the need for astronauts. 12:16 We'd like to see this platform widely used for research in space." 14:10 An AI-based service, created to identify counterfeit goods. 14:16 And a smartphone app designed to support the visually impaired. 14:23 The signal is green. 14:26 Today's On-Site Report shows how image recognition technology is having an impact on everyday life. 16:10 This Tokyo-based startup launched its AI-assisted authentication services in 2019. 16:21 It specializes in checking a range of products 16:23 such as brand name clothing, sneakers and collector's items. 16:32 "Counterfeit products used to appear in the market 16:35 a while after the genuine items were released. 16:39 But these days, they are coming out even before the real thing! 16:43 And the quality and accuracy of the fakes are also shockingly good." 16:49 In order to stop these fakes, the company uses cutting-edge image recognition software. 16:55 It relies on a trove of information sourced from nearly 2 million authentication cases. 17:01 The system is trained to exam and compare the same details 17:05 experts look at when checking items for authenticity. 17:10 For example, this high-end brand bag. 17:15 The logo on the fake item is far less pronounced. 17:20 And in this case, the embroidery is where the AI was able to find an anomaly. 17:28 Popular with sneakerheads, this rare model can sell for over 800 dollars. 17:34 That's 5 times more than the original retail price! 17:39 These shoes look identical, but one of them is a fake. 17:44 So, where do the experts look when trying to determine if it's genuine or a fraud? 17:50 In this case, one area is under the insole. 17:55 The stitching on the original is tighter and well-balanced. 18:00 Closer up, the difference is even more obvious. 18:06 Photos of the different sections of each product are uploaded to the system. 18:15 The AI then identifies specific areas to conduct a detailed analysis of. 18:22 It can verify authenticity in a fraction of the time it would take a human. 18:28 This time, it was determined to be a fake. 18:36 However, the company doesn't rely solely on image recognition technology. 18:40 It has implemented a two-stage process that ensures all items are also checked by a staff. 18:47 Experts can make use of all 5 of their senses. 18:50 For example, by checking the texture or feel of a product - 18:54 something the AI system isn't capable of. 19:01 "The fake insole feels a bit... 19:04 sticky. 19:06 I can't quite put it into words, but the texture just doesn't feel right." 19:14 The company provides its services to various online marketplaces 19:18 that specialize in buying and selling second-hand goods. 19:25 It also works with over 400 retail shops across Japan, many of which also offer used products. 19:35 The service now carries out over 40,000 authentications a month. 19:46 With counterfeits constantly emerging, 19:48 the company must continuously work to keep its database up to date. 21:32 Yoshizumi Hiroyuki lost his eyesight at the age of 11. 21:39 He usually navigates by using a cane to feel his way around. 21:49 Crosswalks require extra caution. 21:54 This time he veered off course. 21:58 He ended up running into the curb, 21:59 so we stopped filming and made sure he was out of danger. 22:04 "I could get hit by a car or something - 22:06 death is waiting just around the corner. 22:09 So, it's important for me to figure out how to stay alive and well." 22:14 Yoshizumi is now using a mobility support app. 22:20 It lets users make use of their smartphone cameras. 22:29 tactile paving 22:32 pedestrian crosswalk 22:34 The signal is red. 22:41 Able to recognize posts and curbs, 22:44 the AI is trained to identify and notify users 22:47 of 20 different types of objects and obstacles. 22:56 Crosswalk ahead. 22:57 The signal is red. 23:00 vehicle 23:03 The signal is green. 23:09 Hayashi Hidemi spent seven years trying out various approaches to creating a guidance system, 23:14 including a range of wearable devices. 23:18 He even designed a robot guide dog, 23:21 but the concept was ultimately scrapped. 23:25 "I decided to go with smartphones because I wanted 23:27 to create something that visually impaired people could use 23:30 without needing to purchase any special equipment. 23:33 I figured this would be the best way to make it accessible to as many people as possible." 23:39 Hayashi has collected a range of data from things commonly encountered when walking in public. 23:44 The AI system has been trained using over one million data points. 23:52 Hayashi also holds workshops across the country to gather user feedback. 24:01 They revealed that the type of guidance needed varies 24:03 depending on the degree and type of visual impairment 24:06 - such as total blindness or tunnel vision - 24:09 as well as the type of location where the system is being used. 24:15 If the system were to give notifications of all 20 types of objects or obstacles at once, 24:20 users would be overwhelmed. 24:25 So, they are able to select only the ones they want to be notified of. 24:33 Yoshizumi says when using the app, 24:36 he now feels comfortable visiting crowded and unfamiliar places. 24:44 "Being able to use AI to know more about my surroundings 24:47 has allowed me to feel both safer and more confident when going out." | 2026-01-13T08:49:02 |
https://docs.python.org/3/faq/library.html | Library and Extension FAQ — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents Library and Extension FAQ General Library Questions Common tasks Threads Input and Output Network/Internet Programming Databases Mathematics and Numerics Previous topic Design and History FAQ Next topic Extending/Embedding FAQ This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » Python Frequently Asked Questions » Library and Extension FAQ | Theme Auto Light Dark | Library and Extension FAQ ¶ Contents Library and Extension FAQ General Library Questions How do I find a module or application to perform task X? Where is the math.py (socket.py, regex.py, etc.) source file? How do I make a Python script executable on Unix? Is there a curses/termcap package for Python? Is there an equivalent to C’s onexit() in Python? Why don’t my signal handlers work? Common tasks How do I test a Python program or component? How do I create documentation from doc strings? How do I get a single keypress at a time? Threads How do I program using threads? None of my threads seem to run: why? How do I parcel out work among a bunch of worker threads? What kinds of global value mutation are thread-safe? Can’t we get rid of the Global Interpreter Lock? Input and Output How do I delete a file? (And other file questions…) How do I copy a file? How do I read (or write) binary data? I can’t seem to use os.read() on a pipe created with os.popen(); why? How do I access the serial (RS232) port? Why doesn’t closing sys.stdout (stdin, stderr) really close it? Network/Internet Programming What WWW tools are there for Python? What module should I use to help with generating HTML? How do I send mail from a Python script? How do I avoid blocking in the connect() method of a socket? Databases Are there any interfaces to database packages in Python? How do you implement persistent objects in Python? Mathematics and Numerics How do I generate random numbers in Python? General Library Questions ¶ How do I find a module or application to perform task X? ¶ Check the Library Reference to see if there’s a relevant standard library module. (Eventually you’ll learn what’s in the standard library and will be able to skip this step.) For third-party packages, search the Python Package Index or try Google or another web search engine. Searching for “Python” plus a keyword or two for your topic of interest will usually find something helpful. Where is the math.py (socket.py, regex.py, etc.) source file? ¶ If you can’t find a source file for a module it may be a built-in or dynamically loaded module implemented in C, C++ or other compiled language. In this case you may not have the source file or it may be something like mathmodule.c , somewhere in a C source directory (not on the Python Path). There are (at least) three kinds of modules in Python: modules written in Python (.py); modules written in C and dynamically loaded (.dll, .pyd, .so, .sl, etc); modules written in C and linked with the interpreter; to get a list of these, type: import sys print ( sys . builtin_module_names ) How do I make a Python script executable on Unix? ¶ You need to do two things: the script file’s mode must be executable and the first line must begin with #! followed by the path of the Python interpreter. The first is done by executing chmod +x scriptfile or perhaps chmod 755 scriptfile . The second can be done in a number of ways. The most straightforward way is to write #!/usr/local/bin/python as the very first line of your file, using the pathname for where the Python interpreter is installed on your platform. If you would like the script to be independent of where the Python interpreter lives, you can use the env program. Almost all Unix variants support the following, assuming the Python interpreter is in a directory on the user’s PATH : #!/usr/bin/env python Don’t do this for CGI scripts. The PATH variable for CGI scripts is often very minimal, so you need to use the actual absolute pathname of the interpreter. Occasionally, a user’s environment is so full that the /usr/bin/env program fails; or there’s no env program at all. In that case, you can try the following hack (due to Alex Rezinsky): #! /bin/sh """:" exec python $0 ${ 1 + " $@ " } """ The minor disadvantage is that this defines the script’s __doc__ string. However, you can fix that by adding __doc__ = """...Whatever...""" Is there a curses/termcap package for Python? ¶ For Unix variants: The standard Python source distribution comes with a curses module in the Modules subdirectory, though it’s not compiled by default. (Note that this is not available in the Windows distribution – there is no curses module for Windows.) The curses module supports basic curses features as well as many additional functions from ncurses and SYSV curses such as colour, alternative character set support, pads, and mouse support. This means the module isn’t compatible with operating systems that only have BSD curses, but there don’t seem to be any currently maintained OSes that fall into this category. Is there an equivalent to C’s onexit() in Python? ¶ The atexit module provides a register function that is similar to C’s onexit() . Why don’t my signal handlers work? ¶ The most common problem is that the signal handler is declared with the wrong argument list. It is called as handler ( signum , frame ) so it should be declared with two parameters: def handler ( signum , frame ): ... Common tasks ¶ How do I test a Python program or component? ¶ Python comes with two testing frameworks. The doctest module finds examples in the docstrings for a module and runs them, comparing the output with the expected output given in the docstring. The unittest module is a fancier testing framework modelled on Java and Smalltalk testing frameworks. To make testing easier, you should use good modular design in your program. Your program should have almost all functionality encapsulated in either functions or class methods – and this sometimes has the surprising and delightful effect of making the program run faster (because local variable accesses are faster than global accesses). Furthermore the program should avoid depending on mutating global variables, since this makes testing much more difficult to do. The “global main logic” of your program may be as simple as if __name__ == "__main__" : main_logic () at the bottom of the main module of your program. Once your program is organized as a tractable collection of function and class behaviours, you should write test functions that exercise the behaviours. A test suite that automates a sequence of tests can be associated with each module. This sounds like a lot of work, but since Python is so terse and flexible it’s surprisingly easy. You can make coding much more pleasant and fun by writing your test functions in parallel with the “production code”, since this makes it easy to find bugs and even design flaws earlier. “Support modules” that are not intended to be the main module of a program may include a self-test of the module. if __name__ == "__main__" : self_test () Even programs that interact with complex external interfaces may be tested when the external interfaces are unavailable by using “fake” interfaces implemented in Python. How do I create documentation from doc strings? ¶ The pydoc module can create HTML from the doc strings in your Python source code. An alternative for creating API documentation purely from docstrings is epydoc . Sphinx can also include docstring content. How do I get a single keypress at a time? ¶ For Unix variants there are several solutions. It’s straightforward to do this using curses, but curses is a fairly large module to learn. Threads ¶ How do I program using threads? ¶ Be sure to use the threading module and not the _thread module. The threading module builds convenient abstractions on top of the low-level primitives provided by the _thread module. None of my threads seem to run: why? ¶ As soon as the main thread exits, all threads are killed. Your main thread is running too quickly, giving the threads no time to do any work. A simple fix is to add a sleep to the end of the program that’s long enough for all the threads to finish: import threading , time def thread_task ( name , n ): for i in range ( n ): print ( name , i ) for i in range ( 10 ): T = threading . Thread ( target = thread_task , args = ( str ( i ), i )) T . start () time . sleep ( 10 ) # <---------------------------! But now (on many platforms) the threads don’t run in parallel, but appear to run sequentially, one at a time! The reason is that the OS thread scheduler doesn’t start a new thread until the previous thread is blocked. A simple fix is to add a tiny sleep to the start of the run function: def thread_task ( name , n ): time . sleep ( 0.001 ) # <--------------------! for i in range ( n ): print ( name , i ) for i in range ( 10 ): T = threading . Thread ( target = thread_task , args = ( str ( i ), i )) T . start () time . sleep ( 10 ) Instead of trying to guess a good delay value for time.sleep() , it’s better to use some kind of semaphore mechanism. One idea is to use the queue module to create a queue object, let each thread append a token to the queue when it finishes, and let the main thread read as many tokens from the queue as there are threads. How do I parcel out work among a bunch of worker threads? ¶ The easiest way is to use the concurrent.futures module, especially the ThreadPoolExecutor class. Or, if you want fine control over the dispatching algorithm, you can write your own logic manually. Use the queue module to create a queue containing a list of jobs. The Queue class maintains a list of objects and has a .put(obj) method that adds items to the queue and a .get() method to return them. The class will take care of the locking necessary to ensure that each job is handed out exactly once. Here’s a trivial example: import threading , queue , time # The worker thread gets jobs off the queue. When the queue is empty, it # assumes there will be no more work and exits. # (Realistically workers will run until terminated.) def worker (): print ( 'Running worker' ) time . sleep ( 0.1 ) while True : try : arg = q . get ( block = False ) except queue . Empty : print ( 'Worker' , threading . current_thread (), end = ' ' ) print ( 'queue empty' ) break else : print ( 'Worker' , threading . current_thread (), end = ' ' ) print ( 'running with argument' , arg ) time . sleep ( 0.5 ) # Create queue q = queue . Queue () # Start a pool of 5 workers for i in range ( 5 ): t = threading . Thread ( target = worker , name = 'worker %i ' % ( i + 1 )) t . start () # Begin adding work to the queue for i in range ( 50 ): q . put ( i ) # Give threads time to run print ( 'Main thread sleeping' ) time . sleep ( 5 ) When run, this will produce the following output: Running worker Running worker Running worker Running worker Running worker Main thread sleeping Worker <Thread(worker 1, started 130283832797456)> running with argument 0 Worker <Thread(worker 2, started 130283824404752)> running with argument 1 Worker <Thread(worker 3, started 130283816012048)> running with argument 2 Worker <Thread(worker 4, started 130283807619344)> running with argument 3 Worker <Thread(worker 5, started 130283799226640)> running with argument 4 Worker <Thread(worker 1, started 130283832797456)> running with argument 5 ... Consult the module’s documentation for more details; the Queue class provides a featureful interface. What kinds of global value mutation are thread-safe? ¶ A global interpreter lock (GIL) is used internally to ensure that only one thread runs in the Python VM at a time. In general, Python offers to switch among threads only between bytecode instructions; how frequently it switches can be set via sys.setswitchinterval() . Each bytecode instruction and therefore all the C implementation code reached from each instruction is therefore atomic from the point of view of a Python program. In theory, this means an exact accounting requires an exact understanding of the PVM bytecode implementation. In practice, it means that operations on shared variables of built-in data types (ints, lists, dicts, etc) that “look atomic” really are. For example, the following operations are all atomic (L, L1, L2 are lists, D, D1, D2 are dicts, x, y are objects, i, j are ints): L . append ( x ) L1 . extend ( L2 ) x = L [ i ] x = L . pop () L1 [ i : j ] = L2 L . sort () x = y x . field = y D [ x ] = y D1 . update ( D2 ) D . keys () These aren’t: i = i + 1 L . append ( L [ - 1 ]) L [ i ] = L [ j ] D [ x ] = D [ x ] + 1 Operations that replace other objects may invoke those other objects’ __del__() method when their reference count reaches zero, and that can affect things. This is especially true for the mass updates to dictionaries and lists. When in doubt, use a mutex! Can’t we get rid of the Global Interpreter Lock? ¶ The global interpreter lock (GIL) is often seen as a hindrance to Python’s deployment on high-end multiprocessor server machines, because a multi-threaded Python program effectively only uses one CPU, due to the insistence that (almost) all Python code can only run while the GIL is held. With the approval of PEP 703 work is now underway to remove the GIL from the CPython implementation of Python. Initially it will be implemented as an optional compiler flag when building the interpreter, and so separate builds will be available with and without the GIL. Long-term, the hope is to settle on a single build, once the performance implications of removing the GIL are fully understood. Python 3.13 is likely to be the first release containing this work, although it may not be completely functional in this release. The current work to remove the GIL is based on a fork of Python 3.9 with the GIL removed by Sam Gross. Prior to that, in the days of Python 1.5, Greg Stein actually implemented a comprehensive patch set (the “free threading” patches) that removed the GIL and replaced it with fine-grained locking. Adam Olsen did a similar experiment in his python-safethread project. Unfortunately, both of these earlier experiments exhibited a sharp drop in single-thread performance (at least 30% slower), due to the amount of fine-grained locking necessary to compensate for the removal of the GIL. The Python 3.9 fork is the first attempt at removing the GIL with an acceptable performance impact. The presence of the GIL in current Python releases doesn’t mean that you can’t make good use of Python on multi-CPU machines! You just have to be creative with dividing the work up between multiple processes rather than multiple threads . The ProcessPoolExecutor class in the new concurrent.futures module provides an easy way of doing so; the multiprocessing module provides a lower-level API in case you want more control over dispatching of tasks. Judicious use of C extensions will also help; if you use a C extension to perform a time-consuming task, the extension can release the GIL while the thread of execution is in the C code and allow other threads to get some work done. Some standard library modules such as zlib and hashlib already do this. An alternative approach to reducing the impact of the GIL is to make the GIL a per-interpreter-state lock rather than truly global. This was first implemented in Python 3.12 and is available in the C API. A Python interface to it is expected in Python 3.13. The main limitation to it at the moment is likely to be 3rd party extension modules, since these must be written with multiple interpreters in mind in order to be usable, so many older extension modules will not be usable. Input and Output ¶ How do I delete a file? (And other file questions…) ¶ Use os.remove(filename) or os.unlink(filename) ; for documentation, see the os module. The two functions are identical; unlink() is simply the name of the Unix system call for this function. To remove a directory, use os.rmdir() ; use os.mkdir() to create one. os.makedirs(path) will create any intermediate directories in path that don’t exist. os.removedirs(path) will remove intermediate directories as long as they’re empty; if you want to delete an entire directory tree and its contents, use shutil.rmtree() . To rename a file, use os.rename(old_path, new_path) . To truncate a file, open it using f = open(filename, "rb+") , and use f.truncate(offset) ; offset defaults to the current seek position. There’s also os.ftruncate(fd, offset) for files opened with os.open() , where fd is the file descriptor (a small integer). The shutil module also contains a number of functions to work on files including copyfile() , copytree() , and rmtree() . How do I copy a file? ¶ The shutil module contains a copyfile() function. Note that on Windows NTFS volumes, it does not copy alternate data streams nor resource forks on macOS HFS+ volumes, though both are now rarely used. It also doesn’t copy file permissions and metadata, though using shutil.copy2() instead will preserve most (though not all) of it. How do I read (or write) binary data? ¶ To read or write complex binary data formats, it’s best to use the struct module. It allows you to take a string containing binary data (usually numbers) and convert it to Python objects; and vice versa. For example, the following code reads two 2-byte integers and one 4-byte integer in big-endian format from a file: import struct with open ( filename , "rb" ) as f : s = f . read ( 8 ) x , y , z = struct . unpack ( ">hhl" , s ) The ‘>’ in the format string forces big-endian data; the letter ‘h’ reads one “short integer” (2 bytes), and ‘l’ reads one “long integer” (4 bytes) from the string. For data that is more regular (e.g. a homogeneous list of ints or floats), you can also use the array module. Note To read and write binary data, it is mandatory to open the file in binary mode (here, passing "rb" to open() ). If you use "r" instead (the default), the file will be open in text mode and f.read() will return str objects rather than bytes objects. I can’t seem to use os.read() on a pipe created with os.popen(); why? ¶ os.read() is a low-level function which takes a file descriptor, a small integer representing the opened file. os.popen() creates a high-level file object, the same type returned by the built-in open() function. Thus, to read n bytes from a pipe p created with os.popen() , you need to use p.read(n) . How do I access the serial (RS232) port? ¶ For Win32, OSX, Linux, BSD, Jython, IronPython: pyserial For Unix, see a Usenet post by Mitch Chapman: https://groups.google.com/groups?selm=34A04430.CF9@ohioee.com Why doesn’t closing sys.stdout (stdin, stderr) really close it? ¶ Python file objects are a high-level layer of abstraction on low-level C file descriptors. For most file objects you create in Python via the built-in open() function, f.close() marks the Python file object as being closed from Python’s point of view, and also arranges to close the underlying C file descriptor. This also happens automatically in f ’s destructor, when f becomes garbage. But stdin, stdout and stderr are treated specially by Python, because of the special status also given to them by C. Running sys.stdout.close() marks the Python-level file object as being closed, but does not close the associated C file descriptor. To close the underlying C file descriptor for one of these three, you should first be sure that’s what you really want to do (e.g., you may confuse extension modules trying to do I/O). If it is, use os.close() : os . close ( stdin . fileno ()) os . close ( stdout . fileno ()) os . close ( stderr . fileno ()) Or you can use the numeric constants 0, 1 and 2, respectively. Network/Internet Programming ¶ What WWW tools are there for Python? ¶ See the chapters titled Internet Protocols and Support and Internet Data Handling in the Library Reference Manual. Python has many modules that will help you build server-side and client-side web systems. A summary of available frameworks is maintained by Paul Boddie at https://wiki.python.org/moin/WebProgramming . What module should I use to help with generating HTML? ¶ You can find a collection of useful links on the Web Programming wiki page . How do I send mail from a Python script? ¶ Use the standard library module smtplib . Here’s a very simple interactive mail sender that uses it. This method will work on any host that supports an SMTP listener. import sys , smtplib fromaddr = input ( "From: " ) toaddrs = input ( "To: " ) . split ( ',' ) print ( "Enter message, end with ^D:" ) msg = '' while True : line = sys . stdin . readline () if not line : break msg += line # The actual mail send server = smtplib . SMTP ( 'localhost' ) server . sendmail ( fromaddr , toaddrs , msg ) server . quit () A Unix-only alternative uses sendmail. The location of the sendmail program varies between systems; sometimes it is /usr/lib/sendmail , sometimes /usr/sbin/sendmail . The sendmail manual page will help you out. Here’s some sample code: import os SENDMAIL = "/usr/sbin/sendmail" # sendmail location p = os . popen ( " %s -t -i" % SENDMAIL , "w" ) p . write ( "To: receiver@example.com \n " ) p . write ( "Subject: test \n " ) p . write ( " \n " ) # blank line separating headers from body p . write ( "Some text \n " ) p . write ( "some more text \n " ) sts = p . close () if sts != 0 : print ( "Sendmail exit status" , sts ) How do I avoid blocking in the connect() method of a socket? ¶ The select module is commonly used to help with asynchronous I/O on sockets. To prevent the TCP connect from blocking, you can set the socket to non-blocking mode. Then when you do the connect() , you will either connect immediately (unlikely) or get an exception that contains the error number as .errno . errno.EINPROGRESS indicates that the connection is in progress, but hasn’t finished yet. Different OSes will return different values, so you’re going to have to check what’s returned on your system. You can use the connect_ex() method to avoid creating an exception. It will just return the errno value. To poll, you can call connect_ex() again later – 0 or errno.EISCONN indicate that you’re connected – or you can pass this socket to select.select() to check if it’s writable. Note The asyncio module provides a general purpose single-threaded and concurrent asynchronous library, which can be used for writing non-blocking network code. The third-party Twisted library is a popular and feature-rich alternative. Databases ¶ Are there any interfaces to database packages in Python? ¶ Yes. Interfaces to disk-based hashes such as DBM and GDBM are also included with standard Python. There is also the sqlite3 module, which provides a lightweight disk-based relational database. Support for most relational databases is available. See the DatabaseProgramming wiki page for details. How do you implement persistent objects in Python? ¶ The pickle library module solves this in a very general way (though you still can’t store things like open files, sockets or windows), and the shelve library module uses pickle and (g)dbm to create persistent mappings containing arbitrary Python objects. Mathematics and Numerics ¶ How do I generate random numbers in Python? ¶ The standard module random implements a random number generator. Usage is simple: import random random . random () This returns a random floating-point number in the range [0, 1). There are also many other specialized generators in this module, such as: randrange(a, b) chooses an integer in the range [a, b). uniform(a, b) chooses a floating-point number in the range [a, b). normalvariate(mean, sdev) samples the normal (Gaussian) distribution. Some higher-level functions operate on sequences directly, such as: choice(S) chooses a random element from a given sequence. shuffle(L) shuffles a list in-place, i.e. permutes it randomly. There’s also a Random class you can instantiate to create independent multiple random number generators. Table of Contents Library and Extension FAQ General Library Questions Common tasks Threads Input and Output Network/Internet Programming Databases Mathematics and Numerics Previous topic Design and History FAQ Next topic Extending/Embedding FAQ This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » Python Frequently Asked Questions » Library and Extension FAQ | Theme Auto Light Dark | © Copyright 2001 Python Software Foundation. This page is licensed under the Python Software Foundation License Version 2. Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License. See History and License for more information. The Python Software Foundation is a non-profit corporation. Please donate. Last updated on Jan 13, 2026 (06:19 UTC). Found a bug ? Created using Sphinx 8.2.3. | 2026-01-13T08:49:02 |
https://dev.to/ericrodriguez10 | Eric Rodríguez - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Eric Rodríguez Software Dev exploring the AWS ecosystem. Turning coffee into cloud architecture (eventually). ☕☁️ Location Madrid, Spain Joined Joined on Dec 25, 2025 More info about @ericrodriguez10 Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 15 posts published Comment 0 comments written Tag 0 tags followed Hosting a React App on AWS S3 in 5 minutes. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 10 Hosting a React App on AWS S3 in 5 minutes. # aws # react # s3 # webdev Comments Add Comment 1 min read Day 14: Scheduling AWS Lambda with EventBridge (The Serverless Cron). Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 9 Day 14: Scheduling AWS Lambda with EventBridge (The Serverless Cron). # aws # serverless # automation # devops Comments Add Comment 1 min read Day 13: Sending AI Reports via Email using AWS SNS and Python. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 8 Day 13: Sending AI Reports via Email using AWS SNS and Python. # aws # python # sns # devops Comments Add Comment 1 min read Day 12: Building a simple RAG pipeline with Lambda, DynamoDB, and Bedrock. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 7 Day 12: Building a simple RAG pipeline with Lambda, DynamoDB, and Bedrock. # aws # python # dynamodb # bedrock Comments Add Comment 1 min read Day 11: Invoking Amazon Titan from AWS Lambda (Serverless GenAI). Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 6 Day 11: Invoking Amazon Titan from AWS Lambda (Serverless GenAI). # ai # aws # python # serverless Comments Add Comment 1 min read Day 10: Storing Financial Data in DynamoDB with Python (Boto3). Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 6 Day 10: Storing Financial Data in DynamoDB with Python (Boto3). # dynamodb # aws # python # database Comments Add Comment 1 min read Day 9: When APIs Fail. How to implement a "Mock Mode" in AWS Lambda. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 3 Day 9: When APIs Fail. How to implement a "Mock Mode" in AWS Lambda. # aws # python # testing # serverless Comments Add Comment 1 min read Day 8: Never Hardcode Keys. Connecting Lambda to APIs using AWS Secrets Manager. Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 2 Day 8: Never Hardcode Keys. Connecting Lambda to APIs using AWS Secrets Manager. # aws # security # python # beginners Comments Add Comment 1 min read Day 7: Designing a Serverless AI Financial Agent (Project Roadmap) Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Jan 1 Day 7: Designing a Serverless AI Financial Agent (Project Roadmap) # aws # architecture # serverless # python Comments Add Comment 1 min read The Last Deploy of 2025: Exposing my Lambda to the World with API Gateway Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 31 '25 The Last Deploy of 2025: Exposing my Lambda to the World with API Gateway # aws # apigateway # serverless # python Comments Add Comment 1 min read I fired my server manager: Running Python on AWS Lambda (Serverless) Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 30 '25 I fired my server manager: Running Python on AWS Lambda (Serverless) # aws # python # serverless # lambda Comments Add Comment 1 min read Beyond Static: Launching My First EC2 Instance with User Data Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 29 '25 Beyond Static: Launching My First EC2 Instance with User Data # aws # ec2 # linux # devops Comments Add Comment 1 min read Goodbye Localhost: Why I deployed my site on raw S3 instead of Netlify Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 27 '25 Goodbye Localhost: Why I deployed my site on raw S3 instead of Netlify # aws # webdev # beginners # s3 Comments Add Comment 2 min read My First AWS Lab: Setting Up a Budget Alarm (Even though I have Credits) Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 26 '25 My First AWS Lab: Setting Up a Budget Alarm (Even though I have Credits) # aws # beginners # tutorial # cloud Comments Add Comment 2 min read Stop Waiting: Why I’m Going All-In on AWS in 2026 (And How I Plan to Survive) Eric Rodríguez Eric Rodríguez Eric Rodríguez Follow Dec 25 '25 Stop Waiting: Why I’m Going All-In on AWS in 2026 (And How I Plan to Survive) Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://webcontainers.io | WebContainers - Dev environments. In your web app. | WebContainers Skip to content Search K Main Navigation Guides Tutorial API Reference AI Pricing GitHub Twitter Discord Appearance GitHub Twitter Discord Go to Console Return to top Dev environments. In your web app. From interactive tutorials to full-blown IDEs, build instant, interactive coding experiences backed by WebContainers: the trusted, browser-based runtime from StackBlitz . Get started Book a demo index.js ⬤ Run index.js ❯ node index.js List files ❯ ls -l Battle-tested by cutting-edge teams On the SvelteKit team, we've fantasized for years about being able to build fully interactive learning material for full stack frameworks. With WebContainers it went from 'impossible' to 'easy' almost overnight. Rich Harris Principal Software Engineer, Vercel As a team working on educational products, StackBlitz WebContainers has been an invaluable tool for us. The ability to embed full-stack applications with customisable, interactive coding environment directly into our products has greatly enhanced the learning experience for our users. Vojta Holik Designer & Developer, Egghead.io WebContainers solve the final frontier in JavaScript developer experience - making full-stack Node.js projects run in the browser as lightweight and disposable and secure as frontend REPLs. Every PR, every npm library maintainer, every devtool company with a Node.js SDK, can benefit from this! swyx I have worked with Web container API for a couple of weeks at Scrimba to make a pooc of backend support. And I can say it's a solid piece of technology. Things just work, and it's also quite fast. I'm super excited about the GA since it will unlock so much opportunities for OSS projects and the industry at large. Abdellah Alaoui Fullstack hacker, Scrimba The WebContainer API is a landmark on the way we think docs. Creating interactive docs and snippets just became so much more feasible! With Server-side code running on the browser, setting up a playground to securely learn Node.js SDKs and compilers became feasible and even fun! Atila Fassina DX Engineer at Xata WebContainers represent a fundamental shift in what is possible in the browser. I'm incredibly excited about the potential this tech unlocks, from secure, browser-based development environments to highly interactive educational content. Nate Moore Senior Software Engineer, The Astro Technology Company For such a powerful piece of tech I was so impressed by how clear to use the API is. Also running WebContainers inside WebContainers had me 🤯 Ramón Huidobro Developer Advocate at Suborbital Software Systems At re:tune, we have been building the missing frontend for GPT-3, on a mission to empower everyone to build AI-first software at the speed of thought. WebContainers set the stage for our AI-native IDE - with a copilot that can not only read and write code, but can also understand and operate in the full runtime context across server and client! DJ Founder & CEO @ re:tune Running chess in a terminal, running a terminal in the browser, check mate! The best position to be in is a creative one and the StackBlitz WebContainers allow that. Manus Nijhoff Co-founder at Touchy Studios & full-stack developer at 100k Power your web app with the WebContainer API Create unmatched user experiences by integrating Node.js directly into your web app. Build fully-branded products without connecting to external servers or directing users away to third-party apps. Run native package managers Run the native versions of npm , pnpm , and yarn , all in the browser, all in your app, up to 10x faster than local. Full browser support Run WebContainer in all major browsers, from Chromium-based, to Firefox or Safari TP. All major frameworks Instantly spin up disposable environments running any major modern framework. Run Wasm out of the box Port your favorite language or framework to Wasm to run it in WebContainers. Yes, really. Set up in only a few steps Boot a WebContainer. Populate the container's file system. Programmatically install packages. Run your development server in-browser. Read more about setting up WebContainer in your web app. hello-world.ts project-files.ts import { WebContainer, FileSystemTree } from '@webcontainer/api' ; import { projectFiles } from './project-files.ts' ; async function main() { // First we boot a WebContainer const webcontainer = await WebContainer.boot() ; // After booting the container we copy all of our project files // into the container's file system await webcontainer.mount(projectFiles) ; // Once the files have been mounted, we install the project's // dependencies by spawning `npm install` const install = await webcontainer.spawn( 'npm' , [ 'i' ]); await install.exit ; // Once all dependencies have been installed, we can spawn `npm` // to run the `dev` script from the project's `package.json` await webcontainer.spawn( 'npm' , [ 'run' , 'dev' ]) ; } Build rich development experiences not possible before Interactive tutorials Learn SvelteKit, a full stack framework, within their custom editor, running on WebContainers, all in the browser. learn.svelte.dev Low code / no code A stress-free editor enabling non-technical contributors to make their own PRs with a live, disposable preview to confirm an error-free build. Web Publisher by StackBlitz AI applications re:tune is setting the stage for AI-native IDEs - with a copilot that can understand and operate in the full runtime context across server and client. retune.so Support for every team Small startups, open source maintainers, and Fortune 500 enterprises all enjoy access to StackBlitz's committed product support, features and improvements. Slash server costs WebContainer API only requires the compute power of your local CPU and browser, eliminating the cost and overhead of managing remote servers. Ship faster No additional teams to build or maintain. Leave the technical support to us and focus on actually shipping your product. Leverage the tech we use in our own products. Years of development by our full-time engineering team, front-line feedback from leading community partners, and funded R&D into future technological possibilities make WebContainer more robust by the day. Get started! Workspaces Popular Frontend Backend Fullstack Vite Docs, Blogs & Slides Vanilla Start a new Project From a Workspace From a GitHub Repo From your computer Product Docs Enterprise Pricing Case Studies Company Blog Careers Community Enterprise Sales Privacy Terms of Service Connect GitHub Twitter Discord © 2024 StackBlitz, Inc. | 2026-01-13T08:49:02 |
https://www.python.org/psf/get-involved/#top | 👋 Hey Community Members! | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Python >>> Get Involved 👋 Hey Community Members! More than 20 ways to get involved & stay informed! Watch any of these talks given about the PSF (most recent one is about PyPI presented by Ee, our Director of Infrastructure!) Want to financially support the PSF? Donate! Read our blog Sign up to receive our quarterly newsletter Follow us on Twitter or Mastodon Become a Basic member If you are already a Basic member, consider becoming a Contributing , Managing , and/or Supporting member. If you want to be a PSF Board Member, add your nomination to this page next time we have an election (May/June 2022) Join the psf-community@ mailing list (basic members or above) Join the psf-vote@ mailing list and be an active voter (must be a Contributing, Managing, Supporting, and/or Fellow member) Nominate someone to be a Fellow member If you are a Fellow member already, join the Fellow Work Group to help vote in new Fellow members Nominate someone to receive a Community Service Award Interested in packaging? Check out the discussion on Discourse Help PyPI test out new beta features Follow PyCon on Twitter! Interested in Python in Education? Join the Education Sig mailing list Interested in jobs.python.org? Help us review job postings or help us improve the functionality Know of a Python community workshop or training that could use additional funding? Direct them to our grants page ! See someone using the Python or PyCon trademark incorrectly? Notify the Trademarks Committee Know of a company that should sponsor the PSF? Tell us or link them to our sponsor page . When the PSF has a donation campaign happening, help us by sharing it with your community and by sharing it on social media (we have one happening right now: https://www.python.org/psf/donations/2021-q4-drive/ ) Participate in the 2021 Python Developers Survey: https://surveys.jetbrains.com/s3/python-developers-survey-2021 The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.bemyeyes.com/ | Accessibility Technology for blind & low vision people - Be My Eyes --> Skip to main content Jump to Business Site Switch color mode controls Switch color mode controls Switch color mode | Language Choose your language Close × 简体中文 Čeština Nederlands English Suomi Français Deutsch Ελληνικά Magyar Italiano 日本語 Melayu Norsk bokmål Português Português Română Русский Slovenčina Español Türkçe Albanian Dansk हिन्दी Indonesia 한국어 Polski Slovenščina ไทย Українська Tiếng Việt Български Svenska Theme Switcher Options Light Theme Dark Theme High Contrast The App Be My Eyes App The App Overview Be My AI™ Be My Eyes Smartglasses Be My Eyes Service Directory Be My Eyes for Windows Download the Be My Eyes App The Be My Eyes App connects blind and low-vision users with real-time visual assistance from volunteers around the world. It’s free, easy to use and always there for you. Download the app today! Available on: Community Community Menu Latest Stories Blog News AppleVis Spotlight Upcoming Events Podcasts AppleVis Podcast Double Tap Be My Eyes Podcast 13 Letters That Real Blind Tech Show Support Be My Eyes Volunteer Hub Be My Eyes help AppleVis Download the Be My Eyes App The Be My Eyes App connects blind and low-vision users with real-time visual assistance from volunteers around the world. It’s free, easy to use and always there for you. Download the app today! Available on: About Us Contact Us For Business Download App Be My Eyes Close menu The App Be My AI Be My Eyes Smartglasses Be My Eyes Service Directory Be My Eyes for Windows Community Latest Stories Blog News AppleVis Spotlight Podcasts Support Be My Eyes Volunteer Hub Be My Eyes Help AppleVis About Us Contact Us For Business Download App Let’s see the world together Be My Eyes connects blind or low vision users who want assistance, with volunteers and companies across the world, through live video and AI. Download App Picture of a Be My Eyes Service User A female with long dark hair dressed in dark trousers and a grey top is holding a white cane in one hand and holds a phone up to her ear with the other. She has a biog smile on her face. She is sitting outside on a concrete wall with trees and buildings behind her. It is a sunny bright blue sky day. Who the App is for Making a difference where it’s needed Users Use your smartphone to get free, instant visual description anytime, day or night. Connect with a volunteer, take a picture and let Be My AI™ describe it, or reach out to our partners through the Service Directory for help with their products. Discover our App Volunteers Our volunteers, now in more than 150 countries around the world, provide real-time descriptions and assistance for people who are blind or have low vision. Join our volunteer community and make a meaningful impact. Discover the Volunteer Hub Businesses Enhance your accessible customer service teams with real-time video and AI support, and resolve up to 90% of cases automatically, while cutting resolution times and costs by 60%. Or provide the tools that make your workplace more accessible for employees who are blind or have low vision. Discover Be My Eyes for Business. Learn More for Business Benefits Real people. Real support. Real impact. Free and unlimited calls Call as often as you need without worrying about costs. Available day and night Connect with our network of volunteers and AI tools 24/7. 100% anonymous Volunteers only hear your voice and see what you share through your camera. Worldwide support We’re available in over 150 countries. Real-time assistance Get instant support as soon as you need it. Accessibility for all We want to make everyday tasks easy for everyone. About Us Every day, we’re making the world more accessible to more people More About Us Live 9,762,755 Volunteers Live 967,336 Blind & low-vision 150+ Countries 180+ Languages Community Discover our community Our goal is to make the world more accessible to people who are blind or have low vision. We couldn’t do this without the help and dedication of our community. Read our blog, listen to our podcasts or read stories from real users from all around the world. Explore the Community Picture of a Be My Eyes Service User and her child <p>A woman with sunglasses and a white cane smiles at a young girl on a scooter. They share a happy moment outdoors. Generated with Be My AI.</p> What’s New Explore the latest stories, updates and insights Blog Be My Eyes Wins Apple’s 2025 App Store Award for Cultural Impact Read More → Blog Meet Dr. Hoby: Cooking Confidently with Barilla and Be My Eyes Read More → Blog Be My Eyes Partners with Guide Dogs NSW/ACT to Support Australians with Low Vision or Blindness Read More → Are you a business? Request a free demo of our business solutions Let’s see the world together About About Us Contact Us AppleVis Careers Products Be My Eyes App Be My AI™ Be My Eyes for Smart Glasses By My Eyes Service Directory Be My Eyes for Windows Community Stories Blog News Podcasts Merchandise Help Help Center Get Visual Assistance System Status Translate Legal Terms of Service Privacy Policy © Be My Eyes 2026 . All rights reserved. | 2026-01-13T08:49:02 |
https://zeroday.forem.com/about#what-were-all-about | About Zero Day Security Community - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close About Zero Day Security Community About the Zero Day Security Community Welcome to Zero Day, the ultimate hub for security professionals, enthusiasts, students, and anyone passionate about the world of security. Whether you're a seasoned CISO, a curious student, or a developer looking to write more secure code, you've found your home. Our Mission Our mission is to create a central, inclusive, and authoritative online community dedicated to fostering collaboration, knowledge sharing, and skill development across all domains of security. We believe in breaking down silos and building bridges between the theoretical and the practical, the digital and the physical. What We're All About Zero Day is a space for deep, meaningful discussion and learning. We are built on a few core principles: Knowledge First: We prioritize accurate, vetted, and practical information. We're here to learn from each other and elevate our collective expertise. Radical Inclusivity: Gatekeeping has no place here. We welcome all skill levels, from absolute beginners to world-renowned experts. We are a community dedicated to mentorship and support, not judgment. Strong Ethical Foundation: We are a strictly white-hat community. All discussions and activities are guided by a commitment to ethical hacking, responsible disclosure, and using our skills for good. What to Expect Here, you'll find a wide range of content and discussions covering the entire security landscape. We encourage posts, questions, and articles on topics like: Offensive Security (Red Team): From web app pentesting and exploit development to social engineering and adversary emulation. Defensive Security (Blue Team): Dive into threat intelligence, digital forensics, incident response (DFIR), and malware analysis. Cloud & Application Security: Explore DevSecOps, secure coding practices, cryptography, and securing cloud infrastructure (AWS, Azure, GCP). Governance, Risk & Compliance (GRC): Discuss frameworks like NIST and ISO 27001, risk management, and compliance challenges. Physical & Hardware Security: Explore everything from lockpicking and access control to IoT and embedded systems hacking. Career & Professional Development: Share advice on certifications (OSCP, CISSP, etc.), get resume feedback, and discuss interview experiences. How to Get Involved This community is powered by you! Here are a few ways to jump in: Introduce Yourself: Head over to the introductions thread and tell us about your interests. Ask Questions: No question is too basic. We are all here to learn. Share Your Knowledge: Write a post about a project you're working on, a tool you love, or a concept you've mastered. Join the Conversation: Upvote quality content and add your perspective to ongoing discussions. Set Your Flair: Edit your profile to add flair that shows your specialty (e.g., Pentester, DFIR, GRC, Student). We're thrilled to have you here. Let's build the best security community on the web, together. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:02 |
https://core.forem.com/t/tv/page/2 | Tv Page 2 - Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close # tv Follow Hide Discussion about television series and episodes Create Post Older #tv posts 1 2 3 4 5 6 7 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:02 |
https://gg.forem.com/contact | Contact Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close Contacts Gamers Forem would love to hear from you! Email: support@dev.to 😁 Twitter: @thepracticaldev 👻 Report a vulnerability: dev.to/security 🐛 To report a bug, please create a bug report in our open source repository. To request a feature, please start a new GitHub Discussion in the Forem repo! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:02 |
https://www.youtube.com/watch?v=x7cQ3mrcKaY | Pete Hunt: React: Rethinking best practices -- JSConf EU - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x48b467f2080e5e94"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtJUDRmUmFmRm5zRSj6jZjLBjIKCgJLUhIEGgAgWg%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRv0MMkwAXMKcW8nsGEkysACMjYgi4Ug8xQ5HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersInfoItemRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","expandableMetadataRenderer","videoSummaryContentViewModel","videoSummaryParagraphViewModel","howThisWasMadeSectionViewModel","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer","microformatDataRenderer"]},"ytConfigData":{"visitorData":"CgtJUDRmUmFmRm5zRSj6jZjLBjIKCgJLUhIEGgAgWg%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwiMjez_kIiSAxUVWA8CHfyVIM8yDHJlbGF0ZWQtYXV0b0im0_DW5pvE28cBmgEFCAMQ-B3KAQQx_PKs","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=cCOL7MC4Pl0\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"cCOL7MC4Pl0","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiMjez_kIiSAxUVWA8CHfyVIM8yDHJlbGF0ZWQtYXV0b0im0_DW5pvE28cBmgEFCAMQ-B3KAQQx_PKs","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=cCOL7MC4Pl0\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"cCOL7MC4Pl0","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiMjez_kIiSAxUVWA8CHfyVIM8yDHJlbGF0ZWQtYXV0b0im0_DW5pvE28cBmgEFCAMQ-B3KAQQx_PKs","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=cCOL7MC4Pl0\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"cCOL7MC4Pl0","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Pete Hunt: React: 모범 사례 재고 -- JSConf EU"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 542,495회"},"shortViewCount":{"simpleText":"조회수 54만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CLoCEMyrARgAIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3g3Y1EzbXJjS2FZGmBFZ3Q0TjJOUk0yMXlZMHRoV1VBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNnM1kxRXpiWEpqUzJGWkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CLoCEMyrARgAIhMIjI3s_5CIkgMVFVgPAh38lSDP"}}],"trackingParams":"CLoCEMyrARgAIhMIjI3s_5CIkgMVFVgPAh38lSDP","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"6.9천","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMUCEKVBIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},{"innertubeCommand":{"clickTrackingParams":"CMUCEKVBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMYCEPqGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMYCEPqGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"x7cQ3mrcKaY"},"likeParams":"Cg0KC3g3Y1EzbXJjS2FZIAAyCwj7jZjLBhD9wLFK"}},"idamTag":"66426"}},"trackingParams":"CMYCEPqGBCITCIyN7P-QiJIDFRVYDwId_JUgzw=="}}}}}}}]}},"accessibilityText":"다른 사용자 6,984명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMUCEKVBIhMIjI3s_5CIkgMVFVgPAh38lSDP","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"6.9천","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMQCEKVBIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},{"innertubeCommand":{"clickTrackingParams":"CMQCEKVBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"x7cQ3mrcKaY"},"removeLikeParams":"Cg0KC3g3Y1EzbXJjS2FZGAAqCwj7jZjLBhDVuLJK"}}}]}},"accessibilityText":"다른 사용자 6,984명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMQCEKVBIhMIjI3s_5CIkgMVFVgPAh38lSDP","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CLoCEMyrARgAIhMIjI3s_5CIkgMVFVgPAh38lSDP","isTogglingDisabled":true}},"likeStatusEntityKey":"Egt4N2NRM21yY0thWSA-KAE%3D","likeStatusEntity":{"key":"Egt4N2NRM21yY0thWSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMICEKiPCSITCIyN7P-QiJIDFRVYDwId_JUgzw=="}},{"innertubeCommand":{"clickTrackingParams":"CMICEKiPCSITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMMCEPmGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMMCEPmGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"x7cQ3mrcKaY"},"dislikeParams":"Cg0KC3g3Y1EzbXJjS2FZEAAiCwj7jZjLBhDd8LNK"}},"idamTag":"66425"}},"trackingParams":"CMMCEPmGBCITCIyN7P-QiJIDFRVYDwId_JUgzw=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMICEKiPCSITCIyN7P-QiJIDFRVYDwId_JUgzw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMECEKiPCSITCIyN7P-QiJIDFRVYDwId_JUgzw=="}},{"innertubeCommand":{"clickTrackingParams":"CMECEKiPCSITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"x7cQ3mrcKaY"},"removeLikeParams":"Cg0KC3g3Y1EzbXJjS2FZGAAqCwj7jZjLBhDrlbRK"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMECEKiPCSITCIyN7P-QiJIDFRVYDwId_JUgzw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CLoCEMyrARgAIhMIjI3s_5CIkgMVFVgPAh38lSDP","isTogglingDisabled":true}},"dislikeEntityKey":"Egt4N2NRM21yY0thWSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egt4N2NRM21yY0thWSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL8CEOWWARgCIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},{"innertubeCommand":{"clickTrackingParams":"CL8CEOWWARgCIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt4N2NRM21yY0thWaABAQ%3D%3D","commands":[{"clickTrackingParams":"CL8CEOWWARgCIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CMACEI5iIhMIjI3s_5CIkgMVFVgPAh38lSDP","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL8CEOWWARgCIhMIjI3s_5CIkgMVFVgPAh38lSDP","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CL0CEOuQCSITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL4CEPuGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dx7cQ3mrcKaY\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL4CEPuGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=x7cQ3mrcKaY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"x7cQ3mrcKaY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=c7b710de6adc29a6\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CL4CEPuGBCITCIyN7P-QiJIDFRVYDwId_JUgzw=="}}}}}},"trackingParams":"CL0CEOuQCSITCIyN7P-QiJIDFRVYDwId_JUgzw=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLsCEOuQCSITCIyN7P-QiJIDFRVYDwId_JUgzw=="}},{"innertubeCommand":{"clickTrackingParams":"CLsCEOuQCSITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLwCEPuGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dx7cQ3mrcKaY\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLwCEPuGBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=x7cQ3mrcKaY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"x7cQ3mrcKaY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=c7b710de6adc29a6\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLwCEPuGBCITCIyN7P-QiJIDFRVYDwId_JUgzw=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLsCEOuQCSITCIyN7P-QiJIDFRVYDwId_JUgzw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CLoCEMyrARgAIhMIjI3s_5CIkgMVFVgPAh38lSDP","dateText":{"simpleText":"2013. 10. 30."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"12년 전"}},"simpleText":"12년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/ytc/AIdro_ltRigbEjK9HfAhlU6gVdqYyHN7uulgrQfff_RXtLU0e-8=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/ytc/AIdro_ltRigbEjK9HfAhlU6gVdqYyHN7uulgrQfff_RXtLU0e-8=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/ytc/AIdro_ltRigbEjK9HfAhlU6gVdqYyHN7uulgrQfff_RXtLU0e-8=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"JSConf","navigationEndpoint":{"clickTrackingParams":"CLkCEOE5IhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"/@jsconf_","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCzoVCacndDCfGDf41P-z0iA","canonicalBaseUrl":"/@jsconf_"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CLkCEOE5IhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"/@jsconf_","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCzoVCacndDCfGDf41P-z0iA","canonicalBaseUrl":"/@jsconf_"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 28.7만명"}},"simpleText":"구독자 28.7만명"},"trackingParams":"CLkCEOE5IhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCzoVCacndDCfGDf41P-z0iA","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CKsCEJsrIhMIjI3s_5CIkgMVFVgPAh38lSDPKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"JSConf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"JSConf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. JSConf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLgCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. JSConf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. JSConf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLcCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. JSConf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CLACEJf5ASITCIyN7P-QiJIDFRVYDwId_JUgzw==","command":{"clickTrackingParams":"CLACEJf5ASITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLACEJf5ASITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CLYCEOy1BBgDIhMIjI3s_5CIkgMVFVgPAh38lSDPMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQQx_PKs","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3pvVkNhY25kRENmR0RmNDFQLXowaUESAggBGAAgBFITCgIIAxILeDdjUTNtcmNLYVkYAA%3D%3D"}},"trackingParams":"CLYCEOy1BBgDIhMIjI3s_5CIkgMVFVgPAh38lSDP","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CLUCEO21BBgEIhMIjI3s_5CIkgMVFVgPAh38lSDPMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQQx_PKs","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3pvVkNhY25kRENmR0RmNDFQLXowaUESAggDGAAgBFITCgIIAxILeDdjUTNtcmNLYVkYAA%3D%3D"}},"trackingParams":"CLUCEO21BBgEIhMIjI3s_5CIkgMVFVgPAh38lSDP","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CLECENuLChgFIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLECENuLChgFIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLICEMY4IhMIjI3s_5CIkgMVFVgPAh38lSDP","dialogMessages":[{"runs":[{"text":"JSConf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CLQCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPMgV3YXRjaMoBBDH88qw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCzoVCacndDCfGDf41P-z0iA"],"params":"CgIIAxILeDdjUTNtcmNLYVkYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CLQCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLMCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CLECENuLChgFIhMIjI3s_5CIkgMVFVgPAh38lSDP"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CKsCEJsrIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CK8CEP2GBCITCIyN7P-QiJIDFRVYDwId_JUgzzIJc3Vic2NyaWJlygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dx7cQ3mrcKaY%26continue_action%3DQUFFLUhqbURIMUZhNFF3V0FyQy0yb2xZNWFXZWlVNldod3xBQ3Jtc0tsT3dDcklEeHIxZ2NfZ2MwMTdrQ1BuWXNVRm9EOXNSVmd6cnNmRDZsMXpuX29hbVh2cDU4V1NtUElNaFdkYTV1UXJ1WjNBUnFYUHhZekV3RG9SaVE1VXRwdjVydWpiRC1BYmkxeS1OQkt6VDBWaWxReHh3clU0S3oxNDhtN2F6MDlkSDQwcU9vZV9peVk2Q1lsZWVWRHZ3V04yQnZwaHpxWXpMeGNMei1HVFk0UGxheTJKN1JScG5QSXg2Ym5XWUVlM0x2NG4\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CK8CEP2GBCITCIyN7P-QiJIDFRVYDwId_JUgz8oBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=x7cQ3mrcKaY","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"x7cQ3mrcKaY","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=c7b710de6adc29a6\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbURIMUZhNFF3V0FyQy0yb2xZNWFXZWlVNldod3xBQ3Jtc0tsT3dDcklEeHIxZ2NfZ2MwMTdrQ1BuWXNVRm9EOXNSVmd6cnNmRDZsMXpuX29hbVh2cDU4V1NtUElNaFdkYTV1UXJ1WjNBUnFYUHhZekV3RG9SaVE1VXRwdjVydWpiRC1BYmkxeS1OQkt6VDBWaWxReHh3clU0S3oxNDhtN2F6MDlkSDQwcU9vZV9peVk2Q1lsZWVWRHZ3V04yQnZwaHpxWXpMeGNMei1HVFk0UGxheTJKN1JScG5QSXg2Ym5XWUVlM0x2NG4","idamTag":"66429"}},"trackingParams":"CK8CEP2GBCITCIyN7P-QiJIDFRVYDwId_JUgzw=="}}}}}},"subscribedEntityKey":"EhhVQ3pvVkNhY25kRENmR0RmNDFQLXowaUEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CKsCEJsrIhMIjI3s_5CIkgMVFVgPAh38lSDPKPgdMgV3YXRjaMoBBDH88qw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCzoVCacndDCfGDf41P-z0iA"],"params":"EgIIAxgAIgt4N2NRM21yY0thWQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CKsCEJsrIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKsCEJsrIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKwCEMY4IhMIjI3s_5CIkgMVFVgPAh38lSDP","dialogMessages":[{"runs":[{"text":"JSConf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CK4CEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPKPgdMgV3YXRjaMoBBDH88qw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCzoVCacndDCfGDf41P-z0iA"],"params":"CgIIAxILeDdjUTNtcmNLYVkYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CK4CEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CK0CEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDP","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"슬라이드: http://www.slideshare.net/floydophone...\n페이스북과 인스타그램의 새로운 오픈소스 자바스크립트 라이브러리인 React는 JavaScript 앱을 개발하는 새로운 방식입니다. 5월 JSConf US에서 소개되었을 때, 청중들은 React의 디자인 원칙 중 일부에 충격을 받았습니다. 한 청중이 남긴 비꼬는 트윗 하나가 React의 철학을 매우 정확하게 표현했습니다. / 339858717451362304 \n\n페이스북과 인스타그램은 React를 통해 웹에서 가능한 것의 한계를 넓히려 노력하고 있습니다. 제 발표는 React 프레임워크에 대한 간략한 소개로 시작하여, 세 가지 논란의 여지가 있는 주제를 심도 있게 다룰 것입니다. 템플릿 개념을 버리고 JavaScript로 뷰를 구축하는 것, 데이터 변경 시 전체 애플리케이션을 \"리렌더링\"하는 것, 그리고 DOM과 이벤트를 가볍게 구현하는 것입니다.\n\n라이선스: 이 영상을 보다 관대한 라이선스 하에 재사용하려면 저희에게 연락해 주세요. 연사는 자신의 공연에 대한 저작권을 보유합니다.","commandRuns":[{"startIndex":6,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDPSKbT8Nbmm8TbxwHKAQQx_PKs","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbmluVjk2UTNyMkt4QVRMaWY3a1pXWTBwMnU2QXxBQ3Jtc0ttUkp6SDU0S1VNdUwyOGRhRFNWRjNlV3dVWGw1MGZmUFNobGZyWTBtajQ3aEktR18zdV96d214Nkx3aVNkSGFHdUZNU0hPUmJXWmNxRXRwR1JyS3VhUElnR3JfNW9mamtvX2E2MFl3Y3ZJcWFKbVBXYw\u0026q=http%3A%2F%2Fwww.slideshare.net%2Ffloydophone%2Freact-preso-v2\u0026v=x7cQ3mrcKaY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbmluVjk2UTNyMkt4QVRMaWY3a1pXWTBwMnU2QXxBQ3Jtc0ttUkp6SDU0S1VNdUwyOGRhRFNWRjNlV3dVWGw1MGZmUFNobGZyWTBtajQ3aEktR18zdV96d214Nkx3aVNkSGFHdUZNU0hPUmJXWmNxRXRwR1JyS3VhUElnR3JfNW9mamtvX2E2MFl3Y3ZJcWFKbVBXYw\u0026q=http%3A%2F%2Fwww.slideshare.net%2Ffloydophone%2Freact-preso-v2\u0026v=x7cQ3mrcKaY","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":227,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CKoCEM2rARgBIhMIjI3s_5CIkgMVFVgPAh38lSDPSKbT8Nbmm8TbxwHKAQQx_PKs","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDJWbmZjNFVWV1AzeUJsc1pWUVlvZm4tMjJBQXxBQ3Jtc0tudG9uREwzWS11VDljbUdKdTlSSG9PNjBjSHFITW5LelZVVUs0c29WaWt6blVNZ1BjLWpDYWw5NVVIRnVlU0FCV3lPdzAtaHZsejZSWkZ1YVVsZlNEQ3NPdVhvdm9RR3ZpNVlyVkpZb2QwZElZc2xpTQ\u0026q=https%3A%2F%2Ftwitter.com%2Fcowboy%2Fstatus%2F339858717451362304\u0026v=x7cQ3mrcKaY","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbDJWbmZjNFVWV1AzeUJsc1pWUVlvZm4tMjJBQXxBQ3Jtc0tudG9uREwzWS11VDljbUdKdTlSSG9PNjBjSHFITW5LelZVVUs0c29WaWt6blVNZ1BjLWpDYWw5NVVIRnVlU0FCV3lPdzAtaHZsejZSWkZ1YVVsZlNEQ3NPdVhvdm9RR3ZpNVlyVkpZb2QwZElZc2xpTQ\u0026q=https%3A%2F%2Ftwitter.com%2Fcowboy%2Fstatus%2F339858717451362304\u0026v=x7cQ3mrcKaY","target":"TARGET_NEW_WINDOW","nofollow":true}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"Twitter Channel Link: 339858717451362304"}}}],"styleRuns":[{"startIndex":0,"length":6,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":6,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":46,"length":181,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":227,"length":24,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}}},{"startIndex":251,"length":297,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}],"attachmentRuns":[{"startIndex":228,"length":0,"element":{"type":{"imageType":{"image":{"sources":[{"url":"https://www.gstatic.com/youtube/img/watch/social_media/twitter_1x_v2.png"}]}}},"properties":{"layoutProperties":{"height":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"width":{"value":14,"unit":"DIMENSION_UNIT_POINT"},"margin":{"top":{"value":0.5,"unit":"DIMENSION_UNIT_POINT"}}}}},"alignment":"ALIGNMENT_VERTICAL_CENTER"}],"decorationRuns":[{"textDecorator":{"highlightTextDecorator":{"startIndex":227,"length":24,"backgroundCornerRadius":8,"bottomPadding":1,"highlightTextDecoratorExtensions":{"highlightTextDecoratorColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":452984831},{"key":"USER_INTERFACE_THEME_LIGHT","value":218103808}]}}}}}]},"headerRuns":[{"startIndex":0,"length":6,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":6,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":46,"length":181,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":227,"length":24,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":251,"length":297,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CKkCELsvGAMiEwiMjez_kIiSAxUVWA8CHfyVIM_KAQQx_PKs","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SC3g3Y1EzbXJjS2FZGAYyJSIRIgt4N2NRM21yY0thWTAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CKkCELsvGAMiEwiMjez_kIiSAxUVWA8CHfyVIM8=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CKgCELovIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/DgVS-zXgMTk/hqdefault.jpg?sqp=-oaymwE8CKgBEF5IWvKriqkDLwgBFQAAAAAYASUAAMhCPQCAokN4AfABAfgB_gmAAtAFigIMCAAQARg4IEgofzAP\u0026rs=AOn4CLDd9xFWrVVKEVfqWgtLVRoYbQFNyQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/DgVS-zXgMTk/hqdefault.jpg?sqp=-oaymwE9CNACELwBSFryq4qpAy8IARUAAAAAGAElAADIQj0AgKJDeAHwAQH4Af4JgALQBYoCDAgAEAEYOCBIKH8wDw==\u0026rs=AOn4CLDHGEZxS1lZ_xrPuC03ftPxwt4X2A","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"40:58","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"DgVS-zXgMTk","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"40분 58초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CKcCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"DgVS-zXgMTk","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKcCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CKYCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"DgVS-zXgMTk"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKYCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJ8CENTEDBgAIhMIjI3s_5CIkgMVFVgPAh38lSDP"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CKUCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKUCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"DgVS-zXgMTk","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CKUCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["DgVS-zXgMTk"],"params":"CAQ%3D"}},"videoIds":["DgVS-zXgMTk"],"videoCommand":{"clickTrackingParams":"CKUCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=DgVS-zXgMTk\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"DgVS-zXgMTk","playerParams":"ugUEEgJlbg%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=0e0552fb35e03139\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKUCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKQCEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJ8CENTEDBgAIhMIjI3s_5CIkgMVFVgPAh38lSDP"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"Pete Hunt: React - 모범 사례 재고(업데이트) - JSConf.Asia 2013"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/ytc/AIdro_ltRigbEjK9HfAhlU6gVdqYyHN7uulgrQfff_RXtLU0e-8=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"JSConf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJ8CENTEDBgAIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"/@jsconf_","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCzoVCacndDCfGDf41P-z0iA","canonicalBaseUrl":"/@jsconf_"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"JSConf"}}]},{"metadataParts":[{"text":{"content":"조회수 5.7만회"}},{"text":{"content":"12년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CKACEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CKMCEP6YBBgAIhMIjI3s_5CIkgMVFVgPAh38lSDP","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CKMCEP6YBBgAIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKMCEP6YBBgAIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"DgVS-zXgMTk","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CKMCEP6YBBgAIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["DgVS-zXgMTk"],"params":"CAQ%3D"}},"videoIds":["DgVS-zXgMTk"],"videoCommand":{"clickTrackingParams":"CKMCEP6YBBgAIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=DgVS-zXgMTk\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"DgVS-zXgMTk","playerParams":"ugUEEgJlbg%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=0e0552fb35e03139\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CKICEJSsCRgBIhMIjI3s_5CIkgMVFVgPAh38lSDP","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CKICEJSsCRgBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKICEJSsCRgBIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtEZ1ZTLXpYZ01Uaw%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CKACEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtEZ1ZTLXpYZ01Uaw%3D%3D","commands":[{"clickTrackingParams":"CKACEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDPygEEMfzyrA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CKECEI5iIhMIjI3s_5CIkgMVFVgPAh38lSDP","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKACEPBbIhMIjI3s_5CIkgMVFVgPAh38lSDP","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"DgVS-zXgMTk","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJ8CENTEDBgAIhMIjI3s_5CIkgMVFVgPAh38lSDP","visibility":{"types":"12"}}},"accessibilityContext":{"label":"Pete Hunt: React - 모범 사례 재고(업데이트) - JSConf.Asia 2013 40분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJ8CENTEDBgAIhMIjI3s_5CIkgMVFVgPAh38lSDPMgdyZWxhdGVkSKbT8Nbmm8TbxwGaAQUIARD4HcoBBDH88qw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=DgVS-zXgMTk\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"DgVS-zXgMTk","playerParams":"ugUEEgJlbg%3D%3D","nofollow":true,"ustreamerConfig":"KgYKBBICZW4=","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=0e0552fb35e03139\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/i793Qm6kv3U/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAxWdIVoLS5UXONChVApGe-HiLmOg","width":168,"height":94},{"url":"https://i.ytimg.com/vi/i793Qm6kv3U/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDKFmrtYLAn30oCLttezZG859iBMQ","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"29:07","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"i793Qm6kv3U","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"29분 7초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHover | 2026-01-13T08:49:02 |
https://popcorn.forem.com/new/tv | New Post - Popcorn Movies and TV Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Popcorn Movies and TV Close Join the Popcorn Movies and TV Popcorn Movies and TV is a community of 3,676,891 amazing enthusiasts Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Popcorn Movies and TV? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/events/python-user-group/past/#site-map | Our Events | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event from the Python User Group Calendar Past Events More Building an AI Agent 25 Nov. 2025 2025 5:30pm UTC – 8pm UTC JetBrains Amsterdam Terrace Tower office; Gelrestraat 16, 1079 MZ, Amsterdam, The Netherlands DELSU Tech Invasion 3.0 19 Nov. 2025 – 20 Nov. 2025 Abraka, Nigeria Python Meeting Düsseldorf - Python Herbst Sprint 2025 15 Nov. 2025 – 16 Nov. 2025 Düsseldorf, Germany Python Kino-Barcamp Südost 14 Nov. 2025 – 16 Nov. 2025 Peißenberg, Germany Python Leiden User Group 13 Nov. 2025 2025 6:15pm UTC – 9pm UTC Leiden, The Netherlands Django Girls Chongoene #2 08 Nov. 2025 2025 Chongoene, Gaza, Mozambique Python Event Subscriptions Subscribe to Python Event Calendars: Events in iCal format Python Events Calendars For Python events near you, please have a look at the Python events map . The Python events calendars are maintained by the events calendar team . Please see the events calendar project page for details on how to submit events , subscribe to the calendars , get Twitter feeds or embed them. Thank you. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://dev.to/x0x7b/observing-behavioral-anomalies-in-web-applications-beyond-signature-scanners-g6p#main-content | Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse 0x7b Posted on Jan 12 Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners # monitoring # performance # security # testing Most web scanners rely on payload signatures and response matching. In practice, I often see cases where the server behaves differently without any explicit error: latency spikes unexpected redirects status changes Signature-based tools usually report these scenarios as “clean”, even though they indicate backend instability or logic issues. The challenge is that these anomalies don’t fit traditional vulnerability categories like SQLi or XSS — they’re about how the system reacts under unusual input, not whether a known exploit triggers. Example Observation Below is a sample result from testing http://testphp.vulnweb.com/artists.php: Screenshot showing latency spikes (RTT) and body hash changes for specific inputs. Signature-based scanners would likely mark this as “clean”. Notice: artist=SLEEP(1) causes response time to jump from ~197ms → 3212ms BODY_HASH changes indicate server response altered Other inputs (%22, %5C, %255c) also trigger body changes without explicit errors These anomalies highlight how a server can behave unexpectedly under test conditions, which traditional signature-based scanners often miss. I’m curious how others in web security detect and interpret these kinds of behavioral anomalies during testing. (Optional reference for context: Blink ) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse 0x7b Follow Joined Jan 12, 2026 Trending on DEV Community Hot Agent Factory Recap: A Deep Dive into Agent Evaluation, Practical Tooling, and Multi-Agent Systems # vertexai # agents # testing # ai Meme Monday # discuss # watercooler # jokes The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/magalucloud/o-que-e-a-magalu-cloud-e-como-usar-o-console-e-a-cli-no-dia-a-dia-4l63 | O que é a Magalu Cloud e como usar o Console e a CLI no dia a dia - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Magalu Cloud for Magalu Cloud Posted on Jan 8 O que é a Magalu Cloud e como usar o Console e a CLI no dia a dia # magalucloud # cloud # braziliandevs A computação em nuvem deixou de ser um tema restrito a grandes empresas e passou a fazer parte do cotidiano de desenvolvedores, startups e times técnicos de todos os tamanhos. Nesse contexto, não basta saber o que é nuvem: é fundamental entender como uma plataforma funciona na prática e como interagir com ela no dia a dia . Neste artigo, você vai conhecer a Magalu Cloud , entender seu posicionamento como nuvem pública brasileira e aprender, de forma prática, como trabalhar com a plataforma usando o Console e a CLI . Ao final, a ideia é simples: você deve saber onde está, como navegar e como executar ações básicas com segurança e previsibilidade. Entendendo o que é a Magalu Cloud A Magalu Cloud é uma nuvem pública desenvolvida para oferecer serviços de computação, armazenamento, rede e governança com foco direto no mercado brasileiro. A plataforma foi pensada desde o início para operar com infraestrutura localizada no Brasil, preços em reais e total aderência à legislação nacional. Na prática, isso se reflete em alguns pontos importantes para quem desenvolve e opera sistemas. A proximidade física dos datacenters reduz a latência de aplicações voltadas ao público brasileiro. A cobrança em moeda local traz previsibilidade financeira e facilita o planejamento de custos. O suporte técnico acontece em português e a plataforma adota uma abordagem aberta, com APIs, CLI e integração com ferramentas de automação amplamente utilizadas no mercado. Mais do que abstrair a complexidade da nuvem, a proposta da Magalu Cloud é torná-la compreensível e controlável , permitindo que o desenvolvedor entenda claramente o que está criando, como os recursos se relacionam e quais impactos técnicos e operacionais isso traz. Console e CLI: duas formas de usar a plataforma Toda interação com a Magalu Cloud acontece, basicamente, de duas maneiras: pelo Console, que é a interface web gráfica, e pela CLI, que é a interface de linha de comando. Essas duas abordagens não competem entre si. Elas atendem a momentos diferentes da jornada técnica e, na prática, costumam ser usadas de forma complementar. O Console é o caminho mais natural para o primeiro contato. Ele facilita a exploração da plataforma, ajuda a entender como os serviços estão organizados e permite criar recursos manualmente com mais segurança visual. Já a CLI entra em cena quando surge a necessidade de repetição, automação ou maior controle sobre o fluxo de operações. Usando o Console da Magalu Cloud no dia a dia O Console é a interface gráfica da Magalu Cloud, acessada pelo navegador. É por ele que muitos desenvolvedores têm o primeiro contato com a plataforma e começam a entender como os serviços se organizam. Ao acessar o Console, você encontra um painel central que agrupa os serviços. Antes de criar qualquer recurso, vale dedicar alguns minutos apenas para navegar. Explore os menus, leia as descrições dos serviços e observe como eles se relacionam. O Console é especialmente útil para esse momento de aprendizado e para criações pontuais, quando você quer validar opções, entender campos de configuração e visualizar o impacto das escolhas que está fazendo. Trabalhando com a CLI da Magalu Cloud de forma prática A CLI da Magalu Cloud é a ferramenta que permite interagir com a plataforma diretamente pelo terminal. Ela é essencial para quem busca produtividade, automação e consistência nos ambientes. Para instalar a CLI, você pode seguir os passos da documentação . Após a instalação, o primeiro passo é autenticar sua conta, com o comando mgc auth login . Esse processo cria uma sessão local vinculada à sua identidade na Magalu Cloud e permite que os comandos executados no terminal tenham efeito real sobre os recursos da sua conta. Um bom ponto de partida é confirmar qual conta (tenant) está ativa no seu ambiente local. Para isso, você pode executar: mgc auth tenant current Enter fullscreen mode Exit fullscreen mode Esse comando retorna informações sobre o tenant autenticado, incluindo um identificador único. Conferir esse dado antes de criar ou alterar recursos é uma boa prática, especialmente se você trabalha com mais de uma conta ou ambiente. A partir daí, a CLI passa a ser uma forma objetiva de consultar e operar recursos. Por exemplo, listar zonas de disponibilidade disponíveis ajuda a entender onde seus recursos podem ser criados: mgc profile availability-zones list Enter fullscreen mode Exit fullscreen mode A saída desses comandos geralmente vem em formato estruturado, o que facilita tanto a leitura quanto o uso em scripts. Com o tempo, é comum combinar a CLI com ferramentas de automação, mas mesmo em uso manual ela já traz ganhos importantes: menos cliques, mais previsibilidade e facilidade para repetir operações. Mesmo que você ainda prefira o Console, usar a CLI desde cedo para consultas simples e validações ajuda a criar familiaridade com a ferramenta e prepara o terreno para cenários mais avançados, como automação e infraestrutura como código. Como escolher entre Console e CLI Na prática, a escolha entre Console e CLI não é uma questão de certo ou errado. O Console costuma ser mais indicado para exploração, aprendizado inicial e criações manuais pontuais. A CLI, por outro lado, se destaca quando você precisa repetir tarefas, automatizar fluxos ou garantir que operações sejam executadas sempre da mesma forma. No dia a dia, muitos times usam o Console para entender e validar configurações e recorrem à CLI para executar e manter ambientes. Essa combinação oferece equilíbrio entre clareza visual e eficiência operacional. Conclusão Antes de pensar em arquiteturas complexas, é essencial compreender a plataforma, as ferramentas disponíveis e a forma correta de interagir com elas. A Magalu Cloud oferece uma interface gráfica acessível e uma CLI poderosa, permitindo que desenvolvedores escolham a abordagem mais adequada para cada momento. Dominar essas duas formas de uso desde o início torna a experiência em nuvem mais segura, previsível e eficiente, além de preparar o caminho para soluções mais robustas no futuro. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Magalu Cloud Follow More from Magalu Cloud Como criar e escalar workloads Kubernetes com Container Registry na Magalu Cloud # cloud # magalucloud # kubernetes # braziliandevs Como provisionar um cluster PostgreSQL no DBaaS da Magalu Cloud com failover automático # magalucloud # cloud # braziliandevs # postgres Como anexar um volume de Block Storage à sua VM Linux na Magalu Cloud (via CLI) # cloud # magalucloud # braziliandevs 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://dev.to/tatyanabayramova/ai-in-assistive-technologies-for-people-with-visual-impairments-3peh#sources | AI in Assistive Technologies for People with Visual Impairments - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Tatyana Bayramova, CPACC Posted on Jan 12 • Originally published at tatanotes.com AI in Assistive Technologies for People with Visual Impairments # discuss # a11y # ai # news The other day, I watched a report on NHK WORLD JAPAN BIZ STREAM program about digital AIs and found out about Eye Navi app, which helps people with visual impairments to see and navigate the world around them. The app uses a smartphone camera to collect information about the environment and then processes it using AI to provide the user with an audio description: "The system provides audible notification of the presence or absence of pedestrians, car stops, and other obstacles to walking, as well as the color of pedestrian signals." Unfortunately, the app is currently only available in Japan, but while researching this topic, I found similar apps available in other countries: Be My Eyes - a free app that connects blind or low vision users who want support with volunteers and companies across the world through live video and AI. Lookout by Google - using your phone's camera, this app makes it easier to get more information about the world around you and allows you to do everyday tasks more efficiently like reading text and documents, sorting mail, etc. Lookout is available only on Android devices. Seeing AI by Microsoft - a free app that describes the world around you. It helps with everyday tasks, such as reading, describing photos, identifying products, and more. Image credit: Eye Navi website. Sources BIZ STREAM "Looking through Digital AIs" Eye Navi Be My Eyes Fee Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Tatyana Bayramova, CPACC Follow Senior Software Engineer | CPACC | IAAP Member | Accessibility Joined Dec 3, 2024 More from Tatyana Bayramova, CPACC Glaucoma Awareness Month # a11y # discuss # news Accessibility Testing on Windows on Mac # a11y # testing # web # discuss Our Rights, Our Future, Right Now - Celebrating Human Rights Day # a11y # discuss # news # learning 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://reactjs.org/docs/getting-started.html#writing-markup-with-jsx | Quick Start – React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog GET STARTED Quick Start Tutorial: Tic-Tac-Toe Thinking in React Installation Creating a React App Build a React App from Scratch Add React to an Existing Project Setup Editor Setup Using TypeScript React Developer Tools React Compiler Introduction Installation Incremental Adoption Debugging and Troubleshooting LEARN REACT Describing the UI Your First Component Importing and Exporting Components Writing Markup with JSX JavaScript in JSX with Curly Braces Passing Props to a Component Conditional Rendering Rendering Lists Keeping Components Pure Your UI as a Tree Adding Interactivity Responding to Events State: A Component's Memory Render and Commit State as a Snapshot Queueing a Series of State Updates Updating Objects in State Updating Arrays in State Managing State Reacting to Input with State Choosing the State Structure Sharing State Between Components Preserving and Resetting State Extracting State Logic into a Reducer Passing Data Deeply with Context Scaling Up with Reducer and Context Escape Hatches Referencing Values with Refs Manipulating the DOM with Refs Synchronizing with Effects You Might Not Need an Effect Lifecycle of Reactive Effects Separating Events from Effects Removing Effect Dependencies Reusing Logic with Custom Hooks Is this page useful? Learn React Quick Start Welcome to the React documentation! This page will give you an introduction to 80% of the React concepts that you will use on a daily basis. You will learn How to create and nest components How to add markup and styles How to display data How to render conditions and lists How to respond to events and update the screen How to share data between components Creating and nesting components React apps are made out of components . A component is a piece of the UI (user interface) that has its own logic and appearance. A component can be as small as a button, or as large as an entire page. React components are JavaScript functions that return markup: function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } Now that you’ve declared MyButton , you can nest it into another component: export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Notice that <MyButton /> starts with a capital letter. That’s how you know it’s a React component. React component names must always start with a capital letter, while HTML tags must be lowercase. Have a look at the result: App.js App.js Reload Clear Fork function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Show more The export default keywords specify the main component in the file. If you’re not familiar with some piece of JavaScript syntax, MDN and javascript.info have great references. Writing markup with JSX The markup syntax you’ve seen above is called JSX . It is optional, but most React projects use JSX for its convenience. All of the tools we recommend for local development support JSX out of the box. JSX is stricter than HTML. You have to close tags like <br /> . Your component also can’t return multiple JSX tags. You have to wrap them into a shared parent, like a <div>...</div> or an empty <>...</> wrapper: function AboutPage ( ) { return ( < > < h1 > About </ h1 > < p > Hello there. < br /> How do you do? </ p > </ > ) ; } If you have a lot of HTML to port to JSX, you can use an online converter. Adding styles In React, you specify a CSS class with className . It works the same way as the HTML class attribute: < img className = "avatar" /> Then you write the CSS rules for it in a separate CSS file: /* In your CSS */ .avatar { border-radius : 50 % ; } React does not prescribe how you add CSS files. In the simplest case, you’ll add a <link> tag to your HTML. If you use a build tool or a framework, consult its documentation to learn how to add a CSS file to your project. Displaying data JSX lets you put markup into JavaScript. Curly braces let you “escape back” into JavaScript so that you can embed some variable from your code and display it to the user. For example, this will display user.name : return ( < h1 > { user . name } </ h1 > ) ; You can also “escape into JavaScript” from JSX attributes, but you have to use curly braces instead of quotes. For example, className="avatar" passes the "avatar" string as the CSS class, but src={user.imageUrl} reads the JavaScript user.imageUrl variable value, and then passes that value as the src attribute: return ( < img className = "avatar" src = { user . imageUrl } /> ) ; You can put more complex expressions inside the JSX curly braces too, for example, string concatenation : App.js App.js Reload Clear Fork const user = { name : 'Hedy Lamarr' , imageUrl : 'https://i.imgur.com/yXOvdOSs.jpg' , imageSize : 90 , } ; export default function Profile ( ) { return ( < > < h1 > { user . name } </ h1 > < img className = "avatar" src = { user . imageUrl } alt = { 'Photo of ' + user . name } style = { { width : user . imageSize , height : user . imageSize } } /> </ > ) ; } Show more In the above example, style={{}} is not a special syntax, but a regular {} object inside the style={ } JSX curly braces. You can use the style attribute when your styles depend on JavaScript variables. Conditional rendering In React, there is no special syntax for writing conditions. Instead, you’ll use the same techniques as you use when writing regular JavaScript code. For example, you can use an if statement to conditionally include JSX: let content ; if ( isLoggedIn ) { content = < AdminPanel /> ; } else { content = < LoginForm /> ; } return ( < div > { content } </ div > ) ; If you prefer more compact code, you can use the conditional ? operator. Unlike if , it works inside JSX: < div > { isLoggedIn ? ( < AdminPanel /> ) : ( < LoginForm /> ) } </ div > When you don’t need the else branch, you can also use a shorter logical && syntax : < div > { isLoggedIn && < AdminPanel /> } </ div > All of these approaches also work for conditionally specifying attributes. If you’re unfamiliar with some of this JavaScript syntax, you can start by always using if...else . Rendering lists You will rely on JavaScript features like for loop and the array map() function to render lists of components. For example, let’s say you have an array of products: const products = [ { title : 'Cabbage' , id : 1 } , { title : 'Garlic' , id : 2 } , { title : 'Apple' , id : 3 } , ] ; Inside your component, use the map() function to transform an array of products into an array of <li> items: const listItems = products . map ( product => < li key = { product . id } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; Notice how <li> has a key attribute. For each item in a list, you should pass a string or a number that uniquely identifies that item among its siblings. Usually, a key should be coming from your data, such as a database ID. React uses your keys to know what happened if you later insert, delete, or reorder the items. App.js App.js Reload Clear Fork const products = [ { title : 'Cabbage' , isFruit : false , id : 1 } , { title : 'Garlic' , isFruit : false , id : 2 } , { title : 'Apple' , isFruit : true , id : 3 } , ] ; export default function ShoppingList ( ) { const listItems = products . map ( product => < li key = { product . id } style = { { color : product . isFruit ? 'magenta' : 'darkgreen' } } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; } Show more Responding to events You can respond to events by declaring event handler functions inside your components: function MyButton ( ) { function handleClick ( ) { alert ( 'You clicked me!' ) ; } return ( < button onClick = { handleClick } > Click me </ button > ) ; } Notice how onClick={handleClick} has no parentheses at the end! Do not call the event handler function: you only need to pass it down . React will call your event handler when the user clicks the button. Updating the screen Often, you’ll want your component to “remember” some information and display it. For example, maybe you want to count the number of times a button is clicked. To do this, add state to your component. First, import useState from React: import { useState } from 'react' ; Now you can declare a state variable inside your component: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; // ... You’ll get two things from useState : the current state ( count ), and the function that lets you update it ( setCount ). You can give them any names, but the convention is to write [something, setSomething] . The first time the button is displayed, count will be 0 because you passed 0 to useState() . When you want to change state, call setCount() and pass the new value to it. Clicking this button will increment the counter: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } React will call your component function again. This time, count will be 1 . Then it will be 2 . And so on. If you render the same component multiple times, each will get its own state. Click each button separately: App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } Show more Notice how each button “remembers” its own count state and doesn’t affect other buttons. Using Hooks Functions starting with use are called Hooks . useState is a built-in Hook provided by React. You can find other built-in Hooks in the API reference. You can also write your own Hooks by combining the existing ones. Hooks are more restrictive than other functions. You can only call Hooks at the top of your components (or other Hooks). If you want to use useState in a condition or a loop, extract a new component and put it there. Sharing data between components In the previous example, each MyButton had its own independent count , and when each button was clicked, only the count for the button clicked changed: Initially, each MyButton ’s count state is 0 The first MyButton updates its count to 1 However, often you’ll need components to share data and always update together . To make both MyButton components display the same count and update together, you need to move the state from the individual buttons “upwards” to the closest component containing all of them. In this example, it is MyApp : Initially, MyApp ’s count state is 0 and is passed down to both children On click, MyApp updates its count state to 1 and passes it down to both children Now when you click either button, the count in MyApp will change, which will change both of the counts in MyButton . Here’s how you can express this in code. First, move the state up from MyButton into MyApp : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { // ... we're moving code from here ... } Then, pass the state down from MyApp to each MyButton , together with the shared click handler. You can pass information to MyButton using the JSX curly braces, just like you previously did with built-in tags like <img> : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } The information you pass down like this is called props . Now the MyApp component contains the count state and the handleClick event handler, and passes both of them down as props to each of the buttons. Finally, change MyButton to read the props you have passed from its parent component: function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } When you click the button, the onClick handler fires. Each button’s onClick prop was set to the handleClick function inside MyApp , so the code inside of it runs. That code calls setCount(count + 1) , incrementing the count state variable. The new count value is passed as a prop to each button, so they all show the new value. This is called “lifting state up”. By moving state up, you’ve shared it between components. App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } Show more Next Steps By now, you know the basics of how to write React code! Check out the Tutorial to put them into practice and build your first mini-app with React. Next Tutorial: Tic-Tac-Toe Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms On this page Overview Creating and nesting components Writing markup with JSX Adding styles Displaying data Conditional rendering Rendering lists Responding to events Updating the screen Using Hooks Sharing data between components Next Steps | 2026-01-13T08:49:02 |
https://www.python.org/community/awards/psf-awards/ | PSF Community Service Awards | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF Community Service Awards Contents Introduction Expiration August 2025 April 2025 November 2024 October 2024 June 2024 March 2024 December 2022 June 2022 March 2022 December 2021 June 2021 March 2021 January 2021 December 2020 October 2020 June 2020 March 2020 December 2019 August 2019 June 2019 March 2019 December 2018 September 2018 June 2018 March 2018 December 2017 September 2017 June 2017 March 2017 December 2016 October 2016 June 2016 March 2016 December 2015 August 2015 July 2015 May 2015 December 2014 October 2014 March 2014 December 2013 November 2013 June 2013 April 2013 December 2012 October 2012 June 2012 February 2012 December 2011 September 2011 April 2011 January 2011 December 2010 October 2010 July 2010 March 2010 December 2009 October 2009 June 2009 March 2009 August 2008 March 2008 Introduction The Python Software Foundation relies on volunteer efforts to achieve many of its goals. The PSF Community Service Awards are a formal way for the PSF Board of Directors to offer recognition of work which, in its opinion, significantly improves the Foundation's fulfillment of its mission and benefits the broader Python community. The intention of these awards is to demonstrate that service to the Python community does lead to recognition and reward, rather than to provide a direct incentive to contributors. Awards will be made periodically, normally every three months, although the Board may choose to consider awards at other times. Any PSF member is entitled to propose an award at any time, stating the reasons for which the award is merited. Proposals should be made confidentially to the Board by sending an email to psf@python.org. The minutes of award considerations will not name the individuals concerned unless an award is made. The Board will contact proposers to keep them informed of the status of their proposals (such as when the proposal will receive Board consideration). If more than one award is proposed in a given period, the Board may elect to hold over a proposal. Awards will be considered in the order in which they are received. While it would be unusual for a single individual to receive multiple awards, repeated awards will be appropriate to acknowledge ongoing contributions. Recipients need not be Foundation members (though receiving an award may be an indication that consideration for membership is appropriate). Recognition will take the form of an award certificate plus both of the following: A cash award of $599. (Non-US based recipients will be subject to Federal US tax withholding of 30% unless all requirements are met, according to our Vendor Policies page. Contact accounting@python.org with any questions.) Free registration at all future PyCon US events, and the opportunity to apply for a travel grant for the recipient's travel and accommodation expenses. (Receipts will be required for all reimbursements.) The Board should consider awards at any quarterly meeting where a member award proposal has been received since the last award consideration. At each such meeting where no proposal has been received within the preceding three months the Board may, at its discretion, make an award to an individual nominated by the Board. Expiration If a Community Service Award recipient has not accepted their award within 6 months of written notification, the award expires. August 2025 Q2 2025 Community Service Award was given to Rodrigo Girão Serrão for contribution to the international Python community through leadership of PyCons in Portugal, speaking regularly at PyCons throughout the world, and contributing to the leadership of the Python community in Europe. Q2 2025 Community Service Award was given to Katie McLaughlin for contributions to the Australian and International Python Communities through leading PyCon AU and leading efforts to recognise Open Source contributions of all forms. Q2 2025 Community Service Award was given to Sarah Kuchinsky for contributions to the international Python community through continued leadership of the PyCon US tutorials, and in regional PyCon organizing. April 2025 Q1 2025 Community Service Award was given to Jay Miller for his service to the global Python community in improving the community’s diversity, inclusion, and equity through founding and sustaining Black Python Devs. Q1 2025 Community Service Award was given to Matt Lebrun & Micaela Reyes for building, growing and sustaining the Python community in the Philippines, including through organising conferences, meetups, and volunteer training programs. November 2024 Q4 2024 Community Service Award was given to Artur Czepiel for his exceptional contributions to the EuroPython Society, and for playing a key role in organizing Python Pizza in the Czech Republic and PyData and Pykonik meetups in Krakow. The Q4 Community Service Award was given to Iqbal Abdullah for contributions to the Python community in the Asia-Pacific region, including PyCon Malaysia, PyCon APAC, and PyCon Japan, as well as contributions to multiple PSF workgroups. October 2024 The Q3 2024 Community Service Award was given to Kojo Idrissa for delivering insightful talks, organizing events like DjangoCon, and engaging in discussions with developers and new Python developers. Kojo consistently champions the growth and inclusivity of the Python ecosystem. The Q3 Community Service Award was given to Joanna Jablonski for her multifaceted contributions across various domains, including her work as contributor to CPython, an interpreter author, and an architect of developer education tools and tutorials. The Q3 Community Service Award was given to Jessica Greene for her work as an organiser of PyLadies Berlin, for her contribution towards PyLadies Berlin, and support of women in the community. She has also been serving the conduct WG of the PSF and has contributed to arranging sponsored CoC workshops for community organisers. Jessica's work has empowered many women who cannot afford the travel to participate in one of the biggest Python conferences in Europe. June 2024 The Q2 2024 Community Service Award was given to Laís Carvalho in recognition of her work as a committee member of Python Ireland since 2019 and volunteer organiser of EuroPython since 2020 (the first online edition). Lais is also a co-organiser of Pyjamas (a Python conference where you can present wearing pajamas), a developer advocate, and she now serves on the EuroPython Society Board. The Q2 2024 Community Service Award was given to Raquel Dou for her exemplary work with the Europython Society as a Board Member and her considerable contributions to the EuroPython Conference serving on the CoC work group, organizing Trans*Code, working with keynotes, and many other conference details. The Q2 2024 Community Service Award was given to Leonard Richardson for his work as the founder and maintainer of the web-scraping library Beautiful Soup, his zine "Tool Safety” as well as his work as an architect and leader on the open source Library Simplified project which makes borrowing ebooks from a public library as easy as buying them from an online bookstore. March 2024 The Q1 2024 Community Service Award was given to Daisy Leigh Brenecki in recognition of her work leading the Python community in Australia, initially as an organizer of DjangoCon AU, and then leading PyCon Australia over four years. Throughout her time leading PyCon Australia, she has repeatedly demonstrated her ability to build teams and lead her events with a commitment to inclusivity and diversity which is an example of the best in the Python community. The Q1 2024 Community Service Award was given to Gregory Szorc as the author of python-build-standalone and PyOxidizer, among many other projects. python-build-standalone has quietly become a crucial component of the wider Python ecosystem. It provides builds of Python that can be installed in a way that avoids any risk of conflict with other existing installations so that Python can be painlessly distributed to users who are not themselves Python developers. The Q1 2024 Community Service Award was given to Mason Egger for his service as the President of the PyTexas Foundation, one of the oldest non-profit Python regional organizations in the USA and his tenure as the PyTexas conference chair from 2022 through 2024 December 2022 The Q4 2022 Community Service Award was given to Ned Deily for his contributions as the MacOS Release Manager since Python 3.2, and the Release Manager for Python 3.6 and 3.7. The Q4 2022 Community Service Award was given to Carol Willing for her work as a Python Core Developer and her years of service on the Python Steering Council. June 2022 The Q2 2022 Community Service Award was given to Philip James for all his contributions to the Python community, most notably his stewardship of the PSF's Code of Conduct Work Group as the Work Group Chair for its first four years. The Q2 2022 Community Service Award was given to Patrick Ben Koetter for his many years serving as postmaster for mail.python.org and supporting the Python community mailing lists and the PSF’s email traffic. March 2022 The Q1 2022 Community Service Award was given to John Hawley for his many years of volunteering on behalf of the PSF to support students and their mentors working on Python projects via Google Summer of Code. The Q1 2022 Community Service Award was given to Matthew Lagoe for his many years of volunteering on behalf of the PSF to support students and their mentors working on Python projects via Google Summer of Code. The Q1 2022 Community Service Award was given to James Lopeman for his many years of volunteering on behalf of the PSF to support students and their mentors working on Python projects via Google Summer of Code. December 2021 The Q4 2021 Community Service Award was given to Manabu Terada a member of the PyCon JP Association, for their work organizing local and regional PyCons, the work of monitoring our trademarks, and in particular organizing the "PyCon JP Charity Talks" raising more than $25,000 USD in funds for the PSF. The Q4 2021 Community Service Award was given to Takanori Suzuki a member of the PyCon JP Association, for their work organizing local and regional PyCons, the work of monitoring our trademarks, and in particular organizing the "PyCon JP Charity Talks" raising more than $25,000 USD in funds for the PSF. The Q4 2021 Community Service Award was given to Takayuki Shimizukawa a member of the PyCon JP Association, for their work organizing local and regional PyCons, the work of monitoring our trademarks, and in particular organizing the "PyCon JP Charity Talks" raising more than $25,000 USD in funds for the PSF. The Q4 2021 Community Service Award was given to Shunsuke Yoshida a member of the PyCon JP Association, for their work organizing local and regional PyCons, the work of monitoring our trademarks, and in particular organizing the "PyCon JP Charity Talks" raising more than $25,000 USD in funds for the PSF. The Q4 2021 Community Service Award was given to Jonas Obrist a member of the PyCon JP Association, for their work organizing local and regional PyCons, the work of monitoring our trademarks, and in particular organizing the "PyCon JP Charity Talks" raising more than $25,000 USD in funds for the PSF. June 2021 The Q3 2021 Community Service Award was given to Daniella Korossy . Daniella has contributed many efforts towards diversity and inclusivity work in the Hungarian Python community, tireless and year-long organization of Django Girls Budapest, and involvement in the Budapest Python user group. The Q3 2021 Community Service Award was given to Vicky Twomey-Lee . Vicky has been a PSF Fellow since 2012 and a long time volunteer to several PSF and Python spaces. 7 years ago she founded and continues to help organize the PyLadies Dublin chapter. Additionally, Vicky has been an active contributor to the PSF's Grants WG since the beginning and continues to provide helpful feedback and reviews. She also helps with EuroPython, Python Ireland, and past PyCon Ireland events. March 2021 The Q2 2021 Community Service Award was given to Dori Czapari . Dori has contributed many efforts towards diversity and inclusivity work in the Hungarian Python community, tireless and year-long organization of Django Girls Budapest, and involvement in the Budapest Python user group. The Q2 2021 Community Service Award was given to Szilvia Kadar . Szilvia has contributed many efforts towards diversity and inclusivity work in the Hungarian Python community, tireless and year-long organization of Django Girls Budapest, and involvement in the Budapest Python user group. January 2021 The Q1 2021 Community Service Award was given to Tereza Iofciu . Tereza is a PSF Code of Conduct WG member and has done a wonderful job helping, participating, and driving the Code of Conduct WG discussions. Tereza formed and continues to help organize the PyLadies Hamburg chapter and was a key organizer for the IWD PyLadies event in 2021. Tereza is also a member of the newly formed PSF Diversity & Inclusion WG. The Q1 2021 Community Service Award to Daniele Procida . Daniele chaired PyCon UK for a number years and was an early part of the organizing team for EuroPython. He was instrumental in starting the Python communities in Namibia and Ghana. Making sure that these conferences had strong support both financially and structurally. Daniele has been an executive member of the Pycon Africa team since we started and has been a consistent source of guidance. He continues to be a member of the Django Software Foundation and has spoken at many PyCons and DjangoCons around the world. December 2020 The Q4 2020 Community Service Award was given to Georgi Ker . Georgi has been instrumental with establishing PyLadies Global, she is also a PyLadies Bangkok organizer, member of the PSF Diversity & Inclusion WG, and an organizer with PyCon Thailand and APAC PyCon. The Q4 2020 Community Service Award was given to Humphrey Butau . Humphrey is the co-founder of PyCon Zimbabwe and was an early member of the Python community in Harare. He is a PSF fellow and has been stewarding our local community for a number of years. Humphrey is also a great speaker and has given talks at many conferences including keynoting DjangoCon Europe, speaking at PyCon Namibia and PyCon Italia. October 2020 The Q3 2020 Community Service Award was given to Elaine Wong for her community work. Elaine is an organizer for PyCon CA, PyLadies Toronto, and CSV Conference, a conference speaker, she co-hosts a monthly virtual Conference Organizer meetup, and Elaine helps with video at community events. The Q3 2020 Community Service Award was given to Rami Chowdhury for his community work. Rami helps organize and contributes to the DC Python user group. For many years Rami has been a volunteer coordinator and incident responder at PyCon US. Most recently Rami has been a helpful member of the PSF Code of Conduct WG. June 2020 The Q2 2020 Community Service Award was given to Noah Alorwu for his contributions to the growth of Python Ghana community, being an executive committee member of PyCon Africa and also organizing Django Girls workshop to bridge the gender gaps in tech. In 2019, he played an active role in organizing the first PyCon Africa and was the chair of the talk committee. Noah is also one of the founders of DjangoCon Africa, the upcoming inaugural conference for Django developers on the continent. He has spoken at several Python conferences including DjangoCon Europe. Noah is a consistent force for good, particularly in the African Python community. The Q2 2020 Community Service Award went to Katia Lira for her contributions to PyCon LatAm as conference chair, which held its inaugural conference in 2019. Additionally she's the DEFNA Vice-President and has collaborated in crafting the vision of PyLadies Global. Katia hosts and produces multiple Python/tech/community podcasts (e.g. El Dev Show), she's a PyCon speaker, speaks at meetups, and is well respected in the community. March 2020 The Q1 2020 Community Service Award has been given to to Manuel Kaufmann for the amazing efforts he put towards Python outreach and education in the Latin American Python communities and most recently in the Spanish Python communities. Most recently, Manuel helped organize efforts to translate Python material to Spanish. The 2020 Q1 Community Service Award went to Abigail Dogbe in recognition of her efforts with leading the PyLadies Ghana community, helping organize PyCon Africa, and volunteering for PyLadies global and PyCon US. December 2019 The Q4 2019 Community Service Award to Débora Azevedo in recognition of her work in supporting the wider Python community in Brazil and the PSF generally. She’s a cofounder of PyLadies Brasil leader, organizer for Django Girls Natal, and helped found and organize the PyLadies Brasil conference. In addition, Débora's also been interested in supporting the wider community. Last year Débora assisted the PSF by translating a survey into Portugese. Additionally, she is a regular presenter and attends many community events. The Q4 2019 Community Service Award went to Mark Sapiro in recognition of years of service maintaining mail.python.org’s Mailman lists and Postfix installation. Through good times and bad, Mark has regularly stepped up to ensure that the system is operating correctly and assist or lead the restoration of data after accidents and outages. August 2019 The Q3 2019 Community Service Award went to Mannie Young for being a humble and thoughtful leader, being an Executive Committee member for PyCon Africa, and for being a leader for Python Ghana. Mannie worked tirelessly to make sure PyCon Africa was a successful event by traveling to Accra several times to work on conference planning and was behind all of the conference design and social media activities for the event. The Q3 2019 Community Service Award went to Katie Bell for her work on PyCon AU as Co-Chair, her contributions in the years before her time as chair to PyCon AU, and helper/keynote/speaker at previous KiwiPyCons. She has also worked exceptionally hard participating in the incident reporting team at PyCon AU 2018 and 2019. This has stood as a go-to example for other conferences in the region, including feeding back into the PyCon Conduct process. She has also been the main person implementing on-site childcare at PyCon AU 2018 & 2019, which has also been an example for other conferences. The Q3 2019 Community Service Award went to Lillian Ryan for her work on PyCon AU as Papers Chair, and her contribution as speaker/keynote to a number of PyCons and DjangoCons. She has also worked extraordinarily hard behind the scenes to implement anonymous proposal submissions for PyCon AU. This effort has enabled PyCon AU to reduce bias in the conference proposal process, and has stood as an example for other conferences. The Q3 2019 Community Service Award went to Jessica Upani for being one of the most active members of PyCon Namibia, as well as the Conference Chair. As a high school mathematics teacher in Namibia, Jessica is bringing Python into the community in several ways such as promoting Python as a language to universities and also helping build out a variety of Python programming in her community for young people (eg PyNam Scholars). Jessica also is a prominent Python speaker having most recently spoke at PyCon Africa. June 2019 The Q2 2019 Community Service Award went to Felipe de Morais for his work towards facilitating the growth of the Python Brazilian community by organizing workshops, contributing to open source code that benefits the Brazilian people and for setting an example for all community organizers. The Q1 2019 Community Service Award also went to Chris Angelico for his work towards fostering the online Python community by helping maintain the pydotorg-www mailing list, helping community members get edit access to the public facing Python wiki, and also for being an active contributor to python-ideas mailing list and the python-dev mailing list. March 2019 The Q1 2019 Community Service Award went to Stefan Behnel for his work as the main developer and maintainer of two important Python projects: Cython and lxml. Stefan forked off Pyrex and started Cython almost 11 years ago. Cython makes writing and maintain a C extension or C library bindings simple. It plays a vital role in the numeric and scientific community, too. Without Cython, Python 3 adoption would have taken much longer. Cython hides much of the Python 2 / 3 C-API differences from the developer. https://pypi.org/project/Cython/ lxml is the fastest and most feature rich XML parsing, transforming and querying package for Python. It's also commonly used to parse HTML. https://pypi.org/project/lxml/ Stefan has been maintaining these two important libraries for over a decade. He is also a regular speaker at conferences and very helpful on the mailing lists. The Q1 2019 Community Service Award also went to Eric Ma for going above and beyond in his responsibilities as PyCon's Financial Aid Co-Chair for two years and this year stepping up to be Chair. Additionally, Eric has been a dedicated PyCon Program Committee member for several years. December 2018 The Q4 award went to Maricela (Mayela) Sánchez Miranda for her work as a PyCon Charlas 2019 Chair and founding member of PyCon Charlas as well as being an organizer for Python Day Mexico, and DjangoGirls Puebla. The Q4 award also went to John Roa for his work as a founder and Conference Chair of PyCon Colombia. September 2018 The Q3 award went to Mariatta Wijaya for her contributions to CPython, her efforts to improve the workflow of the Python core team, and her work to increase diversity in our community. In addition, her work as co-chair of PyCascades helps spread the growth of Python. The Q3 award also went to Alex Gaynor for his contributions to the Python and Django Communities and the Python Software Foundation. Alex previously served as a PSF Director in 2015-2016. He currently serves as an Infrastructure Staff member and contributes to legacy PyPI and the next generation warehouse and has helped legacy warehouse in security (disabling unsupported OpenID) and cutting bandwidth costs by compressing 404 images. June 2018 The Q2 award went to Mario Corchero for his leadership of the organization of PyConES, PyLondinium, and the PyCon Charlas track in 2018. His work has been instrumental in promoting the use of Python and fostering Python communities in Spain, Latin America, and the UK. The Q2 award also went to Chukwudi Nwachukwu for his contribution to spreading the growth of Python to the Nigerian community and his dedication and research to the PSF grants work group. March 2018 The Q1 award went to Jon Clements , Melanie Jutras , Rhys Yorke , Martijn Pieters , Patrice Neff , and Marc-Andre Lemburg . This is the PSF Jobs Volunteer Team and they have received this award for the many hours they have contributed to reviewing and managing the hundreds of job postings submitted on an annual basis December 2017 A. Jesse Jiryu Davis for the work he does on the PSF blog, his outreach & education efforts, and for organizing PyGotham 2017. Russell Keith-Magee for his contributions to Django, for his work on the BeeWare project, and for being an active international speaker at PyCons. September 2017 Eric Floehr for his work Chairing the PyOhio Conference. He is the founder and co-organizer of the Central Ohio Python User Group. COhPy has served as a resource for Python programmers in Columbus, OH. Eric's efforts to "spread Python love" via discussions with leaders of PyNash and IndyPy lead directly to the creation of the annual PyTennessee conference and the Pythonology quarterly mini-conferences. Thomas Kluyver for his contributions to the Scientific Python Community. Thomas has also served on many other open source projects and is active on the Python subreddit helping many people in the Python community. June 2017 Lynn Root for her work as the founder of the San Francisco Chapter of PyLadies, as a member of the Django Software Foundation, and as a tireless volunteer at PyCon. Glyph Lefkowitz for his work on the Twisted network programming framework and his contributions to the Python community in general. March 2017 Brian Costlow for his work organizing and chairing PyOhio, and for being the head volunteer for PyCon US captioning. Ian Cordasco for contributions to PSF elections and active mentoring of women in Python community. December 2016 Shannon Turner is the founder of Hear Me Code, an organization offering free, beginner-friendly Python coding classes for over 1500 women in DC. She teaches them all herself on her own time. She empowers hundreds of women to code with Python by lowering barriers to entry. More than just a class where women learn to build websites, Hear Me Code focuses on leadership development, peer mentoring, and turning students into teachers. Shannon never seeks praise or press because that is not what motivates her. She's a compassionate leader who is more concerned with elevating other women through her networks. Shannon's work, her impact in the Python community and the women who she has empowered to code are all examples that speak loudly for her. Ee Durbin for being a dedicated PSF volunteer for internal and external Python infrastructure as well as their contributions to PyCon US. October 2016 Sheila Miguez and William Kahn-Greene for their monumental work in creating and supporting PyVideo over the years. June 2016 Ned Batchelder for his tireless work helping run the Boston Python user group, being a regular speaker at conferences, maintaining coverage.py, and being a friendly face for the community on IRC and elsewhere. Stéphane Wirtel for his work organizing a Python User Group in Belgium, for his continued work creating marketing material for the PSF, for his continued outreach efforts with spreading the PSF's mission. March 2016 The following awards were announced in March for the 2016 1st Quarter: Damien George for his extensive volunteer work on the BBC micro:bit and MicroPython. Furthermore, Damien has spent time answering questions, offering help and reviewing code from the wider MicroPython/micro:bit community. Through his work on the MicroPython board, optimizations have also been made to CPython's speed. Jacqueline Kazil for her diligent volunteer effort running the Grants Work Group and for her continued assistance with PyCon's PyLadies Auction. December 2015 The following awards were announced in December for the 2015 4th Quarter: Terri Oda her successful organization of Google Summer of Code for the past few years (2013, 2014, 2015). Acting as the GSoC coordinator for Python, Terri organizes students, mentors, and participating Python projects. In 2015, over 70 students participated for Python. Berker Peksağ for his consistent volunteer efforts with pydotorg in 2015 ( https://github.com/python/pythondotorg/graphs/contributors ). August 2015 The following awards were announced in July for the 2015 3rd Quarter: Serhiy Storchaka for his contribution to Python. Serhiy has been a Python core developer since December 2012, and has been the most active core developer over the past three years. Victor Stinner for his contribution to Python. Victor has been a Python core developer since January 2010, and has been the second most active core developer over the past three years. July 2015 The following awards were announced in July for the 2015 2nd Quarter: Nicholas Tollervey for his work in getting Python promoted in UK education, running the education track at PyCon UK for several years and initiating the Python Code Dojo in London. May 2015 The following awards were announced in May for the 2015 1st Quarter: Armin Stross-Radschinski for his work on creating the PSF Python Brochure Jan Ulrich Hasecke for his work on creating the PSF Python Brochure December 2014 The following awards were announced in February 2015 for the 2014 4th Quarter: Ola Sitarska for her work creating and growing Django Girls, an educational program which has reached more than half a dozen countries, and continues to grow to many more Ola Sendecka for her work creating and growing Django Girls, an educational program which has reached more than half a dozen countries, and continues to grow to many more October 2014 The following awards were announced in October for the 2014 3rd Quarter: Christoph Gohlke for his work in providing hundreds of Python C extensions as pre-compiled Windows binaries for the community to use. Without him, a lot of Python software would be next to impossible to run on Windows 64-bit Armin Ronacher for his work on the Jinja2 templating library, the Flask web framework, the Logbook logging library, the Click command line application library (including making all of the preceding Python 2/3 compatible), the python-modernize Python 2/3 migration tool, contributions to the modernisation of the Web Server Gateway Interface for Python 3, as well as invaluable detailed feedback given to the core development team on some of the remaining operating system integration issues in Python 3 March 2014 The following awards were announced in March 2014: Diana Clarke , for work with the Canadian Python community, her organizing efforts for PyCon CA and PyCon US over the past several years, and her mentorship of many others in the community. Benjamin Peterson , for his work as core committer, his work on six and most recently his recent efforts on getting the new www.python.org website working, by fixing bugs faster than anyone else. R. David Murray , for his work as a core committer and as a long-time mentor of new contributors. December 2013 The following awards were announced in December 2013: Donald Stufft , for his tremendous contributions to the Python community by working on Python packaging, pip , security related problems and PyPI maintenance. Harald Armin Massa , < http://www.lightningtalkman.com/ >, for being a great community builder and single-handedly driving the lightning talks sessions on almost all European Python conferences in the past years, giving the talks his very own personal touch and turning them into memorable events every single time. November 2013 The following awards were announced in November 2013: Barry Warsaw for his work on Python 2.6 & Python 3.0, contributions to the CPython project, his work on the GNU Mailman project, and his contributions to the Debian and Ubuntu projects. June 2013 No awards were given. April 2013 The following awards were announced in April 2013: Tim Golden for his work on supporting the Windows Management Interface in Python and supporting that code and Windows users generally on comp.lang.python. Robin Dunn for being the principal maintainer of wxPython. December 2012 The following awards were announced in December 2012: Antoine Pitrou for his contribution to CPython, including his work on the GIL and his work involving the PSF infrastructure. Stefan Krah for his contribution to closing out PEP 3118, including being a maintainer of cdecimal. October 2012 The following awards were announced in October 2012: Kenneth Gonsalves for his significant contributions to furthering the use and awareness of Python in India. Kenneth passed away on August 3, 2012 and the award was presented to his daughter at PyCon India 2012. More information about the award is available on the PSF blog . Simon Cross for his efforts as lead organizer for the first PyCon South Africa, for efforts as a leader in the Cape Town Python User Group, and for contributions around the open source world. More information about the award is available on the PSF blog . June 2012 The following awards were announced in June 2012: Doug Hellmann for his efforts in getting the PSF's communications sorted out, and greatly improving the understanding of what the PSF does and stands for in the Python community. Thomas Heller for his many contributions to the Python codebase and ecosystem, from his work on the ctypes standard library to his work outside of core Python on projects like py2exe. February 2012 The following awards were announced in February, 2012. More information about the awards is available on the PSF blog . Audrey Roy for her outstanding work in creating PyLadies, with outreach and diversity issues, and for keynoting and advocating Python at numerous international conferences. Carl Trachte for his outstanding work to bring in foreign language speakers and support them on the Python Wiki. December 2011 The following awards were announced in December, 2011: Armin Rigo for his efforts in developing the PyPy implementation and his long-term contributions to the Python core. More information about the award is available on the PSF blog . Mike Müller for supporting Python in the scientific world, organizing the first two EuroSciPy conferences and the new annual PyCon DE conference. More information about the award is available on the PSF blog . September 2011 The following awards were announced on October 4, 2011: Arc Riley was awarded in recognition of his dedicated long-term support of the PSFs Summer of Code activities and domain management. More information about the award is available on the PSF blog . Nick Coghlan was awarded in recognition of his outstanding core development work and technical leadership, particularly with reference to the core-mentorship list. More information about the award is available on the PSF blog . The Python Software Foundation is pleased to recognize Arc and Nick's contributions to the community. April 2011 The following awards were announced on October 3, 2011: Laura Creighton was awarded in recognition of her continuous efforts in making community events happen and especially for her work with the PyPy team. More information about the award is available on the PSF blog . Tarek Ziade was awarded in recognition of his hard work on getting Python packaging back on track, maintaining distutils, and forking setuptools into distribute. More information about the award is available on the PSF blog . The Python Software Foundation is pleased to recognize Laura and Tarek's contributions to the community. January 2011 The following awards were announced on September 29, 2011: Van Lindberg was awarded in recognition of his leadership work on PyCon for the past two years as well as the pro bono work done for the PSF over the years. More information about the award is available on the PSF blog . Benjamin Peterson was awarded in recognition of his work as release manager and the numerous contributions to the Python Core. The Python Software Foundation is pleased to recognize Van and Benjamin's contributions to the community. More information about the award is available on the PSF blog . The Python Software Foundation is pleased to recognize Van and Benjamin's contributions to the community. December 2010 The following award was announced on January 6, 2011: Doug Hellmann was awarded in recognition of his contributions to Python online and offline. Doug is the creator and maintainer of the Python Module of the Week < http://www.doughellmann.com/PyMOTW/ > series, worked on Python Magazine, and is the leader of the PSF Communications team. The Python Software Foundation is pleased to give this award to this worthy member of the Python community. The following award was announced on January 3, 2011: Andrew Kuchling was awarded in recognition of his work promoting Python everywhere he can. Andrew chaired PyCon for two years and has contributed significantly to Python's online presence. He also prepares the "What's New" documentation < http://docs.python.org/dev/whatsnew/index.html > for new releases of Python. The Python Software Foundation is pleased to recognize Andrew's contributions to the community. October 2010 The following award was announced on November 03, 2010 in a PSF blog article : Michael Foord was awarded in recognition of his incredible work in promoting Python everywhere he could. Michael is active on IRC channels, mailing lists, conferences, sprints and similar events. On the development side, he has been doing incredible work on unittest and unittest2. Michael also helps maintain the Planet Python RSS feed and python.org website, and with organizing the Europython meeting and Summit . July 2010 The following award was announced on October 30, 2010 in a PSF blog article : John Pinner in recognition of his organizational skills and contributions as one of the primary organizers of PyCon UK and EuroPython received his award at EuroPython 2010. March 2010 The following awards were announced on March 19, 2010 in a PSF blog article : Ken Whitesell has been a PyCon supporter for a very long time. Itâs hard to remember a time when Ken wasnât working behind the reception desk to make sure that delegates received all the help they need. Ken has also done sterling work in presenting many tutorials at PyCon, and has evangelized Python to the commercial world over a long period. Yarko Tymciurak has provided several years meritorious service in developing and maintaining electronic registration and payment systems for PyCon. He has also shown exceptional dedication to providing high levels of customer service to both delegates and sponsors, going above and beyond the call of duty in assisting with registration issues. December 2009 The following awards were announced on March 19, 2010 in a PSF blog article : Catherine Devlin received her award for her long-term contributions to PyCon, the organization of the first two PyOhio regional conferences, for promoting diversity in the Python community and for education efforts. Facundo Batista's award came for organizing PyCon Argentina and the Argentinian Python community as well as contributions to the standard library and work in translating the Python documentation. October 2009 The following awards were announced on October 25, 2009 in a PSF blog article : Noufal Ibrahim was nominated for heading up the organizing team for the recent (and very successful) first PyCon India conference held on September 26 and 27 in Bangalore, attracting 450 delegates. Although Noufal was "first among equals" this award also recognizes the work of everyone who helped to make the inaugural conference so successful. Barry Warsaw . Many people are unaware of the huge volume of mail that is processed by software written in Python every hour of every day. This is because they don't know about the Mailman project, which was Barry's brainchild. Barry, a founding member of the Foundation, also acted as release manager for several recent Python releases. June 2009 The following awards were announced on June 18, 2009 in a PSF blog article : Stephan Deibel was last year's outgoing chairman after four years in harness. This year Stephan has stepped down as a director, after helping to ensure that the Foundation's bylaws were reorganized. Stephan developed pythonology.com to promote Python, and his work as founder of Wingware and a developer of the Wing IDE has also had a significant impact. Sean Reifschneider has master-minded the PyCon networking every time it has worked, and without the support of this always helpful and reliably competent tummy.com director our conferences simply would not have been the same. March 2009 The following awards were announced on March 29, 2009, at PyCon 2009 in Chicago ( PSF blog article ): Mary Rush has given selflessly for four years now, staffing the registration desk and providing a friendly face for PyCon. Carl Karsten has been a great asset to PyCon. His energy and enthusiasm have helped PyCon reach new highs. August 2008 The following awards were announced on August 7, 2008 ( PSF blog article ): Georg Brandl has been an enthusiastic contributor to the core for several years, and a while ago stunned the Python development world by building the Sphinx documentation system as an alternative to the LaTeX-based system we had been using previously, and converting the Python documentation to use it. Brett Cannon has also been an active core developer for many years, but was nominated for his infrastructure work in migrating the Python bug-tracking system off of SourceForge to our own Roundup instance, and for his efforts keeping the Python developer introduction updated. March 2008 The following awards were announced on March 16, 2008, during PyCon in Chicago (and followed up with a PSF blog post ): Matthew Dixon Cowles : Matthew has been a tireless (and unfailingly polite) responder to the many users of the python-help mailing list , used by those seeking assistance not readily available through other channels. This assistance covers not only elementary questions but also quite advanced ones. Matthew has been a member of the Python community for many years, patiently answering questions and enlightening those who seek to get more out of the Python language. Brad Knowles : Brad has managed the python.org e-mail since I can remember, and it's down to him that our lists and newsgroups are so blissfully free of spam. It's hard to appreciate the sheer volume of mail that Brad handles, and he is fiercely defensive of our domain's status on the Internet. Keeping the e-mail flowing is essential not just to the PSF but also to all the users of mailing lists and newsgroups. Brad does all this not because he is a big Python user, but because it needs to be done. This is the community service ethic at its best. Peter Kropf and Martin Thomas : Peter and Martin are probably best known to those people who want to employ Python programmers, as they have jointly been almost the sole workforce behind the Python Job Board for the last several years. The fact that the Job Board exists, and is available free of charge to anyone looking to hire people with Python skills, is possibly more central to Python's rise in popularity than we appreciate. PyCon chairman David Goodger paid tribute to the Job Board as helping him out of unemployment in his opening remarks this year, and I know there are dozens if not hundreds of others who should be similarly grateful to Peter and Martin. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://gg.forem.com/about | About - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close About This is a new Subforem, part of the Forem ecosystem. You are welcome to the community and stay tuned for more! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:02 |
https://tatanotes.com/blog/glaucoma-awareness-month-2026 | TataNotes – Web Accessibility Personal Blog Glaucoma Awareness Month – TataNotes Skip to main content TataNotes… …all about a11y Blog About me Raising Awareness Glaucoma Awareness Month January is Glaucoma Awareness Month, dedicated to raising awareness about glaucoma — a group of eye diseases that can lead to blindness if not treated. Learn what you can do to support people with glaucoma. Reading time: around 2 min Publication date January 11, 2026 Glaucoma is one of the leading causes of blindness worldwide, affecting millions of people. It is estimated that approximately 80 million people globally have glaucoma, and the number is projected to grow to over 111 million by 2040 . Glaucoma is commonly known as the “silent thief of sight” because it usually has no symptoms in its early stages. With this condition, the optic nerve gets damaged slowly, leading to vision field reduction and, if left untreated, blindness. High intraocular pressure (IOP) is a major risk factor for glaucoma. Elevated IOP can damage the optic nerve fibers, leading to progressive vision loss, resulting in glaucoma. However, glaucoma can also occur in individuals with normal IOP levels, known as normal-tension glaucoma. High IOP alone is not a definitive indicator of glaucoma. Unfortunately, due to late diagnosis, one person I know lost their vision. Even though glaucoma has no cure yet, blindness could be prevented with regular eye exams and early treatment, such as applying eye drops, or performing an SLT procedure that helps lower IOP to prevent further damage to the optic nerve. What can you do to support people with glaucoma? Learn more about needs of people with glaucoma Glaucoma affects the way people perceive the environment. Use vision simulators like Glaucoma Vision Simulator or NoCoffee vision simulator for Firefox to understand how glaucoma affects vision. Adapt your digital and physical projects so that they’re easy to use with visual impairments. Similar simulators exist for other visual impairments as well. For digital content, follow WCAG and PDF/UA standards WCAG criteria like 1.1.1. Non-text Content (Level A) , 1.4.4 Resize Text (Level AA) , and 4.1.2 Name, Role, Value (Level A) address needs of people with visual impairments, including glaucoma. This is not an exhaustive list, and you should aim to follow other WCAG criteria to ensure your digital content is accessible to people with disabilities. To ensure PDF accessibility, follow PDF/UA (PDF for Universal Access) standard. This will help make your documents accessible by users of assistive technologies, such as screen readers. Ensure compliance with EN 301 549 standard for a wider range of products European standard EN 301 549 specifies accessibility requirements for a broad range of products and services, including hardware, software, websites, and electronic documents. By following this standard, you can make your digital content is accessible to people with disabilities, including those with visual impairments like glaucoma. Complying with these standards is a great first step, but keep in mind that no guideline or automated tool guarantees accessibility. An effective way to ensure accessibility is to conduct accessibility user testing with people with disabilities. Accomodate for people with visual impairments, including glaucoma Adopt accessible practices in the physical world. Design physical spaces with accessibility in mind — for example, provide printed materials and signage in Braille or large print, whenever possible. To help people with glaucoma navigate the environment, install tactile paving. Support your local glaucoma organizations There are many organizations around the world that support glaucoma research, provide guidance and support groups for people with glaucoma. You can find a glaucoma society in your country on the World Glaucoma Association’s list of member societies . Here are some glaucoma organizations you can support: European Glaucoma Society National Glaucoma Patient Support Groups American Glaucoma Society Glaucoma Research Society of Canada Glaucoma Australia By keeping accessibility barriers in mind, we can help ensure that individuals with glaucoma and other visual impairments can access and benefit from the great variety of products and public services. Sources How fast does glaucoma progress without treatment? Global prevalence of glaucoma and projections of glaucoma burden through 2040: a systematic review and meta-analysis Glaucoma Vision Simulator NoCoffee vision simulator for Firefox WCAG (Web Content Accessibility Guidelines) PDF/UA (PDF for Universal Access) European standard EN 301 549 Tatyana Bayramova © 2024–present Important: All rights reserved | 2026-01-13T08:49:02 |
https://www.python.org/community/awards/ | Python Community Awards | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> News & Community >>> Community Awards Python Community Awards Python Software Foundation Community Service Awards are given to members of the community who significantly improve the Foundation's fulfillment of its mission. Python Software Foundation Distinguished Service Awards are given to members of the community whose long-term efforts have significantly influenced and shaped the Python community. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://hmpljs.forem.com/t/tutorial#main-content | Tutorial - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close # tutorial Follow Hide Tutorial is a general purpose tag. We welcome all types of tutorial - code related or not! It's all about learning, and using tutorials to teach others! Create Post submission guidelines Tutorials should teach by example. This can include an interactive component or steps the reader can follow to understand. Older #tutorial posts 1 2 3 4 5 6 7 8 9 … 75 … 2222 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/psf/records/staff/ | Python Software Foundation Staff | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Python Software Foundation Staff Deb Nicholson Executive Director Deb Nicholson joined the PSF in April 2022. She is an experienced non-profit professional and passionate open source community builder who has worked at the Open Source Initiative, Software Freedom Conservancy and the Open Invention Network. She is also a founding organizer of the Seattle GNU/Linux Conference, an annual event dedicated to surfacing new voices and welcoming new people to the free software community. She'll be building on the PSF's existing work to strengthen and diversify the global Python community, identifying new education and outreach opportunities and increasing technical and organizational capacities. She is a sci-fi nerd who lives with her partner and her lucky black cat in Cambridge, Massachusetts. Loren Crary Deputy Executive Director Loren joined the PSF in November 2021 to grow and diversify the PSF’s base of financial support. She works with members, donors, sponsors, grant-awarding organizations, and the Board of Directors to expand the resources available to run our programs and strengthen the long-term sustainability of the PSF. Loren has a B.A. from Amherst College and a J.D. from Stanford Law School. Prior to the PSF, she spent seven years leading fundraising, U.S. operations, and strategic revenue growth for Educate!, a non-profit social enterprise serving youth in Uganda, Rwanda, and Kenya. Outside of work, Loren enjoys solving cryptic crosswords, making weird art with friends, writing fiction, and playing with her rescue pup. Ee Durbin Director of Infrastructure Ee joined the PSF after years of volunteering with the PSF Infrastructure Working Group, PyPI, and PyCon US. They support Python community infrastructure such as www.python.org, pypi.org, and mail.python.org collaborating with volunteers from from around the globe. Internally, Ee takes responsibility for evaluating, strengthening, and implementing systems used by the PSF staff and board of directors to fulfill our mission. Outside of the PSF Ee enjoys making and consuming tacos, riding their bikes, and convincing themself that their cats love them. Olivia Sauls Program Director Olivia joined the PSF in August 2021 and is the lead planner for the Python Software Foundation's annual flagship event, PyCon US. She holds a B.S. in Biology and a B.S. in Nonprofit Management from the University of Wisconsin-Madison and has worked in various roles throughout the nonprofit sector. When she’s not working, Olivia can be found skiing, hiking with her dog, or spending time with friends and family. Laura Graves Senior Accountant Laura joined the PSF in February 2019 to assist with processing grants and donations, tracking expenses, and other general accounting functions. She has her Master's of Accountancy from the University of Alabama, and has worked in various accounting roles across many industries. When she's not working, Laura can usually be found reading, scuba diving, or petting a nearby dog. Seth Larson Python Security Developer in Residence Seth joined the PSF in June 2023 as the Security Developer in Residence. He works on broadly improving the security posture of the Python ecosystem across many projects including CPython and PyPI. Outside of work, Seth enjoys playing games of all varieties, tending to his garden, and eating at new restaurants in his hometown of Minneapolis, Minnesota. Mike Fiedler PyPI Safety and Security Engineer With over thirty years of software and systems experience, Mike is a seasoned professional who has accumulated extensive knowledge and expertise in the field. He has actively engaged with the Python community, contributing to open source projects and sharing his insights. His leadership roles at companies like Datadog, Warby Parker, and others have enabled him to mentor and guide others in the tech industry. Recognized as an AWS Container Hero and an avid open source maintainer, Mike's dedication to learning, problem-solving reflects his holistic approach to technology. Beyond his professional pursuits, Mike's personal life is just as vibrant. He has been a dedicated volunteer roller derby referee for the past 15 years, and he enjoys experimenting with various vegetarian dishes in the kitchen. Mike currently resides in New York City with his partner, Elyssa. Marie Nordin Community Communications Manager Marie joined the PSF in October 2023 as Community Communications Manager to strengthen our communications, as well as enhance our support of Python community initiatives. She has a background in community architecture, program management, Code of Conduct, and graphic design. Marie's Open Source journey began as an Outreachy intern in 2013 for the Fedora Project, where she has continued to contribute and serve in various roles. She is also a founder of the Creative Freedom Summit, an annual event dedicated to sharing knowledge around creative free software, raising awareness, and connecting artists and designers. Outside of work, Marie enjoys making art, solving the hardest jigsaw puzzles she can find, and playing board and video games. Jacob Coffee Infrastructure Engineer Jacob joined the PSF in July 2024 as an Infrastructure Engineer. With a passion for the Python community and open source in general, he brings valuable experience from his involvement in the greater Python ecosystem. He's also a maintainer in the Litestar organization, contributing to several popular packages. When not immersed in code, Jacob enjoys cooking, baking, and spending time with his two daughters and various pets. Jacob is excited to turn his hobby into a career, supporting the Python community through his role at the PSF. Maria Ashna PyPI Support Specialist Maria has recently worked at the Brain and Creativity Institute at USC working on research related to the impact of music and arts education on the brain and the neuroscience of creativity. Maria is also the founder of The Magic Light Bulb, Inc., a tech and product consulting firm. Previously, Maria has taught and worked as a lecturer in the School of Gerontology at USC, worked at The MIND Research Network, and had various roles in tech, from technical project specialists to product management. Maria is also a classically trained performer who has performed in numerous theater and film productions around the world. She received her first Master's degree in Information Systems and Technology from Claremont Graduate University, and her second Master's in Neuroimaging and Informatics from USC. Maria studied neuroscience and theatre as an undergraduate at the University of New Mexico. Maria has also trained in theatre and performing arts with the Moscow Art Theatre School and American Rep Theatre faculty at Harvard University. She is always hunting for the best sweet potato fries in the land! Jaime Barrera Community Events Coordinator Jaime joined the PSF in January 2025 as the Community Events Coordinator to assist in the planning and support of PyCon US. His relationship with the PSF started over 10 years ago as a vendor at PyCon US providing onsite support with registration and lead retrieval. He has an extensive background in trade shows and conferences from small to large scale across a broad range of industries. His past 3 years as an onsite organizer at PyCon US led him to join the PyCon US team full-time. When he’s not working, he spends his time with his two sons, collecting sneakers and looking for the world’s best taco. Kelly Ragland Finance Manager Kelly joined the PSF as Finance Manager in 2025. She brings over 11 years of higher education experience, including 8 years as Research Center Manager for the Colorado Center for Advanced Ceramics and the Metallurgy and Materials Department at the Colorado School of Mines. In this role, she managed research operations, budgets, and administrative functions for a leading academic research facility. A lifelong Colorado native from Boulder, Kelly currently lives in the mountains at 9,000 feet elevation where she embraces the high-altitude lifestyle. Winter is her favorite season, and she enjoys mountain living. Outside of work, Kelly is actively involved in her children's education and serves as a volunteer coach for recreational athletic clubs. She enjoys contributing to her local school community and helping young athletes develop their skills and teamwork abilities. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/nominations/elections/ | Elections | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> Membership >>> PSF Elections Elections Nominations Closed 2025 Python Software Foundation Board Election The following people were elected to the Board: Abigail Dogbe Jannis Leidel Sheena O’Connell Simon Willison View nominations Election began: Sept. 2, 2025 Nominations Opened: Tue, 29 Jul 2025 14:00:00 +0000 Nominations Closed: Tue, 12 Aug 2025 14:00:00 +0000 2024 Python Software Foundation Board Election The following people were elected to the Board: Tania Allard KwonHan Bae Cristián Maureira-Fredes View nominations Election began: July 2, 2024 Nominations Opened: Tue, 11 Jun 2024 14:00:00 +0000 Nominations Closed: Tue, 25 Jun 2024 14:00:00 +0000 2023 Python Software Foundation Board Election The following people were elected to the Board: Cheuk Ting Ho Denny Perez Georgi Ker Christopher Neugebauer KwonHan Bae View nominations Election began: June 20, 2023 Nominations Opened: Thu, 01 Jun 2023 00:00:00 +0000 Nominations Closed: Thu, 15 Jun 2023 23:59:59 +0000 2022 Python Software Foundation Board Election The following people were elected to the board: Kushal Das Jannis Leidel Dawn Wages Simon Willison View nominations Election began: June 20, 2022 Nominations Opened: Wed, 01 Jun 2022 16:00:00 +0000 Nominations Closed: Thu, 16 Jun 2022 12:00:00 +0000 2021 Bylaws Proposed Changes Election The following resolutions were approved: Section 5.15 Limits on Co-affiliation of Board Members Resolution approved by the board of directors RESOLVED, that the Python Software Foundation board approve the bylaw implementation of 'Section 5.15. Limits on Co-affiliation of Board Members' as proposed here , to be voted on by the membership during the next election. Context The board is focused on promoting a diverse and international community. Many directors work at organizations that are part of our community, sponsor the PSF, and/or volunteer in some other way. It happens occasionally that several board members are employed by the same organization, and this shouldn’t be an impediment for their service. At the same time the Board wants to guard against a situation where a single entity has complete control over the PSF by gaining a majority of the board seats. It’s not quite enough to declare allegiances and let voting members decide who to elect, because for example one company taking over another could result in a majority on the Board. The Bylaw changes aim to prevent such Board capture. Section 4.8. Fellows Resolution approved by the board of directors RESOLVED, that the Python Software Foundation board approve the bylaw updates to 'Section 4.8. Fellows' as proposed here , to be voted on by the membership during the next election. Context The PSF Board noticed that the current bylaws lacked the ability for the board to fully delegate Fellow approvals to the Fellows Work Group. Going forward, the board prefers an option to empower the WG (which is composed of only Fellow members) to accept nominations, vote on them, and officially approve them. If these changes are approved, the pull request will be made against the official bylaw repository. View nominations Election began: June 23, 2021 Nominations Opened: Wed, 30 Jun 2021 19:03:08 +0000 Nominations Closed: Wed, 30 Jun 2021 19:03:09 +0000 2021 Python Software Foundation Board Election The following people were elected to the board: Joannah Nanjekye Débora Azevedo Tania Allard View nominations Election began: June 8, 2021 Nominations Opened: Thu, 06 May 2021 08:00:00 +0000 Nominations Closed: Tue, 01 Jun 2021 08:00:00 +0000 2020 Python Software Foundation Board Election The following people were elected to the board: Nina Zakharenko Dustin Ingram Jeff Triplett Thomas Wouters View nominations Election began: June 8, 2020 Nominations Opened: Wed, 06 May 2020 08:00:00 +0000 Nominations Closed: Thu, 04 Jun 2020 12:02:02 +0000 2019 Python Software Foundation Board Election The following people were elected to the board: Lorena Mesa Kushal Das Marlene Mhangami Jannis Leidel View nominations Election began: June 7, 2019 Nominations Opened: Sun, 05 May 2019 08:00:00 +0000 Nominations Closed: Sat, 01 Jun 2019 08:00:00 +0000 The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/events/python-user-group/#site-map | Our Events | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event from the Python User Group Calendar Upcoming Events Python Meeting Düsseldorf 14 Jan. 2026 2026 5pm UTC – 8pm UTC Düsseldorf, Germany Python Leiden User Group 22 Jan. 2026 2026 6:15pm UTC – 9pm UTC Leiden, The Netherlands PyLadies Amsterdam: Robotics beginner class with MicroPython 27 Jan. 2026 2026 5pm UTC – 8pm UTC Amsterdam, The Netherlands and Online Python BarCamp Karlsruhe 2026 21 Feb. 2026 – 22 Feb. 2026 Karlsruhe, Germany Python Meeting Düsseldorf 22 April 2026 2026 4pm UTC – 7pm UTC Düsseldorf, Germany Python Event Subscriptions Subscribe to Python Event Calendars: Events in iCal format Python Events Calendars For Python events near you, please have a look at the Python events map . The Python events calendars are maintained by the events calendar team . Please see the events calendar project page for details on how to submit events , subscribe to the calendars , get Twitter feeds or embed them. Thank you. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/events/python-user-group/past/#content | Our Events | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event from the Python User Group Calendar Past Events More Building an AI Agent 25 Nov. 2025 2025 5:30pm UTC – 8pm UTC JetBrains Amsterdam Terrace Tower office; Gelrestraat 16, 1079 MZ, Amsterdam, The Netherlands DELSU Tech Invasion 3.0 19 Nov. 2025 – 20 Nov. 2025 Abraka, Nigeria Python Meeting Düsseldorf - Python Herbst Sprint 2025 15 Nov. 2025 – 16 Nov. 2025 Düsseldorf, Germany Python Kino-Barcamp Südost 14 Nov. 2025 – 16 Nov. 2025 Peißenberg, Germany Python Leiden User Group 13 Nov. 2025 2025 6:15pm UTC – 9pm UTC Leiden, The Netherlands Django Girls Chongoene #2 08 Nov. 2025 2025 Chongoene, Gaza, Mozambique Python Event Subscriptions Subscribe to Python Event Calendars: Events in iCal format Python Events Calendars For Python events near you, please have a look at the Python events map . The Python events calendars are maintained by the events calendar team . Please see the events calendar project page for details on how to submit events , subscribe to the calendars , get Twitter feeds or embed them. Thank you. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/prospectus2026/ | PyCon US and PSF Prospectus 2025-26 | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PyCon US and PSF Prospectus 2025-26 PyCon US and Python Software Foundation Sponsorship Prospectus 2025-26 Download and review our sponsorship options today! The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/events/python-user-group/2124/ | Building an AI Agent | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Building an AI Agent JetBrains Amsterdam Terrace Tower office; Gelrestraat 16, 1079 MZ, Amsterdam, The Netherlands 25 Nov. from 5:30pm UTC to 8pm UTC , 2025 Building an AI Agent Explore events -- Change your date range More events at JetBrains Amsterdam Terrace Tower office; Gelrestraat 16, 1079 MZ, Amsterdam, The Netherlands Building an AI Agent ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/faq/ | Python Software Foundation FAQ | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Python Software Foundation FAQ Contents What is the Python Software Foundation? Who are on the PSF board? Who are the officers? How do I reach the PSF? How do I join the PSF? How can I follow PSF activities? How can I provide feedback? What is the Python Software Foundation? From the PSF Mission Statement : The mission of the Python Software Foundation is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers. The Python Software Foundation (PSF) is a non-profit membership organization devoted to advancing open source technology related to the Python programming language. It qualifies under the US Internal Revenue Code as a tax-exempt 501(c)(3) scientific and educational public charity, and conducts its business according to the rules for such organizations. The PSF is a corporation according to U.S. tax law, incorporated in the state of Delaware. Our federal taxpayer ID ("04 number") is 04-3594598. For a quick overview of the PSF's activities, please see the our About page . Who are on the PSF board? Who are the officers? The PSF board and officers are listed on the Board of Directors & Officers page. How do I reach the PSF? For general inquiries, please email psf@python.org . For sponsorship questions, please email sponsors@python.org . For accounting questions, including how to send ACH, wire, Zelle, or other payments to the PSF or suspicious checks, please contact accounting@python.org . Postal address: Python Software Foundation 9450 SW Gemini Dr. ECM# 90772 Beaverton, OR 97008 USA Fax: 1-858-712-8966 How do I join the PSF? See the membership FAQ for detailed information on both basic membership and the other kinds of membership available to individuals. Sponsorship is also available for organizations. See the sponsorship page for details. How can I follow PSF activities? Sign up to receive our newsletter! It is currently sent out about every other month. Python Software Foundation News is a blog announcing and discussing PSF activities. You can follow us on Twitter , Mastodon , and LinkedIn as well. You can sign up here for psf-members-announce , which is a moderated, very low traffic list used for announcements to the PSF members, primarily regarding elections. How can I provide feedback? For questions about the PSF, or for comments on the PSF web pages, please write to psf@python.org . For questions about Python, please write to help@python.org . For comments on the python.org web pages, please write to webmaster@python.org . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/mission/ | Mission | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> About >>> Mission Statement Mission The mission of the Python Software Foundation is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers. You can help fund the PSF by making a donation or becoming a member . The following is the official mission statement of the PSF: The Python Software Foundation (PSF) is a non-profit membership organization devoted to advancing open source technology related to the Python programming language. It qualifies under the US Internal Revenue Code as a tax-exempt 501(c)(3) scientific and educational public charity, and conducts its business according to the rules for such organizations. The PSF: Produces the core Python distribution, made available to the public free of charge. This includes the Python language itself, its standard libraries and documentation, installers, source code, educational materials, and assorted tools and applications. Establishes PSF licenses, ensuring the rights of the public to freely obtain, use, redistribute, and modify intellectual property held by the PSF. Works with the Open Source Initiative to ensure that PSF licenses conform to the Open Source Definition. Holds Python's intellectual property rights for releases 2.1 and following. Seeks to obtain the intellectual property rights for Python releases prior to 2.1, for relicensing under the PSF Python license, to relieve the legal burden on Python's users. The PSF may also seek rights to other Python-related software for relicensing under a PSF license. Protects the Python name, and the names, service marks and trademarks associated with all other intellectual property held by the PSF. Solicits and manages contributions to the Python codebase, and may perform these services on behalf of other open source Python-related codebases. Raises funds to support PSF programs and services. The regulations for public charity funding are complex. Some consequences are that the vast bulk of funding must come from private contributions (including sponsoring memberships) and public grants, must come from a broad base, and that no single private donor can supply a substantial percentage of the PSF's total funding. Additional revenue may be pursued in ways consistent with then-current rules for public charities and with Python's standing as an open source project. For example, the PSF may offer to sell conference proceedings, special Python distributions, or merchandise with distinctive insignia. Publicizes, promotes the adoption of, and facilitates the ongoing development of Python-related technology and educational resources. This includes, but is not limited to, maintaining a public web site, planning Python conferences, and offering grants to Python-related open source projects. Encourages and facilitates Python-related research in the public interest. "Open source" is defined as: freely available technology licensed under terms compatible with Version 1.9 (or later) of the Open Source Definition, as established by the Open Source Initiative (see https://opensource.org/ ). Note The mission statement above was approved by the PSF Board of Directors on March 2, 2002, and amended by the Board on August 15, 2006, and September 14, 2009 (brief version). See the PSF Board Resolutions page for details. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://peps.python.org/pep-0002/ | PEP 2 – Procedure for Adding New Modules | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 2 Toggle light / dark / auto colour theme PEP 2 – Procedure for Adding New Modules Author : Brett Cannon <brett at python.org>, Martijn Faassen <faassen at infrae.com> Status : Active Type : Process Created : 07-Jul-2001 Post-History : 07-Jul-2001, 09-Mar-2002 Table of Contents Introduction Acceptance Procedure Maintenance Procedure Copyright Introduction The Python Standard Library contributes significantly to Python’s success. The language comes with “batteries included”, so it is easy for people to become productive with just the standard library alone. It is therefore important that the usefulness of the standard library be maintained. Due to the visibility and importance of the standard library, it must be maintained thoughtfully. As such, any code within it must be maintained by Python’s development team which leads to a perpetual cost to each addition made. There is also added cognitive load for users in familiarizing themselves with what is in the standard library to be considered. New functionality is commonly added to the library in the form of new modules. This PEP will describe the procedure for the addition of new modules. PEP 4 deals with procedures for deprecation of modules; the removal of old and unused modules from the standard library. Acceptance Procedure For top-level modules/packages, a PEP is required. The procedure for writing a PEP is covered in PEP 1 . For submodules of a preexisting package in the standard library, additions are at the discretion of the general Python development team and its members. General guidance on what modules typically are accepted into the standard library, the overall process, etc. are covered in the developer’s guide . Maintenance Procedure Anything accepted into the standard library is expected to be primarily maintained there, within Python’s development infrastructure. While some members of the development team may choose to maintain a backport of a module outside of the standard library, it is up to them to keep their external code in sync as appropriate. Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0002.rst Last modified: 2025-02-01 08:59:27 GMT Contents Introduction Acceptance Procedure Maintenance Procedure Copyright Page Source (GitHub) | 2026-01-13T08:49:02 |
https://www.python.org/events/python-user-group/2090/ | DELSU Tech Invasion 3.0 | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event DELSU Tech Invasion 3.0 Abraka, Nigeria From 19 Nov. through 20 Nov. , 2025 DELSU Tech Invasion 3.0 Explore events -- Change your date range More events at Abraka, Nigeria DELSU Tech Invasion 3.0 Django Girls Abraka Workshop Django Summit DELSU Django Girls Abraka Workshop 2024 Django Girls Abraka Workshop ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/records/ | Python Software Foundation Public Records | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF >>> About >>> Public Records Python Software Foundation Public Records Incorporation Here is a transcript of the Articles of Incorporation . Bylaws Here are the PSF Bylaws . Board of Directors PSF Board Members & Officers Resolutions Meeting Minutes Python Software Foundation Policies: Conflict of Interest Policy Whistleblower Policy Python.org Email Policy PSF Staff Current staff IRS recognition of tax exempt status The PSF is a United States 501(c)(3) corporation domiciled in Delaware. Final determination letter from the IRS, May 5, 2006 (960KB PDF scan) Advanced ruling exemption letter, Feb. 25, 2003 (OCR of original) Form 872-C (470K scanned JPEG image) The original copies of our tax exempt application, IRS form 1023, have been lost by the PSF. The IRS provided the PSF this letter . The PSF's IRS Form 1023 application requesting 501(c)(3) public charity status, in three formats: MS Word , HTML , plain text . (The latter two formats were generated by MS Word.) Tax Returns and Financial Information The PSF is a United States 501(c)(3) public charity with a strong commitment to transparency and compliance. 2024 filings and related documents 2024 Annual Report 2024 990 To Come 2023 filings and related documents 2023 Annual Report 2023 990 2022 filings and related documents 2022 Annual Report 2022 990 2021 filings and related documents 2021 Annual Report 2021 990 2021 Audited Financial Statements 2020 filings and related documents 2020 Annual Report 2020 990 2020 Audited Financial Statements 2019 filings and related documents 2019 Annual Report 2019 990 2018 filings and related documents 2018 Annual Report 2018 Form 990 2017 990 2016 990 2015 990 2014 990 2013 990 2012 990 2011 990 2010 990 2009 990 2008-EZ 990 2007 990 2006 990 2005 990 2004 990 2003 990-EZ 2002 990-EZ (Filed 990-N because income <$25,000) 2001 990-EZ The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://peps.python.org/pep-0007/ | PEP 7 – Style Guide for C Code | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 7 Toggle light / dark / auto colour theme PEP 7 – Style Guide for C Code Author : Guido van Rossum <guido at python.org>, Barry Warsaw <barry at python.org> Status : Active Type : Process Created : 05-Jul-2001 Post-History : Table of Contents Introduction C standards Common C code conventions Code lay-out Naming conventions Documentation Strings Copyright Introduction This document gives coding conventions for the C code comprising the C implementation of Python. Please see the companion informational PEP describing style guidelines for Python code . Note, rules are there to be broken. Two good reasons to break a particular rule: When applying the rule would make the code less readable, even for someone who is used to reading code that follows the rules. To be consistent with surrounding code that also breaks it (maybe for historic reasons) – although this is also an opportunity to clean up someone else’s mess (in true XP style). C standards Follow the following standards. For features that aren’t in the relevant standard, use CPython-specific wrappers (for example: _Py_atomic_store_int32 , Py_ALWAYS_INLINE , Py_ARITHMETIC_RIGHT_SHIFT ; _Py_ALIGNED_DEF in public headers). When adding such wrappers, try to make them easy to adjust for unsupported compilers. Python 3.11 and newer versions use C11 without optional features . The public C API should be compatible with C99 and C++. (As a reminder to any users reading this: this PEP is a style guide ; these rules are there to be broken.) Python 3.6 to 3.10 use C89 with several select C99 features: Standard integer types in <stdint.h> and <inttypes.h> . We require the fixed width integer types. static inline functions designated initializers (especially nice for type declarations) intermingled declarations booleans C++-style line comments Python versions before 3.6 used ANSI/ISO standard C (the 1989 version of the standard). This meant, amongst many other things, that all declarations were at the top of a block. Common C code conventions Don’t use compiler-specific extensions, such as those of GCC or MSVC. For example, don’t write multi-line strings without trailing backslashes. All function declarations and definitions must use full prototypes. That is, specify the types of all arguments and use (void) to declare functions with no arguments. No compiler warnings with major compilers (gcc, VC++, a few others). static inline functions should be preferred over macros in new code. Code lay-out Use 4-space indents and no tabs at all. No line should be longer than 79 characters. If this and the previous rule together don’t give you enough room to code, your code is too complicated – consider using subroutines. No line should end in whitespace. If you think you need significant trailing whitespace, think again – somebody’s editor might delete it as a matter of routine. Function definition style: function name in column 1, outermost curly braces in column 1, blank line after local variable declarations. static int extra_ivars ( PyTypeObject * type , PyTypeObject * base ) { int t_size = PyType_BASICSIZE ( type ); int b_size = PyType_BASICSIZE ( base ); assert ( t_size >= b_size ); /* type smaller than base! */ ... return 1 ; } Code structure: one space between keywords like if , for and the following left paren; no spaces inside the paren; braces are required everywhere, even where C permits them to be omitted, but do not add them to code you are not otherwise modifying. All new C code requires braces. Braces should be formatted as shown: if ( mro != NULL ) { ... } else { ... } The return statement should not get redundant parentheses: return ( albatross ); /* incorrect */ Instead: return albatross ; /* correct */ Function and macro call style: foo(a, b, c) – no space before the open paren, no spaces inside the parens, no spaces before commas, one space after each comma. Always put spaces around assignment, Boolean and comparison operators. In expressions using a lot of operators, add spaces around the outermost (lowest-priority) operators. Breaking long lines: if you can, break after commas in the outermost argument list. Always indent continuation lines appropriately, e.g.: PyErr_Format ( PyExc_TypeError , "cannot create '%.100s' instances" , type -> tp_name ); When you break a long expression at a binary operator, braces should be formatted as shown: if ( type -> tp_dictoffset != 0 && base -> tp_dictoffset == 0 && type -> tp_dictoffset == b_size && ( size_t ) t_size == b_size + sizeof ( PyObject * )) { return 0 ; /* "Forgive" adding a __dict__ only */ } It’s OK to put operators at ends of lines, especially to be consistent with surrounding code. (See PEP 8 for a longer discussion.) Vertically align line continuation characters in multi-line macros. Macros intended to be used as a statement should use the do { ... } while (0) macro idiom, without a final semicolon. Example: #define ADD_INT_MACRO(MOD, INT) \ do { \ if (PyModule_AddIntConstant((MOD), (#INT), (INT)) < 0) { \ goto error; \ } \ } while (0) // To be used like a statement with a semicolon: ADD_INT_MACRO ( m , SOME_CONSTANT ); #undef file local macros after use. Put blank lines around functions, structure definitions, and major sections inside functions. Comments go before the code they describe. All functions and global variables should be declared static unless they are to be part of a published interface. For external functions and variables, we always have a declaration in an appropriate header file in the “Include” directory, which uses the PyAPI_FUNC() macro and PyAPI_DATA() macro, like this: PyAPI_FUNC ( PyObject * ) PyObject_Repr ( PyObject * ); PyAPI_DATA ( PyTypeObject ) PySuper_Type ; Naming conventions Use a Py prefix for public functions; never for static functions. The Py_ prefix is reserved for global service routines like Py_FatalError ; specific groups of routines (e.g. specific object type APIs) use a longer prefix, e.g. PyString_ for string functions. Public functions and variables use MixedCase with underscores, like this: PyObject_GetAttr , Py_BuildValue , PyExc_TypeError . Occasionally an “internal” function has to be visible to the loader; we use the _Py prefix for this, e.g.: _PyObject_Dump . Macros should have a MixedCase prefix and then use upper case, for example: PyString_AS_STRING , Py_PRINT_RAW . Macro parameters should use ALL_CAPS style, so they are easily distinguishable from C variables and struct members. Documentation Strings Use the PyDoc_STR() or PyDoc_STRVAR() macro for docstrings to support building Python without docstrings ( ./configure --without-doc-strings ). The first line of each function docstring should be a “signature line” that gives a brief synopsis of the arguments and return value. For example: PyDoc_STRVAR ( myfunction__doc__ , "myfunction(name, value) -> bool \n\n \ Determine whether name and value make a valid pair." ); Always include a blank line between the signature line and the text of the description. If the return value for the function is always None (because there is no meaningful return value), do not include the indication of the return type. When writing multi-line docstrings, be sure to always use backslash continuations, as in the example above, or string literal concatenation: PyDoc_STRVAR ( myfunction__doc__ , "myfunction(name, value) -> bool \n\n " "Determine whether name and value make a valid pair." ); Though some C compilers accept string literals without either: /* BAD -- don't do this! */ PyDoc_STRVAR ( myfunction__doc__ , "myfunction(name, value) -> bool \n\n Determine whether name and value make a valid pair . "); not all do; the MSVC compiler is known to complain about this. Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0007.rst Last modified: 2025-08-27 10:48:57 GMT Contents Introduction C standards Common C code conventions Code lay-out Naming conventions Documentation Strings Copyright Page Source (GitHub) | 2026-01-13T08:49:02 |
https://www.python.org/psf/community-stories/#content | Community Stories | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Python >>> Shared Stories Packaging People who need to install Python packages get confused a lot. That's not their fault; that's because the volunteers who maintain the packaging tools don't have enough time to get everything organized so that it's clear and easy to use. In the last few years, the PSF has gotten grants and used that money to massively improve packaging. We overhauled PyPI and we're making pip more consistent, with genuine attention to user experience. With more funding, we can finally make managing packages pleasant as programming in Python. Sumana Harihareswara, Changeset Consulting CPython Development I started using Python in my PhD for performing different simulations of rotating black holes, black hole jets and their properties. I quickly fell in love with the language and its community and that led me to become a core dev some years ago. Since I became a core dev I have worked towards making Python faster and more versatile. Although most of my work is in the parser, the compiler pipeline and the garbage collector I like to work all over the place fixing bugs and trying to spot performance improvement opportunities. Hopefully, in the following years, we can push Python forward to the future by improving its general speed, making it more compatible with other implementations and improving the multi-core experience. Although this will be a challenging path and will require drastic changes in Python itself and its C-API, I am very excited about the things to come and what awaits for the Python Language and its community :) Pablo Galindo Salgado, Python Core Developer Community trainings A huge turning point in my career was a Python workshop. I programmed a bit as a kid, and took a single CS class in college, and tried to poke along doing some self-study so I could get better. And then I attended a Boston Python Workshop for Women And Their Friends http://bostonpythonworkshop.com/ , led by Jessica McKellar. We worked through well-designed exercises and I got hands-on practice that helped me get through that transition, from painstakingly copying individual lines and functions into the interpreter, to thinking in terms of Python's program flow. Years later, my Python and software management skills have been invaluable. I run a small business, where I've been able to hire, train, and mentor contract workers who then go on to get full-time programming jobs. We've helped overhaul the Python Package Index, mentored and recruited contributors to Zulip, helped journalists open-source their code, and more. Right now I'm leading pip's work replacing its dependency resolver, which is a game-changer for future work making Python packaging easier to deal with. People who care about Python invested in running that workshop, and it's paid off very well in my case. Investing in Python events, and the organization that supports them, is a good bet. Sumana Harihareswara, Changeset Consulting PyCon US In 2015, as I was figuring out what I wanted to do next with my career, I attended PyCon North America in Montreal. I volunteered with the GNU Mailman team to expedite the release of Mailman 3.0. At the end of the sprint, I thought, "maybe I could charge for this." Later that year, I started Changeset Consulting, where I expedite long-awaited releases for open source software projects. Through Changeset, I helped the PSF finish and deploy the new PyPI, and I'm working on pip's dependency resolver overhaul and a fresh release of GNU Autoconf. If it weren't for the PSF, my life would be very different, and probably a lot less interesting. Sumana Harihareswara, Changeset Consulting An important community event that the PSF produces is PyCon US, where community members get a chance to receive training, share ideas, or even be mentored. At PyCon US 2019, Sumana Harihareswara helped Brian Rutledge make his 1st contribution to Python Packaging. Months later he became a co-maintainer of Twine, the upload utility for PyPI. As of May 2020, he successfully worked with a newer contributor to finish adding PEP 484 type annotations to Twine's codebase. This will make it easier for us to keep this code bug-free in the future, which means open source maintainers can have a smooth experience sharing their code with us on PyPI! Sumana Harihareswara, Changeset Consulting Grants Program My name is Iqbal and I have been using Python for 18 years. On a professional level Python as a programming tool has given me a career, and on a personal level as an ideology has helped me make friends and given me satisfaction by giving me the opportunity to be part of something bigger than myself. As member or lead of the different conference committee and also as conference chair, I have worked hard to make sure anyone can participate and contribute, regardless of personal situation, among others: Grants program were started for those that are financially constrained, quotas were setup for first time speakers, opportunities to present talks were initiated for non-english speakers, partnership with other groups such as Women Who Code and PyLadies to bolster underrepresented women groups in the conferences. Last but not least, in the beginning I also helped introduce a Code Of Conduct based on PSF's CoC to introduce a safe and welcoming environment for everyone. At that time, it wasn't common yet to have CoCs for conferences. The PSF has done a wonderful job by taking the lead and acting as a standard bearer for us in the rest of the world to follow. Initiatives such as their grants program that helps monetarily and also gives exposure to less known events, knowledge and know-how on how to manage conferences and meetups, and most importantly an access to other people within the community to share and source out ideas have been invaluable to us. Going forward, with the new normal, supporting virtual events is definitely an important thing which the PSF can help with. A step-by-step guide on how to manage virtual events, how tos for tools and a platform to expose events to the worldwide community would be very helpful. In a world that is widening in terms of inequality where we tend to take away more and more, I am happy to be part of a community led by the PSF that continues to share and give: through code, through knowledge, through money and through friendship. Iqbal Abdullah, Regional Conference Organizer ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/community-stories/#site-map | Community Stories | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Python >>> Shared Stories Packaging People who need to install Python packages get confused a lot. That's not their fault; that's because the volunteers who maintain the packaging tools don't have enough time to get everything organized so that it's clear and easy to use. In the last few years, the PSF has gotten grants and used that money to massively improve packaging. We overhauled PyPI and we're making pip more consistent, with genuine attention to user experience. With more funding, we can finally make managing packages pleasant as programming in Python. Sumana Harihareswara, Changeset Consulting CPython Development I started using Python in my PhD for performing different simulations of rotating black holes, black hole jets and their properties. I quickly fell in love with the language and its community and that led me to become a core dev some years ago. Since I became a core dev I have worked towards making Python faster and more versatile. Although most of my work is in the parser, the compiler pipeline and the garbage collector I like to work all over the place fixing bugs and trying to spot performance improvement opportunities. Hopefully, in the following years, we can push Python forward to the future by improving its general speed, making it more compatible with other implementations and improving the multi-core experience. Although this will be a challenging path and will require drastic changes in Python itself and its C-API, I am very excited about the things to come and what awaits for the Python Language and its community :) Pablo Galindo Salgado, Python Core Developer Community trainings A huge turning point in my career was a Python workshop. I programmed a bit as a kid, and took a single CS class in college, and tried to poke along doing some self-study so I could get better. And then I attended a Boston Python Workshop for Women And Their Friends http://bostonpythonworkshop.com/ , led by Jessica McKellar. We worked through well-designed exercises and I got hands-on practice that helped me get through that transition, from painstakingly copying individual lines and functions into the interpreter, to thinking in terms of Python's program flow. Years later, my Python and software management skills have been invaluable. I run a small business, where I've been able to hire, train, and mentor contract workers who then go on to get full-time programming jobs. We've helped overhaul the Python Package Index, mentored and recruited contributors to Zulip, helped journalists open-source their code, and more. Right now I'm leading pip's work replacing its dependency resolver, which is a game-changer for future work making Python packaging easier to deal with. People who care about Python invested in running that workshop, and it's paid off very well in my case. Investing in Python events, and the organization that supports them, is a good bet. Sumana Harihareswara, Changeset Consulting PyCon US In 2015, as I was figuring out what I wanted to do next with my career, I attended PyCon North America in Montreal. I volunteered with the GNU Mailman team to expedite the release of Mailman 3.0. At the end of the sprint, I thought, "maybe I could charge for this." Later that year, I started Changeset Consulting, where I expedite long-awaited releases for open source software projects. Through Changeset, I helped the PSF finish and deploy the new PyPI, and I'm working on pip's dependency resolver overhaul and a fresh release of GNU Autoconf. If it weren't for the PSF, my life would be very different, and probably a lot less interesting. Sumana Harihareswara, Changeset Consulting An important community event that the PSF produces is PyCon US, where community members get a chance to receive training, share ideas, or even be mentored. At PyCon US 2019, Sumana Harihareswara helped Brian Rutledge make his 1st contribution to Python Packaging. Months later he became a co-maintainer of Twine, the upload utility for PyPI. As of May 2020, he successfully worked with a newer contributor to finish adding PEP 484 type annotations to Twine's codebase. This will make it easier for us to keep this code bug-free in the future, which means open source maintainers can have a smooth experience sharing their code with us on PyPI! Sumana Harihareswara, Changeset Consulting Grants Program My name is Iqbal and I have been using Python for 18 years. On a professional level Python as a programming tool has given me a career, and on a personal level as an ideology has helped me make friends and given me satisfaction by giving me the opportunity to be part of something bigger than myself. As member or lead of the different conference committee and also as conference chair, I have worked hard to make sure anyone can participate and contribute, regardless of personal situation, among others: Grants program were started for those that are financially constrained, quotas were setup for first time speakers, opportunities to present talks were initiated for non-english speakers, partnership with other groups such as Women Who Code and PyLadies to bolster underrepresented women groups in the conferences. Last but not least, in the beginning I also helped introduce a Code Of Conduct based on PSF's CoC to introduce a safe and welcoming environment for everyone. At that time, it wasn't common yet to have CoCs for conferences. The PSF has done a wonderful job by taking the lead and acting as a standard bearer for us in the rest of the world to follow. Initiatives such as their grants program that helps monetarily and also gives exposure to less known events, knowledge and know-how on how to manage conferences and meetups, and most importantly an access to other people within the community to share and source out ideas have been invaluable to us. Going forward, with the new normal, supporting virtual events is definitely an important thing which the PSF can help with. A step-by-step guide on how to manage virtual events, how tos for tools and a platform to expose events to the worldwide community would be very helpful. In a world that is widening in terms of inequality where we tend to take away more and more, I am happy to be part of a community led by the PSF that continues to share and give: through code, through knowledge, through money and through friendship. Iqbal Abdullah, Regional Conference Organizer ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse The Python Software Foundation is the charitable organization behind the Python programming language. We support the Python Community through... Grants In 2024, the PSF awarded $655,000 USD to 257 groups or individuals in 61 countries around the world. Infrastructure We support and maintain python.org , The Python Package Index , Python Documentation , and many other services the Python Community relies on. PyCon US We produce and underwrite the PyCon US Conference , the largest annual gathering for the Python community. Support from sponsors, attendees, PyLadies, and CPython enabled us to award more than $384,000 USD in travel grants to 254 attendees for PyCon US 2025. Mastodon Become a Member Help the PSF promote, protect, and advance the Python programming language and community! Membership FAQ Donate Assist the foundation's goals with a donation. The PSF is a recognized 501(c)(3) non-profit organization. How to Contribute Volunteer Learn how you can help the PSF and the greater Python community! How to Volunteer Sponsors Without our sponsors we wouldn't be able to help the Python community grow and prosper. Sponsorship Possibilities PSF Grants Program The Python Software Foundation welcomes grant proposals for projects related to the development of Python, Python-related technology, and educational resources. Proposal Guidelines, FAQ and Examples PSF News PSF News: $500K+ Raised for Python for Everyone, PyCon US, & More! PSF News Special Edition: Python is For Everyone & PyCon US 2026 Sovereign Tech Agency and PSF Security Partnership PSF Code of Conduct Working Group Shares First Transparency Report Python is for Everyone: Grab PyCharm Pro for 30% off—plus a special bonus! Python is for everyone: Join in the PSF year-end fundraiser & membership drive! Connecting the Dots: Understanding the PSF’s Current Financial Outlook Improving security and integrity of Python package archives Open Infrastructure is Not Free: PyPI, the Python Software Foundation, and Sustainability A new PSF Board- Another year of PSF Board Office Hour sessions! ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/community-stories/#top | Community Stories | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Python >>> Shared Stories Packaging People who need to install Python packages get confused a lot. That's not their fault; that's because the volunteers who maintain the packaging tools don't have enough time to get everything organized so that it's clear and easy to use. In the last few years, the PSF has gotten grants and used that money to massively improve packaging. We overhauled PyPI and we're making pip more consistent, with genuine attention to user experience. With more funding, we can finally make managing packages pleasant as programming in Python. Sumana Harihareswara, Changeset Consulting CPython Development I started using Python in my PhD for performing different simulations of rotating black holes, black hole jets and their properties. I quickly fell in love with the language and its community and that led me to become a core dev some years ago. Since I became a core dev I have worked towards making Python faster and more versatile. Although most of my work is in the parser, the compiler pipeline and the garbage collector I like to work all over the place fixing bugs and trying to spot performance improvement opportunities. Hopefully, in the following years, we can push Python forward to the future by improving its general speed, making it more compatible with other implementations and improving the multi-core experience. Although this will be a challenging path and will require drastic changes in Python itself and its C-API, I am very excited about the things to come and what awaits for the Python Language and its community :) Pablo Galindo Salgado, Python Core Developer Community trainings A huge turning point in my career was a Python workshop. I programmed a bit as a kid, and took a single CS class in college, and tried to poke along doing some self-study so I could get better. And then I attended a Boston Python Workshop for Women And Their Friends http://bostonpythonworkshop.com/ , led by Jessica McKellar. We worked through well-designed exercises and I got hands-on practice that helped me get through that transition, from painstakingly copying individual lines and functions into the interpreter, to thinking in terms of Python's program flow. Years later, my Python and software management skills have been invaluable. I run a small business, where I've been able to hire, train, and mentor contract workers who then go on to get full-time programming jobs. We've helped overhaul the Python Package Index, mentored and recruited contributors to Zulip, helped journalists open-source their code, and more. Right now I'm leading pip's work replacing its dependency resolver, which is a game-changer for future work making Python packaging easier to deal with. People who care about Python invested in running that workshop, and it's paid off very well in my case. Investing in Python events, and the organization that supports them, is a good bet. Sumana Harihareswara, Changeset Consulting PyCon US In 2015, as I was figuring out what I wanted to do next with my career, I attended PyCon North America in Montreal. I volunteered with the GNU Mailman team to expedite the release of Mailman 3.0. At the end of the sprint, I thought, "maybe I could charge for this." Later that year, I started Changeset Consulting, where I expedite long-awaited releases for open source software projects. Through Changeset, I helped the PSF finish and deploy the new PyPI, and I'm working on pip's dependency resolver overhaul and a fresh release of GNU Autoconf. If it weren't for the PSF, my life would be very different, and probably a lot less interesting. Sumana Harihareswara, Changeset Consulting An important community event that the PSF produces is PyCon US, where community members get a chance to receive training, share ideas, or even be mentored. At PyCon US 2019, Sumana Harihareswara helped Brian Rutledge make his 1st contribution to Python Packaging. Months later he became a co-maintainer of Twine, the upload utility for PyPI. As of May 2020, he successfully worked with a newer contributor to finish adding PEP 484 type annotations to Twine's codebase. This will make it easier for us to keep this code bug-free in the future, which means open source maintainers can have a smooth experience sharing their code with us on PyPI! Sumana Harihareswara, Changeset Consulting Grants Program My name is Iqbal and I have been using Python for 18 years. On a professional level Python as a programming tool has given me a career, and on a personal level as an ideology has helped me make friends and given me satisfaction by giving me the opportunity to be part of something bigger than myself. As member or lead of the different conference committee and also as conference chair, I have worked hard to make sure anyone can participate and contribute, regardless of personal situation, among others: Grants program were started for those that are financially constrained, quotas were setup for first time speakers, opportunities to present talks were initiated for non-english speakers, partnership with other groups such as Women Who Code and PyLadies to bolster underrepresented women groups in the conferences. Last but not least, in the beginning I also helped introduce a Code Of Conduct based on PSF's CoC to introduce a safe and welcoming environment for everyone. At that time, it wasn't common yet to have CoCs for conferences. The PSF has done a wonderful job by taking the lead and acting as a standard bearer for us in the rest of the world to follow. Initiatives such as their grants program that helps monetarily and also gives exposure to less known events, knowledge and know-how on how to manage conferences and meetups, and most importantly an access to other people within the community to share and source out ideas have been invaluable to us. Going forward, with the new normal, supporting virtual events is definitely an important thing which the PSF can help with. A step-by-step guide on how to manage virtual events, how tos for tools and a platform to expose events to the worldwide community would be very helpful. In a world that is widening in terms of inequality where we tend to take away more and more, I am happy to be part of a community led by the PSF that continues to share and give: through code, through knowledge, through money and through friendship. Iqbal Abdullah, Regional Conference Organizer ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://peps.python.org/pep-0020/ | PEP 20 – The Zen of Python | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 20 Toggle light / dark / auto colour theme PEP 20 – The Zen of Python Author : Tim Peters <tim.peters at gmail.com> Status : Active Type : Informational Created : 19-Aug-2004 Post-History : 22-Aug-2004 Table of Contents Abstract The Zen of Python Easter Egg References Copyright Abstract Long time Pythoneer Tim Peters succinctly channels the BDFL’s guiding principles for Python’s design into 20 aphorisms, only 19 of which have been written down. The Zen of Python Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those! Easter Egg >>> import this References Originally posted to comp . lang . python/python-list @ python . org under a thread called “The Way of Python” Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0020.rst Last modified: 2025-02-01 08:55:40 GMT Contents Abstract The Zen of Python Easter Egg References Copyright Page Source (GitHub) | 2026-01-13T08:49:02 |
https://www.python.org/psf/about/ | About the Python Software Foundation | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> About About the Python Software Foundation The Python Software Foundation is the organization behind the open source Python programming language. We are devoted to creating the conditions for Python and the Python community to grow and thrive. We fulfill our mission through these core activities: Infrastructure STRUCTURE AND STABILITY SO THE PYTHON LANGUAGE, ITS CONTRIBUTORS, AND USERS CAN THRIVE. We distribute Python , free of charge and available to all, for ever. We are the stewards of Python intellectual property—We establish PSF licenses, hold intellectual property rights to most Python releases, and protect Python-related trademarks. We put resources behind and help coordinate and improvements to the Python codebase and new Python releases. Community CONNECTION, DIVERSITY, SUPPORT, AND GROWTH FOR ALL WITHIN THE PYTHON COMMUNITY. We host PyCon US , the longest running annual event for celebrating, learning about, and coming together around Python. We give grants to groups around the world hosting events for and by Pythonistas supporting each other and welcoming newcomers. In 2024, the PSF awarded $655,000 USD to 257 groups or individuals in 61 countries around the world. We are responsible for establishing, maintaining, and enforcing the Python Code of Conduct , to work towards a Python community that is a safe and welcoming space for all. We provide and support resources to attract new Python users and keep the community growing, diverse, and healthy. We fiscally sponsor 20 Python-related community groups, conferences, and projects —including PyLadies, PyCascades, and Palletsto allow them to continue their contributions to the community with organizational infrastructure behind them. Investing in Python & Tools WE BUILD, SUPPORT, AND MAINTAIN CRITICAL PUBLIC GOODs FOR THE PYTHON COMMUNITY. We host PyPI , the Python package repository relied on by thousands of users with a huge range of projects. We've brought on board a Packaging Project Manager to best serve PyPI users We've added a full-time CPython Developer in Residence to our team, who amplifies volunteer contributors’ impact by processing CPython pull requests and tackling structural improvements. OUR SPONSORS DONATE TO THE PSF BECOME A MEMBER GET INVOLVED ANNUAL IMPACT REPORT NEWS & UPDATES PSF FAQ APPLY FOR A GRANT PYCON US The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/dev/peps/pep-3135/ | PEP 3135 – New Super | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 3135 Toggle light / dark / auto colour theme PEP 3135 – New Super Author : Calvin Spealman <ironfroggy at gmail.com>, Tim Delaney <timothy.c.delaney at gmail.com>, Lie Ryan <lie.1296 at gmail.com> Status : Final Type : Standards Track Created : 28-Apr-2007 Python-Version : 3.0 Post-History : 28-Apr-2007 , 29-Apr-2007 , 29-Apr-2007 , 14-May-2007 , 12-Mar-2009 Table of Contents Numbering Note Abstract Rationale Specification Closed Issues Determining the class object to use Should super actually become a keyword? super used with __call__ attributes Alternative Proposals No Changes Dynamic attribute on super type self.__super__.foo(*args) super(self, *args) or __super__(self, *args) super.foo(self, *args) super(*p, **kw) History References Copyright Numbering Note This PEP started its life as PEP 367 . Since it is now targeted for Python 3000, it has been moved into the 3xxx space. Abstract This PEP proposes syntactic sugar for use of the super type to automatically construct instances of the super type binding to the class that a method was defined in, and the instance (or class object for classmethods) that the method is currently acting upon. The premise of the new super usage suggested is as follows: super () . foo ( 1 , 2 ) to replace the old: super ( Foo , self ) . foo ( 1 , 2 ) Rationale The current usage of super requires an explicit passing of both the class and instance it must operate from, requiring a breaking of the DRY (Don’t Repeat Yourself) rule. This hinders any change in class name, and is often considered a wart by many. Specification Within the specification section, some special terminology will be used to distinguish similar and closely related concepts. “super class” will refer to the actual builtin class named “super”. A “super instance” is simply an instance of the super class, which is associated with another class and possibly with an instance of that class. The new super semantics are only available in Python 3.0. Replacing the old usage of super, calls to the next class in the MRO (method resolution order) can be made without explicitly passing the class object (although doing so will still be supported). Every function will have a cell named __class__ that contains the class object that the function is defined in. The new syntax: super () is equivalent to: super ( __class__ , < firstarg > ) where __class__ is the class that the method was defined in, and <firstarg> is the first parameter of the method (normally self for instance methods, and cls for class methods). For functions defined outside a class body, __class__ is not defined, and will result in runtime SystemError . While super is not a reserved word, the parser recognizes the use of super in a method definition and only passes in the __class__ cell when this is found. Thus, calling a global alias of super without arguments will not necessarily work. Closed Issues Determining the class object to use The class object is taken from a cell named __class__ . Should super actually become a keyword? No. It is not necessary for super to become a keyword. super used with __call__ attributes It was considered that it might be a problem that instantiating super instances the classic way, because calling it would lookup the __call__ attribute and thus try to perform an automatic super lookup to the next class in the MRO. However, this was found to be false, because calling an object only looks up the __call__ method directly on the object’s type. The following example shows this in action. class A ( object ): def __call__ ( self ): return '__call__' def __getattribute__ ( self , attr ): if attr == '__call__' : return lambda : '__getattribute__' a = A () assert a () == '__call__' assert a . __call__ () == '__getattribute__' In any case, this issue goes away entirely because classic calls to super(<class>, <instance>) are still supported with the same meaning. Alternative Proposals No Changes Although its always attractive to just keep things how they are, people have sought a change in the usage of super calling for some time, and for good reason, all mentioned previously. Decoupling from the class name (which might not even be bound to the right class anymore!) Simpler looking, cleaner super calls would be better Dynamic attribute on super type The proposal adds a dynamic attribute lookup to the super type, which will automatically determine the proper class and instance parameters. Each super attribute lookup identifies these parameters and performs the super lookup on the instance, as the current super implementation does with the explicit invocation of a super instance upon a class and instance. This proposal relies on sys._getframe(), which is not appropriate for anything except a prototype implementation. self.__super__.foo(*args) The __super__ attribute is mentioned in this PEP in several places, and could be a candidate for the complete solution, actually using it explicitly instead of any super usage directly. However, double-underscore names are usually an internal detail, and attempted to be kept out of everyday code. super(self, *args) or __super__(self, *args) This solution only solves the problem of the type indication, does not handle differently named super methods, and is explicit about the name of the instance. It is less flexible without being able to enacted on other method names, in cases where that is needed. One use case this fails is where a base-class has a factory classmethod and a subclass has two factory classmethods,both of which needing to properly make super calls to the one in the base-class. super.foo(self, *args) This variation actually eliminates the problems with locating the proper instance, and if any of the alternatives were pushed into the spotlight, I would want it to be this one. super(*p, **kw) There has been the proposal that directly calling super(*p, **kw) would be equivalent to calling the method on the super object with the same name as the method currently being executed i.e. the following two methods would be equivalent: def f ( self , * p , ** kw ): super . f ( * p , ** kw ) def f ( self , * p , ** kw ): super ( * p , ** kw ) There is strong sentiment for and against this, but implementation and style concerns are obvious. Guido has suggested that this should be excluded from this PEP on the principle of KISS (Keep It Simple Stupid). History 29-Apr-2007 Changed title from “Super As A Keyword” to “New Super” Updated much of the language and added a terminology section for clarification in confusing places. Added reference implementation and history sections. 06-May-2007 Updated by Tim Delaney to reflect discussions on the python-3000 and python-dev mailing lists. 12-Mar-2009 Updated to reflect the current state of implementation. References [1] Fixing super anyone? ( https://mail.python.org/pipermail/python-3000/2007-April/006667.html ) [2] PEP 3130: Access to Module/Class/Function Currently Being Defined (this) ( https://mail.python.org/pipermail/python-ideas/2007-April/000542.html ) Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-3135.rst Last modified: 2025-02-01 08:55:40 GMT Contents Numbering Note Abstract Rationale Specification Closed Issues Determining the class object to use Should super actually become a keyword? super used with __call__ attributes Alternative Proposals No Changes Dynamic attribute on super type self.__super__.foo(*args) super(self, *args) or __super__(self, *args) super.foo(self, *args) super(*p, **kw) History References Copyright Page Source (GitHub) | 2026-01-13T08:49:02 |
https://www.python.org/psf/developersinresidence/ | PSF Developers in Residence | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF Developers in Residence The Python Software Foundation’s Developer in Residence Program supports full-time developers who are focused on improving the Python programming language and its ecosystem. These developers play a crucial role in advancing Python’s core development, maintaining critical infrastructure, and supporting the broader community through mentorship, documentation, and tooling. Their work also addresses essential areas such as packaging, supply chain security, and the continued development and maintenance of PyPI, ensuring Python remains reliable and accessible for users and contributors worldwide. Our Developers in Residence (DiR) and their work are often funded directly by sponsors. If your organization sees a gap in the Python ecosystem they want to fill with a focused DiR, we are open to additional support for the program. We welcome you to reach out to the sponsors@python.org with inquiries or questions. Łukasz Langa Over the years as the PSF's CPython Developer in Residence, Łukasz Langa has played a key role in shaping the future of Python. He’s worked on everything from improving the user experience—like helping introduce a more modern, user-friendly Python shell—to keeping releases on track and stable. As a longtime release manager and core developer, he’s been involved in many versions of Python, making sure things run smoothly behind the scenes. Łukasz also spends time mentoring others and supporting big-picture changes that help Python grow and evolve for the long term. Łukasz's role is generously sponsored by Meta . Find Łukasz on all the platforms via his website . Mike Fiedler As PyPI’s sole Safety & Security Engineer, Mike focuses on ensuring that all users of PyPI - directly and indirectly - can rest easier knowing that the projects they rely on remain secure. He spends most of his time with the warehouse codebase, the underlying open source project that makes up PyPI.org and serves millions of requests a day. Mike works with communities of security researchers, developing methods to enable rapid response, and increases overall safety of the platform for everyone. As of 2025, Mike’s role is now sponsored by Alpha-Omega . Mike is likely the person responding to your malicious project reports, say hi sometime! Find Mike on all the platforms via his lnk.bio . Petr Viktorin As Deputy Developer in Residence for the PSF, Petr Viktorin focuses on the unglamorous but important work that keeps CPython running smoothly. He’s spent much of his time triaging Buildbot failures, reviewing PRs, and discussing issues—leaving room for volunteers to step in, but digging in himself when needed. He’s reviewed 100+ PRs, commented on hundreds of issues, and authored 56 PRs, often in less-loved parts of the codebase, like ctypes. He’s active in the C API working group, helped with community efforts like PyPI name retention, and speaks at events like PyCon and EuroPython. Petr's role is generously sponsored by Bloomberg . Find Petr on his Mastodon account . Serhiy Storchaka As the PSF's Supporting Developer in Residence, there is no single area of interest for Serhiy. He's active in so many parts of the interpreter and standard library that we're suspicious if he's really a single person. Serhiy is often the fastest responder on new issues and a champion of resolving and closing old ones. His quick reactions and consistent output make Serhiy invaluable for fixing crashes, release blockers, and other obscure issues that puzzle the average core developer. Serhiy's role is generously sponsored by an anonymous donor. Seth Larson As Security Developer-in-Residence Seth focuses on the security posture of the CPython language runtime, Python packaging tools, and the broader Python package ecosystem interactions with vulnerability infrastructure, security standards, and public policy such as the Secure Software Development Framework and EU Cyber Resilience Act. Seth’s work primarily involves the authoring, reviewing, and implementation of standards such as Python Enhancement Proposals (PEPs) and guides on security practices for open source projects. Seth also functions as a coordinator for security incidents affecting many projects in the Python ecosystem, such as handling the follow-up from the backdoor of xz-utils. Seth’s role has been sponsored by Alpha Omega since May 2023. Find Seth online: Blog: https://sethmlarson.dev Mastodon: https://fosstodon.org/@sethmlarson Bluesky: https://bsky.app/profile/sethmlarson.dev Signal: sethmlarson.99 Email: seth@python.org The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/psf/about/legal-and-policies/ | Legal & Policies | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse Legal & Policies Legal Statements Trademark Policy Licenses Contribution Agreements Vendor Info Legal Statements Legal statements on Trademark, Copyright, and Third-Party Content. Trademark Policy PSF trademark usage policy. Licenses About Python licensing. Contribution Agreements Information on contribution licensing and online form for organizations wishing to make software contributions. Vendor Info Accounts payable information and payment options. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.youtube.com/watch?v=ytudH8je5ko&list=PLNG_1j3cPCaZZ7etkzWA7JfdmKWT0pMsa&index=2 | React 18 for app developers - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xa700438d03350fdc"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgsxRFJmdktFTHBldyj6jZjLBjIKCgJLUhIEGgAgYmLfAgrcAjE1LllUPUNySm1IWHdNb1RKdEl3ZGpzeEJtaVBPUlVKWkdiWk0ya19aYWtNZDBXSFgzQmtWMmtZUS1qOHQyby11YlkyZlZQZC0yZm1SZmlOanh5WUwxWXJ0ZURJUEY1U3lsMEZYZlkzdEk4d2c4T285NlVwZTA3MnhyeUVScm9xdEk3WndsOEswWkZFTFFvRjNHSDVwajRENkNRVnJoM3dHNzlPOERzeGhOeTNibFY0V3dmZUhoNE1iaUhnOXQzNGZFUVdJV3hsRHVnTG5vMWlhVUEwLTRrbFZJTHp3amlLcTJndTFfTGNUN3BTUGJGbzF4TF82SXQ4T3lleG0xa0pKWWxDT0xmRVVUVUlFX3dRcEJpUXlSdkprUGc4SklmZlVjVXBzR2Q3SDc3ZFJkYXpKOUtXbktrdkNTcmxweGQ1aGFRWlJuamY3YmFobmtrUHBuZUEtSTYzWVVidw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZR3WCeoSrKIEEbw8aDkfeusA0lQii44cozI7HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","messageRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","continuationItemRenderer","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","adsEngagementPanelContentRenderer","engagementPanelTitleHeaderRenderer","chipBarViewModel","chipViewModel","sectionListRenderer","macroMarkersListRenderer","macroMarkersListItemRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgsxRFJmdktFTHBldyj6jZjLBjIKCgJLUhIEGgAgYmLfAgrcAjE1LllUPUNySm1IWHdNb1RKdEl3ZGpzeEJtaVBPUlVKWkdiWk0ya19aYWtNZDBXSFgzQmtWMmtZUS1qOHQyby11YlkyZlZQZC0yZm1SZmlOanh5WUwxWXJ0ZURJUEY1U3lsMEZYZlkzdEk4d2c4T285NlVwZTA3MnhyeUVScm9xdEk3WndsOEswWkZFTFFvRjNHSDVwajRENkNRVnJoM3dHNzlPOERzeGhOeTNibFY0V3dmZUhoNE1iaUhnOXQzNGZFUVdJV3hsRHVnTG5vMWlhVUEwLTRrbFZJTHp3amlLcTJndTFfTGNUN3BTUGJGbzF4TF82SXQ4T3lleG0xa0pKWWxDT0xmRVVUVUlFX3dRcEJpUXlSdkprUGc4SklmZlVjVXBzR2Q3SDc3ZFJkYXpKOUtXbktrdkNTcmxweGQ1aGFRWlJuamY3YmFobmtrUHBuZUEtSTYzWVVidw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwielu3_kIiSAxUETjgFHYoHLoYyDHJlbGF0ZWQtYXV0b0jKzPvG_KPn7coBmgEFCAMQ-B3KAQRckrFk","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwielu3_kIiSAxUETjgFHYoHLoYyDHJlbGF0ZWQtYXV0b0jKzPvG_KPn7coBmgEFCAMQ-B3KAQRckrFk","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwielu3_kIiSAxUETjgFHYoHLoYyDHJlbGF0ZWQtYXV0b0jKzPvG_KPn7coBmgEFCAMQ-B3KAQRckrFk","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"React 18 for app developers"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 70,675회"},"shortViewCount":{"simpleText":"조회수 7만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CLYCEMyrARgAIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3l0dWRIOGplNWtvGmBFZ3Q1ZEhWa1NEaHFaVFZyYjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNsMGRXUklPR3BsTld0dkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CLYCEMyrARgAIhMInpbt_5CIkgMVBE44BR2KBy6G"}}],"trackingParams":"CLYCEMyrARgAIhMInpbt_5CIkgMVBE44BR2KBy6G","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"968","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMECEKVBIhMInpbt_5CIkgMVBE44BR2KBy6G"}},{"innertubeCommand":{"clickTrackingParams":"CMECEKVBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMICEPqGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMICEPqGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"ytudH8je5ko"},"likeParams":"Cg0KC3l0dWRIOGplNWtvIAAyCwj7jZjLBhCkxN4B"}},"idamTag":"66426"}},"trackingParams":"CMICEPqGBCITCJ6W7f-QiJIDFQROOAUdigcuhg=="}}}}}}}]}},"accessibilityText":"다른 사용자 968명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMECEKVBIhMInpbt_5CIkgMVBE44BR2KBy6G","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"969","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMACEKVBIhMInpbt_5CIkgMVBE44BR2KBy6G"}},{"innertubeCommand":{"clickTrackingParams":"CMACEKVBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"ytudH8je5ko"},"removeLikeParams":"Cg0KC3l0dWRIOGplNWtvGAAqCwj7jZjLBhCKzd8B"}}}]}},"accessibilityText":"다른 사용자 968명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMACEKVBIhMInpbt_5CIkgMVBE44BR2KBy6G","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CLYCEMyrARgAIhMInpbt_5CIkgMVBE44BR2KBy6G","isTogglingDisabled":true}},"likeStatusEntityKey":"Egt5dHVkSDhqZTVrbyA-KAE%3D","likeStatusEntity":{"key":"Egt5dHVkSDhqZTVrbyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL4CEKiPCSITCJ6W7f-QiJIDFQROOAUdigcuhg=="}},{"innertubeCommand":{"clickTrackingParams":"CL4CEKiPCSITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL8CEPmGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL8CEPmGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"ytudH8je5ko"},"dislikeParams":"Cg0KC3l0dWRIOGplNWtvEAAiCwj7jZjLBhC2nOEB"}},"idamTag":"66425"}},"trackingParams":"CL8CEPmGBCITCJ6W7f-QiJIDFQROOAUdigcuhg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL4CEKiPCSITCJ6W7f-QiJIDFQROOAUdigcuhg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL0CEKiPCSITCJ6W7f-QiJIDFQROOAUdigcuhg=="}},{"innertubeCommand":{"clickTrackingParams":"CL0CEKiPCSITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"ytudH8je5ko"},"removeLikeParams":"Cg0KC3l0dWRIOGplNWtvGAAqCwj7jZjLBhD4zOEB"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL0CEKiPCSITCJ6W7f-QiJIDFQROOAUdigcuhg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CLYCEMyrARgAIhMInpbt_5CIkgMVBE44BR2KBy6G","isTogglingDisabled":true}},"dislikeEntityKey":"Egt5dHVkSDhqZTVrbyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egt5dHVkSDhqZTVrbyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLsCEOWWARgCIhMInpbt_5CIkgMVBE44BR2KBy6G"}},{"innertubeCommand":{"clickTrackingParams":"CLsCEOWWARgCIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt5dHVkSDhqZTVrb6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CLsCEOWWARgCIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CLwCEI5iIhMInpbt_5CIkgMVBE44BR2KBy6G","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLsCEOWWARgCIhMInpbt_5CIkgMVBE44BR2KBy6G","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CLkCEOuQCSITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLoCEPuGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DytudH8je5ko\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLoCEPuGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ytudH8je5ko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ytudH8je5ko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=cadb9d1fc8dee64a\u0026ip=1.208.108.242\u0026initcwndbps=3686250\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLoCEPuGBCITCJ6W7f-QiJIDFQROOAUdigcuhg=="}}}}}},"trackingParams":"CLkCEOuQCSITCJ6W7f-QiJIDFQROOAUdigcuhg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLcCEOuQCSITCJ6W7f-QiJIDFQROOAUdigcuhg=="}},{"innertubeCommand":{"clickTrackingParams":"CLcCEOuQCSITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLgCEPuGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DytudH8je5ko\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLgCEPuGBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ytudH8je5ko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ytudH8je5ko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=cadb9d1fc8dee64a\u0026ip=1.208.108.242\u0026initcwndbps=3686250\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLgCEPuGBCITCJ6W7f-QiJIDFQROOAUdigcuhg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLcCEOuQCSITCJ6W7f-QiJIDFQROOAUdigcuhg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CLYCEMyrARgAIhMInpbt_5CIkgMVBE44BR2KBy6G","dateText":{"simpleText":"2021. 12. 9."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"4년 전"}},"simpleText":"4년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"React Conf","navigationEndpoint":{"clickTrackingParams":"CLUCEOE5IhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CLUCEOE5IhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 3.43만명"}},"simpleText":"구독자 3.43만명"},"trackingParams":"CLUCEOE5IhMInpbt_5CIkgMVBE44BR2KBy6G"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UC1hOCRBN2mnXgN5reSoO3pQ","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CKcCEJsrIhMInpbt_5CIkgMVBE44BR2KBy6GKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLQCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLMCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CKwCEJf5ASITCJ6W7f-QiJIDFQROOAUdigcuhg==","command":{"clickTrackingParams":"CKwCEJf5ASITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKwCEJf5ASITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CLICEOy1BBgDIhMInpbt_5CIkgMVBE44BR2KBy6GMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRckrFk","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggBGAAgBFITCgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"trackingParams":"CLICEOy1BBgDIhMInpbt_5CIkgMVBE44BR2KBy6G","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CLECEO21BBgEIhMInpbt_5CIkgMVBE44BR2KBy6GMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRckrFk","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggDGAAgBFITCgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"trackingParams":"CLECEO21BBgEIhMInpbt_5CIkgMVBE44BR2KBy6G","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CK0CENuLChgFIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CK0CENuLChgFIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CK4CEMY4IhMInpbt_5CIkgMVBE44BR2KBy6G","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CLACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GMgV3YXRjaMoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CLACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CK8CEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CK0CENuLChgFIhMInpbt_5CIkgMVBE44BR2KBy6G"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CKcCEJsrIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKsCEP2GBCITCJ6W7f-QiJIDFQROOAUdigcuhjIJc3Vic2NyaWJlygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DytudH8je5ko%26continue_action%3DQUFFLUhqbU5jWG8tYVJuX0RkLVNWSzF1RDRwd285TV9Jd3xBQ3Jtc0tsLWh2bHBFcUNHMkZGMDVMdFlJTWg1RFlWbm1Sdm5tZm5Ybi1uYUpnMmxRaUdLLXN4bExTZ0JoTTJHdllQYjlHdERKNjNZQW5pYTVjU0dkNFBQdUFXa2puODc2RVcyXzA3N0ZKeFdnYzJJbUVCdWhvcVJOMW0yVFIyd2dzeUJGb2huUlRaZG02S0ZTRXc2U1hNcVhiRkFKdnFnNU5BXzFhTEpvT3ZqNGlpUW8ydHlQQ2xnMjhaNW9rRXBZS3pOa1ZCTjlzdWk\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKsCEP2GBCITCJ6W7f-QiJIDFQROOAUdigcuhsoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=ytudH8je5ko","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"ytudH8je5ko","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr5---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=cadb9d1fc8dee64a\u0026ip=1.208.108.242\u0026initcwndbps=3686250\u0026mt=1768293891\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbU5jWG8tYVJuX0RkLVNWSzF1RDRwd285TV9Jd3xBQ3Jtc0tsLWh2bHBFcUNHMkZGMDVMdFlJTWg1RFlWbm1Sdm5tZm5Ybi1uYUpnMmxRaUdLLXN4bExTZ0JoTTJHdllQYjlHdERKNjNZQW5pYTVjU0dkNFBQdUFXa2puODc2RVcyXzA3N0ZKeFdnYzJJbUVCdWhvcVJOMW0yVFIyd2dzeUJGb2huUlRaZG02S0ZTRXc2U1hNcVhiRkFKdnFnNU5BXzFhTEpvT3ZqNGlpUW8ydHlQQ2xnMjhaNW9rRXBZS3pOa1ZCTjlzdWk","idamTag":"66429"}},"trackingParams":"CKsCEP2GBCITCJ6W7f-QiJIDFQROOAUdigcuhg=="}}}}}},"subscribedEntityKey":"EhhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CKcCEJsrIhMInpbt_5CIkgMVBE44BR2KBy6GKPgdMgV3YXRjaMoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"EgIIAxgAIgt5dHVkSDhqZTVrbw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CKcCEJsrIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKcCEJsrIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKgCEMY4IhMInpbt_5CIkgMVBE44BR2KBy6G","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKoCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GKPgdMgV3YXRjaMoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILeXR1ZEg4amU1a28YAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKoCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKkCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CKYCEM2rARgBIhMInpbt_5CIkgMVBE44BR2KBy6G"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CKYCEM2rARgBIhMInpbt_5CIkgMVBE44BR2KBy6G","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CKYCEM2rARgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKYCEM2rARgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CKYCEM2rARgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CKYCEM2rARgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Shruti Kapoor","styleRuns":[{"startIndex":0,"length":13,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":13,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"messageRenderer":{"text":{"runs":[{"text":"댓글이 사용 중지되었습니다. "},{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CKUCEJY7GAAiEwielu3_kIiSAxUETjgFHYoHLobKAQRckrFk","commandMetadata":{"webCommandMetadata":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko"}}}]},"trackingParams":"CKUCEJY7GAAiEwielu3_kIiSAxUETjgFHYoHLoY="}}],"trackingParams":"CKQCELsvGAMiEwielu3_kIiSAxUETjgFHYoHLoY=","sectionIdentifier":"comment-item-section"}}],"trackingParams":"CKMCELovIhMInpbt_5CIkgMVBE44BR2KBy6G"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/pj5N-Khihgc/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBe418zAEgrK8nz2lVa5hfLGw12-Q","width":168,"height":94},{"url":"https://i.ytimg.com/vi/pj5N-Khihgc/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAox6aKNoDup6er69UGEUVApcrr6g","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"18:36","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"pj5N-Khihgc","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"18분 36초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CKICEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"pj5N-Khihgc","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKICEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CKECEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"pj5N-Khihgc"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKECEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJoCENTEDBgAIhMInpbt_5CIkgMVBE44BR2KBy6G"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CKACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"pj5N-Khihgc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CKACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pj5N-Khihgc"],"params":"CAQ%3D"}},"videoIds":["pj5N-Khihgc"],"videoCommand":{"clickTrackingParams":"CKACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3623750\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKACEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJ8CEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJoCENTEDBgAIhMInpbt_5CIkgMVBE44BR2KBy6G"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"스트리밍 서버 렌더링(서스펜스 기능 포함)"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJoCENTEDBgAIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회수 5.2만회"}},{"text":{"content":"4년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJ4CEP6YBBgAIhMInpbt_5CIkgMVBE44BR2KBy6G","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJ4CEP6YBBgAIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJ4CEP6YBBgAIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"pj5N-Khihgc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJ4CEP6YBBgAIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pj5N-Khihgc"],"params":"CAQ%3D"}},"videoIds":["pj5N-Khihgc"],"videoCommand":{"clickTrackingParams":"CJ4CEP6YBBgAIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3623750\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJ0CEJSsCRgBIhMInpbt_5CIkgMVBE44BR2KBy6G","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJ0CEJSsCRgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJ0CEJSsCRgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtwajVOLUtoaWhnYw%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtwajVOLUtoaWhnYw%3D%3D","commands":[{"clickTrackingParams":"CJsCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJwCEI5iIhMInpbt_5CIkgMVBE44BR2KBy6G","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJsCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"pj5N-Khihgc","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJoCENTEDBgAIhMInpbt_5CIkgMVBE44BR2KBy6G","visibility":{"types":"12"}}},"accessibilityContext":{"label":"스트리밍 서버 렌더링(서스펜스 기능 포함) 18분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJoCENTEDBgAIhMInpbt_5CIkgMVBE44BR2KBy6GMgdyZWxhdGVkSMrM-8b8o-ftygGaAQUIARD4HcoBBFySsWQ=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","nofollow":true,"ustreamerConfig":"KgkKBxIFZW4tVVM=","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3623750\u0026mt=1768293891\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/FZ0cG47msEk/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDH5r7Pql2X_EahvH-14ODdUVWJ5Q","width":168,"height":94},{"url":"https://i.ytimg.com/vi/FZ0cG47msEk/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLCTtuJn7VO4tBUlWnafyCq1IkkwwQ","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"33:49","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"FZ0cG47msEk","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"33분 49초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CJkCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"FZ0cG47msEk","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJkCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJgCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"FZ0cG47msEk"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJgCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJECENTEDBgBIhMInpbt_5CIkgMVBE44BR2KBy6G"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJcCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJcCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"FZ0cG47msEk","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJcCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["FZ0cG47msEk"],"params":"CAQ%3D"}},"videoIds":["FZ0cG47msEk"],"videoCommand":{"clickTrackingParams":"CJcCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FZ0cG47msEk","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FZ0cG47msEk","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-jwwy.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=159d1c1b8ee6b049\u0026ip=1.208.108.242\u0026initcwndbps=4377500\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJcCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJYCEPBbIhMInpbt_5CIkgMVBE44BR2KBy6G","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJECENTEDBgBIhMInpbt_5CIkgMVBE44BR2KBy6G"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"React 18 Keynote"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJECENTEDBgBIhMInpbt_5CIkgMVBE44BR2KBy6GygEEXJKxZA==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회�� | 2026-01-13T08:49:02 |
https://www.python.org/psf/sponsorship/ | Sponsor the PSF | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> Sponsorship The Python Software Foundation Sponsorship Program The PSF offers an all-in-one sponsorship program: all PSF sponsorships support the full scope of the PSF’s work, including PyCon US as well as PyPI (Python Package Index), CPython, and more. PSF sponsors receive an array of benefits that include a broad selection of promotional opportunities during PyCon US and also year-round. Join us as a sponsor to help make a difference and stand out in the Python ecosystem! See Sponsorship Options and Apply ABOUT THE PSF The PSF is the charitable organization behind the Python programming language and PyCon US. In addition to hosting PyCon US each year, we provide critical support for the Python language, ecosystem, and community: PYTHON : We hold Python’s IP; we host python.org where Python is downloaded millions of times daily; and we contribute directly to the language’s continuous improvement through our team of three CPython Developers-in-Residence. PYPI : We run the Python Package Index, a public service utilized by millions of users– supported by a full-time PyPI Support Specialist. On average pypi.org receives 6 million unique visitors per month, who download billions of files per day. SECURITY : We proactively maintain and improve security for the full Python ecosystem through our Security Developer-in-Residence and PyPI Safety & Security Engineer. COMMUNITY GRANTS : We support the most events and groups in the thriving global Python community, providing grants to local Python groups around the world as well as travel grants to individuals to attend PyCon US. In 2024, we disbursed a record $952,000 in grants to 174 groups across 52 countries. ABOUT PYCON US PyCon US is the largest, longest-running global Python gathering, with a diverse, unique, and highly engaged audience. At PyCon US, you’ll find a program filled with tutorials and sponsor presentations, 90+ of our community’s best talks, high-profile keynote speakers, a lively Expo Hall, our famed lightning talks, and two days of onsite development sprints. With all Python core developers gathering for the Language Summit, major Python projects hosting open sprints, and the unique blend of Python coders, maintainers and leaders, PyCon US is where the future of Python happens–and you can be part of it. WHY SPONSOR PYCON US MAKE AN IMPRESSION : Get meaningful and high-impact visibility for your brand. CONNECT : Reach a unique audience–many of our attendees don’t go to other, corporate events. RECRUIT : Most PyCon US attendees are developers, many of whom are seeking or open to opportunities, from entry-level to senior. Python developers often tell us they look at our sponsor page when deciding where to work, and frequently they’ve met their employer at PyCon US. SHOW YOUR SUPPORT : Sponsoring the PSF is a powerful way to show you are giving back to the Python community. We hear over and over that our community highly values companies that sponsor the PSF & PyCon US. STAY AHEAD OF THE CURVE : Engage directly with the developers building cutting-edge innovations in AI, data science, and more. Be part of the future of Python where it’s made. DRIVE THE CONVERSATION : Take part in the critical conversations that direct the future of the language & ecosystem, which happen exclusively at PyCon US. The PSF is recognized by the IRS as a 501(c)(3) non-profit charitable organization, and donations are tax-deductible for organizations that pay taxes in the United States. We hope you’ll join us as a sponsor and help make a difference in the Python ecosystem. We’d love to talk with you. Please get in touch by contacting: sponsors@python.org . ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/dev/peps/pep-0541/ | PEP 541 – Package Index Name Retention | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 541 Toggle light / dark / auto colour theme PEP 541 – Package Index Name Retention Author : Łukasz Langa <lukasz at python.org> BDFL-Delegate : Mark Mangoba <mmangoba at python.org> Discussions-To : Distutils-SIG list Status : Final Type : Process Topic : Packaging Created : 12-Jan-2017 Post-History : Resolution : Distutils-SIG message Table of Contents Abstract Rationale Approval Process Specification Implementation Reachability Abandoned projects Continued maintenance of an abandoned project Removal of an abandoned project Name conflict resolution for active projects Invalid projects Intellectual property policy The role of the Python Software Foundation How to request a name transfer Prior art Rejected Proposals References Copyright Acknowledgements Abstract This PEP proposes an extension to the Terms of Use [1] of the Package Index [2] , clarifying expectations of package owners regarding ownership of a package name on the Package Index, specifically with regards to conflict resolution. Existing package repositories such as CPAN [3] , NPM [4] , and GitHub [5] will be investigated as prior art in this field. Rationale Given that package names on the Index are sharing a single flat namespace, a unique name is a finite resource. The growing age of the Package Index causes a constant rise of situations of conflict between the current use of the name and a different suggested use of the same name. This document aims to provide general guidelines for solving the most typical cases of such conflicts. Approval Process As the application of this policy has potential legal ramifications for the Python Software Foundation, the approval process used is more formal than that used for most PEPs. Rather than accepting the PEP directly, the assigned BDFL-Delegate will instead recommend its acceptance to the PSF’s Packaging Working Group. After consultation with the PSF’s General Counsel, adoption of the policy will then be subject to a formal vote within the working group. This formal approval process will be used for both initial adoption of the policy, and for adoption of any future amendments. Specification The main idea behind this document is that the Package Index serves the community. Every user is invited to upload content to the Package Index under the Terms of Use, understanding that it is at the sole risk of the user. While the Package Index is not a backup service, the maintainers of the Package Index do their best to keep that content accessible indefinitely in its published form. However, in certain edge cases the greater community’s needs might overweigh the individual’s expectation of ownership of a package name. The use cases covered by this document are: Abandoned projects: continued maintenance by a different set of users; or removal from the Index for use with a different project. Active projects: resolving disputes over a name. Invalid projects: projects subject to a claim of intellectual property infringement. The proposed extension to the Terms of Use, as expressed in the Implementation section, will be published as a separate document on the Package Index, linked next to existing Terms of Use in the front page footer. Implementation Reachability The user of the Package Index is solely responsible for being reachable by the Package Index maintainers for matters concerning projects that the user owns. In every case where contacting the user is necessary, the maintainers will try to do so at least three times, using the following means of contact: the e-mail address on file in the user’s profile on the Package Index; the e-mail address listed in the Author field for a given project uploaded to the Index; and any e-mail addresses found in the given project’s documentation on the Index or on the listed Home Page. The maintainers stop trying to reach the user after six weeks. Abandoned projects A project is considered abandoned when ALL of the following are met: owner not reachable (see Reachability above); no releases within the past twelve months; and no activity from the owner on the project’s home page (or no home page listed). All other projects are considered active . Continued maintenance of an abandoned project If a candidate appears willing to continue maintenance on an abandoned project, ownership of the name is transferred when ALL of the following are met: the project has been determined abandoned by the rules described above; the candidate is able to demonstrate their own failed attempts to contact the existing owner; the candidate is able to demonstrate improvements made on the candidate’s own fork of the project; the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; and the maintainers of the Package Index don’t have any additional reservations. Under no circumstances will a name be reassigned against the wishes of a reachable owner. Removal of an abandoned project Projects are never removed from the Package Index solely on the basis of abandonment. Artifacts uploaded to the Package Index hold inherent historical value. An abandoned project can be transferred to a new owner for purposes of reusing the name when ALL of the following are met: the project has been determined abandoned by the rules described above; the candidate is able to demonstrate their own failed attempts to contact the existing owner; the candidate is able to demonstrate that the project suggested to reuse the name already exists and meets notability requirements; the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; download statistics on the Package Index for the existing package indicate project is not being used; and the maintainers of the Package Index don’t have any additional reservations. Name conflict resolution for active projects The maintainers of the Package Index are not arbiters in disputes around active projects. There are many possible scenarios here, a non-exclusive list describing some real-world examples is presented below. None of the following qualify for package name ownership transfer: User A and User B share project X. After some time they part ways and each of them wants to continue the project under name X. User A owns a project X outside the Package Index. User B creates a package under the name X on the Index. After some time, User A wants to publish project X on the Index but realizes name is taken. This is true even if User A’s project X gains notability and the User B’s project X is not notable. User A publishes project X to the Package Index. After some time User B proposes bug fixes to the project but no new release is published by User A. This is true even if User A agrees to publish a new version and later doesn’t, even if User B’s changes are merged to the source code repository for project X. Again, the list above is not exclusive. The maintainers of the Package Index recommend users to get in touch with each other and solve the issue by respectful communication (see the PSF Code of Conduct [6] ). Invalid projects A project published on the Package Index meeting ANY of the following is considered invalid and will be removed from the Index: project does not conform to Terms of Use; project is malware (designed to exploit or harm systems or users directly, to facilitate command-and-control attacks, or perform data exfiltration); project is spam (designed to advertise or solicit goods or services); project contains illegal content; project violates copyright, trademarks, patents, or licenses; project is name squatting (package has no functionality or is empty); project name, description, or content violates the Code of Conduct; project uses obfuscation to hide or mask functionality; or project is abusing the Package Index for purposes it was not intended. The Package Index maintainers pre-emptively declare certain package names as unavailable for security reasons. Intellectual property policy It is the policy of Python Software Foundation and the Package Index maintainers to be appropriately responsive to claims of intellectual property infringement by third parties. It is not the policy of the Python Software Foundation nor the Package Index maintainers to pre-screen uploaded packages for any type of intellectual property infringement. Possibly-infringing packages should be reported to legal @ python . org and counsel to the Python Software Foundation will determine an appropriate response. A package can be removed or transferred to a new owner at the sole discretion of the Python Software Foundation to address a claim of infringement. A project published on the Package Index meeting ANY of the following may be considered infringing and subject to removal from the Index or transferral to a new owner: project contains unlicensed copyrighted material from a third party, and is subject to a properly made claim under the DMCA; project uses a third party’s trademark in a way not covered by nominal or fair use guidelines; project clearly implicates a patented system or process, and is the subject of a complaint; or project is subject to an active lawsuit. In the event of a complaint for intellectual property infringement, a copy of the complaint will be sent to the package owner. In some cases, action may be taken by the Package Index maintainers before the owner responds. The role of the Python Software Foundation The Python Software Foundation [7] is the non-profit legal entity that provides the Package Index as a community service. The Package Index maintainers can escalate issues covered by this document for resolution by the Packaging Workgroup if the matter is not clear enough. Some decisions require additional judgement by the Board, especially in cases of Code of Conduct violations or legal claims. Recommendations made by the Board are sent to the Packaging Workgroup [8] for review. The Packaging Workgroup has the final say in any disputes covered by this document and can decide to reassign or remove a project from the Package Index after careful consideration even when not all requirements listed here are met. How to request a name transfer If you want to take over an existing project name on PyPI, these are the steps to follow: Try to contact the current owner(s) directly: email them and open an issue if you can find a related repository. The processes described here are meant as a last resort if the owner cannot be contacted. Check the criteria above to see when a transfer is allowed. In particular, the criteria for reusing a name for a different project are more stringent than for continuing maintenance of the same project - although it’s not easy to get a name transferred in either case. Search the PyPI Support issues to see if anyone else is already requesting the same name. If all the criteria are met to transfer ownership of the name, open a new issue to request it, detailing why you believe each relevant criterion is satisfied. Prior art NPM contains a separate section linked from the front page called Package Name Disputes . It is described as a “living document”, as of January 2017 its contents might be summarized as follows: package name squatting is prohibited; users wanting to reuse a project name are required to contact the existing author, with cc to support @ npmjs . com ; all contact must conform to the NPM Code of Conduct; in case of no resolution after a few weeks, npm inc. holds the right to the final decision in the matter. CPAN lets any user upload modules with the same name. PAUSE, a related index, only lists modules uploaded by the primary maintainer or listed co-maintainers. CPAN documentation doesn’t address disputes otherwise. GitHub’s terms of service contain an exhaustive list of behavior not meeting general conditions of use. While not codified anywhere, GitHub does agree for users to reclaim abandoned account names by archiving the abandoned account and letting the other user or organization rename their account. This is done on a case-by-case basis. Rejected Proposals The original approach was to hope for the best and solve issues as they arise without written policy. This is not sustainable. The lack of generally available guidelines in writing on package name conflict resolution is causing unnecessary tensions. From the perspective of users, decisions made by the Package Index maintainers without written guidelines may appear arbitrary. From the perspective of the Package Index maintainers, solving name conflicts is a stressful task due to risk of unintentional harm due to lack of defined policy. References [ 1 ] Terms of Use of the Python Package Index ( https://pypi.org/policy/terms-of-use/ ) [ 2 ] The Python Package Index ( https://pypi.org/ ) [ 3 ] The Comprehensive Perl Archive Network ( http://www.cpan.org/ ) [ 4 ] Node Package Manager ( https://www.npmjs.com/package/left-pad ) [ 5 ] GitHub ( https://github.com/ ) [ 6 ] Python Community Code of Conduct ( https://www.python.org/psf/codeofconduct/ ) [ 7 ] Python Software Foundation ( https://www.python.org/psf/ ) [ 8 ] Python Packaging Working Group ( https://wiki.python.org/psf/PackagingWG/ ) Copyright This document has been placed in the public domain. Acknowledgements The many participants of the Distutils and Catalog SIGs for their ideas over the years. Source: https://github.com/python/peps/blob/main/peps/pep-0541.rst Last modified: 2025-02-01 08:59:27 GMT Contents Abstract Rationale Approval Process Specification Implementation Reachability Abandoned projects Continued maintenance of an abandoned project Removal of an abandoned project Name conflict resolution for active projects Invalid projects Intellectual property policy The role of the Python Software Foundation How to request a name transfer Prior art Rejected Proposals References Copyright Acknowledgements Page Source (GitHub) | 2026-01-13T08:49:02 |
https://www.python.org/psf/fiscal-sponsorees/ | Fiscal Sponsorees | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> About >>> Fiscal Sponsorees Fiscal Sponsorees The Python Software Foundation promotes, protects, and advances the Python programming language and supports and facilitates the growth of a diverse and international community of Python programmers. Part of that mission includes acting as a fiscal sponsor to mission-related Python events, groups, and projects. The PSF provides 501(c)(3) tax-exempt status to fiscal sponsorees and manages back office issues like cash flow, accounting, budgeting, insurance, and contract/legal support, as well as access to nonprofit discounts. You can support one of the PSF's fiscal sponsorees by using our unified Linktr.ee donation page or scroll down and donation to the project of your choice. Every donation, no matter how small, helps sustain Python events and projects! At this time, the Python Software Foundation is not accepting new fiscal sponsoree requests. When we are able to accept new fiscal sponsoree applications, we will update this page to provide information about the PSF's fiscal sponsorship program. Our general process begins with an email from your project to us . Next, we provide you a fiscal sponsorship questionnaire and materials about how the PSF supports fiscal sponsorees, as well as an introductory call to discuss how your event, group, or project fits with the PSF's charitable mission. Generally, we do pause reviews of new fiscal sponsorship requests the month before and after the annual PyCon US. Bandit Bandit is a prominent open source project that focuses on the field of application security in Python. Developed and maintained by a dedicated community of developers, Bandit is designed to identify and highlight potential security vulnerabilities and weaknesses within Python codebases. As a static code analysis tool, Bandit scans through the source code, leveraging a wide range of security checks and rules to detect common security issues, such as SQL injections, cross-site scripting (XSS) attacks, and insecure cryptographic implementations.. Your contribution sustains Bandit developers and maintainers. Bay Area Python Association (BAPyA) BAPyA is a group of Python community organizers in the San Francisco Bay Area dedicated to supporting local gatherings to learn and discuss Python. Please consider supporting the BAPyA community with a contribution . Boston Python Boston Python is one of the world's largest local Python user groups. We have a presentation night and a project night almost every month, and run weekend workshops to introduce beginners to Python. Your donation helps keep the Python community in Boston vibrant! ChiPy Founded in 2003, ChiPy (Chicago Python User Group) has over 1,000 active members with a focus on the Python Programming Language. Meetings are open to all levels! Our main meetings are on the 2nd Thursday of every month. We also offer several SIGs (Special Interest Groups) in Mentorship, Data Science, Web technologies, and Finance. Please consider supporting the Chicago Python community ! Denver Python Users Group Denver Python Users Group welcomes those interested in learning about Python or connecting with other Python professionals. We have a smaller weekly Meetup for people to work on Python projects and a larger monthly Meetup with speakers and talks. You can help support ongoing meeting costs by donating ! Jazzband Jazzband is a project that secures the long-term maintenance of Python projects that have passed their first life-cycle as single-author projects. Jazzband's intention is to break the cycle of loss of maintenance of established, well-tested, well-documented projects when their original author steps away (bus factor problem) using cooperative coding. You can support Jazzband to help keep Python projects alive. North Bay Python North Bay Python is a boutique, one-track conference held annually in Petaluma, CA. We take inclusion seriously and ensure our speakers come from a diverse, international lineup. To reduce costs for future attendees, consider donating to North Bay Python . Pallets Pallets develops and supports Flask, Jinja, Werkzeug, Click, and other Python libraries. These libraries power applications of all sizes around the world and are downloaded millions of times each month. Despite their popularity, the projects are primarily maintained by only a few developers. You can support Pallets' goal by donating via the PSF or Github Sponsors to grow the community and to create a sustainable group of contributors and users. PhillyPUG PhillyPUG , the Philadelphia Python Users' Group, has 3,200 members growing at a rate of one new member per day. The group holds regular events including project nights, lectures, lightning talks, and workshops to attract all levels of programmers from novices to experts. Your contribution helps support the cost of these events, including event space, refreshments, and other logistical expenses. PuPPy PuPPy , the Puget Sound Programming Python Group, is a fun and friendly user group dedicated to proliferating a diverse and talented Python community in the Puget Sound region. The group is devoted to exploring Python-based programming knowledge, embracing new and experienced members from all walks of life, and helping those members to achieve their professional goals. Consider supporting PuPPy ! PyCascades PyCascades is a regional Python conference that moves between Vancouver, Seattle, and Portland. PyCascades is a two-day, single-track Python conference that celebrates and brings together the Pacific Northwest Python developer and user community. Your donation helps reduce the cost of future conferences, including providing travel grants. PyBeach PyBeach is an annual one-day, single-track event, with a main talks track, open source sprints, “hallway track” space, and an expo hall. Members of the Python communities in the Los Angeles area welcome Python professionals, enthusiasts, and students to join us. It is a welcoming, volunteer-run, community-driven event with the mission to educate and connect its attendees to one another, and promote Python within the local technology community. Your donation will help reduce the cost of the conference and support future conferences. PyHawaii PyHawaii is a community dedicated to the growth and use of the Python Programming Language in Honolulu, the Islands of Hawaii, and across the Pacific. All skill levels are welcome! At PyHawaii, we value community, inclusivity and `ohana - so come join our meetup, where you will find friends, family and fantastic opportunities to learn, grow, contribute and advance your skills. Consider supporting the group with your contribution . PyLadies PyLadies is a mentorship group for women with a focus on helping more women become active participants and leaders in the Python open source community. We have over 100 worldwide chapters and we encourage women to start their own local groups. We support both seasoned and budding developers through workshops, community activities, and local advocacy. Your donation to PyLadies' outreach efforts will help improve the diversity of the software industry as a whole. PyLadies sponsors PyLadiesCon , which is an exciting, online event dedicated to empowerment, learning, and diversity within the PyLadies and Python community! PyLadiesCon appreciates your contribution to help keep the conference free to attendees. You can also support specific chapters such as PyLadies Boston , PyLadies Chicago , and PyLadies San Francisco . PyMNtos PyMNtos (pronounced pie-min-tose) is a Twin Cities group of Python enthusiasts. Members range from beginners to hobbyists to experts. Whoever you are and whatever your skill level is, we would love for you to join us. There is no membership fee or any other barrier to entry. To support the cost of Meetups, please donate ! PyOhio PyOhio is an annual, regional PyCon in Ohio that draws attendees from the Midwest US. Content ranges from beginner to advanced and is intended to be relevant to all types of Python users including students, software professionals, scientists, hobbyists, and anyone looking to learn more. PyPA The Python Packaging Authority (PyPA) is a working group that maintains a core set of software projects used in Python packaging. The software developed through the PyPA is used to package, share, and install Python software and to interact with indexes of downloadable Python software such as PyPI, the Python Package Index. You can support PyPA by supporting them on Github Sponsors . PyRVA PyRVA is a local user group in Richmond, VA. PyRVA believes that Python is best enjoyed in the company of others and organizes talks, hackathons, workshops and more to help build up the Richmond, VA Python community. Donation to PyRVA helps support costs of ongoing events. Python San Diego User Group The Python San Diego User Group is a volunteer-run group that was restarted in February 2012 and has since grown to several hundred members. We have a general meetup each month with technical talks and networking, and also hold weekend workshops and hackathons for new to advanced Python programmers in the area. We depend on individual and corporate sponsors and the PSF to help keep our events free for our members and to grow the Python community. Your donation helps support the venue, food, and expenses for our workshops and meetups. Twisted Twisted is an event-driven networking engine written in Python licensed under the open source MIT License. Twisted makes it easy to implement custom network applications and supports many common network protocols, including SMTP, POP3, IMAP, SSHv2, and DNS. You can sustain Twisted's ongoing development with a contribution ! The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://dev.to/bogaboga1/odoo-core-and-the-cost-of-reinventing-everything-15n1#websocket-implementation | Odoo Core and the Cost of Reinventing Everything - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Boga Posted on Jan 12 Odoo Core and the Cost of Reinventing Everything # python # odoo # qweb # owl Hello, this is my first blog post ever. I’d like to share my experience working with Odoo , an open-source Enterprise Resource Planning (ERP) system, and explain why I believe many of its architectural choices cause unnecessary complexity. Odoo is a single platform that provides many prebuilt modules (mini-applications) that most companies need. For example, almost every company requires a Human Resources system to manage employee details, leaves, attendance, contracts, resignations, and more. Beyond HR, companies also need purchasing, inventory, accounting, authentication, authorization, and other systems. Odoo bundles all of these tightly coupled systems into a single installation. On paper, this sounds great — and from a business perspective, it often is. From a technical perspective , however, things get complicated very quickly. Odoo Core Components Below are the main Odoo components, ranked from least complex to most complex, and all largely developed in-house instead of relying on existing mature frameworks: Odoo HTTP Layer JSON-RPC Website routing Odoo Views XML transformed into Python and JavaScript Odoo ORM Custom inheritance system Query builder Dependency injection Caching layers Cache System Implemented from scratch WebSocket Implementation Very low-level handling Odoo HTTP Layer Odoo is not built on a standard Python web framework like Django or Flask. Instead, it implements its own HTTP framework on top of Werkzeug (a WSGI utility library). This HTTP layer introduces its own abstractions, request lifecycle, routing, and serialization logic, including JSON-RPC and website controllers. While technically impressive, it reinvents many problems that have already been solved — and battle-tested — by existing frameworks. Odoo Views In my opinion, this is one of the most problematic parts of Odoo. Instead of using standard frontend technologies, Odoo relies heavily on XML-based views . These XML files are sent to the browser and then transformed using Abstract Syntax Tree (AST) analysis into JavaScript. In other contexts (like the website), the XML may be converted into Python code and sometimes back into JavaScript again. This creates: High cognitive overhead Difficult debugging Tight coupling between backend and frontend Poor tooling support compared to modern frontend stacks It feels like building a car from raw metal just to drive from point A to point B. Odoo ORM Odoo’s ORM is not a typical ORM. It implements: A custom inheritance system (instead of using Python’s built-in one) Its own dependency injection mechanism A query builder Caching layers (LRU) Model extension via monkey-patching While powerful, this system is extremely complex and hard to reason about. Debugging model behavior often feels like navigating invisible layers of magic. WebSocket Implementation Instead of using a mature real-time framework, Odoo implements its WebSocket handling with very low-level logic, sometimes in surprisingly small and dense files. A single comment from the codebase summarizes this approach better than words ever could: The “Odoo Is Old” Argument A common defense of Odoo’s architecture is that “it’s an old system” — originally developed around 2005 using Python 2. However, this argument no longer holds. Odoo was largely rewritten from scratch around 2017 to support Python 3. At that time, many excellent frameworks already existed and had solved the same problems more cleanly, while continuing to evolve without breaking their ecosystems. Today, even small changes in Odoo’s core can break custom modules unless they are limited to simple CRUD models with minimal dependencies on core behavior. Final Thoughts Odoo is a powerful product and a successful business platform. But from a software engineering perspective, many of its design decisions prioritize control and internal consistency over maintainability, clarity, and developer experience . If you work with Odoo long enough, you stop asking “why does it work this way?” and start asking “how do I survive this upgrade?” Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Boga Follow Senior Software Engineer Joined Jan 12, 2026 Trending on DEV Community Hot 🧱 Beginner-Friendly Guide 'Maximal Rectangle' – LeetCode 85 (C++, Python, JavaScript) # programming # cpp # python # javascript The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning What was your win this week??? # weeklyretro # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://peps.python.org/pep-0387/ | PEP 387 – Backwards Compatibility Policy | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 387 Toggle light / dark / auto colour theme PEP 387 – Backwards Compatibility Policy Author : Benjamin Peterson <benjamin at python.org> PEP-Delegate : Brett Cannon <brett at python.org> Status : Active Type : Process Created : 18-Jun-2009 Post-History : 19-Jun-2009 , 12-Jun-2020 , 19-Dec-2022 , 16-Jun-2023 Replaces : 291 Table of Contents Abstract Rationale Backwards Compatibility Rules Basic policy for backwards compatibility Soft Deprecation Making Incompatible Changes Changelog References Copyright Abstract This PEP outlines Python’s backwards compatibility policy. Rationale As one of the most used programming languages today [1] , the Python core language and its standard library play a critical role in millions of applications and libraries. This is fantastic. However, it means the development team must be very careful not to break this existing 3rd party code with new releases. This PEP takes the perspective that “backwards incompatibility” means preexisting code ceases to comparatively function after a change. It is acknowledged that this is not a concrete definition, but the expectation is people in general understand what is meant by “backwards incompatibility”, and if they are unsure they may ask the Python development team and/or steering council for guidance. Backwards Compatibility Rules This policy applies to all public APIs. These include: Syntax and behavior of these constructs as defined by the reference manual. The C-API. Function, class, module, attribute, and method names and types. Given a set of arguments, the return value, side effects, and raised exceptions of a function. This does not preclude changes from reasonable bug fixes. The position and expected types of arguments and returned values. Behavior of classes with regards to subclasses: the conditions under which overridden methods are called. Documented exceptions and the semantics which lead to their raising. Exceptions commonly raised in EAFP scenarios. Others are explicitly not part of the public API. They can change or be removed at any time in any way. These include: Function, class, module, attribute, method, and C-API names and types that are prefixed by “_” (except special names). Anything documented publicly as being private. Note that if something is not documented at all, it is not automatically considered private. Imported modules (unless explicitly documented as part of the public API; e.g. importing the bacon module in the spam does not automatically mean spam.bacon is part of the public API unless it is documented as such). Inheritance patterns of internal classes. Test suites. (Anything in the Lib/test directory or test subdirectories of packages.) Backward compatibility rules do not apply to any module or API that is explicitly documented as Provisional per PEP 411 . Basic policy for backwards compatibility In general, incompatibilities should have a large benefit to breakage ratio, and the incompatibility should be easy to resolve in affected code. For example, adding an stdlib module with the same name as a third party package is generally not acceptable. Adding a method or attribute that conflicts with 3rd party code through inheritance, however, is likely reasonable. Unless it is going through the deprecation process below, the behavior of an API must not change in an incompatible fashion between any two consecutive releases. Python’s yearly release process ( PEP 602 ) means that the deprecation period must last at least two years. Similarly a feature cannot be removed without notice between any two consecutive releases. For changes that are unable to raise a deprecation warning, consult with the steering council. The steering council may grant exceptions to this policy. In particular, they may shorten the required deprecation period for a feature. Exceptions are only granted for extreme situations such as dangerously broken or insecure features or features no one could reasonably be depending on (e.g., support for completely obsolete platforms). Soft Deprecation A soft deprecation can be used when using an API which should no longer be used to write new code, but it remains safe to continue using it in existing code. The API remains documented and tested, but will not be developed further (no enhancement). The main difference between a “soft” and a (regular) “hard” deprecation is that the soft deprecation does not imply scheduling the removal of the deprecated API. Another difference is that a soft deprecation does not issue a warning: it’s only mentioned in the documentation, whereas usually a “hard” deprecation issues a DeprecationWarning warning at runtime. The documentation of a soft deprecation should explain why the API should be avoided, and if possible propose a replacement. If the decision is made to deprecate (in the regular sense) a feature that is currently soft deprecated, the deprecation must follow the Backwards Compatibility Rules (i.e., there is no exception because the feature is already soft deprecated). Making Incompatible Changes Making an incompatible change is a gradual process performed over several releases: PEP 1: Start with an idea discussion. If the discussion reaches consensus that acceptance is possible a PEP or similar document may be written. Hopefully users of the affected API will pipe up to comment. Add a warning to the current main branch. If behavior is changing, the API may gain a new function or method to perform the new behavior; old usage should raise the warning. If an API is being removed, simply warn whenever it is entered. DeprecationWarning is the usual warning category to use, but PendingDeprecationWarning may be used in special cases where the old and new versions of the API will coexist for many releases [2] . The warning message should include the release the incompatibility is expected to become the default and a link to an issue that users can post feedback to. When feasible, also change typeshed to add the @deprecated decorator (see PEP 702 ) to the deprecated API, so that users of static type checkers have another way to learn about the deprecation. For C API, a compiler warning generated by the Py_DEPRECATED macro is also acceptable. Wait for the warning to appear in at least two minor Python versions of the same major version, or one minor version in an older major version (e.g., for a warning in Python 3.10.0, you either wait until at least Python 3.12 or Python 4.0 to make the change). It is preferred, though, to wait 5 years before removal (e.g., warn starting in Python 3.10, removal in 3.15; this happens to coincide with the current lifetime of a minor release of Python). If the expected maintenance overhead and security risk of the deprecated behavior is small (e.g. an old function is reimplemented in terms of a new, more general one), it can stay indefinitely (or until the situation changes). If the deprecated feature is replaced by a new one, it should generally be removed only after the last Python version without the new feature reaches end of support. See if there’s any feedback. Users not involved in the original discussions may comment now after seeing the warning. Perhaps reconsider. The behavior change or feature removal may now be made default or permanent having reached the declared version. Remove the old version and warning. If a warning cannot be provided to users, consult with the steering council. Changelog 2025-Jan-27: Updated to prefer a 5-year deprecation period before removal. 2023-Nov-14: Added @deprecated decorator per PEP 702 . 2023-Jul-03: Added the Soft Deprecation section, as discussed in https://discuss.python.org/t/27957 . 2023-Jun-26: Multiple smaller updates and clarifications, discussed in https://discuss.python.org/t/22042 . 2022-Apr-04: Added explicit notes to ask the Steering Council in several exceptional cases. 2021-Apr-16: Clarified how long a warning must be emitted before a change can be made. 2020-Jul-20: Initial accepted version. References [ 1 ] TIOBE Programming Community Index https://www.tiobe.com/tiobe-index/ [ 2 ] The warnings module http://docs.python.org/library/warnings.html Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0387.rst Last modified: 2026-01-06 07:07:19 GMT Contents Abstract Rationale Backwards Compatibility Rules Basic policy for backwards compatibility Soft Deprecation Making Incompatible Changes Changelog References Copyright Page Source (GitHub) | 2026-01-13T08:49:02 |
https://dev.to/t/education | Education - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # education Follow Hide Discussions on academic programs, online courses, and learning paths in security. Create Post Older #education posts 1 2 3 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu I Built a Bilingual Open-Source Tree Knowledge Base for Costa Rica (74 Species, Zero Ads) sandgraal sandgraal sandgraal Follow Dec 30 '25 I Built a Bilingual Open-Source Tree Knowledge Base for Costa Rica (74 Species, Zero Ads) # opensource # education Comments Add Comment 1 min read Designing AI-First Study Systems: What We Learned Building for Cognitive Load CramX CramX CramX Follow Dec 25 '25 Designing AI-First Study Systems: What We Learned Building for Cognitive Load # ai # education # learning # productivity Comments 1 comment 3 min read I built LoveToRead.ai – Create personalized children's books with AI Maxwell - IndieDev Maxwell - IndieDev Maxwell - IndieDev Follow Dec 20 '25 I built LoveToRead.ai – Create personalized children's books with AI # news # webdev # ai # education Comments Add Comment 3 min read AI Engineering for Everyone — Simple Explanations of Hard Concepts (Series Announcement) ASHISH GHADIGAONKAR ASHISH GHADIGAONKAR ASHISH GHADIGAONKAR Follow Dec 12 '25 AI Engineering for Everyone — Simple Explanations of Hard Concepts (Series Announcement) # ai # machinelearning # education # deeplearning Comments Add Comment 2 min read Beginner’s Guide to Learning Tech Skills Without a Tech Background AlphaTech AlphaTech AlphaTech Follow Dec 16 '25 Beginner’s Guide to Learning Tech Skills Without a Tech Background # education # technology # beginners # careerdevelopment Comments Add Comment 3 min read Preparing Students for Modern Software Development Toolchains Chris Brown Chris Brown Chris Brown Follow Dec 9 '25 Preparing Students for Modern Software Development Toolchains # tooling # education # softwaredevelopment Comments Add Comment 1 min read Building a Scalable Plagiarism-Detection Pipeline (With Examples) Bredy Lord Bredy Lord Bredy Lord Follow Dec 9 '25 Building a Scalable Plagiarism-Detection Pipeline (With Examples) # plagiarismdetection # education Comments Add Comment 4 min read Neural Networks as a Catalyst for the Evolution of Online Learning ProgKids ProgKids ProgKids Follow Nov 19 '25 Neural Networks as a Catalyst for the Evolution of Online Learning # ai # education Comments Add Comment 3 min read Basic Concepts of C# Data Types — From Bits to LLM‑Ready Mental Models Cristian Sifuentes Cristian Sifuentes Cristian Sifuentes Follow Dec 8 '25 Basic Concepts of C# Data Types — From Bits to LLM‑Ready Mental Models # dotnet # csharp # llms # education 1 reaction Comments 1 comment 9 min read C# Variables, the CPU, and LLMs — From `int age = 25;` to Silicon Cristian Sifuentes Cristian Sifuentes Cristian Sifuentes Follow Dec 8 '25 C# Variables, the CPU, and LLMs — From `int age = 25;` to Silicon # csharp # dotnet # llm # education 1 reaction Comments Add Comment 14 min read Clock circular calculator Alejandro Rivero Alejandro Rivero Alejandro Rivero Follow Oct 23 '25 Clock circular calculator # javascript # children # education # design Comments Add Comment 1 min read Understanding ADHD Coaching: A Path to Clarity, Confidence, and Control Alif TGM Alif TGM Alif TGM Follow Oct 17 '25 Understanding ADHD Coaching: A Path to Clarity, Confidence, and Control # adhd # education Comments Add Comment 3 min read Unlock Guitar Soloing Secrets: A Graph Engine Approach by Arvind Sundararajan Arvind SundaraRajan Arvind SundaraRajan Arvind SundaraRajan Follow Oct 24 '25 Unlock Guitar Soloing Secrets: A Graph Engine Approach by Arvind Sundararajan # guitar # musictech # algorithms # education Comments Add Comment 2 min read Realised vs Unrealised P/L — Money in Your Pocket vs Money on Paper 22s Pocket Portfolio 22s Pocket Portfolio 22s Pocket Portfolio Follow for Pocket Portfolio Oct 23 '25 Realised vs Unrealised P/L — Money in Your Pocket vs Money on Paper # investing # fintech # pocketportfolio # education Comments 1 comment 2 min read Skill vs Degree: What the Future of Education Demands Prabnek Singh Prabnek Singh Prabnek Singh Follow Sep 12 '25 Skill vs Degree: What the Future of Education Demands # skill # education Comments Add Comment 2 min read Learning to Code in 2025: Why Online Communities Are Outpacing Traditional Education Abdul Rehman Khan Abdul Rehman Khan Abdul Rehman Khan Follow Oct 9 '25 Learning to Code in 2025: Why Online Communities Are Outpacing Traditional Education # programming # developer # coding # education 1 reaction Comments 1 comment 2 min read Que estoy aprendiendo ahora AnnaR AnnaR AnnaR Follow Oct 6 '25 Que estoy aprendiendo ahora # student # education Comments Add Comment 1 min read Hola, mundo! AnnaR AnnaR AnnaR Follow Oct 6 '25 Hola, mundo! # student # education Comments Add Comment 1 min read Days 18-19: Weekend Reflection - Our Responsibility to Recent CS Graduates Clay Roach Clay Roach Clay Roach Follow Sep 1 '25 Days 18-19: Weekend Reflection - Our Responsibility to Recent CS Graduates # ai # career # mentorship # education Comments Add Comment 4 min read Learn Vim the Fun Way with VimMaster: An In-Browser Vim Practice Game Andrei Tanase Andrei Tanase Andrei Tanase Follow Aug 28 '25 Learn Vim the Fun Way with VimMaster: An In-Browser Vim Practice Game # game # vim # indiegame # education Comments Add Comment 2 min read Parameters and return type Ligouri S Tittus Ligouri S Tittus Ligouri S Tittus Follow Aug 28 '25 Parameters and return type # programming # education # softwaredevelopment Comments Add Comment 1 min read Building Child-Safe AI Agents: 6 Educational Mentors with 92% AI Autonomy Victor Saly Victor Saly Victor Saly Follow Aug 27 '25 Building Child-Safe AI Agents: 6 Educational Mentors with 92% AI Autonomy # ai # education # childsafety # gamedev Comments Add Comment 7 min read AI yair tover yair tover yair tover Follow Aug 20 '25 AI # discuss # ai # education Comments Add Comment 1 min read 7-Do you really know functions bin bin bin Follow Aug 20 '25 7-Do you really know functions # programming # softwaredevelopment # education 1 reaction Comments Add Comment 1 min read 4-Your first intro to TypeScript docs bin bin bin Follow Aug 19 '25 4-Your first intro to TypeScript docs # typescript # tutorial # education # softwaredevelopment Comments Add Comment 1 min read loading... trending guides/resources Basic Concepts of C# Data Types — From Bits to LLM‑Ready Mental Models C# Variables, the CPU, and LLMs — From `int age = 25;` to Silicon Designing AI-First Study Systems: What We Learned Building for Cognitive Load Neural Networks as a Catalyst for the Evolution of Online Learning Preparing Students for Modern Software Development Toolchains Beginner’s Guide to Learning Tech Skills Without a Tech Background Building a Scalable Plagiarism-Detection Pipeline (With Examples) AI Engineering for Everyone — Simple Explanations of Hard Concepts (Series Announcement) I Built a Bilingual Open-Source Tree Knowledge Base for Costa Rica (74 Species, Zero Ads) I built LoveToRead.ai – Create personalized children's books with AI 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:02 |
https://www.python.org/doc/essays/#content | Python Documentation Index | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Documentation >>> Python Essays Python Documentation Index Python Essays In this directory I place short essays (anything from 500 to 5000 words) on various Python subjects. See also a collection of presentations I have given. See also my blog at blogspot.com and my previous blog at artima.com. -- Guido van Rossum Table of contents (in mostly chronological order) Unifying types and classes in Python 2.2 (See below) Foreword for "Programming Python" (1st ed.) Written in 1996, this gives an overview of the early history and background of Python and some of my philosophy about software design and project management. See also my foreword to the 2nd edition . Implementing Graphs An elegant and perhaps not obvious way to represent graphs using Python's most fundamental and versatile data types, lists and dictionaries. An Optimization Anecdote Required reading if you find that your Python code runs too slow. Metaclass Programming in Python 1.5 Warning: reading this document may cause your brain to explode. Built-in Package Support in Python 1.5 The most official documentation for the new package features in Python 1.5. Standard Exception Classes in Python 1.5 The most official documentation for the new exception features in Python 1.5. (Updated for Python 1.5.2 by Barry Warsaw.) Glue It All Together With Python A position paper I wrote for and presented at the OMG-DARPA-MCC workshop on compositional software architectures in Monterey, California, January 6-8, 1998. What Is Python? Executive Summary A short (two paragraphs) high-level presentation of Python's virtues. Comparing Python to Other Languages Activist ammo or flame fodder? (Note: I received lots of feedback when I posted this to comp.lang.python. Unfortunately the feedback was diverted to a separate mailbox that I didn't know I had -- when I finally found it, I was a bit overwhelmed and so far have not yet found the time to update the article.) Proposed Improvements to Module Cleanup A revised version of the proposal I posted to comp.lang.python on Feb 6, 1998. This has been adopted in Python 1.5.1. Open Source Summit Trip Report My trip report of O'Reilly's Open Source Summit, essentially as posted on c.l.p. This version published in the Linux Gazette (it's an external link), in their May 1998 issue. Debugging Reference Count Problems An edited version of a posting to c.l.p on this subject, on May 27, 1998. Computer Programming for Everybody (old) A funding proposal that was accepted by DARPA in March 1999. Computer Programming for Everybody Revised, extended version of the previous proposal. Interview in Linux Journal Not quite an essay, but a stream of consciousness penned down by a journalist... More thoughts about CP4E. Interview in by Frank Willison for "Frankly Speaking" column Another stream of consciousness transcribed by a friendly listener... Not just on CP4E. Foreword for "Programming Python" (2nd ed.) The story continues... Unifying types and classes in Python 2.2 An introduction to the type/class unification effort in Python 2.2. Note that the unification work is officially labeled experimental and is subject to change in future releases of Python. Parade of the PEPs To start off Developer's Day at the Python10 conference I gave a keynote ending in what I dubbed "the parade of the PEPs". It was a brief overview of all open PEPs , where I gave my highly personal and subjective opinion for each PEP. Later, I realized that this might have been of interest to other developers. I didn't take notes at the conference, so below is a different set of comments that I created from scratch during a single two-hour sitting on March 7, 2002. I intend to occasionally update this with new comments and new PEPs. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://peps.python.org/pep-0545/ | PEP 545 – Python Documentation Translations | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 545 Toggle light / dark / auto colour theme PEP 545 – Python Documentation Translations Author : Julien Palard <julien at palard.fr>, Inada Naoki <songofacandy at gmail.com>, Victor Stinner <vstinner at python.org> Status : Active Type : Process Topic : Governance Created : 04-Mar-2017 Resolution : Python-Dev message Table of Contents Abstract Motivation Rationale Translation Issue tracker Branches Hosting Domain Name, Content negotiation and URL Language Tag Fetching And Building Translations Community Mailing List Chat Repository for PO Files Translation tools python-docs-translations Documentation Contribution Agreement Language Team Alternatives Simplified English Changes Get a Documentation Contribution Agreement Migrate GitHub Repositories Setup a GitHub bot for Documentation Contribution Agreement Patch docsbuild-scripts to Compile Translations List coordinators in the devguide Create sphinx-doc Language Switcher Update sphinx-doc Version Switcher Enhance Rendering of Untranslated and Fuzzy Translations New Translation Procedure Designate a Coordinator Create GitHub Repository Setup the Documentation Contribution Agreement Add support for translations in docsbuild-scripts Add Translation to the Language Switcher Previous Discussions References Copyright Abstract The intent of this PEP is to make existing translations of the Python Documentation more accessible and discoverable. By doing so, we hope to attract and motivate new translators and new translations. Translated documentation will be hosted on python.org. Examples of two active translation teams: https://docs.python.org/fr/ : French https://docs.python.org/ja/ : Japanese https://docs.python.org/en/ will redirect to https://docs.python.org/ . Sources of translated documentation will be hosted in the Python organization on GitHub: https://github.com/python/ . Contributors will have to accept a Documentation Contribution Agreement. Motivation On the French #python-fr IRC channel on freenode, it’s not rare to meet people who don’t speak English and so are unable to read the Python official documentation. Python wants to be widely available to all users in any language: this is also why Python 3 supports any non-ASCII identifiers: PEP 3131 There are at least 4 groups of people who are translating the Python documentation to their native language (French [16] [17] [18] , Japanese [19] [20] , Spanish [21] , Hungarian [26] [27] ) even though their translations are not visible on d.p.o. Other, less visible and less organized groups, are also translating the documentation, we’ve heard of Russian [25] , Chinese and Korean. Others we haven’t found yet might also exist. This PEP defines rules describing how to move translations on docs.python.org so they can easily be found by developers, newcomers and potential translators. The Japanese team has (as of March 2017) translated ~80% of the documentation, the French team ~20%. French translation went from 6% to 23% in 2016 [13] with 7 contributors [14] , proving a translation team can be faster than the rate the documentation mutates. Quoting Xiang Zhang about Chinese translations: I have seen several groups trying to translate part of our official doc. But their efforts are disperse and quickly become lost because they are not organized to work towards a single common result and their results are hold anywhere on the Web and hard to find. An official one could help ease the pain. Rationale Translation Issue tracker Considering that issues opened about translations may be written in the translation language, which can be considered noise but at least is inconsistent, issues should not be placed in the CPython issue tracker . As all translation must have their own GitHub project (see Repository for Po Files ), they must use the associated GitHub issue tracker. Considering the noise induced by translation issues redacted in any languages which may beyond every warnings land in the issue tracker, triage will have to be done. Considering that translations already exist and are not actually a source of noise in issue tracker, an unmanageable amount of work is not to be expected. Considering that Xiang Zhang and Victor Stinner are already triaging, and Julien Palard is willing to help on this task, noise on issue tracker is not to be expected. Also, language team coordinators (see Language Team ) should help with triaging the issue tracker by properly indicating, in the language of the issue author if required, the right issue tracker. Branches Translation teams should focus on last stable versions, and use tools (scripts, translation memory, …) to automatically translate what is done in one branch to other branches. Note Translation memories are a kind of database of previously translated paragraphs, even removed ones. See also Sphinx Internationalization . The newest currently stable branch will be translated and translations can be propagated to other branches. The scripts to build the documentation of older branches needs to be modified to support translation [12] , whereas these branches now only accept security-only fixes. The development branch (main) should have a lower translation priority than stable branches. But docsbuild-scripts should build it anyway so it is possible for a team to work on it to be ready for the next release. Hosting Domain Name, Content negotiation and URL Different translations can be identified by changing one of the following: Country Code Top Level Domain (CCTLD), path segment, subdomain or content negotiation. Buying a CCTLD for each translations is expensive, time-consuming, and sometimes almost impossible when already registered, this solution should be avoided. Using subdomains like “es.docs.python.org” or “docs.es.python.org” is possible but confusing (“is it es.docs.python.org or docs.es.python.org ?”). Hyphens in subdomains like pt-br.doc.python.org is uncommon and SEOMoz [23] correlated the presence of hyphens as a negative factor. Usage of underscores in subdomain is prohibited by the RFC 1123 , section 2.1. Finally, using subdomains means creating TLS certificates for each language. This not only requires more maintenance but will also cause issues in language switcher if, as for version switcher, we want a preflight to check if the translation exists in the given version: preflight will probably be blocked by same-origin-policy. Wildcard TLS certificates are very expensive. Using content negotiation (HTTP headers Accept-Language in the request and Vary: Accept-Language ) leads to a bad user experience where they can’t easily change the language. According to Mozilla: “This header is a hint to be used when the server has no way of determining the language via another way, like a specific URL, that is controlled by an explicit user decision.” [24] . As we want to be able to easily change the language, we should not use the content negotiation as a main language determination, so we need something else. Last solution is to use the URL path, which looks readable, allows for an easy switch from a language to another, and nicely accepts hyphens. Typically something like: “docs.python.org/de/” or, by using a hyphen: “docs.python.org/pt-BR/”. As for the version, sphinx-doc does not support compiling for multiple languages, so we’ll have full builds rooted under a path, exactly like we’re already doing with versions. So we can have “docs.python.org/de/3.6/” or “docs.python.org/3.6/de/”. A question that arises is: “Does the language contain multiple versions or does the version contain multiple languages?”. As versions exist in any case and translations for a given version may or may not exist, we may prefer “docs.python.org/3.6/de/”, but doing so scatters languages everywhere. Having “/de/3.6/” is clearer, meaning: “everything under /de/ is written in German”. Having the version at the end is also a habit taken by readers of the documentation: they like to easily change the version by changing the end of the path. So we should use the following pattern: “docs.python.org/LANGUAGE_TAG/VERSION/”. The current documentation is not moved to “/en/”, instead “docs.python.org/en/” will redirect to “docs.python.org”. Language Tag A common notation for language tags is the IETF Language Tag [4] based on ISO 639, although gettext uses ISO 639 tags with underscores (ex: pt_BR ) instead of dashes to join tags [5] (ex: pt-BR ). Examples of IETF Language Tags: fr (French), ja (Japanese), pt-BR (Orthographic formulation of 1943 - Official in Brazil). It is more common to see dashes instead of underscores in URLs [6] , so we should use IETF language tags, even if sphinx uses gettext internally: URLs are not meant to leak the underlying implementation. It’s uncommon to see capitalized letters in URLs, and docs.python.org doesn’t use any, so it may hurt readability by attracting the eye on it, like in: “ https://docs.python.org/pt-BR/3.6/library/stdtypes.html ”. RFC 5646#section-2.1.1 (Tags for Identifying Languages (IETF)) section-2.1 states that tags are not case sensitive. As the RFC allows lower case, and it enhances readability, we should use lowercased tags like pt-br . We may drop the region subtag when it does not add distinguishing information, for example: “de-DE” or “fr-FR”. (Although it might make sense, respectively meaning “German as spoken in Germany” and “French as spoken in France”). But when the region subtag actually adds information, for example “pt-BR” or “Portuguese as spoken in Brazil”, it should be kept. So we should use IETF language tags, lowercased, like /fr/ , /pt-br/ , /de/ and so on. Fetching And Building Translations Currently docsbuild-scripts are building the documentation [8] . These scripts should be modified to fetch and build translations. Building new translations is like building new versions so, while we’re adding complexity it is not that much. Two steps should be configurable distinctively: Building a new language, and adding it to the language switcher. This allows a transition step between “we accepted the language” and “it is translated enough to be made public”. During this step, translators can review their modifications on d.p.o without having to build the documentation locally. From the translation repositories, only the .po files should be opened by the docsbuild-script to keep the attack surface and probable bug sources at a minimum. This means no translation can patch sphinx to advertise their translation tool. (This specific feature should be handled by sphinx anyway [9] ). Community Mailing List The doc-sig mailing list will be used to discuss cross-language changes on translated documentation. There is also the i18n-sig list but it’s more oriented towards i18n APIs [1] than translating the Python documentation. Chat Due to the Python community being highly active on IRC, we should create a new IRC channel on freenode, typically #python-doc for consistency with the mailing list name. Each language coordinator can organize their own team, even by choosing another chat system if the local usage asks for it. As local teams will write in their native languages, we don’t want each team in a single channel. It’s also natural for the local teams to reuse their local channels like “#python-fr” for French translators. Repository for PO Files Considering that each translation team may want to use different translation tools, and that those tools should easily be synchronized with git, all translations should expose their .po files via a git repository. Considering that each translation will be exposed via git repositories, and that Python has migrated to GitHub, translations will be hosted on GitHub. For consistency and discoverability, all translations should be in the same GitHub organization and named according to a common pattern. Given that we want translations to be official, and that Python already has a GitHub organization, translations should be hosted as projects of the Python GitHub organization . For consistency, translation repositories should be called python-docs-LANGUAGE_TAG [22] , using the language tag used in paths: without region subtag if redundant, and lowercased. The docsbuild-scripts may enforce this rule by refusing to fetch outside of the Python organization or a wrongly named repository. The CLA bot may be used on the translation repositories, but with a limited effect as local coordinators may synchronize themselves with translations from an external tool, like transifex, and lose track of who translated what in the process. Versions can be hosted on different repositories, different directories or different branches. Storing them on different repositories will probably pollute the Python GitHub organization. As it is typical and natural to use branches to separate versions, branches should be used to do so. Translation tools Most of the translation work is actually done on Transifex [15] . Other tools may be used later like https://pontoon.mozilla.org/ and http://zanata.org/ . python-docs-translations The python-docs-translations GitHub organization is home to several useful translation tools including translations.python.org ( python-docs-translations/dashboard ). Documentation Contribution Agreement Documentation does require a license from the translator, as it involves creativity in the expression of the ideas. There’s multiple solutions, quoting Van Lindberg from the PSF asked about the subject: Docs should either have the copyright assigned or be under CCO. A permissive software license (like Apache or MIT) would also get the job done, although it is not quite fit for task. The translators should either sign an agreement or submit a declaration of the license with the translation. We should have in the project page an invitation for people to contribute under a defined license, with acceptance defined by their act of contribution. Such as: “By posting this project on Transifex and inviting you to participate, we are proposing an agreement that you will provide your translation for the PSF’s use under the CC0 license. In return, you may noted that you were the translator for the portion you translate. You signify acceptance of this agreement by submitting your work to the PSF for inclusion in the documentation.” It looks like having a “Documentation Contribution Agreement” is the most simple thing we can do as we can use multiple ways (GitHub bots, invitation page, …) in different context to ensure contributors are agreeing with it. Language Team Each language team should have one coordinator responsible for: Managing the team. Choosing and managing the tools the team will use (chat, mailing list, …). Ensure contributors understand and agree with the documentation contribution agreement. Ensure quality (grammar, vocabulary, consistency, filtering spam, ads, …). Redirect issues posted on issue tracker to the correct GitHub issue tracker for the language. Alternatives Simplified English It would be possible to introduce a “simplified English” version like Wikipedia did [10] , as discussed on python-dev [11] , targeting English learners and children. Pros: It yields a single translation, theoretically readable by everyone and reviewable by current maintainers. Cons: Subtle details may be lost, and translators from English to English may be hard to find as stated by Wikipedia: > The main English Wikipedia has 5 million articles, written by nearly 140K active users; the Swedish Wikipedia is almost as big, 3M articles from only 3K active users; but the Simple English Wikipedia has just 123K articles and 871 active users. That’s fewer articles than Esperanto! Changes Get a Documentation Contribution Agreement The Documentation Contribution Agreement have to be written by the PSF, then listed at https://www.python.org/psf/contrib/ and have its own page like https://www.python.org/psf/contrib/doc-contrib-form/ . Migrate GitHub Repositories We (authors of this PEP) already own French and Japanese Git repositories, so moving them to the Python documentation organization will not be a problem. We’ll however be following the New Translation Procedure . Setup a GitHub bot for Documentation Contribution Agreement To help ensuring contributors from GitHub have signed the Documentation Contribution Agreement, We can setup the “The Knights Who Say Ni” GitHub bot customized for this agreement on the migrated repositories [28] . Patch docsbuild-scripts to Compile Translations Docsbuild-script must be patched to: List the language tags to build along with the branches to build. List the language tags to display in the language switcher. Find translation repositories by formatting github.com:python/python-docs-{language_tag}.git (See Repository for Po Files ) Build translations for each branch and each language. Patched docsbuild-scripts must only open .po files from translation repositories. List coordinators in the devguide Add a page or a section with an empty list of coordinators to the devguide, each new coordinator will be added to this list. Create sphinx-doc Language Switcher Highly similar to the version switcher, a language switcher must be implemented. This language switcher must be configurable to hide or show a given language. The language switcher will only have to update or add the language segment to the path like the current version switcher does. Unlike the version switcher, no preflight are required as destination page always exists (translations does not add or remove pages). Untranslated (but existing) pages still exists, they should however be rendered as so, see Enhance Rendering of Untranslated and Fuzzy Translations . Update sphinx-doc Version Switcher The patch_url function of the version switcher in version_switch.js have to be updated to understand and allow the presence of the language segment in the path. Enhance Rendering of Untranslated and Fuzzy Translations It’s an opened sphinx issue [9] , but we’ll need it so we’ll have to work on it. Translated, fuzzy, and untranslated paragraphs should be differentiated. (Fuzzy paragraphs have to warn the reader what he’s reading may be out of date.) New Translation Procedure Designate a Coordinator The first step is to designate a coordinator, see Language Team , The coordinator must sign the CLA. The coordinator should be added to the list of translation coordinators on the devguide. Create GitHub Repository Create a repository named “python-docs-{LANGUAGE_TAG}” (IETF language tag, without redundant region subtag, with a dash, and lowercased.) on the Python GitHub organization (See Repository For Po Files .), and grant the language coordinator push rights to this repository. Setup the Documentation Contribution Agreement The README file should clearly show the following Documentation Contribution Agreement: NOTE REGARDING THE LICENSE FOR TRANSLATIONS: Python's documentation is maintained using a global network of volunteers. By posting this project on Transifex, GitHub, and other public places, and inviting you to participate, we are proposing an agreement that you will provide your improvements to Python's documentation or the translation of Python's documentation for the PSF's use under the CC0 license (available at `https://creativecommons.org/publicdomain/zero/1.0/legalcode`_). In return, you may publicly claim credit for the portion of the translation you contributed and if your translation is accepted by the PSF, you may (but are not required to) submit a patch including an appropriate annotation in the Misc/ACKS or TRANSLATORS file. Although nothing in this Documentation Contribution Agreement obligates the PSF to incorporate your textual contribution, your participation in the Python community is welcomed and appreciated. You signify acceptance of this agreement by submitting your work to the PSF for inclusion in the documentation. Add support for translations in docsbuild-scripts As soon as the translation hits its first commits, update the docsbuild-scripts configuration to build the translation (but not displaying it in the language switcher). Add Translation to the Language Switcher As soon as the translation hits: 100% of bugs.html with proper links to the language repository issue tracker. 100% of tutorial. 100% of library/functions (builtins). the translation can be added to the language switcher. Previous Discussions [Python-ideas] Cross link documentation translations (January, 2016) [Python-Dev] Translated Python documentation (February 2016) [Python-ideas] https://docs.python.org/fr/ ? (March 2016) References [ 1 ] [I18n-sig] Hello Python members, Do you have any idea about Python documents? ( https://mail.python.org/pipermail/i18n-sig/2013-September/002130.html ) [2] [Doc-SIG] Localization of Python docs ( https://mail.python.org/pipermail/doc-sig/2013-September/003948.html ) [ 4 ] IETF language tag ( https://en.wikipedia.org/wiki/IETF_language_tag ) [ 5 ] GNU Gettext manual, section 2.3.1: Locale Names ( https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html ) [ 6 ] Semantic URL: Slug ( https://en.wikipedia.org/wiki/Clean_URL#Slug ) [ 8 ] Docsbuild-scripts GitHub repository ( https://github.com/python/docsbuild-scripts/ ) [9] ( 1 , 2 ) i18n: Highlight untranslated paragraphs ( https://github.com/sphinx-doc/sphinx/issues/1246 ) [ 10 ] Wikipedia: Simple English ( https://simple.wikipedia.org/wiki/Main_Page ) [ 11 ] Python-dev discussion about simplified English ( https://mail.python.org/pipermail/python-dev/2017-February/147446.html ) [ 12 ] Passing options to sphinx from Doc/Makefile ( https://github.com/python/cpython/commit/57acb82d275ace9d9d854b156611e641f68e9e7c ) [ 13 ] French translation progression ( https://mdk.fr/pycon2016/#/11 ) [ 14 ] French translation contributors ( https://github.com/AFPy/python_doc_fr/graphs/contributors?from=2016-01-01&to=2016-12-31&type=c ) [ 15 ] Python-doc on Transifex ( https://www.transifex.com/python-doc/public/ ) [ 16 ] French translation ( https://www.afpy.org/doc/python/ ) [ 17 ] French translation on Gitea ( https://git.afpy.org/AFPy/python-docs-fr ) [ 18 ] French mailing list ( https://lists.afpy.org/mailman/listinfo/traductions ) [ 19 ] Japanese translation ( https://docs.python.jp/3/ ) [ 20 ] Japanese translation on GitHub ( https://github.com/python-doc-ja/python-doc-ja ) [ 21 ] Spanish translation ( https://docs.python.org/es/3/tutorial/index.html ) [ 22 ] [Python-Dev] Translated Python documentation: doc vs docs ( https://mail.python.org/pipermail/python-dev/2017-February/147472.html ) [ 23 ] Domains - SEO Best Practices | Moz ( https://moz.com/learn/seo/domain ) [ 24 ] Accept-Language ( https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language ) [ 25 ] Документация Python 2.7! ( https://python-lab.ru/documentation/index.html ) [ 26 ] Python-oktató ( https://web.archive.org/web/20170526080729/http://harp.pythonanywhere.com/python_doc/tutorial/index.html ) [ 27 ] The Python-hu Archives ( https://mail.python.org/pipermail/python-hu/ ) [ 28 ] [Python-Dev] PEP 545: Python Documentation Translations ( https://mail.python.org/pipermail/python-dev/2017-April/147752.html ) Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0545.rst Last modified: 2025-11-13 20:48:23 GMT Contents Abstract Motivation Rationale Translation Issue tracker Branches Hosting Domain Name, Content negotiation and URL Language Tag Fetching And Building Translations Community Mailing List Chat Repository for PO Files Translation tools python-docs-translations Documentation Contribution Agreement Language Team Alternatives Simplified English Changes Get a Documentation Contribution Agreement Migrate GitHub Repositories Setup a GitHub bot for Documentation Contribution Agreement Patch docsbuild-scripts to Compile Translations List coordinators in the devguide Create sphinx-doc Language Switcher Update sphinx-doc Version Switcher Enhance Rendering of Untranslated and Fuzzy Translations New Translation Procedure Designate a Coordinator Create GitHub Repository Setup the Documentation Contribution Agreement Add support for translations in docsbuild-scripts Add Translation to the Language Switcher Previous Discussions References Copyright Page Source (GitHub) | 2026-01-13T08:49:02 |
https://www.python.org/doc/essays/#top | Python Documentation Index | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Documentation >>> Python Essays Python Documentation Index Python Essays In this directory I place short essays (anything from 500 to 5000 words) on various Python subjects. See also a collection of presentations I have given. See also my blog at blogspot.com and my previous blog at artima.com. -- Guido van Rossum Table of contents (in mostly chronological order) Unifying types and classes in Python 2.2 (See below) Foreword for "Programming Python" (1st ed.) Written in 1996, this gives an overview of the early history and background of Python and some of my philosophy about software design and project management. See also my foreword to the 2nd edition . Implementing Graphs An elegant and perhaps not obvious way to represent graphs using Python's most fundamental and versatile data types, lists and dictionaries. An Optimization Anecdote Required reading if you find that your Python code runs too slow. Metaclass Programming in Python 1.5 Warning: reading this document may cause your brain to explode. Built-in Package Support in Python 1.5 The most official documentation for the new package features in Python 1.5. Standard Exception Classes in Python 1.5 The most official documentation for the new exception features in Python 1.5. (Updated for Python 1.5.2 by Barry Warsaw.) Glue It All Together With Python A position paper I wrote for and presented at the OMG-DARPA-MCC workshop on compositional software architectures in Monterey, California, January 6-8, 1998. What Is Python? Executive Summary A short (two paragraphs) high-level presentation of Python's virtues. Comparing Python to Other Languages Activist ammo or flame fodder? (Note: I received lots of feedback when I posted this to comp.lang.python. Unfortunately the feedback was diverted to a separate mailbox that I didn't know I had -- when I finally found it, I was a bit overwhelmed and so far have not yet found the time to update the article.) Proposed Improvements to Module Cleanup A revised version of the proposal I posted to comp.lang.python on Feb 6, 1998. This has been adopted in Python 1.5.1. Open Source Summit Trip Report My trip report of O'Reilly's Open Source Summit, essentially as posted on c.l.p. This version published in the Linux Gazette (it's an external link), in their May 1998 issue. Debugging Reference Count Problems An edited version of a posting to c.l.p on this subject, on May 27, 1998. Computer Programming for Everybody (old) A funding proposal that was accepted by DARPA in March 1999. Computer Programming for Everybody Revised, extended version of the previous proposal. Interview in Linux Journal Not quite an essay, but a stream of consciousness penned down by a journalist... More thoughts about CP4E. Interview in by Frank Willison for "Frankly Speaking" column Another stream of consciousness transcribed by a friendly listener... Not just on CP4E. Foreword for "Programming Python" (2nd ed.) The story continues... Unifying types and classes in Python 2.2 An introduction to the type/class unification effort in Python 2.2. Note that the unification work is officially labeled experimental and is subject to change in future releases of Python. Parade of the PEPs To start off Developer's Day at the Python10 conference I gave a keynote ending in what I dubbed "the parade of the PEPs". It was a brief overview of all open PEPs , where I gave my highly personal and subjective opinion for each PEP. Later, I realized that this might have been of interest to other developers. I didn't take notes at the conference, so below is a different set of comments that I created from scratch during a single two-hour sitting on March 7, 2002. I intend to occasionally update this with new comments and new PEPs. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
https://www.python.org/doc/essays/#python-network | Python Documentation Index | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Documentation >>> Python Essays Python Documentation Index Python Essays In this directory I place short essays (anything from 500 to 5000 words) on various Python subjects. See also a collection of presentations I have given. See also my blog at blogspot.com and my previous blog at artima.com. -- Guido van Rossum Table of contents (in mostly chronological order) Unifying types and classes in Python 2.2 (See below) Foreword for "Programming Python" (1st ed.) Written in 1996, this gives an overview of the early history and background of Python and some of my philosophy about software design and project management. See also my foreword to the 2nd edition . Implementing Graphs An elegant and perhaps not obvious way to represent graphs using Python's most fundamental and versatile data types, lists and dictionaries. An Optimization Anecdote Required reading if you find that your Python code runs too slow. Metaclass Programming in Python 1.5 Warning: reading this document may cause your brain to explode. Built-in Package Support in Python 1.5 The most official documentation for the new package features in Python 1.5. Standard Exception Classes in Python 1.5 The most official documentation for the new exception features in Python 1.5. (Updated for Python 1.5.2 by Barry Warsaw.) Glue It All Together With Python A position paper I wrote for and presented at the OMG-DARPA-MCC workshop on compositional software architectures in Monterey, California, January 6-8, 1998. What Is Python? Executive Summary A short (two paragraphs) high-level presentation of Python's virtues. Comparing Python to Other Languages Activist ammo or flame fodder? (Note: I received lots of feedback when I posted this to comp.lang.python. Unfortunately the feedback was diverted to a separate mailbox that I didn't know I had -- when I finally found it, I was a bit overwhelmed and so far have not yet found the time to update the article.) Proposed Improvements to Module Cleanup A revised version of the proposal I posted to comp.lang.python on Feb 6, 1998. This has been adopted in Python 1.5.1. Open Source Summit Trip Report My trip report of O'Reilly's Open Source Summit, essentially as posted on c.l.p. This version published in the Linux Gazette (it's an external link), in their May 1998 issue. Debugging Reference Count Problems An edited version of a posting to c.l.p on this subject, on May 27, 1998. Computer Programming for Everybody (old) A funding proposal that was accepted by DARPA in March 1999. Computer Programming for Everybody Revised, extended version of the previous proposal. Interview in Linux Journal Not quite an essay, but a stream of consciousness penned down by a journalist... More thoughts about CP4E. Interview in by Frank Willison for "Frankly Speaking" column Another stream of consciousness transcribed by a friendly listener... Not just on CP4E. Foreword for "Programming Python" (2nd ed.) The story continues... Unifying types and classes in Python 2.2 An introduction to the type/class unification effort in Python 2.2. Note that the unification work is officially labeled experimental and is subject to change in future releases of Python. Parade of the PEPs To start off Developer's Day at the Python10 conference I gave a keynote ending in what I dubbed "the parade of the PEPs". It was a brief overview of all open PEPs , where I gave my highly personal and subjective opinion for each PEP. Later, I realized that this might have been of interest to other developers. I didn't take notes at the conference, so below is a different set of comments that I created from scratch during a single two-hour sitting on March 7, 2002. I intend to occasionally update this with new comments and new PEPs. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:02 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.