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://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:48:41 |
https://www.lapor.go.id/instansi/kementerian-perdagangan | tags of your website --> Kementerian Perdagangan - LAPOR! Tentang LAPOR! Statistik Lapor! Versi Android Lapor! Versi iOS Toggle navigation Tentang LAPOR! Statistik Daftar Masuk Kementerian Perdagangan Lorem ipsum dolor sit amet, consectetur adipisicing elit. Assumenda necessitatibus modi temporibus nobis optio eos, nostrum vitae veniam officiis non ut corrupti ex expedita similique dolores culpa id, iure sapiente? --> Jalan M. I. Ridwan Rais No. 5 Jakarta Pusat 10110 021-3858171 / 021-3841961/62 contact.us@kemendag.go.id 102 pengikut Ikuti Sampaikan Laporan Anda Sampaikan Laporan Anda --> Pilih Klasifikasi Laporan PENGADUAN ASPIRASI PERMINTAAN INFORMASI Perhatikan Cara Menyampaikan Pengaduan Yang Baik dan Benar Upload Lampiran (Max 2MB) 0 Upload Lampiran Lokasi --> Anonim Rahasia LAPOR! × PANDUAN PENGISIAN PENGADUAN × PANDUAN PENGISIAN ASPIRASI × PANDUAN PENGISIAN PERMINTAAN INFORMASI Berita Kisah Sukses Kepengurusan Surat Keterangan Impor Bahan Kimia Saya ingin impor bahan baku kimia standar untuk penelitian dri china. Bagaimana cara pembuatan surat keterangan impor untuk penelitian maha... Linggar Pratiwi 0 Komentar 0 Dukungan Permohonan NPIK TPT melalui Hak Akses Inatrade Yth. Kementerian Perdagangan, Kami hendak mengajukan permohonan NPIK TPT Baru melalui Hak Akses Inatrade, tetapi saat melakukan pengajuan b... Rizka Wahyu 0 Komentar 0 Dukungan LCD Gedung Kementerian Perdagangan Tidak Berfungsi Yth Kementerian Perdagangan. Layar LCD yang menempel pada Gedung Kementerian Perdagangan tidak berfungsi dengan benar sejak 3 hari yang lal... Muhammad Daud 0 Komentar 1 Dukungan Baca Selengkapnya Kementerian Perdagangan PENILAIAN 0 : 0 Laporan : 0 Laporan : 0 Laporan : 0 Laporan : 0 Laporan Lihat rincian penilaian Unit Instansi Kantor Dagang dan Ekonomi Indonesia di Taipei Lihat seluruhnya (11) DIIKUTI OLEH Lihat seluruhnya (102) Ikuti Translate Page × Disclaimer: Anda menggunakan Google Translate. Kami tidak bertanggung jawab atas keakuratan informasi dalam bahasa diterjemahkan Download aplikasi mobile LAPOR! Dikelola oleh Lebih dekat dengan kami PRIVACY BERANDA BLOG KISAH SUKSES KETENTUAN LAYANAN TENTANG KAMI TUTORIAL VIDEO HUBUNGI KAMI Copyright 2026. Kantor Staf Presiden . Hak cipta dilindungi Undang-Undang. × MASUK Gunakan Akun Media Sosial Anda Facebook Twitter Google --> --> Atau dengan Email Anda --> Email, No. telp, atau username Lupa password? Password Masuk Anda belum memiliki akun? Daftar Sekarang Pilih Lokasi Geser map untuk mendapatkan lokasi yang anda inginkan Silahkan aktifkan fitur pelacakan lokasi Anda pada browser Tutup Hapus Lokasi Pilih Lokasi var mydata = [{"text":"Agama","id":911,"key":911,"inc":[{"text":"Haji dan Umroh","id":1029,"key":1029},{"text":"Lainnya terkait Agama","id":1032,"key":1032},{"text":"Pendidikan Agama","id":1030,"key":1030},{"text":"Penyediaan Fasilitas Ibadah","id":1031,"key":1031}]},{"text":"Corona Virus","key":674,"inc":[{"text":"Alat dan Logistik Kesehatan","key":1052,"inc":[{"text":"Alat Rapid Test","id":1633,"key":1633,"inc":[{"text":"Informasi Alat Rapid Test","id":2255,"key":2255},{"text":"Kualitas Alat Rapid Test","id":2253,"key":2253},{"text":"Kuantitas Alat Rapid Test","id":2252,"key":2252},{"text":"Permohonan Alat Rapid Test","id":2251,"key":2251},{"text":"Produksi Alat Rapid Test","id":2254,"key":2254}]},{"text":"APD","id":1631,"key":1631,"inc":[{"text":"Kualitas APD","id":2245,"key":2245},{"text":"Kuantitas APD","id":2244,"key":2244},{"text":"Penimbun APD","id":2247,"key":2247},{"text":"Produksi APD","id":2246,"key":2246}]},{"text":"Disinfektan, masker, dll","id":1635,"key":1635,"inc":[{"text":"Informasi Logistik Kesehatan Lainnya","id":2264,"key":2264},{"text":"Kualitas Logistik Kesehatan Lainnya","id":2261,"key":2261},{"text":"Penimbun Logistik Kesehatan","id":2263,"key":2263},{"text":"Permohonan Logistik Kesehatan","id":2260,"key":2260},{"text":"Produksi Logistik Kesehatan Lainnya","id":2262,"key":2262}]},{"text":"PCR Kit","id":1632,"key":1632,"inc":[{"text":"Informasi PCR Kit","id":2250,"key":2250},{"text":"Pengaduan PCR Kit","id":2249,"key":2249},{"text":"Permohonan PCR Kit","id":2248,"key":2248}]},{"text":"Ventilator","id":1634,"key":1634,"inc":[{"text":"Informasi Ventilator","id":2259,"key":2259},{"text":"Kualitas Ventilator","id":2257,"key":2257},{"text":"Permohonan Ventilator","id":2256,"key":2256},{"text":"Produksi Ventilator","id":2258,"key":2258}]}]},{"text":"Bantuan Masyarakat Corona","key":1057,"inc":[{"text":"Bansos daerah (Pemprov, Kab\/Kota)","id":1668,"key":1668,"inc":[{"text":"Admin Bansos Daerah Covid","id":2338,"key":2338},{"text":"Besaran Bansos Daerah Covid","id":2340,"key":2340},{"text":"Informasi Bansos Daerah Covid","id":2336,"key":2336},{"text":"Keluhan BansosD aerah Covid","id":2341,"key":2341},{"text":"Kepesertaan Bansos Daerah Covid","id":2337,"key":2337},{"text":"Penyelewengan Bansos Daerah Covid","id":2339,"key":2339}]},{"text":"Bansos K\/L","id":1670,"key":1670,"inc":[{"text":"Admin Bansos Kemendikbud","id":2350,"key":2350},{"text":"Besaran Bansos Kemendikbud","id":2351,"key":2351},{"text":"Informasi Bansos Kemendikbud","id":2348,"key":2348},{"text":"Keluhan Bansos Kemendikbud","id":2354,"key":2354},{"text":"Kepesertaan Bansos Kemendikbud","id":2349,"key":2349},{"text":"Penyelewengan Bansos Kemendikbud","id":2352,"key":2352},{"text":"Realisasi Bansos Kemendikbud","id":2353,"key":2353}]},{"text":"Bansos Presiden Jabodetabek","id":1664,"key":1664,"inc":[{"text":"Besaran Bansos Presiden Jabodetabek","id":2319,"key":2319},{"text":"Informasi Bansos Presiden Jabodetabek","id":2318,"key":2318},{"text":"Keluhan Bansos Presiden Jabodetabek","id":2322,"key":2322},{"text":"Kepesertaan Bansos Presiden Jabodetabek","id":2320,"key":2320},{"text":"Penyaluran Bansos Presiden Jabodetabek","id":2321,"key":2321}]},{"text":"Bantuan Langsung Tunai Dana Desa (BLT DD)","id":1666,"key":1666,"inc":[{"text":"Informasi BLT Desa","id":2328,"key":2328},{"text":"Jumlahuang BLT Desa","id":2330,"key":2330},{"text":"Keluhan BLT Desa","id":2332,"key":2332},{"text":"Penerima BLT Desa","id":2329,"key":2329},{"text":"Tunai BLT Desa","id":2331,"key":2331}]},{"text":"Bantuan Listrik","id":1662,"key":1662,"inc":[{"text":"Informasi Listrik COVID","id":2303,"key":2303},{"text":"Keluhan Listrik COVID","id":2306,"key":2306},{"text":"Kepesertaan Listrik COVID","id":2304,"key":2304},{"text":"Teknis Listrik COVID","id":2305,"key":2305}]},{"text":"Bantuan Sosial Tunai (BST)","id":1665,"key":1665,"inc":[{"text":"Besaran BST Covid","id":2324,"key":2324},{"text":"Informasi BST Covid","id":2323,"key":2323},{"text":"Keluhan BST Covid","id":2327,"key":2327},{"text":"Kepesertaan BST Covid","id":2325,"key":2325},{"text":"Penyaluran BST Covid","id":2326,"key":2326}]},{"text":"Kartu Prakerja","id":1663,"key":1663,"inc":[{"text":"Aplikasi Pra Kerja","id":2314,"key":2314},{"text":"Biaya Kursus Pra Kerja","id":2312,"key":2312},{"text":"Informasi Pra Kerja","id":2307,"key":2307},{"text":"Keluhan Pra Kerja","id":2317,"key":2317},{"text":"KKN Pra Kerja","id":2309,"key":2309},{"text":"Kuota Pra Kerja","id":2315,"key":2315},{"text":"Materi Pelatihan Pra Kerja","id":2310,"key":2310},{"text":"Pendaftaran Online Pra Kerja","id":2308,"key":2308},{"text":"Penyalahgunaan Pra Kerja","id":2316,"key":2316},{"text":"Sasaran Pra Kerja","id":2311,"key":2311},{"text":"Tes Pra Kerja","id":2313,"key":2313}]},{"text":"Keringanan kredit","id":1669,"key":1669,"inc":[{"text":"Biaya Kredit Covid","id":2345,"key":2345},{"text":"Informasi Kredit Covid","id":2342,"key":2342},{"text":"Keluhan Kredit Covid","id":2347,"key":2347},{"text":"Prayarat Kredit Covid","id":2344,"key":2344},{"text":"Realisasi Kredit Covid","id":2343,"key":2343},{"text":"Regulasi Kredit Covid","id":2346,"key":2346}]},{"text":"PKH Program Keluarga Harapan","id":1660,"key":1660,"inc":[{"text":"Bansos PKH","id":2285,"key":2285},{"text":"Data PKH","id":2287,"key":2287},{"text":"Fasilitas PKH","id":2292,"key":2292},{"text":"Informasi PKH","id":2283,"key":2283},{"text":"Keluhan PKH","id":2293,"key":2293},{"text":"KKN PKH","id":2288,"key":2288},{"text":"KKS PKH","id":2290,"key":2290},{"text":"Komplementaritas PKH","id":2286,"key":2286},{"text":"Perbankan PKH","id":2289,"key":2289},{"text":"SDM PKH","id":2284,"key":2284},{"text":"Sosialisasi PKH","id":2291,"key":2291}]},{"text":"Program Keselamatan POLRI","id":1667,"key":1667,"inc":[{"text":"Informasi Program Keselamatan","id":2333,"key":2333},{"text":"Keluhan Program Keselamatan","id":2335,"key":2335},{"text":"Perbankan Program Keselamatan","id":2334,"key":2334}]},{"text":"Program Sembako","id":1661,"key":1661,"inc":[{"text":"Data Program Sembako","id":2296,"key":2296},{"text":"E-Warong","id":2298,"key":2298},{"text":"Informasi Program Sembako","id":2294,"key":2294},{"text":"Keluhan Program Sembako","id":2302,"key":2302},{"text":"KKS Program Sembako","id":2295,"key":2295},{"text":"Paket Program Sembako","id":2299,"key":2299},{"text":"Penyalahgunaan Program Sembako","id":2301,"key":2301},{"text":"Perbankan Program Sembako","id":2297,"key":2297},{"text":"Sosialisasi Program Sembako","id":2300,"key":2300}]},{"text":"Umum (semua JPS Covid atau skema bansos yang lain)","id":1671,"key":1671,"inc":[{"text":"Apresiasi JPS Covid","id":2355,"key":2355}]}]},{"text":"Informasi COVID-19","key":1056,"inc":[{"text":"Lainnya","id":1659,"key":1659,"inc":[{"text":"Informasi Media COVID-19 Lainnya","id":2282,"key":2282}]},{"text":"Pengaduan Hotline\/Call Center 117","id":1655,"key":1655,"inc":[{"text":"Informasi Call Center 117 COVID-19","id":2276,"key":2276},{"text":"Pengaduan Call Center 117 COVID-19","id":2275,"key":2275}]},{"text":"Pengaduan Hotline\/Call Center 119","id":1656,"key":1656,"inc":[{"text":"Informasi Call Center 119 COVID-19","id":2278,"key":2278},{"text":"Pengaduan Call Center 119 COVID-19","id":2277,"key":2277}]},{"text":"Pengaduan Media (Cetak dan Elektronik) tentang COVID-19","id":1658,"key":1658,"inc":[{"text":"Informasi Media Elektronik COVID-19","id":2281,"key":2281},{"text":"Pengaduan Media COVID-19","id":2280,"key":2280}]},{"text":"Pengaduan Website tentang COVID-19","id":1657,"key":1657,"inc":[{"text":"Pengaduan Website COVID-19","id":2279,"key":2279}]}]},{"text":"Pelayanan Kesehatan","key":1053,"inc":[{"text":"Pelayanan Kesehatan Ibu dan Anak","id":1642,"key":1642},{"text":"Pelayanan Kesehatan lain yang terdampak akibat COVID-19","id":1643,"key":1643},{"text":"Pemeriksaan PCR atau Swab","id":1640,"key":1640},{"text":"Pemulasaran Jenazah COVID-19","id":1645,"key":1645},{"text":"Permintaan Rujukan Pasien","id":1636,"key":1636,"inc":[{"text":"Realisasi Rujukan Pasien","id":2375,"key":2375}]},{"text":"Rapid Test","id":1639,"key":1639},{"text":"Rumah Sakit Darurat COVID-19","id":1641,"key":1641},{"text":"Rumah Sakit Rujukan","id":1637,"key":1637},{"text":"Stock Obat","id":1644,"key":1644},{"text":"Tenaga Kesehatan atau Instansi Kesehatan","id":1638,"key":1638}]},{"text":"Pendampingan Kesehatan Jiwa\/Mental","key":1055,"inc":[{"text":"Lainnya","id":1654,"key":1654,"inc":[{"text":"Informasi Kesehatan Jiwa","id":2274,"key":2274}]},{"text":"ODGJ","id":3461,"key":3461},{"text":"Pengaduan Layanan Kesehatan Jiwa\/Mental","id":1652,"key":1652,"inc":[{"text":"Kualitas Pelayanan Kesehatan","id":2272,"key":2272}]},{"text":"Permohonan Pendampingan Psikolog","id":1653,"key":1653,"inc":[{"text":"Permohonan Pendampingan Psikolog","id":2273,"key":2273}]}]},{"text":"Pengaduan Klaim dan Verifikasi Pelayanan Kesehatan Pasien Covid-19","key":1054,"inc":[{"text":"Biaya Perawatan Pasien COVID-19","id":1648,"key":1648,"inc":[{"text":"Pembayaran COVID-19","id":2267,"key":2267},{"text":"Pembayaran COVID-19 Lainnya","id":2268,"key":2268}]},{"text":"Informasi","id":1649,"key":1649,"inc":[{"text":"Informasi Klaim COVID-19","id":2269,"key":2269}]},{"text":"Kriteria Pasien yang ditanggung dalam Skema Covid","id":1650,"key":1650,"inc":[{"text":"Kriteria Pasien","id":2270,"key":2270}]},{"text":"Lainnya","id":1651,"key":1651,"inc":[{"text":"Informasi BPJS COVID Lainnya","id":2271,"key":2271}]},{"text":"Pengajuan Klaim Pelayanan Kesehatan Covid-19","id":1646,"key":1646,"inc":[{"text":"Pengaduan Klaim COVID-19","id":2265,"key":2265}]},{"text":"Proses Verifikasi Data Pasien COVID-19","id":1647,"key":1647,"inc":[{"text":"Verifikasi Klaim COVID-19","id":2266,"key":2266}]}]},{"text":"PSBB","key":1058,"inc":[{"text":"Bekerja dari Rumah (WFH)","id":1673,"key":1673,"inc":[{"text":"WFH","id":2358,"key":2358}]},{"text":"Belajar dari Rumah","id":1674,"key":1674,"inc":[{"text":"Belajar Dari Rumah PT","id":2359,"key":2359},{"text":"Dikdasmen Dari Rumah","id":2360,"key":2360}]},{"text":"Jaga Jarak Aman (Social Distancing)","id":1675,"key":1675,"inc":[{"text":"Pelanggaran Social Distancing","id":2361,"key":2361},{"text":"Social Distancing","id":2362,"key":2362}]},{"text":"Karantina Wilayah","id":1672,"key":1672,"inc":[{"text":"Aspirasi Karantina Wilayah","id":2356,"key":2356},{"text":"Kebijakan Nasional Karantina Wilayah","id":2357,"key":2357}]}]}]},{"text":"Ekonomi\u00a0dan\u00a0Keuangan","key":907,"inc":[{"text":"Anggaran dan Perbendaharaan","id":989,"key":989},{"text":"Bea dan Cukai","id":985,"key":985},{"text":"Jasa Keuangan","key":983,"inc":[{"text":"Industri Keuangan Non-Bank","id":1539,"key":1539,"inc":[{"text":"dana pensiun","id":2235,"key":2235},{"text":"Lainnya terkait Industri Keuangan Non-Bank","id":2239,"key":2239},{"text":"Lembaga Jasa Keuangan Khusus","id":2237,"key":2237},{"text":"Lembaga Keuangan Mikro","id":2238,"key":2238},{"text":"lembaga pembiayaan","id":2236,"key":2236},{"text":"perasuransian","id":2234,"key":2234}]},{"text":"Lainnya terkait Jasa Keuangan","id":1541,"key":1541},{"text":"Layanan Keuangan Digital\/Fintech","id":1540,"key":1540,"inc":[{"text":"Bunga Fintech","id":2241,"key":2241},{"text":"e-meterai","id":3061,"key":3061},{"text":"Informasi Legalitas Fintech","id":2242,"key":2242},{"text":"Lainnya terkait Layanan Keuangan Digital\/Fintech","id":2243,"key":2243},{"text":"Sistem Penagihan Fintech","id":2240,"key":2240}]},{"text":"Pasar Modal","id":1538,"key":1538},{"text":"Perbankan","id":1537,"key":1537}]},{"text":"Kawasan Ekonomi Khusus","id":986,"key":986},{"text":"Kekayaan Negara dan Lelang","id":990,"key":990},{"text":"Kepuasan Konsumen","id":978,"key":978},{"text":"Koperasi, Usaha Kecil, dan Menengah","id":981,"key":981},{"text":"Lainnya terkait Ekonomi dan Keuangan","id":992,"key":992},{"text":"Pajak","id":987,"key":987,"inc":[{"text":"Amnesti Pajak","id":1546,"key":1546},{"text":"Lainnya terkait Pajak","id":1547,"key":1547},{"text":"Pajak Badan","id":1543,"key":1543},{"text":"Pajak Daerah","id":1544,"key":1544},{"text":"Pajak Perorangan","id":1542,"key":1542},{"text":"Retribusi Pajak","id":1545,"key":1545}]},{"text":"Pariwisata","id":980,"key":980,"inc":[{"text":"Destinasi Pariwisata","id":1534,"key":1534},{"text":"Kebudayaan","id":1535,"key":1535},{"text":"Lainnya terkait Pariwisata","id":1536,"key":1536}]},{"text":"Penanaman Modal\/ Investasi","id":976,"key":976},{"text":"Pengadaan Barang\/Jasa","key":984,"inc":[{"text":"Advokasi hukum pemerintah daerah","id":3361,"key":3361},{"text":"Penanganan sengketa\/permasalahan hukum\/penyimpangan tender","id":3369,"key":3369},{"text":"SDM PBJ","id":3341,"key":3341,"inc":[{"text":"Jabatan Fungsional Pengelola PBJ","id":3345,"key":3345},{"text":"Sertifikasi PBJ","id":3353,"key":3353}]},{"text":"Sistem Pengadaan Barang\/Jasa Pemerintah","id":3321,"key":3321,"inc":[{"text":"Sistem Informasi Kinerja Penyedia (SIKaP)","id":3329,"key":3329},{"text":"Sistem Rencana Umum Pengadaan (SiRUP)","id":3325,"key":3325}]}]},{"text":"Pengiriman Barang\/ Logistik","id":988,"key":988,"inc":[{"text":"Lainnya terkait Pengiriman Barang\/ Logistik","id":1550,"key":1550},{"text":"Layanan Pos","id":1548,"key":1548},{"text":"Pengiriman Luar Negeri","id":1549,"key":1549}]},{"text":"Perbankan","id":982,"key":982},{"text":"Perdagangan","id":977,"key":977,"inc":[{"text":"Intrade\/ Perizinanan Perdagangan","id":1527,"key":1527},{"text":"Ketersediaan Barang Kebutuhan Pokok","id":1528,"key":1528},{"text":"Lainnya terkait Perdagangan","id":1530,"key":1530},{"text":"Pemantauan Harga Bahan Pokok","id":1529,"key":1529}]},{"text":"Perimbangan Keuangan Pusat dan Daerah","id":991,"key":991,"inc":[{"text":"APBD","id":1551,"key":1551},{"text":"BUMD","id":1552,"key":1552},{"text":"Lainnya terkait Perimbangan Keuangan Pusat dan Daerah","id":1553,"key":1553}]},{"text":"Perindustrian","id":979,"key":979,"inc":[{"text":"Home Industri","id":1532,"key":1532},{"text":"Lainnya terkait Perindustrian","id":1533,"key":1533},{"text":"Perizinan Home Industri","id":1531,"key":1531}]}]},{"text":"Kesehatan","key":5,"inc":[{"text":"Bantuan Biaya Pendidikan","id":2848,"key":2848,"inc":[{"text":"Afirmasi Dokter\/Dokter Gigi","id":2854,"key":2854},{"text":"Dokter layanan primer","id":2863,"key":2863},{"text":"Dokter spesialis fellowship","id":2860,"key":2860},{"text":"Dokter Sub-Spesialis\/Spesialis dan Dokter Gigi Sub-Spesialis\/Spesialis","id":2857,"key":2857},{"text":"SDM Kesehatan","id":2866,"key":2866}]},{"text":"Gizi Buruk\/Stunting","id":925,"key":925},{"text":"Jaminan Sosial Kesehatan","key":923,"inc":[{"text":"Administrasi BPJS Kesehatan","id":1387,"key":1387,"inc":[{"text":"Alamat domisili peserta tidak sesuai","id":2089,"key":2089},{"text":"Alur pelayanan tidak jelas","id":2104,"key":2104},{"text":"Anak 21 Tahun PPU yg masih kuliah","id":2058,"key":2058},{"text":"Antrian lama","id":2096,"key":2096},{"text":"Aplikasi pendaftaran macet","id":2113,"key":2113},{"text":"Aplikasi pendaftaran sulit di akses","id":2111,"key":2111},{"text":"Aplikasi pendaftaran tidak userfriendly","id":2112,"key":2112},{"text":"Cara menggunakan Aplikasi pendaftaran","id":2074,"key":2074},{"text":"Daftar isian peserta sulit dipahami","id":2105,"key":2105},{"text":"Data di entry tidak sesuai","id":2116,"key":2116},{"text":"Denda sudah di bayarkan namun tidak dapat cetak SEP","id":2125,"key":2125},{"text":"Faskes Tk. I peserta tidak sesuai","id":2127,"key":2127},{"text":"Formulir pendaftaran tidak tersedia","id":2117,"key":2117},{"text":"Frontliner tidak ramah","id":2103,"key":2103},{"text":"Hak kelas rawat peserta tidak sesuai","id":2107,"key":2107},{"text":"Hak peserta","id":2075,"key":2075},{"text":"Hotline Sevice\/Kantor Cabang\/RO Sulit Dihubungi","id":2114,"key":2114},{"text":"Identitas Alamat Domisili\/Surat Menyurat","id":2066,"key":2066},{"text":"Identitas Jenis Kelamin","id":2065,"key":2065},{"text":"Identitas Nama","id":2063,"key":2063},{"text":"Identitas Nomor Handphone\/telpon\/e-mail","id":2067,"key":2067},{"text":"Identitas Tanggal Lahir","id":2064,"key":2064},{"text":"Informasi dari petugas tidak jelas","id":2118,"key":2118},{"text":"Informasi sulit di peroleh","id":2097,"key":2097},{"text":"Informasi tidak jelas","id":2098,"key":2098},{"text":"Informasi tidak sesuai","id":2099,"key":2099},{"text":"Jadwal tidak jelas","id":2120,"key":2120},{"text":"Jaringan Offline","id":2106,"key":2106},{"text":"Jumlah denda pelayanan tidak sesuai","id":2124,"key":2124},{"text":"Kanal Pendaftaran (Lokasi, hari\/jam pelayanan)","id":2072,"key":2072},{"text":"Kanal PIPP","id":2078,"key":2078},{"text":"Kanal PIPP tidak dapat di akses","id":2108,"key":2108},{"text":"Kartu Identitas Peserta","id":2077,"key":2077},{"text":"Kartu tidak diterima lebih dari 6 hari kerja setelah pembayaran iuran pertama","id":2095,"key":2095},{"text":"Keluhan PBPU","id":2132,"key":2132},{"text":"Keluhan PPU","id":2133,"key":2133},{"text":"Kendala Pindah Segmen karena tunggakan iuran","id":2091,"key":2091},{"text":"Kewajiban Peserta","id":2076,"key":2076},{"text":"Lainnya Terkait Administrasi BPJS Kesehatan","id":2134,"key":2134},{"text":"Laporan Ketidakpatuhan Badan Usaha Dalam Memberikan Data yang benar (Kebenaran Data)","id":2129,"key":2129},{"text":"Lokasi KC\/KK sulit ditemukan","id":2100,"key":2100},{"text":"Manfaat Penjaminan","id":2073,"key":2073},{"text":"Nama peserta tidak sesuai","id":2086,"key":2086},{"text":"NIK peserta tidak sesuai","id":2087,"key":2087},{"text":"No HP \/ Email tidak sesuai","id":2090,"key":2090},{"text":"Non-aktif anak PPU usia > 21 tahun","id":2126,"key":2126},{"text":"Non-aktif karena data ganda","id":2082,"key":2082},{"text":"Non-aktif karena iuran","id":2081,"key":2081},{"text":"Non-aktif karena meninggal","id":2083,"key":2083},{"text":"Non-aktif karena tidak masuk SK mensos","id":2084,"key":2084},{"text":"Non-aktif karena usia diatas 90 Tahun","id":2093,"key":2093},{"text":"Non-aktif Penangguhan Peserta","id":2080,"key":2080},{"text":"Non-aktif Setelah perpindahan segmen","id":2085,"key":2085},{"text":"Pelayanan lambat","id":2101,"key":2101},{"text":"Penambahan anggota keluarga","id":2060,"key":2060},{"text":"Penanganan tidak solutif","id":2109,"key":2109},{"text":"Pendaftaran Bayi Baru Lahir","id":2055,"key":2055},{"text":"Pengaktifan Peserta diatas 90 tahun","id":2059,"key":2059},{"text":"Penolakan peserta dari luar daerah di FKTP","id":2128,"key":2128},{"text":"Penonaktifan Peserta Meninggal Dunia","id":2068,"key":2068},{"text":"Permintaan Informasi Tentang Pendaftaran PBI","id":2131,"key":2131},{"text":"Permintaan Informasi Tentang Pendaftaran PPU PNS","id":2130,"key":2130},{"text":"Perubahan Fasilitas Kesehatan Tingkat I","id":2061,"key":2061},{"text":"Perubahan Kelas Rawat","id":2062,"key":2062},{"text":"Perubahan segmen kepesertaan","id":2056,"key":2056},{"text":"Petugas tidak ramah","id":2115,"key":2115},{"text":"Prosedur Pendaftaran","id":2071,"key":2071},{"text":"Prosedur Penggantian kartu","id":2057,"key":2057},{"text":"Proses pendaftaran lama\/ tidak sesuai SLA","id":2119,"key":2119},{"text":"Sarana dan Prasarana tidak memadai","id":2092,"key":2092},{"text":"Satpam tidak ramah","id":2102,"key":2102},{"text":"SLA Penanganan Pengaduan","id":2079,"key":2079},{"text":"Sosialisasi kurang","id":2121,"key":2121},{"text":"Sosialisasi terlambat","id":2123,"key":2123},{"text":"Sosialisasi tidak jelas","id":2122,"key":2122},{"text":"Status Kepesertaan","id":2070,"key":2070},{"text":"Susunan anggota keluarga tidak sesuai KK","id":2094,"key":2094},{"text":"Syarat Pendaftaran","id":2069,"key":2069},{"text":"Tanggal Lahir \/ Jenis Kelamin peserta tidak sesuai","id":2088,"key":2088},{"text":"Waktu Penanganan Pengaduan lama","id":2110,"key":2110}]},{"text":"Iuran dan Denda BPJS Kesehatan","id":1388,"key":1388,"inc":[{"text":"Autodebet pembayaran pertama gagal tidak terinformasikan","id":2148,"key":2148},{"text":"Bank tidak bersedia melakukan registrasi Autodebet","id":2150,"key":2150},{"text":"Besaran Iuran","id":2141,"key":2141},{"text":"Cek Tagihan\/Pembayaran","id":2138,"key":2138},{"text":"Gagal registrasi Autodebet tidak terinformasikan","id":2147,"key":2147},{"text":"Hasil rekonsiliasi iuran tidak sesuai dengan tagihan","id":2145,"key":2145},{"text":"Iuran tidak sesuai","id":2149,"key":2149},{"text":"Iuran tidak tersplit ke anggota keluarga lain","id":2144,"key":2144},{"text":"Lainnya terkait Iuran dan Denda BPJS Kesehatan","id":2154,"key":2154},{"text":"Lamanya proses refund","id":2153,"key":2153},{"text":"Lokasi pembayaran iuran","id":2135,"key":2135},{"text":"Nomor VA tidak dikenal","id":2146,"key":2146},{"text":"Nomor Virtual Account","id":2136,"key":2136},{"text":"Pembayaran iuran bayi baru lahir","id":2143,"key":2143},{"text":"Prosedur Refund","id":2140,"key":2140},{"text":"Proses Autodebet gagal","id":2151,"key":2151},{"text":"Rekonsiliasi\/Penyesuaian Tagihan","id":2139,"key":2139},{"text":"Syarat dan Prosedur Autodebet","id":2142,"key":2142},{"text":"Tagihan iuran tidak muncul setelah 14 hari pendaftaran","id":2152,"key":2152},{"text":"Tata Cara Pembayaran Iuran","id":2137,"key":2137}]},{"text":"Lainnya terkait Jaminan Sosial Kesehatan","id":1391,"key":1391},{"text":"Masalah Jaminan Sosial","id":2728,"key":2728,"inc":[{"text":"Asuransi Kesehatan","id":2731,"key":2731},{"text":"Asuransi Ketenagakerjaan","id":2734,"key":2734},{"text":"Asuransi Profesi","id":2737,"key":2737}]},{"text":"Pelayanan Kesehatan BPJS","id":1389,"key":1389,"inc":[{"text":"Adanya manfaat pelayanan yang seharusnya dijamin namun menjadi tanggungan peserta","id":2173,"key":2173},{"text":"Akses Fasilitas Kesehatan sulit","id":2170,"key":2170},{"text":"Alamat dan Jam Pelayanan Fasilitas Kesehatan","id":2161,"key":2161},{"text":"Alat bantu kesehatan kosong","id":2205,"key":2205},{"text":"Ambulance tidak tersedia di FKTP","id":2201,"key":2201},{"text":"Antrian mendapatkan pelayanan","id":2164,"key":2164},{"text":"dokter di FKTP kurang memahami program rujuk balik","id":2198,"key":2198},{"text":"dokter di RS tidak memberikan surat rujuk balik","id":2197,"key":2197},{"text":"Fasilitas kesehatan kurang memahami program Promotif Preventif","id":2203,"key":2203},{"text":"Fasilitas kesehatan tidak menjalankan program Promotif Preventif","id":2202,"key":2202},{"text":"Gangguan aplikasi Edabu","id":2180,"key":2180},{"text":"Gangguan aplikasi P-Care","id":2179,"key":2179},{"text":"Hak kelas perawatan","id":2166,"key":2166},{"text":"Iur biaya alat bantu kesehatan tidak sesuai ketentuan","id":2204,"key":2204},{"text":"Iur biaya naik kelas tidak sesuai ketentuan","id":2195,"key":2195},{"text":"Iur biaya pelayanan ambulance","id":2200,"key":2200},{"text":"Iur biaya pelayanan FKRTL yang tidak sesuai","id":2191,"key":2191},{"text":"Iur biaya pelayanan FKTP yang tidak sesuai","id":2190,"key":2190},{"text":"Jadwal praktek tidak sesuai","id":2184,"key":2184},{"text":"Kamar hanya tersedia untuk pasien umum\/pembedaan pasien","id":2193,"key":2193},{"text":"kamar penuh","id":2192,"key":2192},{"text":"Kartu Peserta disalah gunakan","id":2186,"key":2186},{"text":"Kekosongan Ruang Perawatan Khusus (ICCU, ICU, NICU, HCU, PICU dll.)","id":2175,"key":2175},{"text":"Ketentuan dan Prosedur pembayaran Denda Pelayanan","id":2169,"key":2169},{"text":"KIS digital tidak diterima di Faskes","id":2185,"key":2185},{"text":"Kurangnya informasi tentang ketersediaan tempat tidur","id":2176,"key":2176},{"text":"Lainnya terkait Pelayanan Kesehatan BPJS","id":2209,"key":2209},{"text":"Lamanya antrian Pendaftaran di Fasilitas kesehatan","id":2188,"key":2188},{"text":"Lamanya antrian untuk mendapatkan tindakan medis\/pelayanan kesehatan","id":2189,"key":2189},{"text":"Lingkup manfaat pelayanan yang di tanggung","id":2159,"key":2159},{"text":"pasien di arahkan untuk naik kelas tanpa penjelasan","id":2196,"key":2196},{"text":"Pelayanan alat bantu kesehatan","id":2168,"key":2168},{"text":"Pelayanan Ambulan","id":2158,"key":2158},{"text":"Pelayanan dengan COB","id":2157,"key":2157},{"text":"Pelayanan di luar wilayah Domisili","id":2160,"key":2160},{"text":"Pelayanan Gawat Darurat","id":2155,"key":2155},{"text":"Pelayanan gawat darurat tidak dilayani di rumah sakit yang belum bekerja sama","id":2178,"key":2178},{"text":"Pelayanan kesehatan yang tidak ditanggung","id":2165,"key":2165},{"text":"Penjaminan peserta di hari libur","id":2174,"key":2174},{"text":"Penolakan persalinan normal di FKRTL","id":2208,"key":2208},{"text":"Permintaan Informasi Tentang Akomadasi atau Ketersediaan Ruang Rawat Inap","id":2207,"key":2207},{"text":"Peserta di rawat dikelas yg tidak sesuai haknya","id":2194,"key":2194},{"text":"Peserta di tolak fasilitas kesehatan diluar wilayah domisili","id":2187,"key":2187},{"text":"Petugas Administrasi tidak ramah","id":2171,"key":2171},{"text":"Petugas Medis dan paramedis tidak ramah","id":2172,"key":2172},{"text":"Poli Rumah Sakit tujuan rujukan tutup\/tidak update","id":2183,"key":2183},{"text":"Program COB tidak berjalan sebagaimana mestinya","id":2206,"key":2206},{"text":"Program Promotif Preventif","id":2167,"key":2167 | 2026-01-13T08:48:41 |
https://openapi.tools/categories/converters | Converters | OpenApi.tools, from APIs You Won't Hate Sponsored by Zudoku - Open-source, highly customizable API documentation powered by OpenAPI Get Started Sponsor openapi.tools GitHub Get Started All Tools All Categories Legacy Tools Contributing Sponsors Sponsor Badges Collections Arazzo Support Overlays Support Open Source Tools SaaS Tools OpenAPI Tool Categories Annotations Code generators Converters Data Validators Documentation Domain-Specific Languages (DSLs) Gateways HTTP Clients IDEs and GUI Editors Learning Miscellaneous Mock Servers Monitoring OpenAPI-aware Frameworks Parsers Schema Validators SDK Generators Security Server Implementations Testing Text Editors © 2026 APIs You Won't Hate Get in touch to become a Sponsor . This site is community-driven and OSS , built with Astro and hosted on Netlify . Converters Various tools to convert to and from OpenAPI and other API description formats. Converters There are additional tools in this category, but they only support legacy versions of OpenAPI. If you really need to work with some old OpenAPI descriptions perhaps these legacy tools could be of use * * * | 2026-01-13T08:48:41 |
https://openapi.tools/tools | All Tools | OpenApi.tools, from APIs You Won't Hate Sponsored by Zudoku - Open-source, highly customizable API documentation powered by OpenAPI Get Started Sponsor openapi.tools GitHub Get Started All Tools All Categories Legacy Tools Contributing Sponsors Sponsor Badges Collections Arazzo Support Overlays Support Open Source Tools SaaS Tools OpenAPI Tool Categories Annotations Code generators Converters Data Validators Documentation Domain-Specific Languages (DSLs) Gateways HTTP Clients IDEs and GUI Editors Learning Miscellaneous Mock Servers Monitoring OpenAPI-aware Frameworks Parsers Schema Validators SDK Generators Security Server Implementations Testing Text Editors © 2026 APIs You Won't Hate Get in touch to become a Sponsor . This site is community-driven and OSS , built with Astro and hosted on Netlify . All Tools Browse all OpenAPI tools that support modern OpenAPI. Showing 161 tools that support OpenAPI v3.1 or later. Looking for older tools? Check out the legacy collection . * * * | 2026-01-13T08:48:41 |
https://openapi.tools/categories/http-clients | HTTP Clients | OpenApi.tools, from APIs You Won't Hate Sponsored by Zudoku - Open-source, highly customizable API documentation powered by OpenAPI Get Started Sponsor openapi.tools GitHub Get Started All Tools All Categories Legacy Tools Contributing Sponsors Sponsor Badges Collections Arazzo Support Overlays Support Open Source Tools SaaS Tools OpenAPI Tool Categories Annotations Code generators Converters Data Validators Documentation Domain-Specific Languages (DSLs) Gateways HTTP Clients IDEs and GUI Editors Learning Miscellaneous Mock Servers Monitoring OpenAPI-aware Frameworks Parsers Schema Validators SDK Generators Security Server Implementations Testing Text Editors © 2026 APIs You Won't Hate Get in touch to become a Sponsor . This site is community-driven and OSS , built with Astro and hosted on Netlify . HTTP Clients Tools and libraries for making HTTP requests to APIs usually with a fancy GUI experience. HTTP Clients * * * | 2026-01-13T08:48:41 |
https://docs.sui.io/guides/developer/getting-started/connect#clone-hello-world | Hello, World! | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Hello, World! On this page Hello, World! You'll build a "Hello, World!" program to learn the fundamentals of programming on Sui. You create programs on Sui by writing and deploying smart contracts to the network. The most basic unit of storage on Sui is an object . Other blockchains typically structure storage using key-value stores. Sui centers storage around objects with unique ID addresses on-chain. Every Sui smart contract is an object that manipulates other objects. Objects can be immutable or mutable: Immutable objects cannot be transferred, changed, or deleted. No one owns them and anyone can access them publicly. Mutable objects can be transferred, changed, and deleted. A Sui address can own them, or they can be shared for public access. Every object's unique ID and version number references it on-chain. Every transaction on the network takes objects as input, then reads, writes, and mutates the inputs to produce new or altered objects as output. Every object knows the hash of the transaction that produced it. When an object is modified by a transaction, the transaction's output writes the object's mutated contents to the same object ID but with a new version number. Sui has limits on the maximum transaction size (128KB) and number of objects (2,048) used in a transaction. For more information on limits, see Building Against Limits in The Move Book. What is Move? Move is the programming language Sui uses to create smart contracts. It is platform agnostic and enables common libraries, tooling, and developer communities across blockchains with vastly different data and execution models. There are three ways to use Move in the context of Sui: Move packages, Move modules, and Move objects. A Sui Move package is also referred to as a Move smart contract. It is a set of Move bytecode published to the Sui network. It is immutable and cannot be changed or removed, however you can upgrade it. Upgrading creates a new version of the package object on-chain, leaving the original intact. All prior versions of a package still exist on-chain. Once you publish it, other packages can import and use the modules it provides. Anyone can view a package's contents and use a Sui Explorer to see how its logic manipulates other objects. Every Move package on Sui includes one or more Sui Move modules that define the package's interaction with on-chain objects. A module's name is always unique within the package that contains it. A Sui Move module governs a Sui Move object , which is typed data from a Sui Move package. Each Move object value is a struct with fields that can contain primitive types, such as integers and addresses, other objects, and non-object structs. Clone "Hello, World!" Prerequisites Install the latest version of Sui . Configure the Sui client . Create a Sui address . Get SUI Testnet tokens . Download and install an IDE. The following are recommended, as they offer Move extensions: VSCode , corresponding Move extension Emacs , corresponding Move extension Vim , corresponding Move extension Zed , corresponding Move extension Alternatively, you can use the Move web IDE , which does not require a download. It does not support all functions necessary for this guide, however. Download and install Git . To demonstrate creating objects, packages, and how to build your first Sui application, start by cloning the "Hello, World!" example: $ git clone \ https://github.com/MystenLabs/sui-stack-hello-world.git $ cd sui-stack-hello-world/move/hello-world In this project, there are two important files that define the package's logic, information, and its dependencies: move/hello-world/sources/greeting.move : Defines the package's logic. In this example, it defines a basic shared greeting object and public functions to interact with it. move/hello-world/Move.toml : The package's configuration file that defines the package name, dependencies, and addresses. Click to open move/hello-world/Move.toml File not found in manifest: move/hello-world/Move.toml . You probably need to run `pnpm prebuild` and restart the site. View the smart contract code Open the greeting.move file in your IDE of choice. You can see the following Move code: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Code explanation First, this code defines a module called greeting : module hello_world :: greeting { use std :: string ; ... } Then, it defines a public struct called Greeting that contains a unique object ID and text. A struct is a type of resource : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Then, it defines the function new that makes an API call to the Greeting struct and initializes it with the text "Hello world!" , storing it in a new shared object: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Lastly, the package defines a function called update_text that can be called to update the text stored in Greeting : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Resource safety A unique aspect of programming applications on Sui is the resource safety enforced by the Move Bytecode Verifier. Move packages must satisfy the following resource safety parameters: All resources must be either moved into global storage or destroyed by the end of a transaction. Resources cannot be copied. In the "Hello, World!" example, the struct Greeting is a resource type. To satisfy the requirement that all resources must be moved or destroyed by the end of a transaction, Greeting is assigned to new_greeting , which the call to transfer::share_object(new_greeting) then moves into global storage. To mutate Greeting , the function update_text takes the input (&mut Greeting) rather than the resource itself. This function satisfies resource safety as the function does not copy the resource and mutates it via a reference. Learn more about the Move Bytecode Verifier. How does this differ from EVM applications? The Ethereum Virtual Machine adopts a gas-based resource safety strategy. Every opcode on an EVM chain has an associated gas price that makes transactions costly, preventing the network from running a single transaction indefinitely. Build the Move package Before you can publish a Move package to the network, you must first build it. Building your package is necessary because the .move source file is a human-readable piece of code, while the network can only understand bytecode. To build your "Hello, World!" package, first confirm your working directory is ~/sui-stack-hello-world/move/hello-world , then run the following command: $ sui move build The build process fetches and compiles the dependencies defined in the Move.toml file. The Move compiler checks your .move code for type errors, syntax errors, and enforces resource safety , then translates your .move code into bytecode that Sui can execute. info You must build your package before you can publish it, but also before you test it. You cannot run tests ( sui move test ) on your code until it has been built. Publish the Move package Now that your package has been built, you need to publish it. After you publish it, other packages and users can use the package's modules and functions by making calls to the package ID. First, confirm your client is configured to use Testnet as the active environment: $ sui client active-env This should return testnet . If it does not return testnet , follow the client configuration instructions before continuing. Then, check your balance of SUI tokens to confirm you have enough to publish to Testnet: $ sui client balance You should have a balance of SUI tokens: ╭────────────────────────────────────────────╮ │ Balance of coins owned by this address │ ├────────────────────────────────────────────┤ │ ╭────────────────────────────────────────╮ │ │ │ coin balance (raw) balance │ │ │ ├────────────────────────────────────────┤ │ │ │ Sui 56804696124 0.50 SUI │ │ │ ╰────────────────────────────────────────╯ │ ╰────────────────────────────────────────────╯ If you do not have a balance, follow the SUI faucet instructions . Now, publish the package to Testnet with the command: $ sui client publish Click to open Output Transaction Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Data │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Owner: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Budget: 9843200 MIST │ │ Gas Price: 1000 MIST │ │ Gas Payment: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Version: 591332925 │ │ │ Digest: FLC4NXntT7WiHcqCkpDuBUq14DFTfi3EFeUiJcSNHdPu │ │ └── │ │ │ │ Transaction Kind: Programmable │ │ ╭─────────────────────────────────────────────────────────────────────────────────── ───────────────────────╮ │ │ │ Input Objects │ │ │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Pure Arg: Type: address, Value: "0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803" │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │ │ ╭─────────────────────────────────────────────────────────────────────────╮ │ │ │ Commands │ │ │ ├─────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Publish: │ │ │ │ ┌ │ │ │ │ │ Dependencies: │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │ │ │ └ │ │ │ │ │ │ │ │ 1 TransferObjects: │ │ │ │ ┌ │ │ │ │ │ Arguments: │ │ │ │ │ Result 0 │ │ │ │ │ Address: Input 0 │ │ │ │ └ │ │ │ ╰─────────────────────────────────────────────────────────────────────────╯ │ │ │ │ Signatures: │ │ mUxqMIofPq+yIzPxxYM+2mSIPTFneDxhWGGxJ7tM02hnRBRy5/FosnnWKxd4OSAjmaw6FNylwVdqUoUlJSxWCQ== │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ ┌── │ │ │ ID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Owner: Immutable │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Object: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Cost Summary: │ │ Storage Cost: 7843200 MIST │ │ Computation Cost: 1000000 MIST │ │ Storage Rebate: 978120 MIST │ │ Non-refundable Storage Fee: 9880 MIST │ │ │ │ Transaction Dependencies: │ │ 2dkJtqsoQcyCZJvjZnskNVPQeynwVtwCcA9goAru6tTi │ │ 7PStztXyh92keJmrDD1aghHaKVdgCoVkVx4ZmLUfmQeK │ │ Dd9pn1zFcSJjinxQewFd2gQdR4XKsHxFioD5MYnwLZQz │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭─────────────────────── ──────╮ │ No transaction block events │ ╰─────────────────────────────╯ ╭──────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Object Changes │ ├──────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created Objects: │ │ ┌── │ │ │ ObjectID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::package::UpgradeCap │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ObjectID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Balance Changes │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ ┌── │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ CoinType: 0x2::sui::SUI │ │ │ Amount: -7865080 │ │ └── │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ When you publish a Move package to the network, the network uploads and stores the bytecode as a Move package with a unique package ID and version number. The network consumes SUI tokens as gas and processes the transaction on-chain. After successfully executing, the output provides details about the transaction used to publish the package, including the gas cost, transaction digest, dependencies, owner, and sender. For this guide, the most important section is Published Objects , which includes the package's ID, version, and its modules: │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── Both the package ID and module are required to interact with the package from the command line. Take note of both values for future use in the Connecting a Frontend guide. Interact with the Move package Interact with the newly published package by first making a call to the new function that creates a new Greeting object and initialize it with the text "Hello world!" : $ sui client call --package <PACKAGE_ID> --module greeting --function new Replace <PACKAGE_ID> with the package ID the output of the sui client publish command returned. You must include the --package , --module , and --function flags. The output of this call includes a newly created object: ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ Owner: Shared( 591332927 ) │ │ │ Version: 591332927 │ │ │ Digest: 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ └── ... To verify that the object contains the text "Hello world!" , make a call to query the object's information: $ sui client object <OBJECT_ID> Replace <OBJECT_ID> with the value under Created Objects, ID: . You should see the object's details, including a value of text: Hello world! : ╭───────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ objectId │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ version │ 591332927 │ │ digest │ 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ objType │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ owner │ ╭────────┬──────────────────────────────────────────╮ │ │ │ │ Shared │ ╭────────────────────────┬─────────────╮ │ │ │ │ │ │ │ initial_shared_version │ 591332927 │ │ │ │ │ │ │ ╰────────────────────────┴─────────────╯ │ │ │ │ ╰────────┴──────────────────────────────────────────╯ │ │ prevTx │ 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ storageRebate │ 1413600 │ │ content │ ╭───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ dataType │ moveObject │ │ │ │ │ type │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ │ │ │ hasPublicTransfer │ false │ │ │ │ │ fields │ ╭──────┬───────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ id │ ╭────┬──────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ │ │ │ id │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ │ │ │ │ │ │ │ ╰────┴──────────────────────────────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ text │ Hello world! │ │ │ │ │ │ │ ╰──────┴───────────────────────────────────────────────────────────────────────────────╯ │ │ │ │ ╰───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────╯ │ ╰───────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Important transaction considerations You cannot send 2 or more transactions simultaneously, otherwise you encounter an error such as: Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. If you receive this error, you must wait until the current epoch is over before submitting your transaction again. You can see how long is left in the current epoch using Sui Explorer or another network explorer like SuiScan . To prevent the same object from being modified by multiple transactions at once, your address 'locks' the object to prevent conflicting modifications. If you'd like to batch multiple transaction commands together, you can use programmable transaction blocks . Transactions also have limitations regarding total size, number of objects, and number of inputs. Learn more about limitations in Building Against Limits in The Move Book. Next steps Create a Full Stack dApp Connect a frontend interface to your "Hello, World!" smart contract. Access Sui Data Learn more about accessing data on Sui. Join the Community Join the Sui developer community, try out other example projects, or read more documentation. Edit this page What is Move? Clone "Hello, World!" View the smart contract code Code explanation Resource safety Build the Move package Publish the Move package Interact with the Move package Important transaction considerations © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:41 |
https://legal.x.com/et/purchaser-terms.html | X-i teenuse Purchaser teenusetingimused X-i teenuse Purchaser teenusetingimused Laadige alla X-i teenuse Purchaser teenusetingimused Tasuliste teenuste tingimused X Premiumi lisatingimused Teenuse Subscriptions lisatingimused Laadige alla X-i teenuse Purchaser teenusetingimused X-i teenuse Purchaser teenusetingimused goglobalwithtwitterbanner Tasuliste teenuste tingimused X Premiumi lisatingimused Sisulooja tellimuste lisatingimused Premium Business ja Premium Organizations lisatingimused Tasuliste teenuste tingimused X Premiumi lisatingimused Sisulooja tellimuste lisatingimused Premium Business ja Premium Organizations lisatingimused X-i teenuse Purchaser teenusetingimused Kehtib alates: 1. augustist 2025 Kui elate väljaspool Euroopa Liitu, EFTA riike või Ühendkuningriiki, sealhulgas kui elate Ameerika Ühendriikides, kehtivad teile järgmised X ostja teenusetingimused . Kui elate Euroopa Liidus, EFTA riikides või Ühendkuningriigis, kehtivad teile need X-i teenuse Purchaser teenusetingimused . X-i teenuse Purchaser teenusetingimused Kui te elate väljaspool Euroopa Liitu, EFTA riike või Ühendkuningriiki, näiteks Ameerika Ühendriikides X võimaldab teil pääseda juurde teatud funktsioonidele ühekordse või korduva tasu eest vastavalt asjakohastele funktsioonidele (eraldi „ tasuline teenus ” ja ühiselt " tasulised teenused "). Näiteks teenust X Premium (nagu on määratletud allpool) ja Subscriptions loetakse „tasuliseks teenuseks“. Kui registreerute tasulise teenuse kasutajaks ja/või kasutate seda, kehtivad teie tasuliste teenuste kasutamise ja vastavate tehingute suhtes: i) siin sätestatud tingimused, sealhulgas iga teie ostetud tasulise teenuse jaoks kohaldatavad tingimused, millest igaüks on loetletud allpool (ühiselt X-i teenuse Purchaser teenusetingimused ) ja ii) kohaldatavad X-i teenusetingimused , X-i privaatsuspoliitika , X-i reeglid ja eeskirjad ning kõik sellesse lisatud eeskirjad (ühiselt X-i kasutajaleping ). Käesolevaid X ostja teenusetingimusi ja ülalnimetatud X kasutajalepingut nimetatakse selles dokumendis ühiselt " tingimusteks ". „ X ” viitab X-üksusele, mis pakub teile tasulisi teenuseid. Palun lugege need X ostja teenusetingimused hoolikalt läbi, et mõistaksite kindlasti kohaldatavaid tingimusi ja erandeid. KUI ELATE AMEERIKA ÜHENDRIIKIDES, SISALDAVAD NEED TINGIMUSED OLULIST TEAVET, MIS KEHTIB TEILE SEOS VAIDLUSTE LAHENDAMISEGA, SEALHULGAS LOOBUMIST TEIE ÕIGUSEST ESITADA NÕUDEID ÜHISHAGIDENA JA PIIRANGUT TEIE ÕIGUSELE ESITADA NÕUDEID X-I VASTU ROHKEM KUI 2 AASTAT PÄRAST VASTAVATE SÜNDMUSTE TOIMUMIST, MIS MÕJUTAVAD TEIE ÕIGUSI JA KOHUSTUSI JUHUL, KUI TEIL TEKIB VAIDLUS X-IGA. NENDE SÄTETE ÜKSIKASJU VT LÕIGUST 6 PEALKIRJAGA ÜLDTINGIMUSED. Vastuvõtmine . Kasutades või avades X-i tasulisi teenuseid, esitades selle alusel makseid ja/või klõpsates nupul ühekordse ostu sooritamiseks või korduvate tellimusmaksete tegemiseks X-i pakutava tasulise teenuse eest, nõustute nende tingimustega. Kui te ei saa tingimustest aru või ei nõustu mõne nende osaga, ei tohi te tasulisi teenuseid kasutada ega avada. Tasulise teenuse ostmiseks ja kasutamiseks peate: i) olema vähemalt 18-aastane või täisealine vastavalt teie elukoha jurisdiktsiooni seadustele või ii) peab teil olema teie vanema või eestkostja selgesõnaline nõusolek selle tasulise teenuse ostmiseks ning kasutamiseks. Kui te olete lapsevanem või seaduslik eestkostja ja te lubate oma lapsel (või lapsel, kelle eestkostja te olete) tasulist teenust osta või kasutada, nõustute, et tingimused kehtivad teile, te järgite neid ja vastutate lapse tegevuse eest tasulistes teenustes, ning selle tagamiseks järgib tingimusi ka laps. Igal juhul, nagu on märgitud X-i teenusetingimuste lõigus „Kes võivad teenuseid kasutada”, peate X-i kasutamiseks olema vähemalt 13-aastane. Kui nõustute nende X-i teenuse Purchaser teenusetingimustega ja kasutate tasulisi teenuseid ettevõtte, organisatsiooni, valitsuse või muu juriidilise isiku nimel, kinnitate ja garanteerite, et teil on selleks volitus ja teil on õigus see juriidiline isik siduda nende X-i teenuse Purchaser teenusetingimustega; sel juhul tähendavad sõnad „teie“ ja „te“ käesolevates X-i teenuse Purchaser teenusetingimustes seda juriidilist isikut. X-i tellija . Sõlmite need X ostja teenusetingimused juriidilise isikuga, mis vastab teie elukohale, nagu on loetletud allpool. See üksus pakub teile tasulisi teenuseid. Ükski teine üksus ei ole seotud nende ostja teenusetingimuste alusel teie ees võetud kohustustega. Teie asukoht Põhja-Ameerika (sh Hawaii) või Lõuna-Ameerika mandrid Tellija X Corp., mille kontor asub aadressil 865 FM 1209, Building 2, Bastrop, TX 78602, USA Teie asukoht Kõik riigid, mis ei kuulu ülalnimetatud kahe asukoha alla, sealhulgas Aasia ja Vaikse ookeani piirkond, Lähis-Ida, Aafrika või Euroopa (välja arvatud EL-i riigid, EFTA riigid ja Ühendkuningriik) Tellija X Global LLC, mille registrijärgne asukoht on 701 S. Carson St., Suite 200, Carson City, NV 89701, USA Tingimuste, tasuliste teenuste ja hindade muudatused 1. Tingimuste muudatused. X võib neid X ostja teenusetingimusi aeg-ajalt muuta, sealhulgas mis tahes ärilistel, rahalistel või juriidilistel põhjustel. Muudatused ei ole tagasiulatuvad ja uusim versioon X-i teenuse Purchaser teenusetingimustest, mis on saadaval aadressil legal.x.com/purchaser-terms , reguleerib tasuliste teenuste kasutamist ja mis tahes vastavaid tehinguid. Kui me muudame või parandame neid tingimusi pärast seda, kui olete nendega nõustunud (näiteks siis, kui neid tingimusi muudetakse pärast tellimuse ostmist), teavitame teid eelnevalt nende tingimuste olulistest muudatustest. Sellise teatise võib esitada elektrooniliselt, sealhulgas (ja ilma piiranguteta) teenuseteatise või meili teel teie kontoga seotud e-posti aadressile. Kui jätkate tasuliste teenuste avamist või kasutamist pärast nende muudatuste jõustumist, nõustute järgima muudetud X-i teenuse Purchaser teenusetingimusi. Kui te ei nõustu neid või mis tahes tulevasi X-i teenuse Purchaser teenusetingimusi järgima, ärge kasutage ega avage tasulisi teenuseid (või jätkake nende kasutamist või avamist). X-i teenuse Purchaser teenusetingimused on kirjutatud inglise keeles, kuid tõlgete kaudu on need saadaval mitmes keeles. X püüab teha tõlked võimalikult täpselt vastavaks ingliskeelsele originaalversioonile. Mis tahes erinevuste või ebakõlade korral on siiski ülimuslik ingliskeelne versioon X-i teenuse Purchaser teenusetingimustest. Nõustute, et X-i teenuse Purchaser teenusetingimuste tõlgendamisel ja koostamisel kasutatakse inglise keelt. 2. Tasuliste teenuste muudatused. Meie tasulised teenused arenevad pidevalt. Seetõttu võivad tasulised teenused aeg-ajalt meie äranägemise järgi muutuda, sealhulgas mis tahes ärilistel, rahalistel või juriidilistel põhjustel. Me võime lõpetada (püsivalt või ajutiselt) tasuliste teenuste või tasuliste teenuste mis tahes funktsioonide pakkumise teile või kasutajatele üldiselt etteteatamisega või ette teatamata. X ei vastuta teie ega ühegi kolmanda osapoole ees tasuliste teenuste muutmise, peatamise või katkestamise eest. Konkreetse tasulise teenuse konkreetsed tingimused (lisatud allpool) täpsustavad, kuidas saate tellimuse tühistada või vajaduse korral raha tagasi taotleda. 3. Hinnakujunduse muudatused. Tasuliste teenuste hinnad, sealhulgas korduvad liitumistasud, võivad aeg-ajalt muutuda, sealhulgas mis tahes ärilistel, rahalistel või juriidilistel põhjustel. X teavitab mõistlikult ette kõigist muutustest tasuliste teenuste hindades. Tellimusteenuste puhul jõustuvad hinnamuudatused järgmise hinnamuudatuse kuupäevale järgneva tellimisperioodi alguses. Kui te hinnamuudatusega ei nõustu, on teil õigus muudatus tagasi lükata, tühistades enne hinnamuudatuse jõustumist kehtiva tasulise teenuse tellimus. Maksetingimused . X pakub erinevaid maksevõimalusi, mis võivad erineda olenevalt tasulisest teenusest, teie seadmest ja/või operatsioonisüsteemist, teie geograafilisest asukohast või muudest teguritest. Võimaluse piires (kuna X võib aeg-ajalt pakkuda erinevaid ostumeetodeid) võivad need maksevõimalused hõlmata võimalust kasutada Google’i või Apple’i pakutavat rakendusesisese makse funktsiooni või teha veebimakset, kasutades X-i kolmanda osapoole maksete töötlejat Stripe ( www.stripe.com – edaspidi Stripe ). Makse sooritamisel nõustute selgesõnaliselt: i) tasuma tasulise teenuse eest loetletud hinna koos täiendavate summadega, mis on seotud kohaldatavate maksude, krediitkaarditasude, pangatasude, välistehingute tasude, valuutavahetustasude ja valuutakõikumistega; ja ii) järgima kõiki asjakohaseid teenusetingimusi, privaatsuspoliitikaid või muid juriidilisi lepinguid või piiranguid (sealhulgas täiendavaid vanusepiiranguid), mille on kehtestanud Google, Apple või Stripe (X-i kolmandast osapoolest maksete töötlejana) seoses teatud makseviisi kasutamisega (näiteks ainult juhul, kui otsustate teha makse Apple’i rakendusesisese ostufunktsiooni kaudu, nõustute järgima kõiki Apple’i kehtestatud asjakohaseid tingimusi, nõudeid ja/või piiranguid). Kõiki privaatseid isikuandmeid, mille esitate seoses tasuliste teenuste kasutamisega, sealhulgas, kuid mitte ainult, maksega seoses esitatud andmed, töödeldakse kooskõlas X-i privaatsuspoliitikaga. X võib teie makseteavet maksete töötlemiseks jagada makseteenuste pakkujatega, et ennetada, avastada ja uurida pettusi või muid keelatud tegevusi, hõlbustada vaidluste lahendamist, näiteks tagasinõuded või -maksed, ja muudel krediit- ja deebetkaartide või ACH aktsepteerimisega seotud eesmärkidel. Teie kohustus on tagada, et teie panga-, krediitkaardi, deebetkaardi ja/või muu makseteave oleks alati ajakohane, täielik ning täpne. Kui maksate tasulise teenuse eest, võime saada teie tehingu kohta sellist teavet, nagu näiteks millal see tehti, millal on tellimus määratud aeguma või automaatselt uuenema, millisel platvormil ostu sooritasite ja muud teavet. X ei vastuta maksete töötleja, Apple’i App Store’i või Google Play poe, teie panga, krediitkaardiettevõtte ja/või mis tahes maksevõrgu tehtud vigade või viivituste eest. Vaadake allpool iga konkreetse tasulise teenuse tingimusi, et näha selle konkreetse tasulise teenuse suhtes kohaldatavaid maksetingimusi, sealhulgas seda, kuidas tellimuste uuendamist käsitletakse, ja muid olulisi tingimusi. X-i kasutajalepingu rakendamine, lõpetamine, tagasimaksete puudumine, mitu X-i kontot ja piirangud 1. Teie suhtes kehtib X-i kasutajaleping. TE OLETE KOHUSTATUD ALATI JÄRGIMA JA TÄITMA X-I KASUTAJALEPINGUT. X-I teenuse, sealhulgas tasuliste teenuste ja funktsioonide kasutamisel kehtib alati X-i kasutajaleping. Kui te ei järgi ega täida X-i kasutajalepingut või kui X on veendunud, et te pole X-i kasutajalepingut järginud ega täitnud, võidakse teie tasulised teenused tühistada. Iga selline tühistamine täiendab (ja on piiranguteta) mis tahes jõustamismeetmeid, mida X võib teie vastu võtta X-i kasutajalepingu alusel. Sellistel juhtudel võite kaotada oma tasuliste teenuste hüved ja teil ei ole õigust saada tasuliste teenuste eest makstud (või ettemakstud) summade eest tagasimakset. 2. Miks võib X teie juurdepääsu tasulistele teenustele lõpetada. X võib peatada või lõpetada teie juurdepääsu tasulis(t)ele teenus(t)ele või lõpetada teile täielikult või osaliselt tasuliste teenuste osutamise või võtta asjakohaseks peetavaid meetmeid, sealhulgas näiteks teie konto peatamine (ilma vastutuseta) igal ajal või põhjuseta, sealhulgas järgmistel põhjustel. a. X leiab omal äranägemisel, et te olete tingimusi rikkunud või teie tasuliste teenuste kasutamine rikub kohaldatavaid seadusi. b. X-ilt on palunud või nõudnud seda pädev kohus, reguleeriv asutus või õiguskaitseasutus. c. X-il esineb ootamatuid tehnilisi või turvaprobleeme. d. X usub oma ainuisikulise äranägemise järgi, et olete rikkunud X-i Kasutajalepingut; e. X usub oma ainuisikulise äranägemise järgi, et tegelete manipuleerimise või muu häiriva või keelatud käitumisega üldiselt või seoses tasuliste teenustega; f. Tekitate riski või võimaliku õigusliku kokkupuute X-i suhtes; g. Teie konto tuleks ebaseadusliku tegevuse tõttu eemaldada. h. Teie konto tuleks pikaajalise tegevusetuse tõttu eemaldada. i. Meie tasuliste teenuste pakkumine (täielikult või osaliselt) teile ei ole enam äriliselt tasuv (X-i äranägemisel). 3. Kõik tehingud on lõplikud. Kõik tasuliste teenuste eest tehtud maksed on lõplikud ning neid ei saa tagastada ega vahetada, välja arvatud juhul, kui see on nõutud kohaldatava seadusega. Me ei anna mingit garantiid tasulise teenuse olemuse, kvaliteedi või väärtuse või selle kättesaadavuse või pakkumise kohta. Ühegi kasutamata või osaliselt kasutatud tasulise teenuse (näiteks osaliselt kasutatud tellimisperioodi) eest ei anta raha tagasi ega krediiti. 4. Tasulisi teenuseid ei saa X-i kontode vahel üle kanda. Iga tasulise teenuse ost kehtib ühele X-i kontole, mis tähendab, et teie ost kehtib ainult kontole, mida kasutasite tasulise teenuse ostmise ajal, ega kehti muudele kontodele, millele teil võib olla juurdepääs või mille üle teil võib olla kontroll. Kui teil on mitu kontot või teil on kontroll mitme konto üle ja soovite iga kontoga juurdepääsu tasulistele teenustele, peate ostma tasulise teenuse igal kontol eraldi. 5. Piirangud ja kohustused. a. Teil on lubatud tasulist teenust osta ja kasutada ainult siis, kui teil on seaduslikult lubatud tasulist teenust oma riigis kasutada ja te elate riigis, mida X toetab kohaldatava tasulise teenuse jaoks. X võib teatud riikides oma äranägemise järgi piirata juurdepääsu tasulisele teenusele või selle ostmise võimalust. X jätab endale õiguse toetatud riikide loendit aeg-ajalt muuta. b. Jätame endale õiguse keelduda tasuliste teenuste tehingutest või tühistada või lõpetada tasulise teenuse müük või kasutamine oma äranägemise järgi. c. Te ei tohi lubada teisel isikul kasutada teie X-i kontot, et pääseda juurde tasulistele teenustele, mida ta pole tellinud. d. Te ei tohi tasulist teenust osta ega kasutada, kui olete isik, kellega USA kodanikel ei ole lubatud tehinguid teha majanduslike sanktsioonide alusel, sealhulgas sanktsioonid, mida haldab Ameerika Ühendriikide rahandusministeeriumi välismaiste varade kontrolli amet või muu kohaldatavate sanktsioonide amet (" keelatud isik "). See hõlmab muuhulgas, kuid mitte ainult, isikuid, kes asuvad või elavad tavaliselt järgmistes riikides ja piirkondades: Kuuba, Iraan, Ukrainas Krimmi piirkonnas, Põhja-Koreas või Süürias. Te avaldate ja kinnitate, et te ei ole keelatud isik. e. TE KINNITATE, ET KASUTATE TASULISI TEENUSEID AINULT SEADUSLIKEL EESMÄRKIDEL JA AINULT TINGIMUSTEGA KOOSKÕLAS. Maksud ja tasud . Teie olete vastutav ja nõustute maksma kõik tasuliste teenuste ostmisega seotud kohaldatavad maksud, lõivud, tariifid ja tasud, sealhulgas need, mis tuleb tasuda kas X-ile või kolmandast osapoolest maksete töötlejale. Need maksud võivad hõlmata, kuid mitte ainult, käibemaksu, üldist müügimaksu, müügimaksu, kinnipeetavat maksu ja mis tahes muid kohaldatavaid makse. Olenevalt teie asukohast võib X vastutada teie tasuliste teenuste ostmisel tekkivate tehingumaksudega seotud teabe kogumise ja aruandluse eest. Te annate X-ile loa edastada oma konto- ja isikuandmed asjakohastele maksuametitele, et saaksime täita maksukogumis- ja aruandluskohustusi. Üldtingimused 1. Kontaktteave. Kui teil on tasuliste teenuste või nende tingimuste kohta küsimusi, vaadake lisateabe saamiseks X tasuliste teenuste abikeskust . Kui olete juba tasulise teenuse ostnud, saate meiega ühendust võtta ka tugilingi kaudu, mis on saadaval teie X-i konto navigeerimismenüüs makse- või liitumisseadete all. Kui teil on lisaküsimusi, võite võtta meiega ühendust siin , kasutades vormi „Abi tasuliste funktsioonidega”. 2. LOOBUMISKLAUSEL. KOHALDATAVATE SEADUSTEGA LUBATUD MAKSIMAALSEL MÄÄRAL ON TEIE JUURDEPÄÄS TASULISTELE TEENUSTELE JA NENDE KASUTAMINE TEIE ENDA VASTUTUSEL. TE MÕISTATE JA NÕUSTUTE, ET TASULISI TEENUSEID PAKUTAKSE TEILE SELLISENA, NAGU NAD ON, JA SAADAVUSE ALUSEL. X ÜTLEB LAHTI KÕIKVÕIMALIKEST SÕNASELGETEST VÕI KAUDSETEST GARANTIIDEST JA TINGIMUSTEST, SH KAUBASTATAVUS, KONKREETSEKS OTSTARBEKS SOBIVUS VÕI ÕIGUSTE MITTERIKKUMINE. X EI ANNA GARANTIID EGA LUBADUST NING LOOBUB IGASUGUSEST VASTUTUSEST: I) TASULISTE TEENUSTE TÄIELIKKUSE, TÄPSUSE, KÄTTESAADAVUSE, AJAKOHASUSE, TURVALISUSE VÕI USALDUSVÄÄRSUSE; JA II) SELLE OSAS, KAS TASULISED TEENUSED VASTAVAD TEIE NÕUETELE VÕI ON SAADAVAL KATKEMATULT, TURVALISELT VÕI VIGADETA. VASTUTATE X-I TEENUSE KASUTAMISE, SH TASULISTE TEENUSTE, JA MIS TAHES TEIE PAKUTAVA SISU EEST. 3. VASTUTUSE PIIRAMINE. KOHALDATAVATE SEADUSTEGA LUBATUD MAKSIMAALSEL MÄÄRAL EI VASTUTA X-I ISIKUD MIS TAHES KAUDSETE, JUHUSLIKE, ERAKORDSETE, TULENEVATE VÕI KARISTUSLIKE KAHJUDE EGA KASUMI VÕI TULU OTSESE VÕI KAUDSE VÄHENEMISE EGA MIS TAHES ANDMETE KADUMISE, KASUTUSE, FIRMAVÄÄRTUSE VÕI MUUDE IMMATERIAALSETE KAHJUDE EEST, MIS TULENEVAD i) TEIE JUURDEPÄÄSUST TASULISTELE TEENUSTELE, NENDE KASUTAMISEST VÕI JUURDEPÄÄSU PUUDUMISEST TASULISTELE TEENUSTELE VÕI NENDE KASUTUSVÕIMALUSE PUUDUMISEST; ii) MIS TAHES KOLMANDATE OSAPOOLTE TEGEVUSEST VÕI SISUST, MIS ON POSTITATUD TASULISTE TEENUSTE KAUDU, SEALHULGAS, KUID MITTE ÜKSNES, MIS TAHES LAIMAV, SOLVAV VÕI ILLEGAALNE TEGEVUS TEISTE KASUTAJATE VÕI KOLMANDATE OSAPOOLTE SUHTES; iii) MIS TAHES TASULISTE TEENUSTE KAUDU SAADUD SISUST; VÕI iv) VOLITAMATA JUURDEPÄÄSUST TEIE EDASTUSTELE VÕI SISULE VÕI NENDE VOLITAMATA KASUTAMISEST VÕI MUUTMISEST. KAHTLUSTE VÄLTIMISEKS ON TASULISTE TEENUSTE MÄÄRATLUS PIIRATUD X-I PAKUTUD FUNKTSIOONIDEGA NING EI SISALDA MUUD SISU, MILLELE TEIL ON JUURDEPÄÄS VÕI MILLEGA SUHTLETE NENDE FUNKTSIOONIDE KASUTAMISE KÄIGUS. X-I ISIKUTE KOGUVASTUTUS EI ÜLETA MINGIL JUHUL SADAT USA DOLLARIT (USD 100,00 $) EGA SUMMAT, MILLE OLETE MEILE NÕUDE ALUSEKS OLEVATE TEENUSTE EEST MAKSNUD VIIMASE KUUE KUU JOOKSUL. SELLE LÕIGU PIIRANGUD KOHALDUVAD IGAT LIIKI VASTUTUSELE – GARANTIIVASTUTUSELE, LEPINGULISELE VASTUTUSELE, KOHUSTUSLIKULE VASTUTUSELE, LEPINGUVÄLISELE (SH HOOLETUSEST TULENEVALE) VASTUTUSELE JA MUULE VASTUTUSELE – VAATAMATA SELLELE, KAS X-I ISIKUID ON ASJAOMASE KAHJU VÕIMALIKKUSEST TEAVITATUD NING ISEGI JUHUL, KUI KÄESOLEVAS ETTENÄHTUD HEASTAMISVIIS LEITAKSE OLEVAT SISULISELT EBAPIISAV. „X-I ISIKUD” VIITAVAD X-ILE, SELLE EMAETTEVÕTETELE, SIDUSETTEVÕTETELE, SEOTUD ETTEVÕTETELE, AMETNIKELE, DIREKTORITELE, TÖÖTAJATELE, AGENTIDELE, ESINDAJATELE, PARTNERITELE JA LITSENTSIANDJATELE. TEIE JURISDIKTSIOONIS KEHTIVATE SEADUSTE KOHASELT EI PRUUGI TEATUD VASTUTUSE PIIRMÄÄRAD OLLA LUBATUD. TEIE JURISDIKTSIOONIS KEHTIVATE SEADUSTEGA NÕUTAVAS ULATUSES EI PIIRA ÜLALTOODU X-I ISIKUTE VASTUTUST PETTUSTE, KURITAHTLIKE VÄÄRESITUSTE, SURMA VÕI ISIKUKAHJU KORRAL, MIDA ON PÕHJUSTANUD MEIE HOOLETUS, RASKE ETTEVAATAMATUS JA/VÕI TAHTLIK TEGUVIIS. X-I ISIKUTE MAKSIMAALNE KOGUVASTUTUS KÕIGI VÄLISTAMATUTE GARANTIIDE KORRAL ON SUURIMAL VÕIMALIKUL MÄÄRAL, MIDA VÕIMALDAVAD KEHTIVAD SEADUSED, PIIRATUD SAJA USA DOLLARIGA (100,00 USA DOLLARIT). 4. Märkus Apple’i kohta. Selles ulatuses, milles ostsite tasulisi teenuseid või kasutate tasulisi teenuseid või pääsete neile juurde iOS-i seadme kaudu, nõustute lisaks selle jaotise tingimustega. Nõustute, et tingimused kehtivad ainult teie ja meie vahel, mitte Apple’iga, ning Apple ei vastuta tasuliste teenuste ja nende sisu eest. Apple’il ei ole mingit kohustust osutada tasuliste teenustega seotud hooldus- ja tugiteenuseid. Juhul, kui tasulised teenused ei vasta mis tahes kohaldatavale garantiile, võite sellest Apple’it teavitada ja Apple tagastab teile tasuliste teenuste eest kohaldatava ostuhinna. Kohaldatava seadusega lubatud maksimaalses ulatuses ei ole Apple’il tasuliste teenuste osas mingeid muid garantiikohustusi. Apple ei vastuta teie või mis tahes kolmanda osapoole nõuete käsitlemise eest, mis on seotud tasuliste teenuste või tasuliste teenuste omamise ja/või kasutamisega, sealhulgas, kuid mitte ainult: i) tootevastutusnõuded; ii) mis tahes nõue, et tasulised teenused ei vasta ühelegi kohaldatavale juriidilisele või regulatiivsele nõudele; ja iii) nõuded, mis tulenevad tarbijakaitse või samalaadsetest õigusaktidest. Apple ei vastuta kolmandate osapoolte nende nõuete uurimise, kaitsmise, lahendamise ega rahuldamise eest, mille kohaselt tasulised teenused ja/või teie mobiilirakenduse omamine ja kasutamine rikuvad selle kolmanda osapoole intellektuaalomandi õigusi. Nõustute tasuliste teenuste kasutamisel järgima kõiki kohaldatavaid kolmanda osapoole tingimusi. Apple ja Apple’i tütarettevõtted on tingimuste kolmandast osapoolest kasusaajad. Kui te nõustute tingimustega, on Apple’il õigus (ja seda loetakse õigusega nõustumiseks) jõustada tingimusi teie kui tingimuste kolmandast osapoolest kasusaaja vastu. Käesolevaga avaldate ja kinnitate, et i) te ei asu riigis, mille suhtes kehtib USA valitsuse embargo või mille USA valitsus on määratlenud kui "terroriste toetav" riik; ja ii) te ei ole loetletud üheski USA valitsuse keelatud või piiratud isikute nimekirjas. 5. Vastuolu. Vastuolu korral käesolevate X-i teenuse Purchaser teenusetingimuste ja X-i kasutajalepingu sätete vahel on sätted nendes X-i teenuse Purchaser teenusetingimustes ülimuslikud ainult teie tasulise teenuse kasutamisel. 6. VAIDLUSTE LAHENDAMINE JA KLASSI MEETMETEST LOOBUMINE a. Esialgne vaidluste lahendamine . Enamikku teie ja X-i vahelisi vaidlusi saab lahendada mitteametlikult. Saate meiega ühendust võtta, kirjutades tasulistele tugiteenustele siin . Kui võtate meiega ühendust, kirjeldage lühidalt oma mure olemust ja põhjuseid, kontaktandmeid ja konkreetset abi, mida soovite. Pooled teevad selle tugiprotsessi kaudu kõik endast oleneva, et lahendada vaidlusi, nõudeid või vastuolusid, mis tulenevad käesolevatest tingimustest ja/või teie programmis osalemisest või on nendega seotud (eraldi " vaidlus" või rohkem kui üks, " vaidlused "). Teie ja meie nõustume, et selles mitteametlikus protsessis on nõutav heauskne osalemine ja see tuleb lõpule viia ülaltoodud viisil, enne kui kumbki pool saab algatada vaidlusega seotud kohtuvaidlusi, välja arvatud erakorralise ettekirjutuse taotluste puhul (" Vabastatud vaidlus "). Kui me ei jõua teiega vaidluses (välja arvatud vabastatud vaidlus) kokkulepitud lahendusele kolmekümne (30) päeva jooksul alates ajast, mil alustatakse vaidluste mitteametlikku lahendamist ülaltoodud vaidluse esmase lahendamise sätte alusel, siis võib teie või meie algatada kohtuvaidlus. b. Õiguse ja kohtualluvuse valik . LUGEGE SEDA LÕIKU HOOLIKALT – SEE VÕIB OLULISELT MÕJUTADA TEIE JURIIDILISI ÕIGUSI, SEALHULGAS TEIE ÕIGUST KOHTUSSE HAGI ESITADA. Neid tingimusi ja kõiki teie ja meie vahel tekkivaid vaidlusi reguleeritakse Texase osariigi seaduste alusel, välja arvatud õiguse valikut käsitlevad sätted, sõltumata muust teie ja meie vahel sõlmitud vastupidistest kokkulepetest. Kõik nende tingimustega seotud vaidlused, sealhulgas vaidlused, nõuded või vastuolud, mis tulenevad nendest tingimustest või on nendega seotud, esitatakse eranditult Ameerika Ühendriikides Texase osariigis Tarranti maakonnas asuvatesse föderaal- või osariigikohtutesse ning nõustute nende foorumite isikliku jurisdiktsiooniga ja loobute kõigist vastuväidetest ebasobiva foorumi kohta. Ilma et see piiraks eeltoodut, nõustute, et X võib oma äranägemise järgi esitada mis tahes nõude, hagi või vaidluse, mis meil teie vastu on, teie elukohariigi mis tahes pädevasse kohtusse, millel on nõude jurisdiktsioon ja koht. Kui olete Ameerika Ühendriikide föderaal-, osariigi- või kohaliku omavalitsuse üksus ja te ei saa juriidiliselt nõustuda ülaltoodud valitseva seaduse, jurisdiktsiooni või kohaklauslitega, siis need klauslid teie suhtes ei kehti. USA föderaalvalitsusasutuste puhul kohalduvad sellele lepingule ja sellega seotud kohtumenetlustele Ameerika Ühendriikide seadused (vaatamata kollisiooninormidele) ning juhul, kui föderaalõiguses puudub kohaldatav norm ja föderaalõigus seda lubab, Texase osariigi seadused (v.a õigusruumi valiku normid). c. TEIL ON X vastu nõude esitamiseks aega kaks aastat. Peate esitama X-i vastu kõik nõuded, mis tulenevad nendest tingimustest või on nendega seotud, kahe (2) aasta jooksul alates vaidluse aluseks oleva sündmuse või asjaolude toimumise kuupäevast, välja arvatud juhul, kui kohaldatav seadus näeb ette, et selle nõude tavapärast aegumistähtaega ei saa kokkuleppega lühendada. Kui te selle aja jooksul nõuet ei esita, loobute alatiseks sellistel sündmustel või faktidel põhineva igasuguse nõude või hagi aluse esitamise õigusest, ja sellised nõuded või hagi aluselt on jäädavalt keelatud, ning X-il pole selliste nõuete suhtes kohustusi. d. Ühishagist loobumine . Seadusega lubatud ulatuses loobute ka õigusest osaleda hageja või esindatavana ühishagis, kollektiivhagis või esindushagis. X-i teenuse Purchaser teenusetingimused Kui te elate Euroopa Liidus, EFTA riikides või Ühendkuningriigis X võimaldab teil pääseda juurde teatud funktsioonidele ühekordse või korduva tasu eest vastavalt asjakohastele funktsioonidele (eraldi „ tasuline teenus ” ja ühiselt " tasulised teenused "). Näiteks teenust X Premium (nagu on määratletud allpool) ja Subscriptions loetakse „tasuliseks teenuseks“. Kui registreerute tasulise teenuse kasutajaks ja/või kasutate seda, kehtivad teie tasuliste teenuste kasutamise ja vastavate tehingute suhtes: i) siin sätestatud tingimused, sealhulgas iga teie ostetud tasulise teenuse jaoks kohaldatavad tingimused, millest igaüks on loetletud allpool (ühiselt " X-i teenuse Purchaser teenusetingimused ") ja ii) kohaldatavad X-i teenusetingimused , X-i privaatsuspoliitika , X-i reeglid ja eeskirjad ning kõik sellesse lisatud eeskirjad (ühiselt " X-i kasutajaleping "). Käesolevaid X ostja teenusetingimusi ja ülalnimetatud X kasutajalepingut nimetatakse selles dokumendis ühiselt " tingimusteks ". „ X ” viitab X-üksusele, mis pakub teile tasulisi teenuseid. Lugege need X-i teenuse Purchaser teenusetingimused hoolikalt läbi veendumaks, et mõistate kohaldatavaid nõudeid, tingimusi ja erandeid. KUI TE ELATE EUROOPA LIIDUS, EFTA RIIKIDES VÕI ÜHENDKUNINGRIIGIS, SISALDAVAD NEED TINGIMUSED OLULIST TEAVET, MIS KEHTIVAD TEILE VAIDLUSTE LAHENDAMISE KOHTA, SEALHULGAS LOOBUMINE ÜHISHAGI ESITAMISE ÕIGUSEST NING PIIRANG TEIE ÕIGUSELE ESITADA HAGI X-I VASTU ENAM KUI ÜKS AASTA PÄRAST ASJAKOHASTE SÜNDMUSTE TOIMUMIST, MIS MÕJUTAVAD X-IGA VAIDLUSE KORRAL TEIE ÕIGUSI JA KOHUTUSI. NENDE SÄTETE ÜKSIKASJU VT LÕIGUST 6 PEALKIRJAGA ÜLDTINGIMUSED. Nõusolek . Kasutades või avades X-i tasulisi teenuseid, esitades selle alusel makseid ja/või klõpsates nupul ühekordse ostu sooritamiseks või korduvate tellimusmaksete tegemiseks X-i pakutava tasulise teenuse eest, nõustute nende tingimustega. Kui te ei saa tingimustest aru või ei nõustu mõne nende osaga, ei tohi te tasulisi teenuseid kasutada ega avada. Tasulise teenuse ostmiseks ja kasutamiseks peate: i) olema vähemalt 18-aastane või täisealine vastavalt teie elukoha jurisdiktsiooni seadustele või ii) peab teil olema teie vanema või eestkostja selgesõnaline nõusolek selle tasulise teenuse ostmiseks ning kasutamiseks. Kui te olete lapsevanem või seaduslik eestkostja ja te lubate oma lapsel (või lapsel, kelle eestkostja te olete) tasulist teenust osta või kasutada, nõustute, et tingimused kehtivad teile, te järgite neid ja vastutate lapse tegevuse eest tasulistes teenustes, ning selle tagamiseks järgib tingimusi ka laps. Igal juhul, nagu on märgitud X-i teenusetingimuste lõigus „Kes võivad teenuseid kasutada”, peate X-i kasutamiseks olema vähemalt 13-aastane. Kui nõustute nende X-i teenuse Purchaser teenusetingimustega ja kasutate tasulisi teenuseid ettevõtte, organisatsiooni, valitsuse või muu juriidilise isiku nimel, kinnitate ja garanteerite, et teil on selleks volitus ja teil on õigus see juriidiline isik siduda nende X-i teenuse Purchaser teenusetingimustega; sel juhul tähendavad sõnad „teie“ ja „te“ käesolevates X-i teenuse Purchaser teenusetingimustes seda juriidilist isikut. X-i tellija . Te sisenete nendesse X-i teenuse Purchaser teenusetingimustesse üksusega, mis vastab teie elukohale, nagu loetletud allpool. See üksus pakub teile tasulisi teenuseid. Ükski teine üksus ei ole seotud nende ostja teenusetingimuste alusel teie ees võetud kohustustega. Teie asukoht Euroopa Liit, EFTA riigid või Ühendkuningriik Tellija X Internet Unlimited Company, mille registrijärgne asukoht on One Cumberland Place, Fenian Street, Dublin 2, D02 AX07 Ireland Tingimuste, tasuliste teenuste ja hindade muudatused 1. Tingimuste muudatused. X võib neid X ostja teenusetingimusi aeg-ajalt kehtivatel ja mõistlikel alustel muuta. Kehtiv ja mõistlik alus võib hõlmata (i) meie teenuste muutumist, näiteks tehnilise, turvalisusega seotud või operatiivse arengu tõttu, (ii) tehniliste vigade kõrvaldamist, (iii) muutust meie äritegevuses, näiteks poliitika, finants- või muude suunamuutuste tõttu, (iv) õigusliku olukorra muutus, näiteks seaduse muutmise tõttu, ametliku asutuse taotlus või kohtu otsus, ja (v) kasutajakogemuse optimeerimine uute funktsioonide rakendamise kaudu. Muudatused ei ole tagasiulatuvad ja uusim versioon X-i teenuse Purchaser teenusetingimustest, mis on saadaval aadressil legal.x.com/purchaser-terms , reguleerib tasuliste teenuste kasutamist ja mis tahes vastavaid tehinguid. Kui muudame või täiustame neid tingimusi pärast seda, kui olete nendega nõustunud (näiteks kui neid tingimusi muudetakse pärast tellimuse ostmist), kohustume teid teavitama kuni 30 päeva ette (olenevalt konkreetsetest muudatustest) nende tingimuste oluliste muudatuste jõustumisest, määrates kasutajale muudatuste tegemiseks mõistliku tähtaja ning teavitades teid jätkuva kasutamise tagajärgedest pärast tähtaja möödumist. Sellise teatise võib esitada elektrooniliselt, sealhulgas (ja ilma piiranguteta) teenuseteatise või meili teel teie kontoga seotud e-posti aadressile. Juhul, kui jätkate tasuliste teenuste kasutamist pärast eelnimetatud tähtaja möödumist, nõustute järgima X ostja muudetud teenusetingimusi. Kui te ei nõustu X-i teenuse Purchaser teenusetingimuste muudatustega, peate lõpetama tasuliste teenuste kasutamise või neile juurdepääsu. X-i teenuse Purchaser teenusetingimused on kirjutatud inglise keeles, kuid tõlgete kaudu on need saadaval mitmes keeles. X püüab teha tõlked võimalikult täpselt vastavaks ingliskeelsele originaalversioonile. Mis tahes erinevuste või ebakõlade korral on siiski ülimuslik ingliskeelne versioon X-i teenuse Purchaser teenusetingimustest. Nõustute, et X-i teenuse Purchaser teenusetingimuste tõlgendamisel ja koostamisel kasutatakse inglise keelt. 2. Tasuliste teenuste muudatused. Meie tasulised teenused ning meie tooted ja teenused arenevad pidevalt. X võib tasulisi teenuseid mõistlikul ja kehtival alusel muuta. Selline kehtiv ja mõistlik alus võib hõlmata (i) tehnilisi, turvalisusega seotud või operatiivseid arenguid, (ii) tehniliste vigade kõrvaldamist, (iii) vastavust muutunud õiguslikule olukorrale, näiteks seadusemuudatuse, ametiasutuse taotluse või kohtu otsuse tõttu, (iv) kasutajakogemuse optimeerimist uute funktsioonide juurutamise kaudu, ja (v) muutus meie äritegevuses, näiteks poliitika, finantsolukorra või muude suunamuutuste tõttu. Teavitame teid tasuliste teenuste muudatustest kuni 30 päeva enne nende jõustumist, näiteks teenuseteate või teie kontoga seotud e-posti aadressile saadetud e-kirjaga, täpsustades muudatuste omadused ja jõustumiskuupäeva ning teavitades teid teie võimalikust õigusest tellimus lõpetada. Ohutusega seotud muudatuste korral võib tähtaega lühendada. Tasuliste teenuste muudatusteks käesoleva sätte tähenduses ei loeta: (i) muudatused, mis mõjutavad tasuliste teenuste põhiolemust ja X-i poolt osutatava teenuse põhiomadusi, ning (ii) teenuste alaline lõpetamine. X ei vastuta teie ees tasuliste teenuste muutmise, peatamise või katkestamise eest. Kui see on seadusega ette nähtud, ei kohaldata eespool nimetatud vastutuse piirangut (i) ettenähtava kahju hüvitamisele kohustuste kerge hooletuse tõttu, kui nende täitmine on oluline lepingu nõuetekohaseks täitmiseks ja kasutajad võivad olla kindlad, et X või tema seaduslikud esindajad või asendusesindajad täidavad need (olulised lepingulised kohustused); ja (ii) X-i vastutus (a) kahju, mis tuleneb kahjust elule, kehale või tervisele, samuti kahjude eest, mis on põhjustatud tahtlusest või raskest hooletusest X-i, tema seaduslike esindajate või asendusesindajate poolt, ja (b) kahju eest, mis on põhjustatud garantii või garanteeritud omaduse mittejärgimisest või pettuse teel varjatud puuduse tagajärjel. Konkreetse tasulise teenuse eritingimused (lisatud allpool) täpsustavad, kuidas saate tellimuse tühistada või vajaduse korral tagasimakset taotleda. 3. Hinnakujunduse muudatused. Tasuliste teenuste hinnad, sealhulgas korduvad liitumistasud, võivad seoses käitamise, hoolduse, tehnilise pakkumise, ärikaalutluste ning kolmandate osapoolte või seadusjärgsete tasude kulude muutumisega, meie mõistliku äranägemise järgi aeg-ajalt muutuda. Kulude suurenemise korral jätab X endale õiguse muuta tasuliste teenuste hindu. X teavitab teid kõigist hinnamuutustest kirjalikult kuni 30 päeva enne nende jõustumist, näiteks teenuseteate või e-kirjaga teie kontoga seotud e-posti aadressile, märkides ära teie õigused ja nende kasutamata jätmise tagajärjed. Hinnamuutuse korral võite vastava tasulise teenuse tellimuse või kasutajalepingu lõpetada kuni 24 tundi enne järgmise arveldustsükli algust, tingimusel et tühistamine toimub 30 päeva jooksul pärast teate saamist. Vastasel juhul jõustub hinnamuutus teavituses märgitud ajal. Tellimusteenuste puhul jõustuvad hinnamuudatused hinnamuudatuse jõustumise kuupäevale järgneva tellimisperioodi alguses. Maksetingimused . X pakub erinevaid maksevõimalusi, mis võivad erineda olenevalt tasulisest teenusest, teie seadmest ja/või operatsioonisüsteemist, teie geograafilisest asukohast või muudest teguritest. Võimaluse piires (kuna X võib aeg-ajalt pakkuda erinevaid ostumeetodeid) võivad need maksevõimalused hõlmata võimalust kasutada Google’i või Apple’i pakutavat rakendusesisese makse funktsiooni või teha veebimakset, kasutades X-i kolmanda osapoole maksete töötlejat Stripe ( www.stripe.com – edaspidi Stripe ). Makse sooritamisel nõustute selgesõnaliselt: i) tasuma tasulise teenuse eest loetletud hinna koos täiendavate summadega, mis on seotud kohaldatavate maksude, krediitkaarditasude, pangatasude, välistehingute tasude, valuutavahetustasude ja valuutakõikumistega; ja ii) järgima kõiki asjakohaseid teenusetingimusi, privaatsuspoliitikaid või muid juriidilisi lepinguid või piiranguid (sealhulgas täiendavaid vanusepiiranguid), mille on kehtestanud Google, Apple või Stripe (X-i kolmandast osapoolest maksete töötlejana) seoses teatud makseviisi kasutamisega (näiteks ainult juhul, kui otsustate teha makse Apple’i rakendusesisese ostufunktsiooni kaudu, nõustute järgima kõiki Apple’i kehtestatud asjakohaseid tingimusi, nõudeid ja/või piiranguid). Kõiki privaatseid isikuandmeid, mille esitate seoses tasuliste teenuste kasutamisega, sealhulgas, kuid mitte ainult, maksega seoses esitatud andmed, töödeldakse kooskõlas X-i privaatsuspoliitikaga. X võib teie makseteavet maksete töötlemiseks jagada makseteenuste pakkujatega, et ennetada, avastada ja uurida pettusi või muid keelatud tegevusi, hõlbustada vaidluste lahendamist, näiteks tagasinõuded või -maksed, ja muudel krediit- ja deebetkaartide või ACH aktsepteerimisega seotud eesmärkidel. Teie kohustus on tagada, et teie panga-, krediitkaardi, deebetkaardi ja/või muu makseteave oleks alati ajakohane, täielik ning täpne. Kui maksate tasulise teenuse eest, võime saada teie tehingu kohta sellist teavet, nagu näiteks millal see tehti, millal on tellimus määratud aeguma või automaatselt uuenema, millisel platvormil ostu sooritasite ja muud teavet. X ei vastuta maksete töötleja, Apple’i App Store’i või Google Play poe, teie panga, krediitkaardiettevõtte ja/või mis tahes maksevõrgu tehtud vigade või viivituste eest. Vaadake allpool iga konkreetse tasulise teenuse tingimusi, et näha selle konkreetse tasulise teenuse suhtes kohaldatavaid maksetingimusi, sealhulgas seda, kuidas tellimuste uuendamist käsitletakse, ja muid olulisi tingimusi. X-i kasutajalepingu rakendamine, lõpetamine, tagasimaksete puudumine, mitu X-i kontot ja piirangud 1. Teie suhtes kehtib X-i kasutajaleping. TE OLETE KOHUSTATUD ALATI JÄRGIMA JA TÄITMA X-I KASUTAJALEPINGUT. X-I teenuse, sealhulgas tasuliste teenuste ja funktsioonide kasutamisel kehtib alati X-i kasutajaleping. Kui te ei järgi ega täida X-i kasutajalepingut või kui X on veendunud, et te pole X-i kasutajalepingut järginud ega täitnud, võidakse teie tasulised teenused tühistada. Iga selline tühistamine täiendab (ja on piiranguteta) mis tahes jõustamismeetmeid, mida X võib teie vastu võtta X-i kasutajalepingu alusel. Sellistel juhtudel võite kaotada oma tasuliste teenuste hüved ja teil ei ole õigust saada tasuliste teenuste eest makstud (või ettemakstud) summade eest tagasimakset. 2. Miks võib X teie juurdepääsu tasulistele teenustele lõpetada. X võib peatada või lõpetada teie juurdepääsu tasulis(t)ele teenus(t)ele või lõpetada teile täielikult või osaliselt tasuliste teenuste osutamise või rakendada asjakohaseks peetavaid meetmeid, sealhulgas näiteks teie konto peatamist (ilma vastutuseta) igal ajal või põhjuseta, sealhulgas järgmistel põhjustel. a. X leiab omal äranägemisel, et te olete tingimusi rikkunud või teie tasuliste teenuste kasutamine rikub kohaldatavaid seadusi. b. X-ilt on palunud või nõudnud seda pädev kohus, reguleeriv asutus või õiguskaitseasutus. c. X-il esineb ootamatuid tehnilisi või turvaprobleeme. d. X usub oma ainuisikulise mõistliku äranägemise järgi, et olete rikkunud X-i Kasutajalepingut; e. X usub mõjuvatel põhjustel, näiteks kui tegelete manipuleerimise, mängimise või muu häiriva või keelatud käitumisega seoses tasuliste teenustega; f. Tekitate riski või võimaliku õigusliku kokkupuute X-i suhtes; g. Teie konto tuleks ebaseadusliku tegevuse tõttu eemaldada. h. Teie konto tuleks pikaajalise tegevusetuse tõttu eemaldada. i. Meie tasuliste teenuste pakkumine (täielikult või osaliselt) teile ei ole enam äriliselt tasuv (X-i äranägemisel). 3. Kõik tehingud on lõplikud. Kõik tasuliste teenuste eest tehtud maksed on lõplikud ning neid ei saa tagastada ega vahetada, välja arvatud juhul, kui see on nõutud kohaldatava seadusega. Me ei anna mingit garantiid tasulise teenuse olemuse, kvaliteedi või väärtuse või selle kättesaadavuse või pakkumise kohta. Ühegi kasutamata või osaliselt kasutatud tasulise teenuse (näiteks osaliselt kasutatud tellimisperioodi) eest ei anta raha tagasi ega krediiti. 4. Tasulisi teenuseid ei saa X-i kontode vahel üle kanda. Iga tasulise teenuse ost kehtib ühele X-i kontole, mis tähendab, et teie ost kehtib ainult kontole, mida kasutasite tasulise teenuse ostmise ajal, ega kehti muudele kontodele, millele teil võib olla juurdepääs või mille üle teil võib olla kontroll. Kui teil on mitu kontot või teil on kontroll mitme konto üle ja soovite iga kontoga juurdepääsu tasulistele teenustele, peate ostma tasulise teenuse igal kontol eraldi. 5. Piirangud ja kohustused. a. Teil on lubatud tasulist teenust osta ja kasutada ainult siis, kui teil on seaduslikult lubatud tasulist teenust oma riigis kasutada ja te elate riigis, mida X toetab kohaldatava tasulise teenuse jaoks. X võib teatud riikides oma äranägemise järgi piirata juurdepääsu tasulisele teenusele või selle ostmise võimalust. X jätab endale õiguse toetatud riikide loendit aeg-ajalt muuta. b. Jätame endale õiguse keelduda tasuliste teenuste tehingutest või tühistada või lõpetada tasulise teenuse müük või kasutamine oma äranägemise järgi. c. Te ei tohi lubada teisel isikul kasutada teie X-i kontot, et pääseda juurde tasulistele teenustele, mida ta pole tellinud. d. Te ei tohi tasulist teenust osta ega kasutada, kui olete isik, kellega USA kodanikel ei ole lubatud tehinguid teha majanduslike sanktsioonide alusel, sealhulgas sanktsioonid, mida haldab Ameerika Ühendriikide rahandusministeeriumi välismaiste varade kontrolli amet või muu kohaldatavate sanktsioonide amet (" keelatud isik "). See hõlmab muuhulgas, kuid mitte ainult, isikuid, kes asuvad või elavad tavaliselt järgmistes riikides ja piirkondades: Kuuba, Iraan, Ukrainas Krimmi piirkonnas, Põhja-Koreas või Süürias. Te avaldate ja kinnitate, et te ei ole keelatud isik. e. TE KINNITATE, ET KASUTATE TASULISI TEENUSEID AINULT SEADUSLIKEL EESMÄRKIDEL JA AINULT TINGIMUSTEGA KOOSKÕLAS. Maksud ja tasud . Teie olete vastutav ja nõustute maksma kõik tasuliste teenuste ostmisega seotud kohaldatavad maksud, lõivud, tariifid ja tasud, sealhulgas need, mis tuleb tasuda kas X-ile või kolmandast osapoolest maksete töötlejale. Need maksud võivad hõlmata, kuid mitte ainult, käibemaksu, üldist müügimaksu, müügimaksu, kinnipeetavat maksu ja mis tahes muid kohaldatavaid makse. Olenevalt teie asukohast võib X vastutada teie tasuliste teenuste ostmisel tekkivate tehingumaksudega seotud teabe kogumise ja aruandluse eest. Te annate X-ile loa edastada oma konto- ja isikuandmed asjakohastele maksuametitele, et saaksime täita maksukogumis- ja aruandluskohustusi. Üldtingimused 1. Kontaktteave. Kui teil on tasuliste teenuste või nende tingimuste kohta küsimusi, vaadake lisateabe saamiseks X tasuliste teenuste abikeskust . Kui olete juba tasulise teenuse ostnud, saate meiega ühendust võtta ka tugilingi kaudu, mis on saadaval teie X-i konto navigeerimismenüüs makse- või liitumisseadete all. Kui teil on lisaküsimusi, võite võtta meiega ühendust siin , kasutades vormi „Abi tasuliste funktsioonidega”. 2. LOOBUMISKLAUSEL. KOHALDATAVATE SEADUSTEGA LUBATUD MAKSIMAALSEL MÄÄRAL ON TEIE JUURDEPÄÄS TASULISTELE TEENUSTELE JA NENDE KASUTAMINE TEIE ENDA VASTUTUSEL. TE MÕISTATE JA NÕUSTUTE, ET TASULISI TEENUSEID PAKUTAKSE TEILE SELLISENA, NAGU NAD ON, JA SAADAVUSE ALUSEL. X ÜTLEB LAHTI KÕIKVÕIMALIKEST SÕNASELGETEST VÕI KAUDSETEST GARANTIIDEST JA TINGIMUSTEST, SH KAUBASTATAVUS, KONKREETSEKS OTSTARBEKS SOBIVUS VÕI ÕIGUSTE MITTERIKKUMINE. X EI ANNA GARANTIID EGA LUBADUST NING LOOBUB IGASUGUSEST VASTUTUSEST: I) TASULISTE TEENUSTE TÄIELIKKUSE, TÄPSUSE, KÄTTESAADAVUSE, AJAKOHASUSE, TURVALISUSE VÕI USALDUSVÄÄRSUSE; JA II) SELLE OSAS, KAS TASULISED TEENUSED VASTAVAD TEIE NÕUETELE VÕI ON SAADAVAL KATKEMATULT, TURVALISELT VÕI VIGADETA. VASTUTATE X-I TEENUSE KASUTAMISE, SH TASULISTE TEENUSTE, JA MIS TAHES TEIE PAKUTAVA SISU EEST. 3. VASTUTUSE PIIRAMINE. KOHALDATAVATE SEADUSTEGA LUBATUD MAKSIMAALSEL MÄÄRAL EI VASTUTA X-I ISIKUD MIS TAHES KAUDSETE, JUHUSLIKE, ERAKORDSETE, TULENEVATE VÕI KARISTUSLIKE KAHJUDE EGA KASUMI VÕI TULU OTSESE VÕI KAUDSE VÄHENEMISE EGA MIS TAHES ANDMETE KADUMISE, KASUTUSE, FIRMAVÄÄRTUSE VÕI MUUDE IMMATERIAALSETE KAHJUDE EEST, MIS TULENEVAD i) TEIE JUURDEPÄÄSUST TASULISTELE TEENUSTELE, NENDE KASUTAMISEST VÕI JUURDEPÄÄSU PUUDUMISEST TASULISTELE TEENUSTELE VÕI NENDE KASUTUSVÕIMALUSE PUUDUMISEST; ii) MIS TAHES KOLMANDATE OSAPOOLTE TEGEVUSEST VÕI SISUST, MIS ON POSTITATUD TASULISTE TEENUSTE KAUDU, SEALHULGAS, KUID MITTE ÜKSNES, MIS TAHES LAIMAV, SOLVAV VÕI ILLEGAALNE TEGEVUS TEISTE KASUTAJATE VÕI KOLMANDATE OSAPOOLTE SUHTES; iii) MIS TAHES TASULISTE TEENUSTE KAUDU SAADUD SISUST; VÕI iv) VOLITAMATA JUURDEPÄÄSUST TEIE EDASTUSTELE VÕI SISULE VÕI NENDE VOLITAMATA KASUTAMISEST VÕI MUUTMISEST. KAHTLUSTE VÄLTIMISEKS ON TASULISTE TEENUSTE MÄÄRATLUS PIIRATUD X-I PAKUTUD FUNKTSIOONIDEGA NING EI SISALDA MUUD SISU, MILLELE TEIL ON JUURDEPÄÄS VÕI MILLEGA SUHTLETE NENDE FUNKTSIOONIDE KASUTAMISE KÄIGUS. X-I ISIKUTE KOGUVASTUTUS EI ÜLETA MINGIL JUHUL SADAT EUROT (100,00 €) EGA SUMMAT, MILLE OLETE MEILE NÕUDE ALUSEKS OLEVATE TEENUSTE EEST MAKSNUD VIIMASE KUUE KUU JOOKSUL. SELLE LÕIGU PIIRANGUD KOHALDUVAD IGAT LIIKI VASTUTUSELE – GARANTIIVASTUTUSELE, LEPINGULISELE VASTUTUSELE, KOHUSTUSLIKULE VASTUTUSELE, LEPINGUVÄLISELE (SH HOOLETUSEST TULENEVALE) VASTUTUSELE JA MUULE VASTUTUSELE – VAATAMATA SELLELE, KAS X-I ISIKUID ON ASJAOMASE KAHJU VÕIMALIKKUSEST TEAVITATUD NING ISEGI JUHUL, KUI KÄESOLEVAS ETTENÄHTUD HEASTAMISVIIS LEITAKSE OLEVAT SISULISELT EBAPIISAV. „X-I ISIKUD” VIITAVAD X-ILE, SELLE EMAETTEVÕTETELE, SIDUSETTEVÕTETELE, SEOTUD ETTEVÕTETELE, AMETNIKELE, DIREKTORITELE, TÖÖTAJATELE, AGENTIDELE, ESINDAJATELE, PARTNERITELE JA LITSENTSIANDJATELE. TEIE JURISDIKTSIOONIS KEHTIVATE SEADUSTE KOHASELT EI PRUUGI TEATUD VASTUTUSE PIIRMÄÄRAD OLLA LUBATUD. TEIE JURISDIKTSIOONIS KEHTIVATE SEADUSTEGA NÕUTAVAS ULATUSES EI PIIRA ÜLALTOODU X-I ISIKUTE VASTUTUST PETTUSTE, KURITAHTLIKE VÄÄRESITUSTE, SURMA VÕI ISIKUKAHJU KORRAL, MIDA ON PÕHJUSTANUD MEIE HOOLETUS, RASKE ETTEVAATAMATUS JA/VÕI TAHTLIK TEGUVIIS. X-I ISIKUTE MAKSIMAALNE KOGUVASTUTUS KÕIGI VÄLISTAMATUTE GARANTIIDE KORRAL ON SUURIMAL VÕIMALIKUL MÄÄRAL, MIDA VÕIMALDAVAD KEHTIVAD SEADUSED, PIIRATUD SAJA EUROGA (100,00 EUROT). 4. Märkus Apple’i kohta. Selles ulatuses, milles ostsite tasulisi teenuseid või kasutate tasulisi teenuseid või pääsete neile juurde iOS-i seadme kaudu, nõustute lisaks selle jaotise tingimustega. Nõustute, et tingimused kehtivad ainult teie ja meie vahel, mitte Apple’iga, ning Apple ei vastuta tasuliste teenuste ja nende sisu eest. Apple’il ei ole mingit kohustust osutada tasuliste teenustega seotud hooldus- ja tugiteenuseid. Juhul, kui tasulised teenused ei vasta mis tahes kohaldatavale garantiile, võite sellest Apple’it teavitada ja Apple tagastab teile tasuliste teenuste eest kohaldatava ostuhinna. Kohaldatava seadusega lubatud maksimaalses ulatuses ei ole Apple’il tasuliste teenuste osas mingeid muid garantiikohustusi. Apple ei vastuta teie või mis tahes kolmanda osapoole nõuete käsitlemise eest, mis on seotud tasuliste teenuste või tasuliste teenuste omamise ja/või kasutamisega, sealhulgas, kuid mitte ainult: i) tootevastutusnõuded; ii) mis tahes nõue, et tasulised teenused ei vasta ühelegi kohaldatavale juriidilisele või regulatiivsele nõudele; ja iii) nõuded, mis tulenevad tarbijakaitse või samalaadsetest õigusaktidest. Apple ei vastuta kolmandate osapoolte nende nõuete uurimise, kaitsmise, lahendamise ega rahuldamise eest, mille kohaselt tasulised teenused ja/või teie mobiilirakenduse omamine ja kasutamine rikuvad selle kolmanda osapoole intellektuaalomandi õigusi. Nõustute tasuliste teenuste kasutamisel järgima kõiki kohaldatavaid kolmanda osapoole tingimusi. Apple ja Apple’i tütarettevõtted on tingimuste kolmandast osapoolest kasusaajad. Kui te nõustute tingimustega, on Apple’il õigus (ja seda loetakse õigusega nõustumiseks) jõustada tingimusi teie kui tingimuste kolmandast osapoolest kasusaaja vastu. Käesolevaga avaldate ja kinnitate, et i) te ei asu riigis, mille suhtes kehtib USA valitsuse embargo või mille USA valitsus on määratlenud kui "terroriste toetav" riik; ja ii) te ei ole loetletud üheski USA valitsuse keelatud või piiratud isikute nimekirjas. 5. Vastuolu. Vastuolu korral käesolevate X-i teenuse Purchaser teenusetingimuste ja X-i kasutajalepingu sätete vahel on sätted nendes X-i teenuse Purchaser teenusetingimustes ülimuslikud ainult teie tasulise teenuse kasutamisel. 6. VAIDLUSTE LAHENDAMINE JA KLASSI MEETMETEST LOOBUMINE a. Esmane vaidluste lahendamine . Enamik teie ja X vahelisi vaidlusi saab lahendada mitteametlikult. Saate meiega ühendust võtta, kirjutades tasulistele tugiteenustele siin . Kui võtate meiega ühendust, kirjeldage lühidalt oma mure olemust ja põhjuseid, kontaktandmeid ja konkreetset abi, mida soovite. Osapooled teevad selle tugiprotsessi kaudu kõik endast oleneva, et lahendada vaidlused, nõuded või vastuolud, mis tulenevad nendest tingimustest ja/või teie osalemisest programmis või on nendega seotud (ainsuses vaidlus , mitmuses vaidlused ). Teie ja me nõustume, et selles mitteametlikus protsessis on nõutav heauskne osalemine ja see tuleb lõpule viia ülaltoodud viisil, enne kui kumbki pool saab algatada kohtuvaidluse mis tahes vaidluse kohta, välja arvatud erakorralise ettekirjutuse taotluste puhul (" Erandlik vaidlus "). Kui me ei jõua teiega vaidluses (välja arvatud vabastatud vaidlus) kokkulepitud lahendusele kolmekümne (30) päeva jooksul alates ajast, mil alustatakse vaidluste mitteametlikku lahendamist ülaltoodud vaidluse esmase lahendamise sätte alusel, siis võib teie või meie algatada kohtuvaidlus. b. Seaduse valik ja foorumi valik . LUGEGE SEDA LÕIKU HOOLIKALT – SEE VÕIB OLULISELT MÕJUTADA TEIE JURIIDILISI ÕIGUSI, SEALHULGAS TEIE ÕIGUST KOHTUSSE HAGI ESITADA. Kõik nende tingimustega seotud vaidlused, sealhulgas nendest tingimustest tulenevad või nendega seotud vaidlused, nõuded või vastu | 2026-01-13T08:48:41 |
https://forem.com/eriadura/comment/2k549 | *Matt Eland is a passionate learner, speaker, and author dedicated to explori... - 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 DEV Community Close Discussion on: S27:E8 - Learning AI (Matt Eland) View post Collapse Expand SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow I am a website developer and a game developer Email samuel.adeniji2012@gmail.com Location Nigeria Education Codingal online class Pronouns Mr Work website developer Joined May 30, 2024 • Dec 5 '24 Dropdown menu Copy link Hide * Matt Eland is a passionate learner, speaker, and author dedicated to exploring and sharing knowledge in the most enthusiastic ways. As a Microsoft MVP in AI, he actively contributes to the tech community through his two blogs, YouTube channel, and by organizing the Central Ohio .NET Developer Group. Currently, Matt is balancing his work on a second book and course while also completing his master's degree. * Like comment: Like comment: 7 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 💎 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:48:41 |
https://openapi.tools/categories/gateways | Gateways | OpenApi.tools, from APIs You Won't Hate Sponsored by Zudoku - Open-source, highly customizable API documentation powered by OpenAPI Get Started Sponsor openapi.tools GitHub Get Started All Tools All Categories Legacy Tools Contributing Sponsors Sponsor Badges Collections Arazzo Support Overlays Support Open Source Tools SaaS Tools OpenAPI Tool Categories Annotations Code generators Converters Data Validators Documentation Domain-Specific Languages (DSLs) Gateways HTTP Clients IDEs and GUI Editors Learning Miscellaneous Mock Servers Monitoring OpenAPI-aware Frameworks Parsers Schema Validators SDK Generators Security Server Implementations Testing Text Editors © 2026 APIs You Won't Hate Get in touch to become a Sponsor . This site is community-driven and OSS , built with Astro and hosted on Netlify . Gateways API Gateways and related tools that have integrated support for OpenAPI. Gateways There are additional tools in this category, but they only support legacy versions of OpenAPI. If you really need to work with some old OpenAPI descriptions perhaps these legacy tools could be of use * * * | 2026-01-13T08:48:41 |
https://docs.python.org/3/tutorial/controlflow.html#positional-or-keyword-arguments | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | 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:48:41 |
https://support.google.com/chrome/answer/95647?hl=en&co=GENIE.Platform%3DDesktop | Delete, allow, and manage cookies in Chrome - Computer - Google Chrome Help Skip to main content Google Chrome Help Sign in Google Help Help Center Community Google Chrome Privacy Policy Terms of Service Submit feedback Send feedback on... This help content & information General Help Center experience Next Help Center Community Google Chrome Delete, allow, and manage cookies in Chrome You can choose to delete existing cookies, allow or block third-party cookies, and set preferences for certain websites. Understand cookies Cookies are files created by websites you visit. By saving information about your visit, they make your online experience easier. For example, sites can keep you signed in, remember your site preferences, and give you locally relevant content. There are 2 types of cookies: First-party cookies: Created by the site you visit. The site is shown in the address bar. Third-party cookies: Created by other sites. A site you visit can embed content from other sites, for example images, ads, and text. Any of these sites can use third-party cookies to personalize content and ads, and learn about actions you take on other sites. Tip: Some sites may prompt you to accept or reject cookies. There are other ways that sites can personalize content and ads. Features like ad topics and site-suggested ads in Chrome allow sites to show you personalized content. These features limit what sites and their partners can learn about you. Learn more about managing these features . Delete all cookies Important: If you delete cookies, you may get signed out of sites that remember you. Your saved preferences can also be deleted. This applies whenever a cookie is deleted. On your computer, open Chrome. At the top right, select More Delete browsing data . Select Basic or Advanced Cookies and other site data . Next to "Time range," from the dropdown menu, choose the browsing data time range you want to delete: Last hour Last 24 hours Last 7 days Last 4 weeks All time Check other items you want to delete. To confirm, select Delete data . Delete specific cookies On your computer, open Chrome. At the top right, select More Settings . Select Privacy and security Third-party cookies . Select See all site data and permissions . At the top right, search for the website's name. To the right of the site, select Delete . To confirm, select Delete . Change your third-party cookie settings You can allow or block third-party cookies for any site. Allow or block third-party cookies Important: If you don't allow sites to save cookies, sites may not work as expected. To manage first-party cookies, learn more about on-device site data in Chrome . By default, third-party cookies are blocked in Incognito mode. Learn how to browse in Incognito mode . You can allow or block third-party cookies by default. On your computer, open Chrome. At the top right, select More Settings . Select Privacy and security Third-party cookies . Select an option: Allow third-party cookies . Block third-party cookies . If you block third-party cookies, all third-party cookies from other sites are blocked unless the site is allowed on your exceptions list. Allow third-party cookies for a specific site Important: If you’re using your Chromebook at work or school, you might not be able to change this setting. For more help, contact your administrator. In Incognito mode, third-party cookies are blocked by default. If third-party cookies are blocked, some sites that rely on them may not work as expected. To allow third-party cookies for specific sites, you can add them to your exceptions list. Sites on this list can use third-party cookies in both regular and Incognito browsing modes. On your computer, open Chrome. At the top right, select More Settings . Select Privacy and security Third-party cookies . Under "Sites allowed to use third-party cookies," select Add . Enter the web address. To create an exception for an entire domain, insert [*.] before the domain name. For example, [*.]google.com will match drive.google.com and calendar.google.com . You can also put an IP address or a web address that doesn't start with http:// . Select Add . To remove an exception you don't want any more, to the right of the website, select Remove . Allow third-party cookies temporarily for a specific site Important: In Incognito mode, third-party cookies are blocked by default. If third-party cookies are blocked, some sites that rely on them may not work as expected. You can try to restore functionality for the site you’re on by temporarily allowing third-party cookies: If you apply this setting in regular browsing mode, the site is added to your exceptions list. The site is allowed to use third-party cookies for 90 days or until you turn the setting off. If you apply this setting in Incognito mode, the setting lasts only for the duration of your Incognito session. On your computer, open Chrome. In the address bar, at the top left: To allow third-party cookies: Select Third-party cookies blocked and turn on Third-party cookies . To block third-party cookies: Select Third-party cookies allowed and turn off Third-party cookies . To close the dialog box and reload the page, select Close . You can also select anywhere outside of the dialog box to close it. When the page reloads, the address bar shows “Third-party cookies allowed,” or “Third-party cookies blocked,” depending on your settings. Tip: This option is temporary and only applies to the site you’re on. Allow related sites to access your activity A company can define a group of sites that are related to each other. For example, a company might want to keep you signed in as you move between acme-music.example and acme-video.example . If you allow third-party cookies: Related sites are allowed to access your activity to personalize content or keep you signed in across sites. If you block third-party cookies: It often prevents this kind of connection between sites. You can block third-party cookies while you allow sites in the same group to improve your experience. You can find the full list of companies who define groups of related sites on Github . Learn more about related sites and third-party cookies . To allow related sites to find your activity within the group: On your computer, open Chrome. At the top right, select More Settings . Select Privacy and security Third-party cookies . Select Block third-party cookies . Turn Allow related sites to see your activity in the group on or off. To show related sites in the same group: On your computer, open Chrome. At the top right, select More Settings . Select Privacy and security Third-party cookies See all site data and permissions . Choose a site. To show sites in the same group, select the drop down arrow . Tip: To find related sites, in the address bar, select View site information Cookies and site data Manage on-device site data . About embedded content Sites you visit can embed content from other sites, for example images, ads, text, and even features — like a text editor or weather widget. These other sites can ask for permission to use info they’ve saved about you (often saved using cookies) in order for their content to function properly. For example, imagine you normally compose documents on docs.google.com . While completing a task for school, you need to collaborate with other students on your school’s class portal that offers direct access to Google Docs. With your permission: Google Docs can access its third-party cookies while you use your school’s site, allowing a connection between the site and Google Docs. This may allow Google Docs to verify who you are, find your info, and save changes you make to your documents on the site. In some cases, this info can be used to track your activity as you browse sites. You can decide when to allow embedded content to access your data for sites you trust. Tip: The connection uses cookies and lasts for 30 days or as long as you remain active. You can stop allowing the connection anytime in Settings . To allow or decline permission When you browse a site that displays a prompt requesting permission for the embedded content to use information they’ve saved about you: Select Allow to give the site access to information they’ve saved about you (using cookies) Select Don’t allow to deny access Tips: To stop allowing access, learn how to manage site settings permissions. You can also manage access by clicking View site information to the left of the address bar, and then turning Embedded content on or off. Related resources Change site settings permissions Delete browsing data in Chrome Clear cache & cookies Manage your ad privacy in Chrome Learn about on-device site data in Chrome Was this helpful? How can we improve it? Yes No Submit Computer Android iPhone & iPad More Need more help? Try these next steps: Post to the help community Get answers from community members true Help 1 of 7 Delete browsing data in Chrome 2 of 7 Export your data from Chrome 3 of 7 Check or delete your Chrome browsing history 4 of 7 Delete, allow, and manage cookies in Chrome 5 of 7 Manage passwords in Chrome 6 of 7 Reset Chrome settings to default 7 of 7 Learn about on-device site data in Chrome Want a preview of what's coming soon? Download the beta version of Chrome , then join our community and let us know how well it works for you. ©2026 Google Privacy Policy Terms of Service Language Afrikaans‎ català‎ dansk‎ Deutsch‎ eesti‎ English (United Kingdom)‎ español‎ español (Latinoamérica)‎ Filipino‎ français‎ hrvatski‎ Indonesia‎ isiZulu‎ italiano‎ Kiswahili‎ latviešu‎ lietuvių‎ magyar‎ Melayu‎ Nederlands‎ norsk‎ polski‎ português‎ português (Brasil)‎ română‎ slovenčina‎ slovenščina‎ suomi‎ svenska‎ Tiếng Việt‎ Türkçe‎ čeština‎ Ελληνικά‎ български‎ русский‎ српски‎ українська‎ ‏ עברית ‏ العربية ‏ فارسی मराठी‎ हिन्दी‎ తెలుగు‎ ไทย‎ አማርኛ‎ 中文（简体）‎ 中文（繁體）‎ 日本語‎ 한국어‎ English‎ Enable Dark Mode Send feedback on... This help content & information General Help Center experience Search Clear search Close search Google apps Main menu var n,aaa=[];function la(a){return function(){return aaa[a].apply(this,arguments)}} function ma(a,b){return aaa[a]=b} var baa=typeof Object.create=="function"?Object.create:function(a){function b(){} b.prototype=a;return new b},na=typeof Object.defineProperties=="function"?Object.defineProperty:function(a,b,c){if(a==Array.prototype||a==Object.prototype)return a; a[b]=c.value;return a}; function caa(a){a=["object"==typeof globalThis&&globalThis,a,"object"==typeof window&&window,"object"==typeof self&&self,"object"==typeof global&&global];for(var b=0;b >>0)+"_",f=0;return b}); ra("Symbol.iterator",function(a){if(a)return a;a=Symbol("Symbol.iterator");na(Array.prototype,a,{configurable:!0,writable:!0,value:function(){return naa(haa(this))}}); return a}); function naa(a){a={next:a};a[Symbol.iterator]=function(){return this}; return a} ra("Promise",function(a){function b(k){this.o=0;this.oa=void 0;this.ma=[];this.ya=!1;var l=this.ua();try{k(l.resolve,l.reject)}catch(p){l.reject(p)}} function c(){this.o=null} function e(k){return k instanceof b?k:new b(function(l){l(k)})} if(a)return a;c.prototype.ma=function(k){if(this.o==null){this.o=[];var l=this;this.oa(function(){l.qa()})}this.o.push(k)}; var f=oa.setTimeout;c.prototype.oa=function(k){f(k,0)}; c.prototype.qa=function(){for(;this.o&&this.o.length;){var k=this.o;this.o=[];for(var l=0;l =h}}); ra("String.prototype.endsWith",function(a){return a?a:function(b,c){var e=Ua(this,b,"endsWith");b+="";c===void 0&&(c=e.length);c=Math.max(0,Math.min(c|0,e.length));for(var f=b.length;f>0&&c>0;)if(e[--c]!=b[--f])return!1;return f f)e=f;e=Number(e);e =0&&b 56319||b+1===e)return f;b=c.charCodeAt(b+1);return b 57343?f:(f-55296)*1024+b+9216}}}); ra("String.fromCodePoint",function(a){return a?a:function(b){for(var c="",e=0;e 1114111||f!==Math.floor(f))throw new RangeError("invalid_code_point "+f);f >>10&1023|55296),c+=String.fromCharCode(f&1023|56320))}return c}}); ra("String.prototype.repeat",function(a){return a?a:function(b){var c=Ua(this,null,"repeat");if(b 1342177279)throw new RangeError("Invalid count value");b|=0;for(var e="";b;)if(b&1&&(e+=c),b>>>=1)c+=c;return e}}); ra("Array.prototype.findIndex",function(a){return a?a:function(b,c){return oaa(this,b,c).i}}); function Wa(a){a=Math.trunc(a)||0;a =this.length))return this[a]} ra("Array.prototype.at",function(a){return a?a:Wa}); daa("at",function(a){return a?a:Wa}); ra("String.prototype.at",function(a){return a?a:Wa}); ra("String.prototype.padStart",function(a){return a?a:function(b,c){var e=Ua(this,null,"padStart");b-=e.length;c=c!==void 0?String(c):" ";return(b>0&&c?c.repeat(Math.ceil(b/c.length)).substring(0,b):"")+e}}); ra("Promise.prototype.finally",function(a){return a?a:function(b){return this.then(function(c){return Promise.resolve(b()).then(function(){return c})},function(c){return Promise.resolve(b()).then(function(){throw c; })})}}); ra("Array.prototype.flatMap",function(a){return a?a:function(b,c){var e=[];Array.prototype.forEach.call(this,function(f,h){f=b.call(c,f,h,this);Array.isArray(f)?e.push.apply(e,f):e.push(f)}); return e}}); ra("Array.prototype.flat",function(a){return a?a:function(b){b=b===void 0?1:b;var c=[];Array.prototype.forEach.call(this,function(e){Array.isArray(e)&&b>0?(e=Array.prototype.flat.call(e,b-1),c.push.apply(c,e)):c.push(e)}); return c}}); ra("Promise.allSettled",function(a){function b(e){return{status:"fulfilled",value:e}} function c(e){return{status:"rejected",reason:e}} return a?a:function(e){var f=this;e=Array.from(e,function(h){return f.resolve(h).then(b,c)}); return f.all(e)}}); ra("Array.prototype.toSpliced",function(a){return a?a:function(b,c,e){var f=Array.from(this);Array.prototype.splice.apply(f,arguments);return f}}); ra("Number.parseInt",function(a){return a||parseInt});/* Copyright The Closure Library Authors. SPDX-License-Identifier: Apache-2.0 */ var Ya=Ya||{},Za=this||self;function $a(a,b){var c=ab("CLOSURE_FLAGS");a=c&&c[a];return a!=null?a:b} function ab(a,b){a=a.split(".");b=b||Za;for(var c=0;c >>0),raa=0;function saa(a,b,c){return a.call.apply(a.bind,arguments)} function taa(a,b,c){if(!a)throw Error();if(arguments.length>2){var e=Array.prototype.slice.call(arguments,2);return function(){var f=Array.prototype.slice.call(arguments);Array.prototype.unshift.apply(f,e);return a.apply(b,f)}}return function(){return a.apply(b,arguments)}} function eb(a,b,c){eb=Function.prototype.bind&&Function.prototype.bind.toString().indexOf("native code")!=-1?saa:taa;return eb.apply(null,arguments)} function fb(a,b){var c=Array.prototype.slice.call(arguments,1);return function(){var e=c.slice();e.push.apply(e,arguments);return a.apply(this,e)}} function gb(){return Date.now()} function hb(a,b){a=a.split(".");for(var c=Za,e;a.length&&(e=a.shift());)a.length||b===void 0?c[e]&&c[e]!==Object.prototype[e]?c=c[e]:c=c[e]={}:c[e]=b} function jb(a){return a} function kb(a,b){function c(){} c.prototype=b.prototype;a.yh=b.prototype;a.prototype=new c;a.prototype.constructor=a;a.base=function(e,f,h){for(var k=Array(arguments.length-2),l=2;l >6|192;else{if(h>=55296&&h =56320&&k >18|240;e[c++]=h>>12&63|128;e[c++]=h>>6&63|128;e[c++]=h&63|128;continue}else f--}if(b)throw Error("Found an unpaired surrogate");h=65533}e[c++]=h>>12|224;e[c++]=h>>6&63|128}e[c++]=h&63|128}}a=c===e.length?e:e.subarray(0,c)}return a} ;function qb(a){Za.setTimeout(function(){throw a;},0)} ;function rb(a,b){return a.lastIndexOf(b,0)==0} function sb(a){return/^[\s\xa0]*$/.test(a)} var tb=String.prototype.trim?function(a){return a.trim()}:function(a){return/^[\s\xa0]*([\s\S]*?)[\s\xa0]*$/.exec(a)[1]}; function ub(a,b){return a.indexOf(b)!=-1} function Baa(a,b){var c=0;a=tb(String(a)).split(".");b=tb(String(b)).split(".");for(var e=Math.max(a.length,b.length),f=0;c==0&&f b?1:0} ;var Caa=$a(1,!0),xb=$a(610401301,!1);$a(899588437,!1);$a(772657768,!0);$a(513659523,!1);$a(568333945,!0);$a(1331761403,!1);$a(651175828,!1);$a(722764542,!1);$a(748402145,!1);$a(748402146,!1);var Daa=$a(748402147,!0),yb=$a(824648567,!0),Ab=$a(824656860,Caa);$a(333098724,!1);$a(2147483644,!1);$a(2147483645,!1);$a(2147483646,Caa);$a(2147483647,!0);function Bb(){var a=Za.navigator;return a&&(a=a.userAgent)?a:""} var Cb,Eaa=Za.navigator;Cb=Eaa?Eaa.userAgentData||null:null;function Db(a){if(!xb||!Cb)return!1;for(var b=0;b 0:!1} function Gb(){return Fb()?!1:Eb("Opera")} function Hb(){return Fb()?!1:Eb("Trident")||Eb("MSIE")} function Faa(){return Fb()?Db("Microsoft Edge"):Eb("Edg/")} function Ib(){return Eb("Firefox")||Eb("FxiOS")} function Jb(){return Eb("Safari")&&!(Lb()||(Fb()?0:Eb("Coast"))||Gb()||(Fb()?0:Eb("Edge"))||Faa()||(Fb()?Db("Opera"):Eb("OPR"))||Ib()||Eb("Silk")||Eb("Android"))} function Lb(){return Fb()?Db("Chromium"):(Eb("Chrome")||Eb("CriOS"))&&!(Fb()?0:Eb("Edge"))||Eb("Silk")} ;function Mb(){return xb?!!Cb&&!!Cb.platform:!1} function Nb(){return Mb()?Cb.platform==="Android":Eb("Android")} function Ob(){return Eb("iPhone")&&!Eb("iPod")&&!Eb("iPad")} function Pb(){return Ob()||Eb("iPad")||Eb("iPod")} function Rb(){return Mb()?Cb.platform==="macOS":Eb("Macintosh")} function Gaa(){return Mb()?Cb.platform==="Linux":Eb("Linux")} function Sb(){return Mb()?Cb.platform==="Windows":Eb("Windows")} function Haa(){return Mb()?Cb.platform==="Chrome OS":Eb("CrOS")} ;var Iaa=Array.prototype.indexOf?function(a,b){return Array.prototype.indexOf.call(a,b,void 0)}:function(a,b){if(typeof a==="string")return typeof b!=="string"||b.length!=1?-1:a.indexOf(b,0); for(var c=0;c =0} function Wb(a,b){b=Iaa(a,b);var c;(c=b>=0)&&Array.prototype.splice.call(a,b,1);return c} function Xb(a){var b=a.length;if(b>0){for(var c=Array(b),e=0;e parseFloat(fc)){ec=String(ic);break a}}ec=fc}var Vaa=ec;var Waa=Ib(),Xaa=Ob()||Eb("iPod"),Yaa=Eb("iPad"),Zaa=Eb("Android")&&!(Lb()||Ib()||Gb()||Eb("Silk")),jc=Lb(),$aa=Jb()&&!Pb();var aba={},kc=null,bba=bc||cc,cba=bba||typeof Za.btoa=="function",dba=bba||!$aa&&typeof Za.atob=="function";function lc(a,b){b===void 0&&(b=0);eba();b=aba[b];for(var c=Array(Math.floor(a.length/3)),e=b[64]||"",f=0,h=0;f >2];k=b[(k&3) >4];l=b[(l&15) >6];p=b[p&63];c[h++]=""+r+k+l+p}r=0;p=e;switch(a.length-f){case 2:r=a[f+1],p=b[(r&15) >2]+b[(a&3) >4]+p+e}return c.join("")} function nc(a,b){if(cba&&!b)a=Za.btoa(a);else{for(var c=[],e=0,f=0;f 255&&(c[e++]=h&255,h>>=8);c[e++]=h}a=lc(c,b)}return a} function oc(a,b){if(cba&&!b)a=Za.btoa(unescape(encodeURIComponent(a)));else{for(var c=[],e=0,f=0;f >6|192:((h&64512)==55296&&f+1 >18|240,c[e++]=h>>12&63|128):c[e++]=h>>12|224,c[e++]=h>>6&63|128),c[e++]=h&63|128)}a=lc(c,b)}return a} function pc(a,b){if(dba&&!b)return Za.atob(a);var c="";fba(a,function(e){c+=String.fromCharCode(e)}); return c} function gba(a){var b=a.length,c=b*3/4;c%3?c=Math.floor(c):ub("=.",a[b-1])&&(c=ub("=.",a[b-2])?c-2:c-1);var e=new Uint8Array(c),f=0;fba(a,function(h){e[f++]=h}); return f!==c?e.subarray(0,f):e} function fba(a,b){function c(p){for(;e >4);k!=64&&(b(h >2),l!=64&&b(k a.o.length&&(e=a.o,c=b.o);if(c.lastIndexOf(e,0)!==0)return!1;for(b=e.length;b =b||(e[a]=c+1,uba())}} ;function Ac(){return typeof BigInt==="function"} ;var Bc=typeof Symbol==="function"&&typeof Symbol()==="symbol";function Dc(a,b,c){return typeof Symbol==="function"&&typeof Symbol()==="symbol"?(c===void 0?0:c)&&Symbol.for&&a?Symbol.for(a):a!=null?Symbol(a):Symbol():b} var vba=Dc("jas",void 0,!0),Ec=Dc(void 0,"0di"),Fc=Dc(void 0,"1oa"),wba=Dc(void 0,"0dg"),Gc=Dc(void 0,Symbol()),xba=Dc(void 0,"0ub"),yba=Dc(void 0,"0ubs"),Hc=Dc(void 0,"0ubsb"),zba=Dc(void 0,"0actk"),Aba=Dc("m_m","Hqa",!0),Bba=Dc(void 0,"vps"),Cba=Dc();var Dba={FT:{value:0,configurable:!0,writable:!0,enumerable:!1}},Eba=Object.defineProperties,Ic=Bc?vba:"FT",Jc,Fba=[];Kc(Fba,7);Jc=Object.freeze(Fba);function Lc(a,b){Bc||Ic in a||Eba(a,Dba);a[Ic]|=b} function Kc(a,b){Bc||Ic in a||Eba(a,Dba);a[Ic]=b} function Gba(a){if(4&a)return 512&a?512:1024&a?1024:0} function Mc(a){Lc(a,34);return a} function Nc(a){Lc(a,8192);return a} function Oc(a){Lc(a,32);return a} ;var Hba={};function Pc(a){return a[Aba]===Hba} function Qc(a,b){return b===void 0?a.ma!==Rc&&!!(2&(a.Aa[Ic]|0)):!!(2&b)&&a.ma!==Rc} var Rc={};function Sc(a,b,c){if(a==null){if(!c)throw Error();}else if(typeof a==="string")a=a?new uc(a,tc):vc();else if(a.constructor!==uc)if(rc(a))a=a.length?new uc(new Uint8Array(a),tc):vc();else{if(!b)throw Error();a=void 0}return a} function Tc(a,b){if(typeof b!=="number"||b =a.length)throw Error();} function Iba(a,b){if(typeof b!=="number"||b a.length)throw Error();} function Uc(a,b,c){this.o=a;this.ma=b;this.thisArg=c} Uc.prototype.next=function(){var a=this.o.next();a.done||(a.value=this.ma.call(this.thisArg,a.value));return a}; Uc.prototype[Symbol.iterator]=function(){return this}; var Vc=Object.freeze({}),Jba=Object.freeze({});function Kba(a,b,c){var e=b&128?0:-1,f=a.length,h;if(h=!!f)h=a[f-1],h=h!=null&&typeof h==="object"&&h.constructor===Object;var k=f+(h?-1:0);for(b=b&128?1:0;b =Qba&&a b.length)return!1;if(a.length f)return!1;if(e >>0;bd=b;cd=(a-b)/4294967296>>>0} function fd(a){if(a >>0;cd=b>>>0}else ed(a)} function Wba(a){var b=dd||(dd=new DataView(new ArrayBuffer(8)));b.setFloat32(0,+a,!0);cd=0;bd=b.getUint32(0,!0)} function hd(a,b){var c=b*4294967296+(a>>>0);return Number.isSafeInteger(c)?c:jd(a,b)} function Xba(a,b){return $c(Ac()?BigInt.asUintN(64,(BigInt(b>>>0) >>0)):jd(a,b))} function kd(a,b){var c=b&2147483648;c&&(a=~a+1>>>0,b=~b>>>0,a==0&&(b=b+1>>>0));a=hd(a,b);return typeof a==="number"?c?-a:a:c?"-"+a:a} function Yba(a,b){return Ac()?$c(BigInt.asIntN(64,(BigInt.asUintN(32,BigInt(b)) >31;c=(c >>31)^e;a(b >>1|b >>1^e;return c(a,b)} function jd(a,b){b>>>=0;a>>>=0;if(b >>24|b >16&65535,a=(a&16777215)+c*6777216+b*6710656,c+=b*8147497,b*=2,a>=1E7&&(c+=a/1E7>>>0,a%=1E7),c>=1E7&&(b+=c/1E7>>>0,c%=1E7),c=b+bca(c)+bca(a));return c} function bca(a){a=String(a);return"0000000".slice(a.length)+a} function ld(a,b){b&2147483648?Ac()?a=""+(BigInt(b|0) >>0)):(b=v(gd(a,b)),a=b.next().value,b=b.next().value,a="-"+jd(a,b)):a=jd(a,b);return a} function md(a){if(a.length >>0,cd=Number(a>>BigInt(32)&BigInt(4294967295));else{var b=+(a[0]==="-");cd=bd=0;for(var c=a.length,e=0+b,f=(c-b)%6+b;f =4294967296&&(cd+=Math.trunc(bd/4294967296),cd>>>=0,bd>>>=0);b&&(b=v(gd(bd,cd)),a=b.next().value,b=b.next().value,bd=a,cd=b)}} function gd(a,b){b=~b;a?a=~a+1:b+=1;return[a,b]} ;function nd(a){return Array.prototype.slice.call(a)} ;function od(a,b){throw Error(b===void 0?"unexpected value "+a+"!":b);} ;var pd=typeof BigInt==="function"?BigInt.asIntN:void 0,qd=typeof BigInt==="function"?BigInt.asUintN:void 0,rd=Number.isSafeInteger,sd=Number.isFinite,td=Math.trunc;function ud(a){if(a==null||typeof a==="number")return a;if(a==="NaN"||a==="Infinity"||a==="-Infinity")return Number(a)} function cca(a){return Sc(a,!1,!1)} function vd(a){if(a!=null&&typeof a!=="boolean")throw Error("Expected boolean but got "+bb(a)+": "+a);return a} function wd(a){if(a==null||typeof a==="boolean")return a;if(typeof a==="number")return!!a} var dca=/^-?([1-9][0-9]*|0)(\.[0-9]+)?$/;function xd(a){switch(typeof a){case "bigint":return!0;case "number":return sd(a);case "string":return dca.test(a);default:return!1}} function yd(a){if(!sd(a))throw yc("enum");return a|0} function zd(a){return a==null?a:yd(a)} function Ad(a){return a==null?a:sd(a)?a|0:void 0} function Bd(a){if(typeof a!=="number")throw yc("int32");if(!sd(a))throw yc("int32");return a|0} function Cd(a){return a==null?a:Bd(a)} function Dd(a){if(a==null)return a;if(typeof a==="string"&&a)a=+a;else if(typeof a!=="number")return;return sd(a)?a|0:void 0} function Ed(a){if(typeof a!=="number")throw yc("uint32");if(!sd(a))throw yc("uint32");return a>>>0} function Fd(a){if(a==null)return a;if(typeof a==="string"&&a)a=+a;else if(typeof a!=="number")return;return sd(a)?a>>>0:void 0} function Gd(a,b){b!=null||(b=Ab?1024:0);if(!xd(a))throw yc("int64");var c=typeof a;switch(b){case 512:switch(c){case "string":return Hd(a);case "bigint":return String(pd(64,a));default:return Id(a)}case 1024:switch(c){case "string":return eca(a);case "bigint":return $c(pd(64,a));default:return fca(a)}case 0:switch(c){case "string":return Hd(a);case "bigint":return $c(pd(64,a));default:return Jd(a)}default:return od(b,"Unknown format requested type for int64")}} function Kd(a){return a==null?a:Gd(a,void 0)} function gca(a){var b=a.length;if(a[0]==="-"?b =0&&rd(a)||(fd(a),a=hd(bd,cd));return a} function Id(a){a=td(a);rd(a)?a=String(a):(fd(a),a=ld(bd,cd));return a} function Md(a){a=td(a);a>=0&&rd(a)?a=String(a):(fd(a),a=jd(bd,cd));return a} function Hd(a){var b=td(Number(a));if(rd(b))return String(b);b=a.indexOf(".");b!==-1&&(a=a.substring(0,b));return gca(a)} function eca(a){var b=td(Number(a));if(rd(b))return $c(b);b=a.indexOf(".");b!==-1&&(a=a.substring(0,b));return Ac()?$c(pd(64,BigInt(a))):$c(gca(a))} function fca(a){return rd(a)?$c(Jd(a)):$c(Id(a))} function ica(a){return rd(a)?$c(Ld(a)):$c(Md(a))} function Nd(a){var b=td(Number(a));if(rd(b)&&b>=0)return String(b);b=a.indexOf(".");b!==-1&&(a=a.substring(0,b));return hca(a)} function jca(a){var b=td(Number(a));if(rd(b)&&b>=0)return $c(b);b=a.indexOf(".");b!==-1&&(a=a.substring(0,b));return Ac()?$c(qd(64,BigInt(a))):$c(hca(a))} function Od(a){if(a==null)return a;if(typeof a==="bigint")return ad(a)?a=Number(a):(a=pd(64,a),a=ad(a)?Number(a):String(a)),a;if(xd(a))return typeof a==="number"?Jd(a):Hd(a)} function Pd(a,b){b=b===void 0?!1:b;var c=typeof a;if(a==null)return a;if(c==="bigint")return String(pd(64,a));if(xd(a))return c==="string"?Hd(a):b?Id(a):Jd(a)} function Qd(a){var b=typeof a;if(a==null)return a;if(b==="bigint")return $c(pd(64,a));if(xd(a))return b==="string"?eca(a):fca(a)} function kca(a){var b=void 0;b!=null||(b=Ab?1024:0);if(!xd(a))throw yc("uint64");var c=typeof a;switch(b){case 512:switch(c){case "string":return Nd(a);case "bigint":return String(qd(64,a));default:return Md(a)}case 1024:switch(c){case "string":return jca(a);case "bigint":return $c(qd(64,a));default:return ica(a)}case 0:switch(c){case "string":return Nd(a);case "bigint":return $c(qd(64,a));default:return Ld(a)}default:return od(b,"Unknown format requested type for int64")}} function Rd(a){var b=typeof a;if(a==null)return a;if(b==="bigint")return $c(qd(64,a));if(xd(a))return b==="string"?jca(a):ica(a)} function Td(a){if(a==null)return a;var b=typeof a;if(b==="bigint")return String(pd(64,a));if(xd(a)){if(b==="string")return Hd(a);if(b==="number")return Jd(a)}} function Ud(a){if(a==null)return a;var b=typeof a;if(b==="bigint")return String(qd(64,a));if(xd(a)){if(b==="string")return Nd(a);if(b==="number")return Ld(a)}} function lca(a){if(a==null||typeof a=="string"||a instanceof uc)return a} function Vd(a){if(typeof a!=="string")throw Error();return a} function Wd(a){if(a!=null&&typeof a!=="string")throw Error();return a} function Xd(a){return a==null||typeof a==="string"?a:void 0} function Yd(a,b,c,e){if(a!=null&&Pc(a))return a;if(!Array.isArray(a))return c?e&2?b[Ec]||(b[Ec]=mca(b)):new b:void 0;c=a[Ic]|0;e=c|e&32|e&2;e!==c&&Kc(a,e);return new b(a)} function mca(a){a=new a;Mc(a.Aa);return a} ;var nca={};function Zd(a){return a} ;function oca(a,b){if(typeof b==="string")try{b=qc(b)}catch(c){return!1}return rc(b)&&mba(a,b)} function pca(a){switch(a){case "bigint":case "string":case "number":return!0;default:return!1}} function qca(a,b){if(Pc(a))a=a.Aa;else if(!Array.isArray(a))return!1;if(Pc(b))b=b.Aa;else if(!Array.isArray(b))return!1;return $d(a,b,void 0,2)} function ae(a,b,c){return $d(a,b,c,0)} function $d(a,b,c,e){if(a===b||a==null&&b==null)return!0;if(a instanceof Map)return rca(a,b,c);if(b instanceof Map)return rca(b,a,c);if(a==null||b==null)return!1;if(a instanceof uc)return rba(a,b);if(b instanceof uc)return rba(b,a);if(rc(a))return oca(a,b);if(rc(b))return oca(b,a);var f=typeof a,h=typeof b;if(f!=="object"||h!=="object")return Number.isNaN(a)||Number.isNaN(b)?String(a)===String(b):pca(f)&&pca(h)?""+a===""+b:f==="boolean"&&h==="number"||f==="number"&&h==="boolean"?!a===!b:!1;if(Pc(a)|| Pc(b))return qca(a,b);if(a.constructor!=b.constructor)return!1;if(a.constructor===Array){h=a[Ic]|0;var k=b[Ic]|0,l=a.length,p=b.length,r=Math.max(l,p);f=(h|k|64)&128?0:-1;if(e===1||(h|k)&1)e=1;else if((h|k)&8192)return sca(a,b);h=l&&a[l-1];k=p&&b[p-1];h!=null&&typeof h==="object"&&h.constructor===Object||(h=null);k!=null&&typeof k==="object"&&k.constructor===Object||(k=null);l=l-f-+!!h;p=p-f-+!!k;for(var t=0;t b.length)return!1;b=nd(b);Array.prototype.sort.call(b,je);for(var e=0,f=void 0,h=b.length-1;h>=0;h--){var k=b[h];if(!k||!Array.isArray(k)||k.length!==2)return!1;var l=k[0];if(l!==f){f=void 0;if(!ae(a.get(l),k[1],(f=c)==null?void 0:f.o(2)))return!1;f=l;e++}}return e===a.size} function sca(a,b){if(!Array.isArray(a)||!Array.isArray(b))return!1;a=nd(a);b=nd(b);Array.prototype.sort.call(a,je);Array.prototype.sort.call(b,je);var c=a.length,e=b.length;if(c===0&&e===0)return!0;for(var f=0,h=0;f =c&&h>=e} function yca(a){return[a,this.get(a)]} var Bca;function Cca(){return Bca||(Bca=new ee(Mc([]),void 0,void 0,void 0,uca))} ;function ke(a){var b=jb(Gc);return b?a[b]:void 0} function le(){} function me(a,b){for(var c in a)!isNaN(c)&&b(a,+c,a[c])} function Dca(a){var b=new le;me(a,function(c,e,f){b[e]=nd(f)}); b.zG=a.zG;return b} function Eca(a,b){a=a.Aa;var c=jb(Gc);c&&c in a&&(a=a[c])&&delete a[b]} var Fca={yV:!0};function Gca(a,b){var c=c===void 0?!1:c;if(jb(Cba)&&jb(Gc)&&void 0===Cba){var e=a.Aa,f=e[Gc];if(!f)return;if(f=f.zG)try{f(e,b,Fca);return}catch(h){qb(h)}}c&&Eca(a,b)} function Hca(a,b){var c=jb(Gc),e;Bc&&c&&((e=a[c])==null?void 0:e[b])!=null&&zc(xba,3)} function Ica(a,b){b =k){var pa=y-t,ta=void 0;((ta=b)!=null?ta:b={})[pa]=E}else h[y]=E}if(w)for(var Aa in w)l= w[Aa],l!=null&&(l=c(l,e))!=null&&(y=+Aa,E=void 0,r&&!Number.isNaN(y)&&(E=y+t) 0?void 0:a===0?Nca||(Nca=[0,void 0]):[-a,void 0];case "string":return[0,a];case "object":return a}} function re(a,b){return Pca(a,b[0],b[1])} function se(a,b,c){return Pca(a,b,c,2048)} function Pca(a,b,c,e){e=e===void 0?0:e;if(a==null){var f=32;c?(a=[c],f|=128):a=[];b&&(f=f&-16760833|(b&1023) =1024)throw Error("pvtlmt");for(var p in l)h= +p,h 1024)throw Error("spvt");f=f&-16760833|(p&1023) =h){var k=a[h];if(k!=null&&typeof k==="object"&&k.constructor===Object){c=k[b];var l=!0}else if(f===h)c=k;else return}else c=a[f];if(e&&c!=null){e=e(c);if(e==null)return e;if(!Object.is(e,c))return l?k[b]=e:a[f]=e,e}return c}} function Ce(a,b,c,e){xe(a);var f=a.Aa;De(f,f[Ic]|0,b,c,e);return a} function De(a,b,c,e,f){var h=c+(f?0:-1),k=a.length-1;if(k>=1+(f?0:-1)&&h>=k){var l=a[k];if(l!=null&&typeof l==="object"&&l.constructor===Object)return l[c]=e,b}if(h >14&1023||536870912;c>=k?e!=null&&(h={},a[k+(f?0:-1)]=(h[c]=e,h)):a[h]=e}return b} function Ee(a,b,c){a=a.Aa;return Fe(a,a[Ic]|0,b,c)!==void 0} function Ge(a,b,c,e){var f=a.Aa;return Fe(f,f[Ic]|0,b,He(a,e,c))!==void 0} function Ie(a,b){return Ke(a,a[Ic]|0,b)} function Le(a,b,c){var e=a.Aa;return Me(a,e,e[Ic]|0,b,c,3).length} function Ne(a,b,c,e,f){Oe(a,b,c,f,e,1);return a} function Pe(a){return a===Vc?2:4} function Qe(a,b,c,e,f,h,k){var l=a.Aa,p=l[Ic]|0;e=Qc(a,p)?1:e;f=!!f||e===3;e===2&&we(a)&&(l=a.Aa,p=l[Ic]|0);var r=Re(l,b,k),t=r===Jc?7:r[Ic]|0,w=Se(t,p);var y=w;4&y?h==null?a=!1:(!f&&h===0&&(512&y||1024&y)&&(a.constructor[wba]=(a.constructor[wba]|0)+1) 32)for(e|=(l&127)>>4,f=3;f >>0,e>>>0);throw Error();} function dda(a){return og(a,function(b,c){return aca(b,c,Yba)})} function qg(a,b){a.o=b;if(b>a.oa)throw Error();} function rg(a){var b=a.ma,c=a.o,e=b[c++],f=e&127;if(e&128&&(e=b[c++],f|=(e&127) >>0} function tg(a){return og(a,kd)} function ug(a){return og(a,ld)} function vg(a){return og(a,Yba)} function wg(a){var b=a.ma,c=a.o,e=b[c+0],f=b[c+1],h=b[c+2];b=b[c+3];qg(a,a.o+4);return(e >>0} function xg(a){var b=wg(a);a=wg(a);return Xba(b,a)} function yg(a){var b=wg(a);a=(b>>31)*2+1;var c=b>>>23&255;b&=8388607;return c==255?b?NaN:a*Infinity:c==0?a*1.401298464324817E-45*b:a*Math.pow(2,c-150)*(b+8388608)} function zg(a){var b=wg(a),c=wg(a);a=(c>>31)*2+1;var e=c>>>20&2047;b=4294967296*(c&1048575)+b;return e==2047?b?NaN:a*Infinity:e==0?a*4.9E-324*b:a*Math.pow(2,e-1075)*(b+4503599627370496)} function Ag(a){for(var b=0,c=a.o,e=c+10,f=a.ma;c a.oa)throw Error();a.o=b;return c} function gda(a,b){if(b==0)return vc();var c=fda(a,b);a.Ww&&a.qa?c=a.ma.subarray(c,c+b):(a=a.ma,b=c+b,c=c===b?new Uint8Array(0):Vba?a.slice(c,b):new Uint8Array(a.subarray(c,b)));return c.length==0?vc():new uc(c,tc)} var mg=[];function hda(a,b,c,e){if(mg.length){var f=mg.pop();f.init(a,b,c,e);a=f}else a=new cda(a,b,c,e);this.ma=a;this.qa=this.ma.getCursor();this.o=this.ua=this.oa=-1;this.setOptions(e)} n=hda.prototype;n.setOptions=function(a){a=a===void 0?{}:a;this.UC=a.UC===void 0?!1:a.UC}; function ida(a,b,c,e){if(Bg.length){var f=Bg.pop();f.setOptions(e);f.ma.init(a,b,c,e);return f}return new hda(a,b,c,e)} n.free=function(){this.ma.clear();this.o=this.oa=this.ua=-1;Bg.length >>3,e=b&7;if(!(e>=0&&e =b?mb():(p=a[h++],l =b-1?mb():(p=a[h++],(p&192)!==128||l===224&&p =160||((f=a[h++])&192)!==128?(h--,mb()):c.push((l&15) =b-2?mb():(p=a[h++],(p&192)!==128||(l >30!==0||((f=a[h++])&192)!==128||((e=a[h++])&192)!==128?(h--,mb()):(l=(l&7) >10&1023)+55296,(l&1023)+56320))):mb(),c.length>=8192&&(k=vaa(k,c),c.length=0);h=vaa(k,c)}return h} function Fg(a){var b=sg(a.ma);return gda(a.ma,b)} function Gg(a,b,c){var e=sg(a.ma);for(e=a.ma.getCursor()+e;a.ma.getCursor() >>0;this.o=b>>>0} function kda(a){a=BigInt.asUintN(64,a);return new Hg(Number(a&BigInt(4294967295)),Number(a>>BigInt(32)))} function Ig(a){if(!a)return lda||(lda=new Hg(0,0));if(!/^\d+$/.test(a))return null;md(a);return new Hg(bd,cd)} var lda;function Jg(a,b){this.ma=a>>>0;this.o=b>>>0} function mda(a){a=BigInt.asUintN(64,a);return new Jg(Number(a&BigInt(4294967295)),Number(a>>BigInt(32)))} function Kg(a){if(!a)return nda||(nda=new Jg(0,0));if(!/^-?\d+$/.test(a))return null;md(a);return new Jg(bd,cd)} var nda;function Lg(){this.o=[]} Lg.prototype.length=function(){return this.o.length}; Lg.prototype.end=function(){var a=this.o;this.o=[];return a}; function Mg(a,b,c){for(;c>0||b>127;)a.o.push(b&127|128),b=(b>>>7|c >>0,c>>>=7;a.o.push(b)} function Og(a,b){for(;b>127;)a.o.push(b&127|128),b>>>=7;a.o.push(b)} function Pg(a,b){if(b>=0)Og(a,b);else{for(var c=0;c >=7;a.o.push(1)}} function oda(a,b){md(b);Zba(function(c,e){Mg(a,c>>>0,e>>>0)})} Lg.prototype.writeUint8=function(a){this.o.push(a>>>0&255)}; function Qg(a,b){a.o.push(b>>>0&255);a.o.push(b>>>8&255);a.o.push(b>>>16&255);a.o.push(b>>>24&255)} Lg.prototype.writeInt8=function(a){this.o.push(a>>>0&255)};function pda(){this.oa=[];this.ma=0;this.o=new Lg} function Rg(a,b){b.length!==0&&(a.oa.push(b),a.ma+=b.length)} function Sg(a,b){Tg(a,b,2);b=a.o.end();Rg(a,b);b.push(a.ma);return b} function Ug(a,b){var c=b.pop();for(c=a.ma+a.o.length()-c;c>127;)b.push(c&127|128),c>>>=7,a.ma++;b.push(c);a.ma++} function Tg(a,b,c){Og(a.o,b*8+c)} function qda(a,b,c){if(c!=null)switch(Tg(a,b,0),typeof c){case "number":a=a.o;fd(c);Mg(a,bd,cd);break;case "bigint":c=mda(c);Mg(a.o,c.ma,c.o);break;default:c=Kg(c),Mg(a.o,c.ma,c.o)}} function rda(a,b,c){if(c!=null)switch(sda(c),Tg(a,b,1),typeof c){case "number":a=a.o;ed(c);Qg(a,bd);Qg(a,cd);break;case "bigint":c=kda(c);a=a.o;b=c.o;Qg(a,c.ma);Qg(a,b);break;default:c=Ig(c),a=a.o,b=c.o,Qg(a,c.ma),Qg(a,b)}} function tda(a,b,c){c!=null&&(c=parseInt(c,10),Tg(a,b,0),Pg(a.o,c))} function Wg(a,b,c){Tg(a,b,2);Og(a.o,c.length);Rg(a,a.o.end());Rg(a,c)} function Xg(a,b,c,e){c!=null&&(b=Sg(a,b),e(c,a),Ug(a,b))} function uda(a){switch(typeof a){case "string":Kg(a)}} function sda(a){switch(typeof a){case "string":Ig(a)}} ;function Yg(){function a(){throw Error();} Object.setPrototypeOf(a,a.prototype);return a} var Zg=Yg(),vda=Yg(),$g=Yg(),ah=Yg(),bh=Yg(),wda=Yg(),xda=Yg(),ch=Yg(),yda=Yg(),zda=Yg(),dh=Yg(),eh=Yg(),fh=Yg(),gh=Yg(),hh=Yg();function ih(a,b,c){this.Aa=se(a,b,c)} n=ih.prototype;n.toJSON=function(){return Lca(this)}; n.serialize=function(a){return JSON.stringify(Lca(this,a))}; function jh(a,b){if(b==null||b=="")return new a;b=JSON.parse(b);if(!Array.isArray(b))throw Error("dnarr");return new a(Oc(b))} function kh(a,b){return a===b||a==null&&b==null||!(!a||!b)&&a instanceof b.constructor&&qca(a,b)} n.clone=function(){var a=this.Aa,b=a[Ic]|0;return ve(this,a,b)?ue(this,a,!0):new this.constructor(te(a,b,!1))}; n.Gr=function(){return!Qc(this)}; function lh(a,b,c){Eca(a,b.fieldIndex);return b.ctor?b.oa(a,b.ctor,b.fieldIndex,c,b.o):b.oa(a,b.fieldIndex,c,b.o)} n.toBuilder=function(){return he(this)}; ih.prototype[Aba]=Hba;ih.prototype.toString=function(){return this.Aa.toString()}; function Ada(a,b){if(b==null)return new a;if(!Array.isArray(b))throw Error();if(Object.isFrozen(b)||Object.isSealed(b)||!Object.isExtensible(b))throw Error();return new a(Oc(b))} ;function mh(a,b,c){this.o=a;this.ma=b;a=jb(Zg);(a=!!a&&c===a)||(a=jb(vda),a=!!a&&c===a);this.oa=a} function nh(a,b){var c=c===void 0?Zg:c;return new mh(a,b,c)} function Bda(a,b,c,e,f){Xg(a,c,oh(b,e),f)} var Cda=nh(function(a,b,c,e,f){if(a.o!==2)return!1;Dg(a,kf(b,e,c),f);return!0},Bda),Dda=nh(function(a,b,c,e,f){if(a.o!==2)return!1; Dg(a,kf(b,e,c),f);return!0},Bda),qh=Symbol(),rh=Symbol(),sh=Symbol(),Eda=Symbol(),Fda=Symbol(),th,uh; function vh(a,b,c,e){var f=e[a];if(f)return f;f={};f.NQ=e;f.Hv=Oca(e[0]);var h=e[1],k=1;h&&h.constructor===Object&&(f.extensions=h,h=e[++k],typeof h==="function"&&(f.lL=!0,th!=null||(th=h),uh!=null||(uh=e[k+1]),h=e[k+=2]));for(var l={};h&&Gda(h);){for(var p=0;p 0} function Hda(a){return Array.isArray(a)?a[0]instanceof mh?a:[Dda,a]:[a,void 0]} function oh(a,b){if(a instanceof ih)return a.Aa;if(Array.isArray(a))return re(a,b)} ;function wh(a,b,c,e){var f=c.o;a[b]=e?function(h,k,l){return f(h,k,l,e)}:f} function xh(a,b,c,e,f){var h=c.o,k,l;a[b]=function(p,r,t){return h(p,r,t,l||(l=vh(rh,wh,xh,e).Hv),k||(k=yh(e)),f)}} function yh(a){var b=a[sh];if(b!=null)return b;var c=vh(rh,wh,xh,a);b=c.lL?function(e,f){return th(e,f,c)}:function(e,f){for(;jda(f)&&f.o!=4;){var h=f.oa,k=c[h]; if(k==null){var l=c.extensions;l&&(l=l[h])&&(l=Ida(l),l!=null&&(k=c[h]=l))}if(k==null||!k(f,e,h)){k=f;l=k.qa;Cg(k);if(k.UC)var p=void 0;else{var r=k.ma.getCursor()-l;k.ma.setCursor(l);p=gda(k.ma,r)}r=l=k=void 0;var t=e;p&&((k=(l=(r=t[Gc])!=null?r:t[Gc]=new le)[h])!=null?k:l[h]=[]).push(p)}}if(e=ke(e))e.zG=c.NQ[Fda];return!0}; a[sh]=b;a[Fda]=Jda.bind(a);return b} function Jda(a,b,c,e){var f=this[rh],h=this[sh],k=re(void 0,f.Hv),l=ke(a);if(l){var p=!1,r=f.extensions;if(r){f=function(pa,ta,Aa){if(Aa.length!==0)if(r[ta])for(pa=v(Aa),ta=pa.next();!ta.done;ta=pa.next()){ta=ida(ta.value);try{p=!0,h(k,ta)}finally{ta.free()}}else e==null||e(a,ta,Aa)}; if(b==null)me(l,f);else if(l!=null){var t=l[b];t&&f(l,b,t)}if(p){var w=a[Ic]|0;if(w&2&&w&2048&&(c==null||!c.yV))throw Error();var y=Xc(w),E=function(pa,ta){if(Be(a,pa,y)!=null)switch(c==null?void 0:c.Sqa){case 1:return;default:throw Error();}ta!=null&&(w=De(a,w,pa,ta,y));delete l[pa]}; b==null?Kba(k,k[Ic]|0,function(pa,ta){E(pa,ta)}):E(b,Be(k,b,y))}}}} function Ida(a){a=Hda(a);var b=a[0].o;if(a=a[1]){var c=yh(a),e=vh(rh,wh,xh,a).Hv;return function(f,h,k){return b(f,h,k,e,c)}}return b} ;function zh(a,b,c){a[b]=c.ma} function Ah(a,b,c,e){var f,h,k=c.ma;a[b]=function(l,p,r){return k(l,p,r,h||(h=vh(qh,zh,Ah,e).Hv),f||(f=Kda(e)))}} function Kda(a){var b=a[Eda];if(!b){var c=vh(qh,zh,Ah,a);b=function(e,f){return Lda(e,f,c)}; a[Eda]=b}return b} function Lda(a,b,c){Kba(a,a[Ic]|0,function(e,f){if(f!=null){var h=Mda(c,e);h?h(b,f,e):e >BigInt(63);bd=Number(BigInt.asUintN(32,b));cd=Number(BigInt.asUintN(32,b>>BigInt(32)));Mg(a,bd,cd);break;default:oda(a.o,b)}},zda),oea=[!0, x,ci],Ai=[!0,x,hi],pea=[!0,x,x];function Bi(a,b,c){this.fieldIndex=a;this.ctor=c;this.isRepeated=0;this.ma=lf;this.oa=of;this.defaultValue=void 0;this.o=b.messageId!=null?Lba:void 0} Bi.prototype.register=function(){Zb(this)};function Ci(a,b){return function(c,e){var f={gB:!0};e&&Object.assign(f,e);c=ida(c,void 0,void 0,f);try{var h=new a,k=h.Aa;yh(b)(k,c);var l=h}finally{c.free()}return l}} function Di(a){return function(){return Pda(this,a)}} function Ei(a){return Yc(function(b){return b instanceof a&&!Qc(b)})} function Fi(a){return function(b){return jh(a,b)}} ;var qea=[0,[4],vi,2,oi,[0,hi,-1]];var Gi=[0,vi];var rea=[0,Gi,qea,Wh];var sea=[0,vi,bi,Wh];function Hi(a){this.Aa=se(a)} u(Hi,ih);Hi.prototype.getLanguage=function(){return Ef(this,3)}; Hi.prototype.setLanguage=function(a){return dg(this,3,a)};var tea=[0,x,Wh,x];Hi.prototype.Ca=Di(tea);var uea=[0,Wh,-1];function Ii(a){this.Aa=se(a)} u(Ii,ih);var Ji=[2,3];var Ki=[0,Ji,Wh,oi,uea,oi,tea];Ii.prototype.Ca=Di(Ki);var Li=[0,vi,bi];var vea=[0,x,-1];function Mi(a){this.Aa=se(a)} u(Mi,ih);Mi.prototype.Tf=function(){return Ef(this,4)};var Ni=[0,Wh,vi,hi,x,-1,ni,vea,vi,-1,ni,[0,[5,6,7,8],x,-3,oi,[0,x,-2],oi,[0,x,-3,ni,[0,x,-5]],oi,[0,x,-2],oi,[0,x,-1]],hi];Mi.prototype.Ca=Di(Ni);var Oi=[0,Wh,-1];function Pi(a){this.Aa=se(a)} u(Pi,ih);Pi.prototype.getType=function(){return Ff(this,1,1)}; Pi.prototype.setType=function(a){return fg(this,1,a)};var wea=[0,vi,Oi,-1,Wh,-1,Oi,-3];Pi.prototype.Ca=Di(wea);function Qi(a){this.Aa=se(a)} u(Qi,ih);Qi.prototype.getId=function(){return Cf(this,1)}; Qi.prototype.setId=function(a){return $f(this,1,a)}; function Ri(a){return wf(a,1)} ;function Si(a){this.Aa=se(a)} u(Si,ih);Si.prototype.getState=function(){return Ff(this,1)}; Si.prototype.getVisibility=function(){return Ff(this,2)}; Si.prototype.setVisibility=function(a){return fg(this,2,a)}; Si.prototype.clearOffTopic=function(){return Ce(this,7)};function Ti(a){this.Aa=se(a)} u(Ti,ih);n=Ti.prototype;n.getInfo=function(){return lf(this,Qi,1)}; n.getIndex=function(){return Df(this,2)}; n.getMetadata=function(){return lf(this,Si,5)}; n.Lf=function(a){return of(this,Si,5,a)}; n.getTypeInfo=function(){return lf(this,Pi,6)}; n.aE=la(0);n.getLanguage=function(){return Ef(this,39)}; n.setLanguage=function(a){return dg(this,39,a)}; n.gp=la(2);var xea=[0,vi,Wh,-1];var Ui=[0,[4,5,6,7],vi,Wh,-1,zi,-3];var Vi=[0,Ph,-1,hi,x,-2];var Wi=[0,x,-1,ci,x,vi,-1,Gi,x,vi,-1,x,hi];var yea=[0,x,-3,ni,[0,x,-1,vi],ki];var Xi=[0,Wh,ai,Wh,bi];Qi.prototype.Ca=Di(Xi);var zea=[0,hi,bi,hi,wi];var Yi=[0,vi,-1,hi,Gi,x,-1,hi,-2,zea];Si.prototype.Ca=Di(Yi);var Zi=[0,qi,bi,-1,x];var $i=[0,Xi,bi,Wh,x,Yi,wea,-1,1,ni,Wi,1,vi,bi,vi,yea,x,Wh,bi,17,Vi,xea,Wh,ni,Zi,x,-1,1,Ni,Ui,ni,Ni,Li];Ti.prototype.Ca=Di($i);var Aea=[0,vi,bi];var Bea=[0,x,-1];var Cea=[0,x,-1];function aj(a){this.Aa=se(a)} u(aj,ih);n=aj.prototype;n.getKey=function(){return Of(this,1)}; n.setKey=function(a){return dg(this,1,a)}; n.getValue=function(){return Of(this,2)}; n.setValue=function(a){return dg(this,2,a)}; n.Tb=function(){return ig(this,2)};var Dea=[0,x,-1];aj.prototype.Ca=Di(Dea);var Eea=[0,Wh,-2,bi,vi,[0,vi,-1,Wh,-1],Wh];function bj(a){this.Aa=se(a)} u(bj,ih);n=bj.prototype;n.getInfo=function(){return lf(this,Qi,1)}; n.Ms=la(4);n.getTitle=function(){return Of(this,9)}; n.setTitle=function(a){return dg(this,9,a)}; n.getLanguage=function(){return Of(this,14)}; n.setLanguage=function(a){return dg(this,14,a)}; n.getState=function(){return Ff(this,15,10)}; n.setProperty=function(a,b){return Ne(this,16,aj,a,b)}; n.getMetadata=function(){return lf(this,Si,12)}; n.Lf=function(a){return of(this,Si,12,a)}; n.bE=la(5);n.Bc=function(){return Of(this,22)}; n.Yb=function(){return Jf(this,44)}; n.Lc=function(a,b){return af(this,44,Vd,a,b,Xd)}; n.lw=la(6);var cj=[49,50];var Fea=[0,vi,Ph,Wh,-1];var Gea=[0,x,hi,x,Wh,1,x,-1,Wh,1,x,Wh,vi,-1];var Hea=[0,Wh,vi,x];var Iea=[0,x,-6,ki,hi,2,Wh,[0,x,ui,-1],-4];var Jea=[0,Iea,Gea,vi,ni,Hea,hi];var dj=[0,cj,Xi,2,hi,-1,1,Wh,bi,x,bi,1,Yi,x,-1,vi,ni,Dea,bi,ni,Wi,1,bi,vi,x,bi,vi,hi,Ki,yea,vi,x,-1,Wh,vi,Xh,ni,Eea,Vi,hi,Wh,xea,bi,ni,Fea,bi,1,Ki,ki,x,ki,ni,Zi,x,oi,Bea,oi,Cea,hi,Jea,bi,x,Ui,hi,Aea,Li,x];bj.prototype.Ca=Di(dj);var ej=[0,vi,hi];var Kea=[0,ui,-2];var Lea=[0,hi,-4];var Mea=[0,5,Rh,hi,-1,vi];var fj=[0,1,Wh,vi,ki,wi];var gj=[0,fj,Mea,ni,Kea,-6];var Nea=[0,rea,-2,ci,hi,Yh,ni,sea];function hj(a){this.Aa=se(a)} u(hj,ih);hj.prototype.getLanguage=function(a){return Jf(this,5,a)}; hj.prototype.setLanguage=function(a,b){return af(this,5,Vd,a,b,Xd)};var Oea=[0,x,hi,-2,ki,x,hi,Xh,hi,x,bi,x,Lea,ej,vi,-1,x,hi,-2,Wh,hi,Wh,hi,-1,Yh,Wh,-1,hi];hj.prototype.Ca=Di(Oea);function ij(a){this.Aa=se(a)} u(ij,ih);ij.prototype.getName=function(){return Ef(this,1)}; ij.prototype.Sf=function(){return Of(this,1)}; ij.prototype.setName=function(a){return dg(this,1,a)}; ij.prototype.tf=la(10);var jj=[0,x,-1,Wh,x,-3];ij.prototype.Ca=Di(jj);function kj(a){this.Aa=se(a)} u(kj,ih);function lj(a,b){return of(a,ij,2,b)} kj.prototype.yk=la(11);kj.prototype.gH=function(a){return of(this,hj,3,a)};var mj=[0,Wh,jj,Oea,hi,-1,Gi,Wi,Nea,hi,Ui];kj.prototype.Ca=Di(mj);var Pea=[0,ki];var Qea=[0,x];var nj=[0,x,-1];var oj=[0,Wh,-2,ni,nj,x,hi,-1];var Rea=[0,Wh,-2,x,-1];function pj(a){this.Aa=se(a)} u(pj,ih);pj.prototype.getSeconds=function(){return Cf(this,1)}; pj.prototype.setSeconds=function(a){return Ye(this,1,Kd(a),"0")}; pj.prototype.getNanos=function(){return Bf(this,2)}; pj.prototype.setNanos=function(a){return Ye(this,2,Cd(a),0)}; function qj(a){var b=Number;var c=c===void 0?"0":c;var e;var f=(e=ada(a,1))!=null?e:c;b=b(f);a=a.getNanos();return new Date(b*1E3+a/1E6)} function rj(){var a=new Date(Date.now()),b=new pj;a=a.getTime();Number.isFinite(a)||(a=0);return b.setSeconds(Math.floor(a/1E3)).setNanos((a%1E3+1E3)%1E3*1E6)} ;function sj(a){this.Aa=se(a)} u(sj,ih);var tj=[0,Zh,fi];pj.prototype.Ca=Di(tj);var uj=[0,ni,oj,x,Gh,Ai,ni,Qea,ni,Rea,x,[0,[0,vi,tj],tj],Gh,[!0,Wh,Pea]];sj.prototype.Ca=Di(uj);var vj=[0,ni,function(){return vj}, x,-3,Xh,hi,ni,function(){return vj}, hi,vi,x,vi,x,-1,vi];function wj(a){this.Aa=se(a)} u(wj,ih);n=wj.prototype;n.getName=function(){return Ef(this,1)}; n.Sf=function(){return Of(this,1)}; n.setName=function(a){return dg(this,1,a)}; n.tf=la(9);n.Uo=function(){return Af(this,3)}; n.Qh=function(a){return Xf(this,3,a)};var xj=[0,x,-1,hi,Wh];wj.prototype.Ca=Di(xj);function yj(a){this.Aa=se(a)} u(yj,ih);yj.prototype.getFrdIdentifier=function(){return Ff(this,1)}; function zj(a,b){return fg(a,1,b)} yj.prototype.Yq=function(){return Ff(this,2)}; yj.prototype.Wc=function(a){return fg(this,2,a)};function Aj(a){this.Aa=se(a)} u(Aj,ih);Aj.prototype.Lg=function(a){return Xe(this,1,a,cca)}; Aj.prototype.getValue=function(a){var b=Kf(this,3,void 0,!0);Tc(b,a);return b[a]}; Aj.prototype.setValue=function(a,b){return af(this,1,cca,a,b,Ve)};function Bj(a){this.Aa=se(a)} u(Bj,ih);function Cj(a){return Qe(a,1,Qd,1,void 0,1024)} function Sea(a,b){return Xe(a,1,b,Gd)} ;function Dj(a){this.Aa=se(a)} u(Dj,ih);function Ej(a){return Qe(a,1,Qd,1,void 0,1024)} Dj.prototype.Lg=function(a){return Xe(this,1,a,Gd)}; Dj.prototype.getValue=function(a){return Hf(this,1,a)}; Dj.prototype.setValue=function(a,b){return af(this,1,Gd,a,b,Od)};function Fj(a){this.Aa=se(a)} u(Fj,ih);function Gj(a){return nf(a,Dj,1,Pe())} function Hj(a,b){return qf(a,1,b)} ;function Ij(a){this.Aa=se(a)} u(Ij,ih);function Jj(a,b){return If(a,1,Pe(b))} Ij.prototype.Lg=function(a){return Xe(this,1,a,Vd)}; Ij.prototype.getValue=function(a){return Jf(this,1,a)}; Ij.prototype.setValue=function(a,b){return af(this,1,Vd,a,b,Xd)};function Kj(a){this.Aa=se(a)} u(Kj,ih);function Lj(a){return Pf(a,Ij,8,Rf)} function Mj(a,b){return pf(a,8,Rf,b)} n=Kj.prototype;n.zg=function(){return Pf(this,Dj,2,Rf)}; n.Ji=function(a){return pf(this,2,Rf,a)}; n.ej=function(){return Pf(this,Ij,3,Rf)}; n.Kg=function(a){return pf(this,3,Rf,a)}; function Nj(a){return Pf(a,Bj,4,Rf)} function Oj(a,b){return pf(a,4,Rf,b)} function Pj(a){return Pf(a,Aj,5,Rf)} function Qj(a,b){return pf(a,5,Rf,b)} n.hm=function(){return Pf(this,Fj,6,Rf)}; n.hw=function(a){return pf(this,6,Rf,a)}; n.Uo=function(){return Lf(this,7,Rf)}; n.Qh=function(a){return bf(this,7,Rf,vd(a))}; var Rf=[2,3,4,5,6,7,8];function Rj(a){this.Aa=se(a)} u(Rj,ih);Rj.prototype.getFrdContext=function(){return lf(this,yj,1)}; function Sj(a,b){return of(a,yj,1,b)} Rj.prototype.Oy=function(){return Ee(this,yj,1)}; Rj.prototype.getFrdIdentifier=function(){return Ff(this,5)}; function Tj(a,b){return fg(a,5,b)} function Uj(a){return lf(a,Kj,2)} function Vj(a,b){return of(a,Kj,2,b)} Rj.prototype.setFieldName=function(a){return dg(this,4,a)};var Wj=[0,Wh,x];var Yj=[0,vi,-1];yj.prototype.Ca=Di(Yj);var Tea=[0,ri];Aj.prototype.Ca=Di(Tea);var Uea=[0,Xh];Bj.prototype.Ca=Di(Uea);var Zj=[0,Xh];Dj.prototype.Ca=Di(Zj);var Vea=[0,ni,Zj];Fj.prototype.Ca=Di(Vea);var ak=[0,ki];Ij.prototype.Ca=Di(ak);var bk=[0,Rf,1,oi,Zj,oi,ak,oi,Uea,oi,Tea,oi,Vea,ji,oi,ak];Kj.prototype.Ca=Di(bk);var ck=[0,Yj,bk,vi,x,vi,bk];Rj.prototype.Ca=Di(ck);var Wea=[0,1,x,3,x,vi,2,x];var Xea=[0,x,hi,-1,Xh,hi,x,-2];var Yea=[0,x,-4,ni,[0,x,Xh]];var dk=[0,x,-1,vi,x,Xh,x,-1,hi,91,x];var Zea=[0,x,-1,[0,ki],x];var $ea=[0,ni,nj];var afa=[0,x,-2,hi,ki,hi];var bfa=[0,x,Wh];var ek=[0,Wj,ck,-1,ni,ck];var cfa=[0,x,-2,vi];var dfa=[0,x,ni,[0,x,vi]];var efa=[0,x];var ffa=[0,x,vi];var gfa=[0,x,-2];var hfa=[0,vi,1,vi,ni,[0,vi,x,-1]];var ifa=[0,[4],vi,ci,x,gi,x];var jfa=[0,ni,[0,[2,3],x,oi,[0,ki],oi,[0,x],hi,-1],vi];var kfa=[0,x,-2];var lfa=[0,hi,ci];var mfa=[0,lfa];var nfa=[0,ci];var gk=[0,Gh,[!0,x,function(){return fk}]],fk=[0, [1,2,3,4,5,6],zi,Qh,mi,ji,oi,function(){return gk}, oi,function(){return ofa}],ofa=[0, ni,function(){return fk}];var pfa=[0,x,vi,[0,hi,ni,[0,vi,ni,[0,x,-2,fk]]],[0,hi,ni,[0,x,-1,ni,[0,x,-1]]]];var qfa=[0,ni,[0,x,ci,hi,vi,hi,vi,[0,vi,x],pfa],ci,vi,pfa,hi];var rfa=[0,vi,ni,nj];var sfa=[0,vi,2,wi];var tfa=[0,x,-1,ci];var ufa=[0,x,-1,hi,-1,x,-1,1,hi,Xh,ck,sfa,Yh,ki];function hk(a){this.Aa=se(a)} u( | 2026-01-13T08:48:41 |
https://openapi.tools/categories/security | Security | OpenApi.tools, from APIs You Won't Hate Sponsored by Zudoku - Open-source, highly customizable API documentation powered by OpenAPI Get Started Sponsor openapi.tools GitHub Get Started All Tools All Categories Legacy Tools Contributing Sponsors Sponsor Badges Collections Arazzo Support Overlays Support Open Source Tools SaaS Tools OpenAPI Tool Categories Annotations Code generators Converters Data Validators Documentation Domain-Specific Languages (DSLs) Gateways HTTP Clients IDEs and GUI Editors Learning Miscellaneous Mock Servers Monitoring OpenAPI-aware Frameworks Parsers Schema Validators SDK Generators Security Server Implementations Testing Text Editors © 2026 APIs You Won't Hate Get in touch to become a Sponsor . This site is community-driven and OSS , built with Astro and hosted on Netlify . Security By poking around your OpenAPI description, some tools can look out for attack vectors you might not have noticed. Security There are additional tools in this category, but they only support legacy versions of OpenAPI. If you really need to work with some old OpenAPI descriptions perhaps these legacy tools could be of use * * * | 2026-01-13T08:48:41 |
https://parenting.forem.com/privacy#a-information-you-provide-to-us-directly | Privacy Policy - Parenting 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 Parenting Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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 Parenting — 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. 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 . Parenting © 2016 - 2026. Navigating the chaos and joy of parenting. Log in Create account | 2026-01-13T08:48:41 |
https://survivejs.com/consulting/ | SurviveJS - Consulting Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Consulting Since officially starting my personal limited company in 2016, I have occasionally worked as a consultant to earn additional income and to develop my competence as consulting cases allow me to stay grounded in reality. In addition, I’ve been pursuing a doctorate since 2022 at Aalto University ↗ . Services I offer a variety of services and I have listed examples below. Custom development Occasionally I have been hired to perform custom development. Example cases include developing a complex table component or building up a new system in collaboration with a design system developer. I understand different aspects of modern frontend development well and work best in the interface between frontend and backend that you might characterize as the backend of the frontend. Workshops To train up staff, I have run several workshops throughout the years in my specialized topics. I have focused mainly on webpack and React although I have given workshops on topics like Deno and Qwik too. These days I prefer a hands-on approach and like to run my workshops through predesigned katas that allow attendees at different levels understand the topic and dive straight into the topic. I can also provide a short lecture on the topic in the beginning if needed. Conference organizing I have been running conferences since 2017 ( React Finland ↗ , GraphQL Finland ↗ , Future Frontend ↗ ) and have gained a strong understanding on how the business works. I have run both physical and online events and have operated mainly as a conference director focused on the big picture (concept, speakers, marketing). In case you have questions related how to build up your own concept, I might some kind of answers to this. Research Since 2022, I have been working as a doctoral researcher for Aalto University. Through my research, I have learned how the world of scientific publishing works. I have not done any commercial research cases but I have not ruled out the option in case a suitable case becomes available. I have done mainly surveys and empirical research so I understand both qualitative and quantitative ends of the spectrum. See my research outputs if you are interested in the academic side. Cleaning up Let's face it, not all development is clean and sometimes you have to go fast and make a mess. That is the situation when you might need someone like me to address your technical debt in a fast and effective manner. I can support your clean-up efforts on different levels by for example doing a superficial review to provide clear points for improvements or dig down into details and for example migrate your webpack configuration to the latest standard or a more effective tool. Coaching These days I tend to work a lot with university students as they learn academic writing. In case you are looking for a personal coach, you could hire me to spend a focused hour or two per week around development and JavaScript related topics in your mind to grow as a professional. I am happy to provide my expertise to you in the form of coaching. References I have worked with numerous companies during my career as a consultant. To mention some, consider the following list: AlphaSense ↗ , eBay ↗ , Kitchen Reklamebyrå ↗ , Kleiner Perkins ↗ , Typeform ↗ , Wix ↗ , Xeneta ↗ . Consulting examples I negotiate each consulting case to fit the needs of the client. For example, with Kapsch ↗ I helped the company to facilitate refactoring of an internal tool including two days of on-site training. With eBay ↗ , I helped the company with internal training and development work. For Typeform ↗ , I did a full week on-site with training on relevant topics as needed. These are only a few cases out of many and the offering is always customized to suit the needs of the client. Testimonials I have listed several of my testimonials below. In some cases I bring needed additional expertise on board through my broad personal networks to complement my own knowledge. Kapsch ↗ - “Great and helpful workshops with @bebraw @filipematossilv and @wSokra Thank you, guys. Great work!” Source ↗ . Namics ↗ - “This will bring our Webpack builds to the next level: great workshop with deep knowledge from @bebraw and @wsokra. Thank you guys!” Quantifio ↗ - “I learned and understood more of webpack in a two-hour masterclass than all previous training combined. Juho has the skills and repertoire to improvise content and fine tune relevancy - he connected the dots on specific topics in an Electron environment and had the answers you wont find online.” How to hire me? In case you are interested in hiring me or collaborating in some manner, please fill my contact form ↗ and I will get back to you. Generally more specialized and intense work tends to be more expensive while lower commitment tends to come with a lower price. I cannot guarantee instant or full-time availability, but the situation can change fast so it is worth sending a query regardless. Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://docs.python.org/3/tutorial/controlflow.html#recap | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | 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:48:41 |
https://openapi.tools/categories/schema-validators | Schema Validators | OpenApi.tools, from APIs You Won't Hate Sponsored by Zudoku - Open-source, highly customizable API documentation powered by OpenAPI Get Started Sponsor openapi.tools GitHub Get Started All Tools All Categories Legacy Tools Contributing Sponsors Sponsor Badges Collections Arazzo Support Overlays Support Open Source Tools SaaS Tools OpenAPI Tool Categories Annotations Code generators Converters Data Validators Documentation Domain-Specific Languages (DSLs) Gateways HTTP Clients IDEs and GUI Editors Learning Miscellaneous Mock Servers Monitoring OpenAPI-aware Frameworks Parsers Schema Validators SDK Generators Security Server Implementations Testing Text Editors © 2026 APIs You Won't Hate Get in touch to become a Sponsor . This site is community-driven and OSS , built with Astro and hosted on Netlify . Schema Validators Check your API description or schema to see if it is valid OpenAPI. Schema Validators There are additional tools in this category, but they only support legacy versions of OpenAPI. If you really need to work with some old OpenAPI descriptions perhaps these legacy tools could be of use * * * | 2026-01-13T08:48:41 |
https://dev.to/vjnvisakh/mastering-interview-body-language-techniques-a-guide-to-non-verbal-communication-58nb#comments | Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication - 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 Visakh Vijayan Posted on Jan 11 • Originally published at dumpd.in Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication # career # interview # tutorial Interview (8 Part Series) 1 Unveiling the Top 50 Full-Stack Interview Questions 2 Unveiling the Top 50 Python Interview Questions: A Deep Dive into Python Proficiency ... 4 more parts... 3 Unlocking the Future: Top 50 DevOps Interview Questions You Must Know 4 Unveiling the Top 50 Cloud Computing Interview Questions 5 Mastering Full-Stack: Top 50 Interview Questions Revealed 6 Mastering Frontend Development: Top 50 Interview Questions Revealed 7 Mastering Technical Interviews: Top 50 Tips for Success 8 Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication The Importance of Body Language in Interviews Body language plays a crucial role in communication, often conveying more than words alone. In an interview setting, your body language can influence the perception of your confidence, credibility, and interest in the role. Key Body Language Techniques to Master 1. Eye Contact Eye contact is a powerful form of non-verbal communication that demonstrates attentiveness and confidence. Maintain good eye contact with your interviewer to show your engagement. interviewer = Interviewer() interviewee = Interviewee() interviewer.make_eye_contact(interviewee) 2. Posture Your posture speaks volumes about your confidence and professionalism. Sit up straight, avoid slouching, and lean slightly forward to show interest. interviewee.sit_up_straight() interviewee.avoid_slouching() interviewee.lean_forward() 3. Hand Gestures Use purposeful hand gestures to emphasize key points and convey enthusiasm. Avoid fidgeting or excessive movements that may distract from your message. interviewee.use_hand_gestures() interviewee.avoid_fidgeting() Practicing and Refining Your Body Language Practice your body language techniques in front of a mirror or with a friend to receive feedback. Focus on creating a positive and professional impression through your non-verbal cues. Conclusion Mastering interview body language techniques can significantly enhance your communication skills and overall interview performance. By paying attention to your non-verbal cues, you can convey confidence, credibility, and enthusiasm effectively. Interview (8 Part Series) 1 Unveiling the Top 50 Full-Stack Interview Questions 2 Unveiling the Top 50 Python Interview Questions: A Deep Dive into Python Proficiency ... 4 more parts... 3 Unlocking the Future: Top 50 DevOps Interview Questions You Must Know 4 Unveiling the Top 50 Cloud Computing Interview Questions 5 Mastering Full-Stack: Top 50 Interview Questions Revealed 6 Mastering Frontend Development: Top 50 Interview Questions Revealed 7 Mastering Technical Interviews: Top 50 Tips for Success 8 Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication 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 Visakh Vijayan Follow There is nothing else in this world that gives as much happiness as coding Location Kolkata, West Bengal Education MCA Pronouns he/him/his Work Full Stack Developer at JTC Joined Sep 2, 2018 More from Visakh Vijayan Unleashing the Power of Arrow Functions in JavaScript # beginners # javascript # tutorial Unlocking TypeScript's Power: Mastering Type Guards for Safer, Smarter Code # javascript # tutorial # typescript Unleashing the Power of Enums in TypeScript # typescript # programming # tutorial # beginners 💎 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:48:41 |
https://www.linkedin.com/company/open-source-hardware-association/ | Open Source Hardware Association | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Register now Open Source Hardware Association Civic and Social Organizations Boulder, Colorado 3,282 followers Fostering technological knowledge and encouraging research that is accessible, collaborative and respects user freedom. Follow View all 12 employees Report this company About us The Open Source Hardware Association (OSHWA) aims to foster technological knowledge and encourage research that is accessible, collaborative and respects user freedom. OSHWA’s primary activities include hosting the annual Open Hardware Summit and maintaining the Open Source Hardware certification, which allows the community to quickly identify and represent hardware that complies with the community definition of open source hardware. Website https://www.oshwa.org/ External link for Open Source Hardware Association Industry Civic and Social Organizations Company size 2-10 employees Headquarters Boulder, Colorado Type Nonprofit Founded 2012 Locations Primary Boulder, Colorado 80303, US Get directions Employees at Open Source Hardware Association Wendy Ju Katherine Scott Kunvar Chokshi Michael Weinberg See all employees Updates Open Source Hardware Association 3,282 followers 16h Report this post Curious about what's coming with the Open Healthware Certification? Read all about it right here: https://lnkd.in/dEn5TJqK OSHWA’s New Open Healthware Certification: How We Got Here and Where We’re Going oshwa.org 5 Like Comment Share Open Source Hardware Association reposted this Hackster.io 56,590 followers 6d Report this post 11 new certifications were added to the Open Source Hardware Association database in December, including desktop and pocket PCs along with a CPC machine to measure air quality. Here are a few of OSHWA's favorites from last month! https://lnkd.in/eMSF2dd2 32 Like Comment Share Open Source Hardware Association 3,282 followers 3w Report this post going live in ten minutes! come hang and hear about three really cool porjects! Open Source Hardware Association 3,282 followers 3w TOMORROW! another Show & Tell Monthly livestream with work from Nicolás Méndez, Michael Di-Rocco and Nathan Nifong! Join us to learn about their work and how their projects came together: https://lnkd.in/ezMcDDeB 1 Like Comment Share Open Source Hardware Association 3,282 followers 3w Report this post TOMORROW! another Show & Tell Monthly livestream with work from Nicolás Méndez, Michael Di-Rocco and Nathan Nifong! Join us to learn about their work and how their projects came together: https://lnkd.in/ezMcDDeB 9 Like Comment Share Open Source Hardware Association 3,282 followers 4w Report this post It’s the final week to get your proposals in for OHS2026!! https://lnkd.in/eapzPcPD 10 Like Comment Share Open Source Hardware Association 3,282 followers 1mo Report this post Out on Make magazine! Three new projects we think are sooo cool! Check out Nathan Nifong's Stringman robot, Tanmoy Dutta's Autonoe and our very first Colombian certification from Insituto Technologico Metropolitano. Read more: https://lnkd.in/eS_AywMy Open Source Hardware Certifications for November 2025 - Make: https://makezine.com 17 Like Comment Share Open Source Hardware Association reposted this Hackster.io 56,590 followers 1mo Report this post 15 new certifications were added to the Open Source Hardware Association database last month, including a spectrometer, an LED controller, and a laundry-helping robot. Learn more in OSHWA's November roundup! November 2025 Open Source Hardware Certification Roundup hackster.io 11 Like Comment Share Open Source Hardware Association reposted this Helen Leigh 1mo Report this post I'll be hosting this upcoming livestream on Thurs 18th Dec. My guest will be dr lee wilkins : Cyborg, Chair of the Open Hardware Summit and Exec Director of the Montreal-based hackerspace Radio Snack. We'll be talking about some exciting plans for next year's summit, which will be held in Berlin on Friday May 23rd and Saturday May 24th 2026. The call for proposals is open until the 21st Dec, and ticket sales will start soon. If you have questions or ideas, turn up and share them in the live chat. This is one of my fave events on the calendar and lee is always a delight to hang out with. I am also hoping to be able to share some news about Teardown 2026. I hope some of you will join us! - Open Source Hardware Association Crowd Supply 1,562 followers 1mo Join us for a livestream about Open Hardware Summit 2026! Sponsored by Qorvo, Inc. This content isn’t available here Access this content and more in the LinkedIn app Download the app 23 1 Comment Like Comment Share Open Source Hardware Association reposted this SemiTO-V RISC-V Team 294 followers 1mo Edited Report this post Jeff Geerling has showcased our fully open source RP2350 GPIO Expansion Card in his DC-ROMA RISC-V AI PC review video. Thank you Jeff for trying our little card! Thank you DeepComputing , Framework and NextPCB for sponsoring us! Full video here: https://lnkd.in/dBe9xja4 158 9 Comments Like Comment Share Open Source Hardware Association reposted this Katherine Scott 1mo Report this post It is giving Tuesday, if you would like to keep the future of robotics and hardware free and open source the Open Source Hardware Association and Open Robotics could both really use your help. Smaller open source organizations are not nearly as well-funded as you may think, and they rely on gifts from the community to continue operating. Contributions from large tech companies have fallen significantly since the pandemic, and we need individual donors to step up to help sustain these organizations. If you've ever benefited from downloading a pre-compiled ROS binary from apt, or used an open hardware project as a starting point for your own design, please consider supporting the organizations that make these things possible. OSHWA Donation Page: 🔗 https://lnkd.in/g_qKQK92 OSRF Donation Page: 🔗 https://lnkd.in/gnMuxHMv 62 1 Comment Like Comment Share Join now to see what you are missing Find people you know at Open Source Hardware Association Browse recommended jobs for you View all updates, news, and articles Join now Similar pages Hackster.io Software Development San Francisco, CA Red Rabbit Robotics Robotics Engineering Open Robotics Research Services Mountain View, California OpenCV Non-profit Organizations Open Sauce Entertainment Providers Los Angeles , CA Build a CubeSat Space Research and Technology Jara Primary and Secondary Education San Francisco, California Journal of Open Hardware Book and Periodical Publishing Cambridge, Cambridgeshire Hackaday Computers and Electronics Manufacturing Make: Media Production Santa Rosa, CA Show more similar pages Show fewer similar pages Browse jobs Electronic Engineer jobs 37,860 open jobs Electrical Engineer jobs 60,569 open jobs Intern jobs 71,196 open jobs Mechanical Engineer jobs 46,392 open jobs Engineer jobs 555,845 open jobs More searches More searches Electronic Engineer jobs Product Marketing Intern jobs Summer Intern jobs Product Manager jobs Marketing Manager jobs Intern jobs Research And Development Engineer jobs PHD jobs Mechanical Engineer jobs Scientist jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (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)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at Open Source Hardware Association Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:41 |
https://docs.python.org/3/license.html#select-kqueue | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:48:41 |
https://stackoverflow.com/questions/tagged/package | Newest 'package' Questions - Stack Overflow Skip to main content Stack Overflow About Products For Teams Stack Internal Implement a knowledge platform layer to power your enterprise and AI tools. Stack Data Licensing Get access to top-class technical expertise with trusted & attributed content. Stack Ads Connect your brand to the world’s most trusted technologist communities. Releases Keep up-to-date on features we add to Stack Overflow and Stack Internal. About the company Visit the blog s-popover#show" data-s-popover-placement="bottom-start" /> Loading… current community Stack Overflow help chat Meta Stack Overflow your communities Sign up or log in to customize your list. more stack exchange communities company blog Log in Sign up Home Questions AI Assist Tags Challenges Chat Articles Users Companies Collectives Communities for your favorite technologies. Explore all Collectives Stack Internal Stack Overflow for Teams is now called Stack Internal . Bring the best of human thought and AI automation together at your work. Try for free Learn more Stack Internal Bring the best of human thought and AI automation together at your work. Learn more Collectives™ on Stack Overflow Find centralized, trusted content and collaborate around the technologies you use most. Learn more about Collectives Stack Internal Knowledge at work Bring the best of human thought and AI automation together at your work. Explore Stack Internal 17,018 questions se-uql#toggleEditor"> Newest Active Bountied Unanswered More Bountied 0 Unanswered Frequent Score Trending Week Month Unanswered (my tags) Filter Filter by No answers No upvoted or accepted answers No Staging Ground Has bounty Days old Sorted by Newest Recent activity Highest score Most frequent Bounty ending soon Trending Most activity Tagged with My watched tags The following tags: Apply filter Cancel Best practices 0 votes 4 replies 100 views Record global state variables in R I am trying to write an R package that uses JuliaCall to connect to a julia instance, load a julia library and call it from R (the julia library is called MAGEMin). I therefore need to record the ... r package jfmoyen 517 asked Dec 2, 2025 at 11:18 1 vote 1 answer 126 views How can I programmatically determine the imports for an R function? Suppose I have a function like the below in a large R script, and I am trying to refactor it into a package to make it re-usable in other scripts: mymean <- function(x) { assert_that(is.numeric(... r import package namespaces Ryan C. Thompson 42.4k asked Dec 1, 2025 at 19:43 Advice 1 vote 2 replies 74 views Unable to download package I have issues with downloading "@stream-io/openai-realtime-api" package in NextJS project. Error: enter image description here I tried to clear cash, change registry, used "--legacy-... typescript npm next.js package openai-api Ktsarvi 1 asked Nov 30, 2025 at 18:13 Best practices 0 votes 0 replies 44 views When packaging a bash binary produced by Bazel, do I need to keep the rlocation/data location boilerplate? I was trying to exercise with Bazel by packaging a deb package from a collection of scripts I'm writing to automate a few tasks at work. Right now, I keep them either in /usr/local/bin or \~/.local/... bash deployment package bazel bazel-rules Alessandro Bertulli 682 asked Nov 23, 2025 at 10:11 Tooling 6 votes 1 replies 1k views IntelliCode extensions are deprecated The popular package "IntelliCode" is now deprecated and the replacement is "GitHub Copilot Chat". I have used both packages, the Copilot chat is just annoying to use, most of the ... package vscode-extensions intellicode zeepaul 19 asked Nov 19, 2025 at 14:56 1 vote 3 answers 120 views Building a WAR package, that can be deployed under Tomcat and can be executed in the CLI as well I would like to create a WAR package with maven, that can be deployed under Tomcat (9 or above) and also can be executed on the command line (= CLI). I already realised to make a package, that could ... java maven tomcat package deemon 145 asked Nov 13, 2025 at 17:24 3 votes 1 answer 92 views Unable to install Krona package in Anaconda I'm having issues while trying to install Krona in Anaconda. When I run this line in Anaconda Prompt: conda install -c bioconda krona I get this error: InvalidArchiveError('Error with archive C:\... python installation package anaconda mvcm11235 33 asked Nov 7, 2025 at 12:03 Best practices 0 votes 1 replies 28 views Using stats link functions in Rcpp How can I use C functions from the stats package in C++ code written with Rcpp? I'd like to use the logit link-function and link-inverse from the stats package. Since it's just two simple functions, I ... package rcpp snaut 2,682 asked Nov 3, 2025 at 14:33 1 vote 0 answers 126 views Importing pyannote.audio into collab Installation of all the packages I'm using into the collab environment worked fine However whenever I try to run the following code cell from pyannote.audio.pipelines.speaker_verification import ... installation package google-colaboratory version Yazad Pardiwala 73 asked Oct 29, 2025 at 12:20 1 vote 1 answer 113 views How to download an R package including all dependencies from behind a proxy server My R (and R Studio) cannot access either the CRAN repository or any of its mirrors due to the network's proxy configuration. Though it is not possible to install a package directly with install.... r installation package dependencies repository Glory2Ukraine 1,078 asked Oct 23, 2025 at 6:42 2 votes 0 answers 62 views Python package to compute ekman velocities in the water column from observations? [closed] Is there any python package to compute ekman velocities in the water column from wind data observations? I have wind direction and velocity on an specific location and I would like to obtain a ... python jupyter-notebook package physics ocean Eva Chamorro Garrido 19 asked Oct 16, 2025 at 9:19 0 votes 3 answers 76 views Relative Import With Parent Package src testing test.py utils_dataset px_chol.py another_file.py test.py ---> is calling a class declared in px_chol.py. therefore, it has from utils_dataset.px_chol import CLASS_NAME declaration ... python package Carlo Allocca 697 asked Oct 10, 2025 at 16:49 0 votes 0 answers 90 views Python packages are asking for two different versions of websockets package My python script is using atproto and simpleobsws but they are both asking for incompatible versions of websockets.. simpleobsws 1.4.3 requires websockets>=14.0 atproto 0.0.62 requires websockets&... python python-3.x package version slowcoder 25 asked Oct 10, 2025 at 1:02 -4 votes 1 answer 123 views A global sync.Mutex don't work with multiple client packages? I have a package "tools" that expose a method that must execute some logic only one time. The next calls don't do nothing. The file tools/tools.go is like: package tools import ( "... go concurrency package integration-testing mutex Santiago Rincon 35 asked Oct 10, 2025 at 0:49 0 votes 0 answers 341 views Unreal Engine 5.6.1 Packaging Compiler Error {LogOutputDevice: Error: Ensure condition failed: bCustomPropertyListForPostConstructionInitialized} I'm having a problem that I can't solve because I'm just to rookie for it, and I spent the last day trying to find a solution that it didn't work, I tried to rename it, it didn't work, I tried ... compiler-errors package unreal-engine5 unreal-blueprint Tex 1 asked Oct 7, 2025 at 20:04 -1 votes 1 answer 56 views i got an issue while using location package in flutter Problem : while using location package in flutter i see no implementations found i used the below code in emulator import 'package:location/location.dart'; Future<String> getLocation() async { ... flutter package location SRI SARAN P 1 asked Oct 5, 2025 at 15:18 3 votes 2 answers 147 views How to deal with incompatibility of similar instances of generic packages defined in different translation units in Ada? I've created a generic package called Generic_Functions which must be instantiated in similar fashion to the standard Ada.Numerics.Generic_Real_Arrays and has next specification: with Ada.Numerics.... generics package ada tymurmchyk 71 asked Sep 24, 2025 at 20:08 0 votes 1 answer 123 views How to get git commit of a package? I am using the scarthgap version of yocto to build an image. I managed to build the image, but now I need to get information which git commit is of a gstreamer library. How to do it? git package yocto BЈовић 64.7k asked Sep 23, 2025 at 5:26 0 votes 2 answers 122 views How do I import package when running I have a directory structure that can be simplified like this: test/ scripts/ a.py src/ b.py In a.py, I have the line: import src.b If I'm in the test directory, I want this ... python python-3.x import module package user1801359 422 asked Sep 16, 2025 at 13:25 1 vote 1 answer 293 views 401 invalid credentials error when running source_gist I am trying to install this function from GitHub. I ran this line devtools::source_gist("00772ccea2dd0b0f1745", filename = "001_bag_functions.r") Previously, this has worked for ... r github package gist sofia 21 asked Sep 15, 2025 at 21:01 -3 votes 2 answers 101 views how should I access things of other directory in the same path in java [closed] I have the following file directories: project/ │ ├── A/ │ └── Fuel.java │ └── B/ └── Car.java package A; public class Fuel{ public static fuelLevel(){ ... } } package B; ... java package 0xChaitanya 71 asked Sep 14, 2025 at 17:58 0 votes 0 answers 131 views How to overwrite or delete an existing package version in GitLab Package Registry from CI/CD? I have a GitLab CI/CD pipeline that builds and deploys a package into the GitLab Package Registry. For a specific (and temporary) use case, I need the pipeline to delete the package from the registry ... java spring-boot jar gitlab package Ryley38 401 asked Sep 10, 2025 at 14:09 0 votes 1 answer 45 views How to fix validation error for select SV? When select +503 need to show 8/8, not 11/11 validation How to fix intl_phone_field validation for El Salvador (+503)? It shows 11 digits required, but SV numbers are only 8 digits. I need validation ... flutter package Bavanthi Shanika 1 asked Sep 9, 2025 at 2:50 0 votes 0 answers 61 views Getting "current target" error for "Flutter Run" on Android Emulator After I added assets_audio_player package I started to get this error : FAILURE: Build failed with an exception. What went wrong: Execution failed for task ':assets_audio_player:compileDebugKotlin'. ... android flutter kotlin package flutter-dependencies Tugba Ozkan 61 asked Sep 5, 2025 at 7:36 0 votes 0 answers 113 views MacOS altool validate: Signature in a bundle provisioning profile is Invalid I am trying to build and upload a macOS distribution package to the Apple app store, but I am having difficulty validating the package using xcrun altool --validate-app. Note: I do not use Xcode. I ... macos package certificate software-distribution A Abraham 11 asked Sep 2, 2025 at 19:13 2 votes 1 answer 50 views roxygen and a single help file for multiple data sets, deleting extra information I am trying to create a help file that services multiple data sets that are all similar. However, roxygen generates a sequence of text that says something like "An object of class...", but ... r package roxygen helpfile kpr62 575 asked Aug 31, 2025 at 18:18 0 votes 0 answers 32 views Integrating a flutter application into another, and I'm facing troubles with navigation We had two applications, Let's call them Application A , and Application B. Our company wanted to Integrate App B into A as one app.. So, B will now be a mini-app inside A. The problem with is that ... flutter package integration flutter-navigation materialapp Ziad H. 729 asked Aug 30, 2025 at 11:36 3 votes 1 answer 61 views Can classes owned by a package have package visibility? So far I assumed that classes in a package can have package visibility, as suggested by the quote in The UML User's Guide, 2nd ed. by Booch, Rumbaugh & Jacobson: Package visibility indicates that ... package language-lawyer uml visibility package-diagram Christophe 75.1k asked Aug 8, 2025 at 23:01 0 votes 0 answers 48 views What can corrupt memory in Julia -- "probably modified after bring freed?" I am very new to Julia. I am working on a project written in Julia and I am using the following script: import Pkg Pkg.activate(@__DIR__) project_root = normpath(joinpath(@__DIR__, "..", &... optimization memory package julia Raul Guarini Riva 815 asked Aug 5, 2025 at 20:21 0 votes 0 answers 278 views How to compile Nim code as a Python extension module using Nimpy? I'm working with a set of stateless data processing functions written in Nim, and I want to use them from Python. I initially tried compiling a shared object (.so) file and importing it in Python ... python package nim-lang rookie 11 asked Jul 31, 2025 at 22:52 0 votes 1 answer 64 views How to show both calendar and type-in time input in one modal using react-native-modal-datetime-picker? I'm using the react-native-modal-datetime-picker package in my React Native project and want to display a single modal that contains both: A calendar to select the date A text input (not a clock ... javascript react-native datetime package datetimepicker Anu Robinson 130 asked Jul 29, 2025 at 11:50 0 votes 0 answers 77 views Error: package or namespace load failed for 'caret' (conda environment with r-base = 4.4.3 and r-essentials) Set-up conda version 24.7.1 Created new environment in anaconda prompt: conda create --name r_env2 conda conda-forge::r-essentials conda-forge::r-base=4.4.3 Confirmed that r-essentials included caret ... r package conda load caret KLODell 1 asked Jul 14, 2025 at 0:19 0 votes 0 answers 26 views Python tenserflow.keras is not working properly tensorflow.keras not resolving despite TensorFlow 2.10.0 I'm using TensorFlow 2.10.0 and Keras 2.10.0 inside a conda environment (Python 3.10.16) on Windows, specifically because 2.10.0 is the last ... python package Nadia Harrabi 1 asked Jun 21, 2025 at 11:44 0 votes 0 answers 58 views How can you communicate that a .xcframework is a dependency of the swift package inside Swift package definition? I am sort of trying to do the opposite of what others are doing. I have a target called CopyFramework that creates a CopyFramework.framework within my main xcproj file. I set up this target because a ... swift xcode package CalebK 747 asked Jun 20, 2025 at 22:12 0 votes 0 answers 38 views NuGet include referenced project in the final package I always thought that if I created a project (let's call it "TestNuGet") that referenced another project (let's call it "ReferencedProject") and created the NuGet package for ... .net dll package nuget IFrank 523 asked Jun 19, 2025 at 10:27 1 vote 2 answers 323 views How do I install Lockbox3 in Delphi 12.3? The GetIt version does not seem to work and the repo doesn't seem to have a package for the codecs? I have installed both "Lockbox 3" (2025.03) and "Lockbox VCL and FMX" (2025.03) from the GetIt package manager in Delphi 12.3. The "Lockbox VCL" components (THash, TCodec,... delphi package components lockbox-3 dallin 9,524 asked Jun 19, 2025 at 2:19 1 vote 0 answers 63 views When importing python library, package is sometimes found, at other times not found due to location of file in the project I have the following project structure: PYTHON_DEVELOPMENT [WSL: UBUNTU2504] ├── mattlibrary ├── test_bench │ └── testme.ipynb └── test.ipynb My problem is that when I import mattlibrary inside ... python import package Matt 7,316 asked Jun 18, 2025 at 8:26 0 votes 1 answer 244 views pip dependency conflict requires same version of package I am trying to install fairseq and I had to modify the setup.py file to resolve a dependency conflict. However I still get a conflict error that I can't understand, as it seems that the conflicting ... python pip package dependencies fairseq Alice Mabille 23 asked Jun 4, 2025 at 9:02 1 vote 0 answers 44 views How to start the ebook from where the user left last time in flutter using epub_view Hello guys I am bulding an ebook reader app in flutter and got struck at the bookmark part or where the user left reading last time at the specific page of the EBOOK. Well, I am using epub_view ... flutter dart package epub Arsh 11 asked May 29, 2025 at 12:42 0 votes 1 answer 34 views Python ModuleNotFoundError when importing sibling package inside src/ layout I use VS code with PyLint for my python coding. My main coding language is Matlab but want to transition to Python for doing my scientific computing. This is my first attempt. I have the following ... python import package directory-structure seaphd 1 asked May 19, 2025 at 22:21 0 votes 0 answers 88 views Centreon plugin fails with 'Can't locate ZMQ/LibZMQ4.pm' despite zeromq installed – conflict with system packages I'm trying to use the Centreon plugin for VMware (apps::vmware::connector::plugin) on a poller running RHEL 9 / AlmaLinux 9. The plugin fails with the following error: UNKNOWN: Cannot load module --... module package shared-libraries centreon-api jonathan 1 asked May 16, 2025 at 9:48 0 votes 0 answers 11 views Sync `import.meta` with third party npm package I have both a React app and a npm package built using Vite. The package requires an environment variable to run. /** * main from npm package */ export const checkEnv = () => { console.log(&... npm package environment-variables vite KawaLo 2,442 asked May 15, 2025 at 17:12 0 votes 0 answers 51 views macOS: possible to compile standalone (static-linked) pdf2svg? Under macOS, s it possible to compile/package pdf2svg so that it doesn't require separate libaries (Cairo, Poppler, etc.)? I distribute a freeware ApppleScript applet that uses Ghostscript to convert ... macos pdf compilation package emendelson 551 asked May 15, 2025 at 12:16 0 votes 0 answers 22 views Couldn't find executable named imu_tf_pose below /home/slam/catkin_ws/src/imu_path I create a new package IMU_path the following step is the create process. mkdir -p catkin_ws/src cd catkin_ws/src catkin_create_pkg imu_path roscpp rospy tf nav_msgs cd .. put the imu_tf_pose.cpp in ... package ros catkin jack-liu 1 asked May 15, 2025 at 1:51 2 votes 0 answers 597 views Python hatch, build more than one package from same source I've started to migrate my project from poetry to hatch. Hatch supports dynamic versioning and other dynamic properties Hatch supports uv Hatch supports multiple build targets / Project mode In my ... python-3.x build package monorepo hatch Wör Du Schnaffzig 1,150 asked May 12, 2025 at 15:04 -2 votes 1 answer 91 views How should I name packages for arch vs for manjaro or any other arch-based distro, which uses the same package format (.pkg.tar.[zst/xz/gz]) I want to release packages of my software for arch and manjaro and I am packaging it using makepkg and I cannot find any official way to name packages for arch or manjaro differently as opposed to for ... package archlinux naming manjaro linux-distro Stas Badzi 968 asked May 5, 2025 at 21:23 1 vote 1 answer 96 views Installed my own package but python can't find the modules I've created my own package: python_perso/ └── mypackage/ ├── mypackage/ │ ├── __init__.py │ ├── main.py │ ├── scrapper.py │ └── helpers.py └── setup.py __init__.py is ... python python-3.x pip package Noah7 25 asked May 5, 2025 at 17:29 0 votes 0 answers 61 views :app:processDebugMainManifest FAILED -> Incorrect Package on EAS Android Build I'm working on a React Native mobile application for iOS and Android. I've always been able to make development builds using the command: eas build --profile development --platform android --clear-... build expo package build-error eas Arne Wittouck 1 asked May 5, 2025 at 15:02 0 votes 0 answers 59 views python 3.8 package installed but pkg_resources not able to found Using old python version 3.8.6. I created virtual environment in /var/virtualenvs/myvenv and installed mypkg.bouncer.client but when we import that, it gives below error. Traceback (most recent call ... python import package python-3.8 NPatel 21.4k asked Apr 29, 2025 at 17:12 0 votes 0 answers 66 views Plotting function in R package eHOF My species dataset consists of species relative abundances at sites (i.e., percent). I'd like to plot the eHOF model of distributions of species values over an environmental gradient with the y axis ... r plot package user30269133 1 asked Apr 14, 2025 at 19:56 1 2 3 4 5 … 341 Next The Overflow Blog Now everyone can chat on Stack Overflow Vibe code anything in a Hanselminute Featured on Meta A proposal for bringing back Community Promotion & Open Source Ads Community Asks Sprint Announcement – January 2026: Custom site-specific badges! Policy: Generative AI (e.g., ChatGPT) is banned Modernizing curation: A proposal for The Workshop and The Archive All users on Stack Overflow can now participate in chat Hot Network Questions Gender for 3rd person pronoun of a person with nickname How common was the belief in early British India that crossing the sea led to loss of caste? Selecting non-white/non-black color for any given background color кач - is this a slang word? Cryptic Family Reunion: Sticker Set Manipulate within another Manipulate: How do I set the initial values of the control variables to reflect the inner Manipulate's last state? Where to get feedback on a math paper? Does the success of physics justify a belief in Physicalism? Time waits for an island Implicit methods than can be invoked without mentioning the method name Category-theoretic development of the Thomason model structure Matrix row operation mental practice tool are manual/electric typewriter receptive to script readers and agents? Designing offline-first sync for a multi-user desktop app that must keep working through network outages How to perform an "on this date" check with a spreadsheet formula? tikz: using the pos key to place nodes along a plot I found a paper that basically covers my whole thesis lua-unicode-math clash with mismath usage of alcohol based perfumes (I Thessalonians 1:3) A question about prepositions at the end of this verse (comment added) What makes Certificate-Based Authentication phishing resistant? D.C. al fine and repeats in the same bar for ABABA Mig Welding a Nut to a Sched 40 Galvanized Pipe Why is there no right to a passport in the USA? more hot questions Newest package questions feed Subscribe to RSS Newest package questions feed To subscribe to this RSS feed, copy and paste this URL into your RSS reader. Stack Overflow Questions Help Chat Business Stack Internal Stack Data Licensing Stack Ads Company About Press Work Here Legal Privacy Policy Terms of Service Contact Us cookie-settings#toggle" class="s-btn s-btn__link py4 js-gps-track -link" data-gps-track="footer.click({ location: 5, link: 38 })" data-consent-popup-loader="footer"> Cookie Settings Cookie Policy Stack Exchange Network Technology Culture & recreation Life & arts Science Professional Business API Data Blog Facebook Twitter LinkedIn Instagram Site design / logo © 2026 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2026.1.12.38533 | 2026-01-13T08:48:41 |
https://docs.python.org/3/tutorial/controlflow.html#more-on-defining-functions | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | 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:48:41 |
http://opensource.org/docs/osd | The Open Source Definition – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home The Open Source Definition The Open Source Definition Page created on July 7, 2006 | Last modified on February 16, 2024 Introduction Open source doesn’t just mean access to the source code. The distribution terms of open source software must comply with the following criteria: 1. Free Redistribution The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale. 2. Source Code The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost, preferably downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed. 3. Derived Works The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software. 4. Integrity of The Author’s Source Code The license may restrict source-code from being distributed in modified form only if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software. 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons. 6. No Discrimination Against Fields of Endeavor The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research. 7. Distribution of License The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties. 8. License Must Not Be Specific to a Product The rights attached to the program must not depend on the program’s being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program’s license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution. 9. License Must Not Restrict Other Software The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open source software. 10. License Must Be Technology-Neutral No provision of the license may be predicated on any individual technology or style of interface. The Open Source Definition was originally derived from the Debian Free Software Guidelines (DFSG). Version 1.9, last modified, 2007-03-22 Here’s the historical “ Annotated OSD ” from the early 2000’s. Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:41 |
https://docs.python.org/3/tutorial/controlflow.html#break-and-continue-statements | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | 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:48:41 |
https://oshwa.org/resources/open-source-hardware-definition/ | Open Source Hardware Definition | OSHWA menu menu chevron_left home About Team Programs Community Membership Events OSHW 101 Documents and Policies Resources Announcements English العَرَبِيةُ Català 中文 Français Deutsch Ελληνικά עִבְרִית Italiano 日本語 한글 Latina Português Español Svenska Open Source Hardware Definition Open source hardware is hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell the design or hardware based on that design. The hardware’s source, the design from which it is made, is available in the preferred format for making modifications to it. Ideally, open source hardware uses readily-available components and materials, standard processes, open infrastructure, unrestricted content, and open-source design tools to maximize the ability of individuals to make and use hardware. Open source hardware gives people the freedom to control their technology while sharing knowledge and encouraging commerce through the open exchange of designs. The open-source hardware statement of principles and definition were developed by members of the OSHWA board and working group along with others. These documents were originally edited on the wiki at freedomdefined.org , which you can visit to see endorsements of the definition and to add your own. Open Source Hardware (OSHW) Statement of Principles 1.0 Open source hardware is hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell the design or hardware based on that design. The hardware’s source, the design from which it is made, is available in the preferred format for making modifications to it. Ideally, open source hardware uses readily-available components and materials, standard processes, open infrastructure, unrestricted content, and open-source design tools to maximize the ability of individuals to make and use hardware. Open source hardware gives people the freedom to control their technology while sharing knowledge and encouraging commerce through the open exchange of designs. Open Source Hardware (OSHW) Definition 1.0 The Open Source Hardware (OSHW) Definition 1.0 is based on the Open Source Definition for Open Source Software. That definition was created by Bruce Perens and the Debian developers as the Debian Free Software Guidelines. Introduction Open Source Hardware (OSHW) is a term for tangible artifacts — machines, devices, or other physical things — whose design has been released to the public in such a way that anyone can make, modify, distribute, and use those things. This definition is intended to help provide guidelines for the development and evaluation of licenses for Open Source Hardware. Hardware is different from software in that physical resources must always be committed for the creation of physical goods. Accordingly, persons or companies producing items (“products”) under an OSHW license have an obligation to make it clear that such products are not manufactured, sold, warrantied, or otherwise sanctioned by the original designer and also not to make use of any trademarks owned by the original designer. The distribution terms of Open Source Hardware must comply with the following criteria: 1. Documentation The hardware must be released with documentation including design files, and must allow modification and distribution of the design files. Where documentation is not furnished with the physical product, there must be a well-publicized means of obtaining this documentation for no more than a reasonable reproduction cost, preferably downloading via the Internet without charge. The documentation must include design files in the preferred format for making changes, for example the native file format of a CAD program. Deliberately obfuscated design files are not allowed. Intermediate forms analogous to compiled computer code — such as printer-ready copper artwork from a CAD program — are not allowed as substitutes. The license may require that the design files are provided in fully-documented, open format(s). 2. Scope The documentation for the hardware must clearly specify what portion of the design, if not all, is being released under the license. 3. Necessary Software If the licensed design requires software, embedded or otherwise, to operate properly and fulfill its essential functions, then the license may require that one of the following conditions are met: a) The interfaces are sufficiently documented such that it could reasonably be considered straightforward to write open source software that allows the device to operate properly and fulfill its essential functions. For example, this may include the use of detailed signal timing diagrams or pseudocode to clearly illustrate the interface in operation. b) The necessary software is released under an OSI-approved open source license. 4. Derived Works The license shall allow modifications and derived works, and shall allow them to be distributed under the same terms as the license of the original work. The license shall allow for the manufacture, sale, distribution, and use of products created from the design files, the design files themselves, and derivatives thereof. 5. Free redistribution The license shall not restrict any party from selling or giving away the project documentation. The license shall not require a royalty or other fee for such sale. The license shall not require any royalty or fee related to the sale of derived works. 6. Attribution The license may require derived documents, and copyright notices associated with devices, to provide attribution to the licensors when distributing design files, manufactured products, and/or derivatives thereof. The license may require that this information be accessible to the end-user using the device normally, but shall not specify a specific format of display. The license may require derived works to carry a different name or version number from the original design. 7. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons. 8. No Discrimination Against Fields of Endeavor The license must not restrict anyone from making use of the work (including manufactured hardware) in a specific field of endeavor. For example, it must not restrict the hardware from being used in a business, or from being used in nuclear research. 9. Distribution of License The rights granted by the license must apply to all to whom the work is redistributed without the need for execution of an additional license by those parties. 10. License Must Not Be Specific to a Product The rights granted by the license must not depend on the licensed work being part of a particular product. If a portion is extracted from a work and used or distributed within the terms of the license, all parties to whom that work is redistributed should have the same rights as those that are granted for the original work. 11. License Must Not Restrict Other Hardware or Software The license must not place restrictions on other items that are aggregated with the licensed work but not derivative of it. For example, the license must not insist that all other hardware sold with the licensed item be open source, nor that only open source software be used external to the device. 12. License Must Be Technology-Neutral No provision of the license may be predicated on any individual technology, specific part or component, material, or style of interface or use thereof. Afterword The signatories of this Open Source Hardware definition recognize that the open source movement represents only one way of sharing information. We encourage and support all forms of openness and collaboration, whether or not they fit this definition. Become a Member Donate Newsletter | 2026-01-13T08:48:41 |
https://docs.python.org/3/library/functions.html#float | Built-in Functions — Python 3.14.2 documentation Theme Auto Light Dark Previous topic Introduction Next topic Built-in Constants This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Built-in Functions | Theme Auto Light Dark | Built-in Functions ¶ The Python interpreter has a number of functions and types built into it that are always available. They are listed here in alphabetical order. Built-in Functions A abs() aiter() all() anext() any() ascii() B bin() bool() breakpoint() bytearray() bytes() C callable() chr() classmethod() compile() complex() D delattr() dict() dir() divmod() E enumerate() eval() exec() F filter() float() format() frozenset() G getattr() globals() H hasattr() hash() help() hex() I id() input() int() isinstance() issubclass() iter() L len() list() locals() M map() max() memoryview() min() N next() O object() oct() open() ord() P pow() print() property() R range() repr() reversed() round() S set() setattr() slice() sorted() staticmethod() str() sum() super() T tuple() type() V vars() Z zip() _ __import__() abs ( number , / ) ¶ Return the absolute value of a number. The argument may be an integer, a floating-point number, or an object implementing __abs__() . If the argument is a complex number, its magnitude is returned. aiter ( async_iterable , / ) ¶ Return an asynchronous iterator for an asynchronous iterable . Equivalent to calling x.__aiter__() . Note: Unlike iter() , aiter() has no 2-argument variant. Added in version 3.10. all ( iterable , / ) ¶ Return True if all elements of the iterable are true (or if the iterable is empty). Equivalent to: def all ( iterable ): for element in iterable : if not element : return False return True awaitable anext ( async_iterator , / ) ¶ awaitable anext ( async_iterator , default , / ) When awaited, return the next item from the given asynchronous iterator , or default if given and the iterator is exhausted. This is the async variant of the next() builtin, and behaves similarly. This calls the __anext__() method of async_iterator , returning an awaitable . Awaiting this returns the next value of the iterator. If default is given, it is returned if the iterator is exhausted, otherwise StopAsyncIteration is raised. Added in version 3.10. any ( iterable , / ) ¶ Return True if any element of the iterable is true. If the iterable is empty, return False . Equivalent to: def any ( iterable ): for element in iterable : if element : return True return False ascii ( object , / ) ¶ As repr() , return a string containing a printable representation of an object, but escape the non-ASCII characters in the string returned by repr() using \x , \u , or \U escapes. This generates a string similar to that returned by repr() in Python 2. bin ( integer , / ) ¶ Convert an integer number to a binary string prefixed with “0b”. The result is a valid Python expression. If integer is not a Python int object, it has to define an __index__() method that returns an integer. Some examples: >>> bin ( 3 ) '0b11' >>> bin ( - 10 ) '-0b1010' If the prefix “0b” is desired or not, you can use either of the following ways. >>> format ( 14 , '#b' ), format ( 14 , 'b' ) ('0b1110', '1110') >>> f ' { 14 : #b } ' , f ' { 14 : b } ' ('0b1110', '1110') See also enum.bin() to represent negative values as twos-complement. See also format() for more information. class bool ( object = False , / ) ¶ Return a Boolean value, i.e. one of True or False . The argument is converted using the standard truth testing procedure . If the argument is false or omitted, this returns False ; otherwise, it returns True . The bool class is a subclass of int (see Numeric Types — int, float, complex ). It cannot be subclassed further. Its only instances are False and True (see Boolean Type - bool ). Changed in version 3.7: The parameter is now positional-only. breakpoint ( * args , ** kws ) ¶ This function drops you into the debugger at the call site. Specifically, it calls sys.breakpointhook() , passing args and kws straight through. By default, sys.breakpointhook() calls pdb.set_trace() expecting no arguments. In this case, it is purely a convenience function so you don’t have to explicitly import pdb or type as much code to enter the debugger. However, sys.breakpointhook() can be set to some other function and breakpoint() will automatically call that, allowing you to drop into the debugger of choice. If sys.breakpointhook() is not accessible, this function will raise RuntimeError . By default, the behavior of breakpoint() can be changed with the PYTHONBREAKPOINT environment variable. See sys.breakpointhook() for usage details. Note that this is not guaranteed if sys.breakpointhook() has been replaced. Raises an auditing event builtins.breakpoint with argument breakpointhook . Added in version 3.7. class bytearray ( source = b'' ) class bytearray ( source , encoding , errors = 'strict' ) Return a new array of bytes. The bytearray class is a mutable sequence of integers in the range 0 <= x < 256. It has most of the usual methods of mutable sequences, described in Mutable Sequence Types , as well as most methods that the bytes type has, see Bytes and Bytearray Operations . The optional source parameter can be used to initialize the array in a few different ways: If it is a string , you must also give the encoding (and optionally, errors ) parameters; bytearray() then converts the string to bytes using str.encode() . If it is an integer , the array will have that size and will be initialized with null bytes. If it is an object conforming to the buffer interface , a read-only buffer of the object will be used to initialize the bytes array. If it is an iterable , it must be an iterable of integers in the range 0 <= x < 256 , which are used as the initial contents of the array. Without an argument, an array of size 0 is created. See also Binary Sequence Types — bytes, bytearray, memoryview and Bytearray Objects . class bytes ( source = b'' ) class bytes ( source , encoding , errors = 'strict' ) Return a new “bytes” object which is an immutable sequence of integers in the range 0 <= x < 256 . bytes is an immutable version of bytearray – it has the same non-mutating methods and the same indexing and slicing behavior. Accordingly, constructor arguments are interpreted as for bytearray() . Bytes objects can also be created with literals, see String and Bytes literals . See also Binary Sequence Types — bytes, bytearray, memoryview , Bytes Objects , and Bytes and Bytearray Operations . callable ( object , / ) ¶ Return True if the object argument appears callable, False if not. If this returns True , it is still possible that a call fails, but if it is False , calling object will never succeed. Note that classes are callable (calling a class returns a new instance); instances are callable if their class has a __call__() method. Added in version 3.2: This function was first removed in Python 3.0 and then brought back in Python 3.2. chr ( codepoint , / ) ¶ Return the string representing a character with the specified Unicode code point. For example, chr(97) returns the string 'a' , while chr(8364) returns the string '€' . This is the inverse of ord() . The valid range for the argument is from 0 through 1,114,111 (0x10FFFF in base 16). ValueError will be raised if it is outside that range. @ classmethod ¶ Transform a method into a class method. A class method receives the class as an implicit first argument, just like an instance method receives the instance. To declare a class method, use this idiom: class C : @classmethod def f ( cls , arg1 , arg2 ): ... The @classmethod form is a function decorator – see Function definitions for details. A class method can be called either on the class (such as C.f() ) or on an instance (such as C().f() ). The instance is ignored except for its class. If a class method is called for a derived class, the derived class object is passed as the implied first argument. Class methods are different than C++ or Java static methods. If you want those, see staticmethod() in this section. For more information on class methods, see The standard type hierarchy . Changed in version 3.9: Class methods can now wrap other descriptors such as property() . Changed in version 3.10: Class methods now inherit the method attributes ( __module__ , __name__ , __qualname__ , __doc__ and __annotations__ ) and have a new __wrapped__ attribute. Deprecated since version 3.11, removed in version 3.13: Class methods can no longer wrap other descriptors such as property() . compile ( source , filename , mode , flags = 0 , dont_inherit = False , optimize = -1 ) ¶ Compile the source into a code or AST object. Code objects can be executed by exec() or eval() . source can either be a normal string, a byte string, or an AST object. Refer to the ast module documentation for information on how to work with AST objects. The filename argument should give the file from which the code was read; pass some recognizable value if it wasn’t read from a file ( '<string>' is commonly used). The mode argument specifies what kind of code must be compiled; it can be 'exec' if source consists of a sequence of statements, 'eval' if it consists of a single expression, or 'single' if it consists of a single interactive statement (in the latter case, expression statements that evaluate to something other than None will be printed). The optional arguments flags and dont_inherit control which compiler options should be activated and which future features should be allowed. If neither is present (or both are zero) the code is compiled with the same flags that affect the code that is calling compile() . If the flags argument is given and dont_inherit is not (or is zero) then the compiler options and the future statements specified by the flags argument are used in addition to those that would be used anyway. If dont_inherit is a non-zero integer then the flags argument is it – the flags (future features and compiler options) in the surrounding code are ignored. Compiler options and future statements are specified by bits which can be bitwise ORed together to specify multiple options. The bitfield required to specify a given future feature can be found as the compiler_flag attribute on the _Feature instance in the __future__ module. Compiler flags can be found in ast module, with PyCF_ prefix. The argument optimize specifies the optimization level of the compiler; the default value of -1 selects the optimization level of the interpreter as given by -O options. Explicit levels are 0 (no optimization; __debug__ is true), 1 (asserts are removed, __debug__ is false) or 2 (docstrings are removed too). This function raises SyntaxError or ValueError if the compiled source is invalid. If you want to parse Python code into its AST representation, see ast.parse() . Raises an auditing event compile with arguments source and filename . This event may also be raised by implicit compilation. Note When compiling a string with multi-line code in 'single' or 'eval' mode, input must be terminated by at least one newline character. This is to facilitate detection of incomplete and complete statements in the code module. Warning It is possible to crash the Python interpreter with a sufficiently large/complex string when compiling to an AST object due to stack depth limitations in Python’s AST compiler. Changed in version 3.2: Allowed use of Windows and Mac newlines. Also, input in 'exec' mode does not have to end in a newline anymore. Added the optimize parameter. Changed in version 3.5: Previously, TypeError was raised when null bytes were encountered in source . Added in version 3.8: ast.PyCF_ALLOW_TOP_LEVEL_AWAIT can now be passed in flags to enable support for top-level await , async for , and async with . class complex ( number = 0 , / ) ¶ class complex ( string , / ) class complex ( real = 0 , imag = 0 ) Convert a single string or number to a complex number, or create a complex number from real and imaginary parts. Examples: >>> complex ( '+1.23' ) (1.23+0j) >>> complex ( '-4.5j' ) -4.5j >>> complex ( '-1.23+4.5j' ) (-1.23+4.5j) >>> complex ( ' \t ( -1.23+4.5J ) \n ' ) (-1.23+4.5j) >>> complex ( '-Infinity+NaNj' ) (-inf+nanj) >>> complex ( 1.23 ) (1.23+0j) >>> complex ( imag =- 4.5 ) -4.5j >>> complex ( - 1.23 , 4.5 ) (-1.23+4.5j) If the argument is a string, it must contain either a real part (in the same format as for float() ) or an imaginary part (in the same format but with a 'j' or 'J' suffix), or both real and imaginary parts (the sign of the imaginary part is mandatory in this case). The string can optionally be surrounded by whitespaces and the round parentheses '(' and ')' , which are ignored. The string must not contain whitespace between '+' , '-' , the 'j' or 'J' suffix, and the decimal number. For example, complex('1+2j') is fine, but complex('1 + 2j') raises ValueError . More precisely, the input must conform to the complexvalue production rule in the following grammar, after parentheses and leading and trailing whitespace characters are removed: complexvalue : floatvalue | floatvalue ( "j" | "J" ) | floatvalue sign absfloatvalue ( "j" | "J" ) If the argument is a number, the constructor serves as a numeric conversion like int and float . For a general Python object x , complex(x) delegates to x.__complex__() . If __complex__() is not defined then it falls back to __float__() . If __float__() is not defined then it falls back to __index__() . If two arguments are provided or keyword arguments are used, each argument may be any numeric type (including complex). If both arguments are real numbers, return a complex number with the real component real and the imaginary component imag . If both arguments are complex numbers, return a complex number with the real component real.real-imag.imag and the imaginary component real.imag+imag.real . If one of arguments is a real number, only its real component is used in the above expressions. See also complex.from_number() which only accepts a single numeric argument. If all arguments are omitted, returns 0j . The complex type is described in Numeric Types — int, float, complex . Changed in version 3.6: Grouping digits with underscores as in code literals is allowed. Changed in version 3.8: Falls back to __index__() if __complex__() and __float__() are not defined. Deprecated since version 3.14: Passing a complex number as the real or imag argument is now deprecated; it should only be passed as a single positional argument. delattr ( object , name , / ) ¶ This is a relative of setattr() . The arguments are an object and a string. The string must be the name of one of the object’s attributes. The function deletes the named attribute, provided the object allows it. For example, delattr(x, 'foobar') is equivalent to del x.foobar . name need not be a Python identifier (see setattr() ). class dict ( ** kwargs ) class dict ( mapping , / , ** kwargs ) class dict ( iterable , / , ** kwargs ) Create a new dictionary. The dict object is the dictionary class. See dict and Mapping Types — dict for documentation about this class. For other containers see the built-in list , set , and tuple classes, as well as the collections module. dir ( ) ¶ dir ( object , / ) Without arguments, return the list of names in the current local scope. With an argument, attempt to return a list of valid attributes for that object. If the object has a method named __dir__() , this method will be called and must return the list of attributes. This allows objects that implement a custom __getattr__() or __getattribute__() function to customize the way dir() reports their attributes. If the object does not provide __dir__() , the function tries its best to gather information from the object’s __dict__ attribute, if defined, and from its type object. The resulting list is not necessarily complete and may be inaccurate when the object has a custom __getattr__() . The default dir() mechanism behaves differently with different types of objects, as it attempts to produce the most relevant, rather than complete, information: If the object is a module object, the list contains the names of the module’s attributes. If the object is a type or class object, the list contains the names of its attributes, and recursively of the attributes of its bases. Otherwise, the list contains the object’s attributes’ names, the names of its class’s attributes, and recursively of the attributes of its class’s base classes. The resulting list is sorted alphabetically. For example: >>> import struct >>> dir () # show the names in the module namespace ['__builtins__', '__name__', 'struct'] >>> dir ( struct ) # show the names in the struct module ['Struct', '__all__', '__builtins__', '__cached__', '__doc__', '__file__', '__initializing__', '__loader__', '__name__', '__package__', '_clearcache', 'calcsize', 'error', 'pack', 'pack_into', 'unpack', 'unpack_from'] >>> class Shape : ... def __dir__ ( self ): ... return [ 'area' , 'perimeter' , 'location' ] ... >>> s = Shape () >>> dir ( s ) ['area', 'location', 'perimeter'] Note Because dir() is supplied primarily as a convenience for use at an interactive prompt, it tries to supply an interesting set of names more than it tries to supply a rigorously or consistently defined set of names, and its detailed behavior may change across releases. For example, metaclass attributes are not in the result list when the argument is a class. divmod ( a , b , / ) ¶ Take two (non-complex) numbers as arguments and return a pair of numbers consisting of their quotient and remainder when using integer division. With mixed operand types, the rules for binary arithmetic operators apply. For integers, the result is the same as (a // b, a % b) . For floating-point numbers the result is (q, a % b) , where q is usually math.floor(a / b) but may be 1 less than that. In any case q * b + a % b is very close to a , if a % b is non-zero it has the same sign as b , and 0 <= abs(a % b) < abs(b) . enumerate ( iterable , start = 0 ) ¶ Return an enumerate object. iterable must be a sequence, an iterator , or some other object which supports iteration. The __next__() method of the iterator returned by enumerate() returns a tuple containing a count (from start which defaults to 0) and the values obtained from iterating over iterable . >>> seasons = [ 'Spring' , 'Summer' , 'Fall' , 'Winter' ] >>> list ( enumerate ( seasons )) [(0, 'Spring'), (1, 'Summer'), (2, 'Fall'), (3, 'Winter')] >>> list ( enumerate ( seasons , start = 1 )) [(1, 'Spring'), (2, 'Summer'), (3, 'Fall'), (4, 'Winter')] Equivalent to: def enumerate ( iterable , start = 0 ): n = start for elem in iterable : yield n , elem n += 1 eval ( source , / , globals = None , locals = None ) ¶ Parameters : source ( str | code object ) – A Python expression. globals ( dict | None ) – The global namespace (default: None ). locals ( mapping | None ) – The local namespace (default: None ). Returns : The result of the evaluated expression. Raises : Syntax errors are reported as exceptions. Warning This function executes arbitrary code. Calling it with user-supplied input may lead to security vulnerabilities. The source argument is parsed and evaluated as a Python expression (technically speaking, a condition list) using the globals and locals mappings as global and local namespace. If the globals dictionary is present and does not contain a value for the key __builtins__ , a reference to the dictionary of the built-in module builtins is inserted under that key before source is parsed. That way you can control what builtins are available to the executed code by inserting your own __builtins__ dictionary into globals before passing it to eval() . If the locals mapping is omitted it defaults to the globals dictionary. If both mappings are omitted, the source is executed with the globals and locals in the environment where eval() is called. Note, eval() will only have access to the nested scopes (non-locals) in the enclosing environment if they are already referenced in the scope that is calling eval() (e.g. via a nonlocal statement). Example: >>> x = 1 >>> eval ( 'x+1' ) 2 This function can also be used to execute arbitrary code objects (such as those created by compile() ). In this case, pass a code object instead of a string. If the code object has been compiled with 'exec' as the mode argument, eval() 's return value will be None . Hints: dynamic execution of statements is supported by the exec() function. The globals() and locals() functions return the current global and local dictionary, respectively, which may be useful to pass around for use by eval() or exec() . If the given source is a string, then leading and trailing spaces and tabs are stripped. See ast.literal_eval() for a function that can safely evaluate strings with expressions containing only literals. Raises an auditing event exec with the code object as the argument. Code compilation events may also be raised. Changed in version 3.13: The globals and locals arguments can now be passed as keywords. Changed in version 3.13: The semantics of the default locals namespace have been adjusted as described for the locals() builtin. exec ( source , / , globals = None , locals = None , * , closure = None ) ¶ Warning This function executes arbitrary code. Calling it with user-supplied input may lead to security vulnerabilities. This function supports dynamic execution of Python code. source must be either a string or a code object. If it is a string, the string is parsed as a suite of Python statements which is then executed (unless a syntax error occurs). [ 1 ] If it is a code object, it is simply executed. In all cases, the code that’s executed is expected to be valid as file input (see the section File input in the Reference Manual). Be aware that the nonlocal , yield , and return statements may not be used outside of function definitions even within the context of code passed to the exec() function. The return value is None . In all cases, if the optional parts are omitted, the code is executed in the current scope. If only globals is provided, it must be a dictionary (and not a subclass of dictionary), which will be used for both the global and the local variables. If globals and locals are given, they are used for the global and local variables, respectively. If provided, locals can be any mapping object. Remember that at the module level, globals and locals are the same dictionary. Note When exec gets two separate objects as globals and locals , the code will be executed as if it were embedded in a class definition. This means functions and classes defined in the executed code will not be able to access variables assigned at the top level (as the “top level” variables are treated as class variables in a class definition). If the globals dictionary does not contain a value for the key __builtins__ , a reference to the dictionary of the built-in module builtins is inserted under that key. That way you can control what builtins are available to the executed code by inserting your own __builtins__ dictionary into globals before passing it to exec() . The closure argument specifies a closure–a tuple of cellvars. It’s only valid when the object is a code object containing free (closure) variables . The length of the tuple must exactly match the length of the code object’s co_freevars attribute. Raises an auditing event exec with the code object as the argument. Code compilation events may also be raised. Note The built-in functions globals() and locals() return the current global and local namespace, respectively, which may be useful to pass around for use as the second and third argument to exec() . Note The default locals act as described for function locals() below. Pass an explicit locals dictionary if you need to see effects of the code on locals after function exec() returns. Changed in version 3.11: Added the closure parameter. Changed in version 3.13: The globals and locals arguments can now be passed as keywords. Changed in version 3.13: The semantics of the default locals namespace have been adjusted as described for the locals() builtin. filter ( function , iterable , / ) ¶ Construct an iterator from those elements of iterable for which function is true. iterable may be either a sequence, a container which supports iteration, or an iterator. If function is None , the identity function is assumed, that is, all elements of iterable that are false are removed. Note that filter(function, iterable) is equivalent to the generator expression (item for item in iterable if function(item)) if function is not None and (item for item in iterable if item) if function is None . See itertools.filterfalse() for the complementary function that returns elements of iterable for which function is false. class float ( number = 0.0 , / ) ¶ class float ( string , / ) Return a floating-point number constructed from a number or a string. Examples: >>> float ( '+1.23' ) 1.23 >>> float ( ' -12345 \n ' ) -12345.0 >>> float ( '1e-003' ) 0.001 >>> float ( '+1E6' ) 1000000.0 >>> float ( '-Infinity' ) -inf If the argument is a string, it should contain a decimal number, optionally preceded by a sign, and optionally embedded in whitespace. The optional sign may be '+' or '-' ; a '+' sign has no effect on the value produced. The argument may also be a string representing a NaN (not-a-number), or positive or negative infinity. More precisely, the input must conform to the floatvalue production rule in the following grammar, after leading and trailing whitespace characters are removed: sign : "+" | "-" infinity : "Infinity" | "inf" nan : "nan" digit : <a Unicode decimal digit, i.e. characters in Unicode general category Nd> digitpart : digit ([ "_" ] digit )* number : [ digitpart ] "." digitpart | digitpart [ "." ] exponent : ( "e" | "E" ) [ sign ] digitpart floatnumber : number [ exponent ] absfloatvalue : floatnumber | infinity | nan floatvalue : [ sign ] absfloatvalue Case is not significant, so, for example, “inf”, “Inf”, “INFINITY”, and “iNfINity” are all acceptable spellings for positive infinity. Otherwise, if the argument is an integer or a floating-point number, a floating-point number with the same value (within Python’s floating-point precision) is returned. If the argument is outside the range of a Python float, an OverflowError will be raised. For a general Python object x , float(x) delegates to x.__float__() . If __float__() is not defined then it falls back to __index__() . See also float.from_number() which only accepts a numeric argument. If no argument is given, 0.0 is returned. The float type is described in Numeric Types — int, float, complex . Changed in version 3.6: Grouping digits with underscores as in code literals is allowed. Changed in version 3.7: The parameter is now positional-only. Changed in version 3.8: Falls back to __index__() if __float__() is not defined. format ( value , format_spec = '' , / ) ¶ Convert a value to a “formatted” representation, as controlled by format_spec . The interpretation of format_spec will depend on the type of the value argument; however, there is a standard formatting syntax that is used by most built-in types: Format Specification Mini-Language . The default format_spec is an empty string which usually gives the same effect as calling str(value) . A call to format(value, format_spec) is translated to type(value).__format__(value, format_spec) which bypasses the instance dictionary when searching for the value’s __format__() method. A TypeError exception is raised if the method search reaches object and the format_spec is non-empty, or if either the format_spec or the return value are not strings. Changed in version 3.4: object().__format__(format_spec) raises TypeError if format_spec is not an empty string. class frozenset ( iterable = () , / ) Return a new frozenset object, optionally with elements taken from iterable . frozenset is a built-in class. See frozenset and Set Types — set, frozenset for documentation about this class. For other containers see the built-in set , list , tuple , and dict classes, as well as the collections module. getattr ( object , name , / ) ¶ getattr ( object , name , default , / ) Return the value of the named attribute of object . name must be a string. If the string is the name of one of the object’s attributes, the result is the value of that attribute. For example, getattr(x, 'foobar') is equivalent to x.foobar . If the named attribute does not exist, default is returned if provided, otherwise AttributeError is raised. name need not be a Python identifier (see setattr() ). Note Since private name mangling happens at compilation time, one must manually mangle a private attribute’s (attributes with two leading underscores) name in order to retrieve it with getattr() . globals ( ) ¶ Return the dictionary implementing the current module namespace. For code within functions, this is set when the function is defined and remains the same regardless of where the function is called. hasattr ( object , name , / ) ¶ The arguments are an object and a string. The result is True if the string is the name of one of the object’s attributes, False if not. (This is implemented by calling getattr(object, name) and seeing whether it raises an AttributeError or not.) hash ( object , / ) ¶ Return the hash value of the object (if it has one). Hash values are integers. They are used to quickly compare dictionary keys during a dictionary lookup. Numeric values that compare equal have the same hash value (even if they are of different types, as is the case for 1 and 1.0). Note For objects with custom __hash__() methods, note that hash() truncates the return value based on the bit width of the host machine. help ( ) ¶ help ( request ) Invoke the built-in help system. (This function is intended for interactive use.) If no argument is given, the interactive help system starts on the interpreter console. If the argument is a string, then the string is looked up as the name of a module, function, class, method, keyword, or documentation topic, and a help page is printed on the console. If the argument is any other kind of object, a help page on the object is generated. Note that if a slash(/) appears in the parameter list of a function when invoking help() , it means that the parameters prior to the slash are positional-only. For more info, see the FAQ entry on positional-only parameters . This function is added to the built-in namespace by the site module. Changed in version 3.4: Changes to pydoc and inspect mean that the reported signatures for callables are now more comprehensive and consistent. hex ( integer , / ) ¶ Convert an integer number to a lowercase hexadecimal string prefixed with “0x”. If integer is not a Python int object, it has to define an __index__() method that returns an integer. Some examples: >>> hex ( 255 ) '0xff' >>> hex ( - 42 ) '-0x2a' If you want to convert an integer number to an uppercase or lower hexadecimal string with prefix or not, you can use either of the following ways: >>> ' %#x ' % 255 , ' %x ' % 255 , ' %X ' % 255 ('0xff', 'ff', 'FF') >>> format ( 255 , '#x' ), format ( 255 , 'x' ), format ( 255 , 'X' ) ('0xff', 'ff', 'FF') >>> f ' { 255 : #x } ' , f ' { 255 : x } ' , f ' { 255 : X } ' ('0xff', 'ff', 'FF') See also format() for more information. See also int() for converting a hexadecimal string to an integer using a base of 16. Note To obtain a hexadecimal string representation for a float, use the float.hex() method. id ( object , / ) ¶ Return the “identity” of an object. This is an integer which is guaranteed to be unique and constant for this object during its lifetime. Two objects with non-overlapping lifetimes may have the same id() value. CPython implementation detail: This is the address of the object in memory. Raises an auditing event builtins.id with argument id . input ( ) ¶ input ( prompt , / ) If the prompt argument is present, it is written to standard output without a trailing newline. The function then reads a line from input, converts it to a string (stripping a trailing newline), and returns that. When EOF is read, EOFError is raised. Example: >>> s = input ( '--> ' ) --> Monty Python's Flying Circus >>> s "Monty Python's Flying Circus" If the readline module was loaded, then input() will use it to provide elaborate line editing and history features. Raises an auditing event builtins.input with argument prompt before reading input Raises an auditing event builtins.input/result with the result after successfully reading input. class int ( number = 0 , / ) ¶ class int ( string , / , base = 10 ) Return an integer object constructed from a number or a string, or return 0 if no arguments are given. Examples: >>> int ( 123.45 ) 123 >>> int ( '123' ) 123 >>> int ( ' -12_345 \n ' ) -12345 >>> int ( 'FACE' , 16 ) 64206 >>> int ( '0xface' , 0 ) 64206 >>> int ( '01110011' , base = 2 ) 115 If the argument defines __int__() , int(x) returns x.__int__() . If the argument defines __index__() , it returns x.__index__() . For floating-point numbers, this truncates towards zero. If the argument is not a number or if base is given, then it must be a string, bytes , or bytearray instance representing an integer in radix base . Optionally, the string can be preceded by + or - (with no space in between), have leading zeros, be surrounded by whitespace, and have single underscores interspersed between digits. A base-n integer string contains digits, each representing a value from 0 to n-1. The values 0–9 can be represented by any Unicode decimal digit. The values 10–35 can be represented by a to z (or A to Z ). The default base is 10. The allowed bases are 0 and 2–36. Base-2, -8, and -16 strings can be optionally prefixed with 0b / 0B , 0o / 0O , or 0x / 0X , as with integer literals in code. For base 0, the string is interpreted in a similar way to an integer literal in code , in that the actual base is 2, 8, 10, or 16 as determined by the prefix. Base 0 also disallows leading zeros: int('010', 0) is not legal, while int('010') and int('010', 8) are. The integer type is described in Numeric Types — int, float, complex . Changed in version 3.4: If base is not an instance of int and the base object has a base.__index__ method, that method is called to obtain an integer for the base. Previous versions used base.__int__ instead of base.__index__ . Changed in version 3.6: Grouping digits with underscores as in code literals is allowed. Changed in version 3.7: The first parameter is now positional-only. Changed in version 3.8: Falls back to __index__() if __int__() is not defined. Changed in version 3.11: int string inputs and string representations can be limited to help avoid denial of service attacks. A ValueError is raised when the limit is exceeded while converting a string to an int or when converting an int into a string would exceed the limit. See the integer string conversion length limitation documentation. Changed in version 3.14: int() no longer delegates to the __trunc__() method. isinstance ( object , classinfo , / ) ¶ Return True if the object argument is an instance of the classinfo argument, or of a (direct, indirect, or virtual ) subclass thereof. If object is not an object of the given type, the function always returns False . If classinfo is a tuple of type objects (or recursively, other such tuples) or a Union Type of multiple types, return True if object is an instance of any of the types. If classinfo is not a type or tuple of types and such tuples, a TypeError exception is raised. TypeError may not be raised for an invalid type if an earlier check succeeds. Changed in version 3.10: classinfo can be a Union Type . issubclass ( class , classinfo , / ) ¶ Return True if class is a subclass (direct, indirect, or virtual ) of classinfo . A class is considered a subclass of itself. classinfo may be a tuple of class objects (or recursively, other such tuples) or a Union Type , in which case return True if class is a subclass of any entry in classinfo . In any other case, a TypeError exception is raised. Changed in version 3.10: classinfo can be a Union Type . iter ( iterable , / ) ¶ iter ( callable , sentinel , / ) Return an iterator object. The first argument is interpreted very differently depending on the presence of the second argument. Without a second argument, the single argument must be a collection object which supports the iterable protocol (the __iter__() method), or it must support the sequence protocol (the __getitem__() method with integer arguments starting at 0 ). If it does not support either of those protocols, TypeError is raised. If the second argument, sentinel , is given, then the first argument must be a callable object. The iterator created in this case will call callable with no arguments for each call to its __next__() method; if the value returned is equal to sentinel , StopIteration will be raised, otherwise the value will be returned. See also Iterator Types . One useful application of the second form of iter() is to build a block-reader. For example, reading fixed-width blocks from a binary database file until the end of file is reached: from functools import partial with open ( 'mydata.db' , 'rb' ) as f : for block in iter ( partial ( f . read , 64 ), b '' ): process_block ( block ) len ( object , / ) ¶ Return the length (the number of items) of an object. The argument may be a sequence (such as a string, bytes, tuple, list, or range) or a collection (such as a dictionary, set, or frozen set). CPython implementation detail: len raises OverflowError on lengths larger than sys.maxsize , such as range(2 ** 100) . class list ( iterable = () , / ) Rather than being a function, list is actually a mutable sequence type, as documented in Lists and Sequence Types — list, tuple, range . locals ( ) ¶ Return a mapping object representing the current local symbol table, with variable names as the keys, and their currently bound references as the values. At module scope, as well as when using exec() or eval() with a single namespace, this function returns the same namespace as globals() . At class scope, it returns the namespace that will be passed to the metaclass constructor. When using exec() or eval() with separate local and global arguments, it returns the local namespace passed in to the function call. In all of the above cases, each call to locals() in a given frame of execution will return the same mapping object. Changes made through the mapping object returned from locals() will be visible as assigned, reassigned, or deleted local variables, and assigning, reassigning, or deleting local variables will immediately affect the contents of the returned mapping object. In an optimized scope (including functions, generators, and coroutines), each call to locals() instead returns a fresh dictionary containing the current bindings of the function’s local variables and any nonlocal cell references. In this case, name binding changes made via the returned dict are not written back to the corresponding local variables or nonlocal cell references, and assigning, reassigning, or deleting local variables and nonlocal cell references does not affect the contents of previously returned dictionaries. Calling locals() as part of a comprehension in a function, generator, or coroutine is equivalent to calling it in the containing scope, except that the comprehension’s initialised iteration variables will be included. In other scopes, it behaves as if the comprehension were running as a nested function. Calling locals() as part of a generator expression is equivalent to calling it in a nested generator function. Changed in version 3.12: The behaviour of locals() in a comprehension has been updated as described in PEP 709 . Changed in version 3.13: As part of PEP 667 , the semantics of mutating the mapping objects returned from this function are now defined. The behavior in optimized scopes is now as described above. Aside from being defined, the behaviour in other scopes remains unchanged from previous versions. map ( function , iterable , / , * iterables , strict = False ) ¶ Return an iterator that applies function to every item of iterable , yielding the results. If additional iterables arguments are passed, function must take that many arguments and is applied to the items from all iterables in parallel. With multiple iterables, the iterator stops when the shortest iterable is exhausted. If strict is True and one of the iterables is exhausted before the others, a ValueError is raised. For cases where the function inputs are already arranged into argument tuples, see itertools.starmap() . Changed in version 3.14: Added the strict parameter. max ( iterable , / , * , key = None ) ¶ max ( iterable , / , * , default , key = None ) max ( arg1 , arg2 , / , * args , key = None ) Return the largest item in an iterable or the largest of two or more arguments. If one positional argument is provided, it should be an iterable . The largest item in the iterable is returned. If two or more positional arguments are provided, the largest of the positional arguments is returned. There are two optional keyword-only arguments. The key argument specifies a one-argument ordering function like that used for list.sort() . The default argument specifies an object to return if the provided iterable is empty. If the iterable is empty and default is not provided, a ValueError is raised. If multiple items are maximal, the function returns the first one encountered. This is consistent with other sort-stability preserving tools such as sorted(iterable, key=keyfunc, reverse=True)[0] and heapq.nlargest(1, iterable, key=keyfunc) . Changed in version 3.4: Added the default keyword-only parameter. Changed in version 3.8: The key can be None . class memoryview ( object ) Return a “memory view” object created from the given argument. See Memory Views for more information. min ( iterable , / , * , key = None ) ¶ min ( iterable , / , * , default , key = None ) min ( arg1 , arg2 , / , * args , key = None ) Return the smallest item in an iterable or the smallest of two or more arguments. If one positional argument is provided, it should be an iterable . The smallest item in the iterable is returned. If two or more positional arguments are provided, the smallest of the positional arguments is returned. There are two optional keyword-only arguments. The key argument specifies a one-argument ordering function like that used for list.sort() . The default argument specifies an object to return if the provided iterable is empty. If the iterable is empty and default is not provided, a ValueError is raised. If multiple items are minimal, the function returns the first one encountered. This is consistent with other sort-stability preserving tools such as sorted(iterable, key=keyfunc)[0] and heapq.nsmallest(1, iterable, key=keyfunc) . Changed in version 3.4: Added the default keyword-only parameter. Changed in version 3.8: The key can be None . next ( iterator , / ) ¶ next ( iterator , default , / ) Retrieve the next item from the iterator by calling its __next__() method. If default is given, it is returned if the iterator is exhausted, otherwise StopIteration is raised. class object ¶ This is the ultimate base class of all other classes. It has methods that are common to all instances of Python classes. When the constructor is called, it returns a new featureless object. The constructor does not accept any arguments. Note object instances do not have __dict__ attributes, so you can’t assign arbitrary attributes to an instance of object . oct ( integer , / ) ¶ Convert an integer number to an octal string prefixed with “0o”. The result is a valid Python expression. If integer is not a Python int object, it has to define an __index__() method that returns an integer. For example: >>> oct ( 8 ) '0o10' >>> oct ( - 56 ) '-0o70' If you want to convert an integer number to an octal string either with the prefix “0o” or not, you can use either of the following ways. >>> ' %#o ' % 10 , ' %o ' % 10 ('0o12', '12') >>> format ( 10 , '#o' ), format ( 10 , 'o' ) ('0o12', '12') >>> f ' { 10 : #o } ' , f ' { 10 : o } ' ('0o12', '12') See also format() for more information. open ( file , mode = 'r' , buffering = -1 , encoding = None , errors = None , newline = None , closefd = True , opener = None ) ¶ Open file and return a corresponding file object . If the file cannot be opened, an OSError is raised. See Reading and Writing Files for more examples of how to use this function. file is a path-like object giving the pathname (absolute or relative to the current working directory) of the file to be opened or an integer file descriptor of the file to be wrapped. (If a file descriptor is given, it is closed when the returned I/O object is closed unless closefd is set to False .) mode is an optional string that specifies the mode in which the file is opened. It defaults to 'r' which means open for reading in text mode. Other common values are 'w' for writing (truncating the file if it already exists), 'x' for exclusive creation, and 'a' for appending (which on some Unix systems, means that all writes append to the end of the file regardless of the current seek position). In text mode, if encoding is not specified the encoding used is platform-dependent: locale.getencoding() is called to get the current locale encoding. (For reading and writing raw bytes use binary mode and leave encoding unspecified.) The available modes are: Character Meaning 'r' open for reading (default) 'w' open for writing, truncating the file first 'x' open for exclusive creation, failing if the file already exists 'a' open for writing, appending to the end of file if it exists 'b' binary mode 't' text mode (default) '+' open for updating (reading and writing) The default mode is 'r' (open for reading text, a synonym of 'rt' ). Modes 'w+' and 'w+b' open and truncate the file. Modes 'r+' and 'r+b' open the file with no truncation. As mentioned in the Overview , Python distinguishes between binary and text I/O. Files opened in binary mode (including 'b' in the mode argument) return contents as bytes objects without any decoding. In text mode (the default, or when 't' is included in the mode argument), the contents of the file are returned as str , the bytes having been first decoded using a platform-dependent encoding or using the specified encoding if given. Note Python doesn’t depend on the underlying operating system’s notion of text files; all the processing is done by Python itself, and is therefore platform-independent. buffering is an optional integer used to set the buffering policy. Pass 0 to switch buffering off (only allowed in binary mode), 1 to select line buffering (only usable when writing in text mode), and an integer > 1 to indicate the size in bytes of a fixed-size chunk buffer. Note that specifying a buffer size this way applies for binary buffered I/O, but TextIOWrapper (i.e., files opened with mode='r+' ) would have another buffering. To disable buffering in TextIOWrapper , consider using the write_through flag for io.TextIOWrapper.reconfigure() . When no buffering argument is given, the default buffering policy works as follows: Binary files are buffered in fixed-size chunks; the size of the buffer is max(min(blocksize, 8 MiB), DEFAULT_BUFFER_SIZE) when the device block size is available. On most systems, the buffer will typically be 128 kilobytes long. “Interactive” text files (files for which isatty() returns True ) use line buffering. Other text files use the policy described above for binary files. encoding is the name of the encoding used to decode or encode the file. This should only be used in text mode. The default encoding is platform dependent (whatever locale.getencoding() returns), but any text encoding supported by Python can be used. See the codecs module for the list of supported encodings. errors is an optional string that specifies how encoding and decoding errors are to be handled—this cannot be used in binary mode. A variety of standard error handlers are available (listed under Error Handlers ), though any error handling name that has | 2026-01-13T08:48:41 |
https://docs.python.org/3/tutorial/controlflow.html#match-statements | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | 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:48:41 |
https://share.transistor.fm/s/9bb11fc4/transcript | APIs You Won't Hate | Funding Open Source with Dudley Carr from Stack Aid APIs You Won't Hate 40 ? 30 : 10)" @keyup.document.left="seekBySeconds(-10)" @keyup.document.m="toggleMute" @keyup.document.s="toggleSpeed" @play="play(false, true)" @loadedmetadata="handleLoadedMetadata" @pause="pause(true)" preload="none" @timejump.window="seekToSeconds($event.detail.timestamp); shareTimeFormatted = formatTime($event.detail.timestamp)" > Trailer Bonus 10 40 ? 30 : 10)" class="seek-seconds-button" > 40 ? 30 : 10"> Subscribe Share More Info Download More episodes Subscribe newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyFeedUrl()" class="form-input-group" > Copied to clipboard Apple Podcasts Spotify Pocket Casts Overcast Castro YouTube Goodpods Goodpods Metacast Amazon Music Pandora CastBox Anghami Anghami Fountain JioSaavn Gaana iHeartRadio TuneIn TuneIn Player FM SoundCloud SoundCloud Deezer Podcast Addict Share newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyShareUrl()" class="form-input-group" > Share Copied to clipboard newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyEmbedHtml()" class="form-input-group" > Embed Copied to clipboard Start at Trailer Bonus Full Transcript View the website updateDescriptionLinks($el))" class="episode-description" > Chapters January 23, 2023 by APIs You Won't Hate View the website Listen On Apple Podcasts Listen On Spotify Listen On YouTube RSS Feed Subscribe RSS Feed RSS Feed URL Copied! Follow Episode Details / Transcript Mike chats with Co-Founder of Stack Aid, Dudley Carr, about the importance of funding Open Source projects, and Stack Aid's approach to helping Open Source organizations get paid. Show Notes Stack Aid - https://www.stackaid.us/ Dudley Carr - @dudley@mastodon.social Creators and Guests Host Mike Bifulco Cofounder and host of APIs You Won't Hate. Blogs at https://mikebifulco.com Into 🚴♀️, espresso ☕, looking after 🌍. ex @Stripe @Google @Microsoft What is APIs You Won't Hate? A no-nonsense (well, some-nonsense) podcast about API design & development, new features in the world of HTTP, service-orientated architecture, microservices, and probably bikes. Mike Bifulco: Hello, hello, and welcome back to APIs you won't Hate. My name is Mike Balco. I am one of your api co-hosts and guide through the world of designing APIs and building APIs, and doing all sorts of good stuff with API tech. I am joined today for an interview with a new friend of mine, someone who I met at a conference here in North Carolina. We're gonna be talking a little bit today about his project and some of the sort of mission of open source and supporting open source and things like that. So today I'm chatting with Dudley Carr from Stack A Dudley. How are you doing today? Dudley Carr: I'm doing great. Thanks for having me on. Mike Bifulco: Yeah, of course. Super happy to have you here. I have lots of questions for you and I'm, I'm super glad you were able to make it because from our initial conversations when we sort of bumped into each other all over the place at all Things Open your work seemed very interesting to me. And I think a lot of the squad here that is part of the APIs you won't hate community will really. What you're doing. So I wanna talk all about that. I wanna talk about how you got to where you are and what you're doing at Stack and just kinda get some of the history on, on the project in yourself. So tell me a bit about yourself and tell me about Stack. Dudley Carr: Absolutely. So I've been a, in the software engineering space for the. 22 years. I did my undergraduate in computer science at Stanford and graduated at the peak of the dot com bubble burst. And briefly did a stint in finance, actually worked at Lehman Brothers on their exotic derivatives until I realized that stuff is insane and I got out. In the last 20 years, I've spent all of it working with my brother, who also did computer science, and so we've gone from one venture to the next. So he is not here, but is probably the. More important of the duo. And anyway, we did our first startup in Rhode Island in my parents' basement. I think there was radon in that basement, but we we managed we actually built in the, you know, 2002, 2003, we built a product that. Became g talker. It was flash-based, you know, pre action. It was action script, but before it was even before they released all of their UI toolkits and stuff like that. And back backend was Python. It was initially a desktop application, then became a. Web-based product. And we developed that out and ended up selling that to Google and moving to Seattle in 2006 to join the Google Talk team and work on that. And we spent about five years at Google going from one project to the next. First we were in apps and and then eventually I worked on Google Voice and then before leaving. So that was super formative for us. We learned a lot of things, met a lot of great people. I think that was kind of the heyday for Google And and then after that we, we did some more startups food, food related things. And then we joined a company called Moz that does SEO here in Seattle. And we spent another four or five years there, I helped run a large portion of their engineering team and then grew some of their product areas. That was also really formative for us in terms of, you know, understanding that space, growing teams and you know, just going through various product life cycles and things like that. At the end of our MOS experience, we actually did another startup with a friend here in Seattle around crowdfunding. And this was actually crowdfunding for sports team. So, There was another platform that was really taking off. We found out about Stripe Connect and started using that. And really the, the basis for it was, you know, you have like a high school football team. They're selling candy bars and things like that. There's a lot of inefficiencies there and there's a lot of price gouging actually by merchants who sell products to schools to do that. And so there was. You know, 2017, 2018, there was a real impetus to you know, move all of that stuff online. And we have a lot of learnings that I think happy to chat about, but that was kind of formative for us in terms of thinking about, you know, how you move money from a set of people who wanna support something to, to the recipients and what all is involved in that. That was also just kind of how we, we transitioned from that into consulting. So we've been doing consulting for. Four years you know, we're kind of embedded engineers and product specialists in inside of organizations and to help them transfer in companies. And that's gives us a ton of flexibility and allows us to do cool things like what we've done over the last couple of years. At the beginning of the pandemic by the way, we launched something called Covid Trace. So we had the hot idea to do contact tracing. We tried to launch an app immediately. It was blocked by Google and Apple. Mike Bifulco: Oh wow. Dudley Carr: you're, you're not doing anything location based and we're gonna sort this out first, which is great. I think it was totally the right move on their part. We ended up adopting their the exposure notification. APIs that they have, and we ended up lo, I think we were the second app to launch in the United States. And so we launched with the state of Nevada and worked with them over the course of two years doing exposure notifications, rolling that out for iOS and Android, and then eventually moving all of Nevada off of our custom app onto IOS's, built-in exposure notification function. And at the same time building out other things in terms of getting results to people and things like that. So really interesting problems around health totally unanticipated. So that, that was actually that was all open source. We released all of that infrastructure, open source and the apps. And then, yeah, about a year ago we started on decade. Mike Bifulco: Wow. Yeah, that's some in incredible back history there. I, I. Was not prepared for that, that much. Incredible problem solving that you've gotten into in your, your career. For sure. As someone who lived through an entire pandemic of being, you know, Locked in my home and not leaving and being very concerned about public health and those things. Super, super cool to hear, hear you worked on that and, and obviously impacted so many people. And also, you know, collaborated with the, the big organizations like Apple and Google. That's massively cool to hear. I also don't think I realized that you and I had some sort of shared overlap not overlap, but, but maybe an odd Venn diagram of career stuff before working at Stripe, I worked at Google for a couple years. Not quite on Google Voice, on Google Assistant, so voice related stuff at Google. Although I'm no longer there and actually probably worth mentioning for posterity since you and I met at All Things Open. I'm also no longer at Stripe. So I'm, I've left Stripe in the past couple weeks, but I'm very curious to hear about your experiences with Stripe Connect and, and all that. And so. All of this history of all the crazy things you've done and, and like working with complex teams and big problems and across devices and problem spaces, and I'm sure languages and all the other things that have changed since what, 2003 when you first got into the the, the world of, of building things has led you to where you're at now. So tell me a little bit about Stack Aid and what you're doing. There. Dudley Carr: Yeah, so Stack stack is a service that allows you to fund your second first order and second order dependencies automatically. It, the impetus for it came about a year and a half ago when we. You know, repeatedly saw articles about people exasperated by their inability to sustain their open source project because, you know, the demands have increased on what they have to deliver and the reach, you the reach of their open sources beyond their wildest dreams, but, you know, they, they basically pay for it in their spare time or it takes away from other paying opportunities that they have. And so you see a lot of people kind of torn in those situations. We, that really resonated with us. As I mentioned, you know, we had spent time in the fundraising arena and we, you know, we saw. Definitely momentum around Get Up sponsors an open collective, but we, we thought that there was an opportunity there. You know, I think what's super interesting about the software development space as opposed to any other space where people are trying to raise money is that we know we know what, what you use, right? There's sometimes it's imperative, but increasingly it's a declarative. Way of specifying all your dependencies. And so we can, we can do so many things automatically to determine what you use and, and potentially influence how we allocate money. And so the, the, the seed of an idea was there and we started exploring, you know, the feasibility of it and what that would look like, and is it an effective model, things like that. And so that's been like the last year and it's, it's. Super interesting. Kind of flushing that out and we're, we've been super happy with the results and the initial reception when we launched a couple of months ago. Mike Bifulco: So. I've seen it and I'm sort of familiar with the product, but I wanna make sure that you know, it's abundantly clear what you mean when you're talking about this. So we're talking about funding open source projects in a way that is sort of sustainable and based on your dependency graph for projects that you're using. So when you say first and second order dependencies, what do you mean? Dudley Carr: Yeah. So by first order, so let's take a Packers saw JSON in the node E. The first order of dependencies are the the dependencies and dev dependencies that you list directly in that za js o n. Now, those first order dependencies in turn have their own za js o, where they list their dependencies. That would be the second order of dependencies. Now you can walk that tree down all the way down, and there are gonna be lots and lots more. not unusual for a project to have literally thousands of. Dependencies in their dependency tree. But you know, from a funding perspective, you have to draw the line somewhere. Otherwise, you know, you take a certain amount of money and divide it into tiny little pieces and it becomes somewhat meaningless. So we wanted to, you know, the, the easy thing was would be to just fund first order dependencies. But we, we realized, you know, a lot of those open source projects also want to give. And if we, you know, defaults matter. And we realize that if we came up with a mechanism that, you know, when you find a first order dependency, it passes some of that onto its dependencies. You know, you're doing that automatically for the ecosystem. You're bene, you don't have to have everyone opt-in in order to have further reach into the ecosystem. And so yeah, that was the impetus to fund first and second order depend. Mike Bifulco: Yeah. Got it. So from the, I I, gosh, I don't even know what, what you would consider to be the end user, but from the perspective of someone who is doing the funding, doing the supporting what does that look like? Like what is, what is the process for me? Say for a project I'm running, let's say APIs, you won't hate.com, right? It's a, it's a no JS project. We've got a whole heap of dependencies that are sort of built into this thing. What would I need to do to adopt. Dudley Carr: a great question. So, you know, when you go to Staca us, there's the first step in the onboarding process is oh, often thing with GitHub and actually adding the GitHub app to either your personal organization or some other organization where repositories are we then scanned those repositories for you know, files like Bax, J S O N, or you know, others depending on whatever language you're. And we use those declarative list of dependencies, we ingest that and start looking at that dependency tree. Once we have that, we, you know, we, we put you in the dashboard. We show you what we had discovered, like which files and which repositories we're pulling from. And we presume initially that you ne you want to fund all of those. You can, you can be selective, right? So I wanna fund these repositories and these package digest and things like, Based on that, based on the first order and second order dependencies we've pulled from that. And you can then indicate as a level of support that you wanna do on a monthly basis. We then calculate how much would go to each of those projects. So it's hard to des describe, but there's a tree that we have in the, in the dashboard and it shows you, okay, you've got React or low dash, for example, as a first order dependency. It has these second order dependencies and it shows you the amount of your subscription that goes to each one of those. And so that breaks down when you're, the next step is to enter a credit card and then, then you're off to the races. Mike Bifulco: Yeah. Okay. So from, from my perspective, it is, you know off with GitHub, get this thing added to my stack of or to my GitHub organization. It'll go and, and I guess introspect and look at, or I guess inspect is probably even the right word there. Go look at all the projects I have and give me the the first and second order dependencies for each is the target. Then from there to say like, just using easy numbers I want to donate a hundred bucks a month. To these various organizations. I, I have one fixed cost and Stack Aid kind of does the rest from there. Dudley Carr: That's, that's exactly right. Yes. Mike Bifulco: Yeah. Wow. So how, well man, I, I feel like I have so many questions. How does the money get from A to B? Like, how do you track down the the various projects that are then being funded? Dudley Carr: Yeah, so that's the fun part about building something like this is because it's effectively kind of like a marketplace, right? I mean, we have, we're engaging with both. Individual developers and companies who are supporters and of course have a relationship with open source, maintain. So we have slowly been reaching out to open source maintainers kind of as we drive awareness or if they've receiving funding, we will reach out to them individually. , but we also have been realizing that, you know, a lot of these people don't know who we are. There's a lot of things grabbing at their attention. So if they have an existing relationship with GI UP sponsors or Open Collective, we actually just use our corporate credit card and make the donation on those platforms. So our, you know, our goal is to get the money in their hands. And if they have an existing relationship, we, we lean on that. So that, that's worked out well. But but primarily over time, I think for for the ease of developers and to give them more control in terms of, you know, how those funds are allocated. Especially if there are multiple people working on a project. Things like. You know, we we would like people to, you know, claim their project on stack. Mike Bifulco: Yeah, sure. What does that look like? Dudley Carr: So we use Stripe Connect under underneath. So you know, when you log into the dashboard and you owe off you also have to oth with GI up at the moment. We're working on other. Hosting platforms, but you o often we actually verify that you actually are a maintainer on those repositories that you're trying to claim. We list out those repositories you claim them. And then as part of that claiming process, we also need to collect the a Stripe account. So we send you over to Stripe. They get all of the, the details necessary. To basically give us a, a stripe account so that we can deposit funds into at the end of the month. And then that's it. Then you're, then you're able to collect money from stack. Mike Bifulco: Yeah. Wow, that's great. So, so I'd imagine there's some population of people who are very pleased to find out they can come to Stack Aid, click a couple of buttons and have money being funneled into their project every month. That, that's gotta feel pretty cool to be able to, I don't know, land that dream so seamlessly. Dudley Carr: Yeah, I mean, I think it speaks more distract than to us. I mean, honestly, that flow is amazing and there's so much complexity abstracted. But I think from an end developer perspective, it is surprisingly easy to get up and running. And yeah, and I think it's, it's pretty great, you know, when you show up that a lot of the times there's, you know, a couple of bucks at the very least waiting for you there, and you immediately get that. I think that has been an important part of stack it, which is, you know, you, you don't have to be a developer. Like the developer doesn't have to have an account in order for money to accrue for them. So you know, you have this kind of problem I think on GitHub sponsors an open collective initially where people didn't have a relationship with those platforms, so there wasn't a way to get money to them. A lot of people have set it up, but there's also a large portion of the ecosystem that has no relationship with them. And so it was important for us to be able to accrue money and, you know, show people that you can actually. there's money in the open source that they've contributed and have that as a carrot for them to sign up. Mike Bifulco: Sure. Yeah, that's, that's a really interesting model and having been exposed to GitHub sponsors a little bit, I know that like one of the nice things that comes along with this actually may, might be a Stripe Connect requirement, but to access Stripe Connect, you have to essentially have viable tax information, right? Like the, the right information to be able to be paid out. So that you're not just, you know, sending off money to some anonymous bucket somewhere. But instead, theoretically it's tied to like an L L C or an individual proprietor or, you know, a more complex corporation in the case of vicar businesses. But a lot of that is, I would imagine abstracted away from you. You just need them to, to, you know, click the button and connect to stack with Stripe Connect. Dudley Carr: One of the biggest concerns that we had out of the gate was you. All open source doesn't happen in the United States. There are people across the world, and the United States in particular has a requirement called know your customer. And so you need a lot of details in order to verify their identity and make, you know, make sure that this isn't for money laundering or some other scheme like that. And so that is actually all abstracted away for us. And that is pretty phenomenal if we. A, a two person operation. There's just no way you're gonna Mike Bifulco: Yeah, Dudley Carr: that. Mike Bifulco: the, the scope and scale of those money laundering operations is far more complex and sophisticated than, you know, I think we might realize as, as sort of an average consumer. You know, again, I'm, I'm not at Stripe any longer, but during my tenure there, like you, you do Financial crimes training and it's pretty astonishing in the creative ways people, you know, will, will go to lengths to make money disappear or just harder to trace whatever the case may be. And nice that you don't have to worry about that. There's a lot of mechanisms in place to detect and prevent that fraud as well. . Okay. So I, I want to know a little bit about when did you what, what signals were you given that this was something that was going to work? In other words that when you're starting to build stack, because it's only a year and change old at this point was there a moment or a series of events that sort of made you feel like, oh, this is something that actually has some momentum behind it? Dudley Carr: Yeah, I think well, I think we had to prove to ourselves that it's viable and, you know, we, we have, there's some nuance to the model in terms of how we distribute that money. And, and more importantly, what's interesting about this problem is that it's not a one-time thing. So if no one shows up to collect the money, what do you do with that money? So there's a time component to it as well. Mike Bifulco: Yeah. Dudley Carr: we wanted, so we. There's complexity around the model to some degree in terms of implementing and doing it right, and we, we knew that the model itself needed to be validated and be comparable to things like get up sponsors and, and Open Collective. So we actually spent a large portion of the development. Building out a simulation. And so there's a, like simulation Dots US has. It's, it's effectively like the, it's our entire site, but it has 5,000 made up subscribers at various price points using Pax JSONs that we had discovered on GitHub using source graph. Source graph was pretty instrumental in terms of d doing that. And we, we needed package js os that weren't on n p, right? We didn't want to grab load Dash's, patch json accidentally. And because that, that's not representative of potential end users. So we took those 5,000 subscribers, plugged them in, you know, gave them some subscription amount between $25 per month to a hundred dollars per month. And we. Look to see what happens. Right? What's the outcome of, of this? Like, is it just a couple of projects that get all the money or, you know, what does that distribution look like and the, the, the end result is that, yeah, you, you still have a power power law curve just like you do on Get up sponsors in Open Collective, but it was it was more stretched. So we ended up, we ended up funding a larger percentage of the, let's say the top 25% of funds included a significantly larger set of projects. So even though they're at the tip of this parallel curve, they, you know, there's more of them included. That's great. But the middle, the middle was much broader. Right. A lot more of the money was going into that, and so that, that was the validation that we needed, right, internally to know that, yeah, we can reach more of this. I think in terms of the broader like readiness for this type of product, I, I think, you know, there's just a drumbeat of vulnerabilities and also just individuals. Really talking about the lack of funding, the lack of maintenance around this, around this. And so that is the validation that we continue to look for you know, as an opportunity to do something about, I think we're, we're very nascent in terms of evangelizing this and, and driving awareness. But I think, you know, those two things kind of has given us the confidence that you know, the timing is hopefully right and it's the right product for the time. Mike Bifulco: Yeah. Yeah. I, it's an interesting, almost, it's not that you have a chicken and an egg problem to, to work with, but I feel like the whole funding nut to crack is that like we, we all on some level, developers, engineering teams or organizations understand that it's important to Keep these projects funded so that they stay up to date so that vulnerabilities get shut down, bugs get addressed, functionality gets added, whatever the case may be. it seems like a lot of the social pressure lands on individuals to do the funding in a lot of ways, and I think that maybe is a law of numbers thing. Like people you know, you get a lot more call to action as an individual to go fund things. But my guess is that the bulk of the volume of money is coming from organizations who are willing to fund open source things. Is that roughly. Dudley Carr: Yeah, so we actually were able to analyze all of the Open Collective transactions. They do this amazing job of every transaction on Open, the Open Source collective, on Open Collective. You can literally download all of the transactions and so, I did that and I went Mike Bifulco: Oh wow. Dudley Carr: And yes, you know, organizations like Google and, and others, they do put in a ton of money. But if I remember correctly, I would say, Over 60% of it are from individuals donating at at much smaller amounts. So they're, they have a long tail and it is a significant portion of the contributions. And so it, it's, it wasn't as skewed as you would think towards large organizations. Mike Bifulco: That that is a, a bigger percentage than I would've guess. That's really interesting. So what, what is your call to action or maybe your pitch for those who might have the capacity to donate? Like how, how is the I guess the, is there a sales process for this? Is it something that you're going to organizations and people and trying to get them to discover and use Stack as donors? Dudley Carr: You know, I think, I think there are certain organizations that are very attuned to open source and, you know, they have open source program offices and they are actively engaging those communities and they are. they're looking, you know, they're either doing this themselves. So century is a customer of Stack and they did a ton of this by themselves. They, they wrote custom things to analyze their dependencies, and they had a big spreadsheet and it's super impressive, but it's incredibly time consuming. And I think Indeed and others are also analyzing their dependencies and trying to figure out where to allocate money. So this is something that is happening today. So we're looking to engage with those types of organizations and understand, you know, how STACK can potentially be a part of that. So I think step one is to really engage with organizations that are receptive to it. I think that's the kind of low hanging fruit. And I think beyond that, you know, there's, there's or organizations that are certainly consuming large. Portion of open source and you know, there's kind of a, a sales, different sales process around, you know, here are the ways that you engage with open source at those organizations. Funding is one aspect of that. And so I think over time that's where that conversation's going. But I think the organizations that are currently funding open source to some degree, You know, they're kind of making the case for that and, and we, you know, we're trying to expand that conversation and, and as well as piggyback off of that, Mike Bifulco: right? Yeah. It's nice that it's kind of the zeitgeist is that it seems that support has really changed in the past, I don't know, maybe 10 years to, like open source is something we can try or should try to, open source is something that, you know, I is the infrastructure of the internet in a lot of ways and something that you know, almost the, the ethical impetus is to support open source projects and to also be a part of that if you're able. So, okay. I, I guess one more important question then, if I'm an open source developer what, what are actions I can take to be proactive about I, I guess making sure that I'm, I'm covered by stack or that you know, that I'm doing the right things to seek funding. Dudley Carr: Yeah, I think you know, one. One theory that we have is that, you know, the, there are organizations like we were just talking about that are attuned and are willing to donate, but I, I actually think a fundamental shift will is dependent on individual developers donating and independent of the platform, but actively participating in that way of funding open source be it GI UP sponsors, open Collective Stack. Thanks, DD Dev, any of those platforms is a good way to start. But there, there has, you know, we have to have that expectation that developers are doing this just like they do other types of open source contributions. And I think that. That groundswell of developers participating and educating and kind of demanding this in their organizations is what actually turns the tide. And so our focus initially is actually to get individual developers to come on board and we're, we hope that we're. You know, one of those solutions that makes it a lot simpler. But if GitHub sponsors is the way that you do it, great. Right? Go, go on there. Fund, fund the people or the projects that you really care about. But I think that speaks volumes, right? And that I, I think is the thing that actually moves the needle. And those platforms have made it simpler. We hopefully have made it simpler based on, you know, what some set of people care about. But, you know, our, our goal is to evangelize individual developers. Contributing more. Mike Bifulco: Yeah, that's a noble conceit and definitely one of those things that I think all of the people listening to the show can probably relate to. I certainly identify with it. I, one of the things I've been mulling over a lot lately especially, especially in the past few weeks that I've been like reconsidering my personal budget and the way I allocate money for things is that I, I think I would like to be a little more public in sharing and explaining. The ways that I spend money in four good ways, right? Like charities that I donate to on one side, but open source things that I donate to projects that I support. And also, this is more on the creator economy side, but like Patreon and things like that, where there's like, you know, I love this podcast, so I give them a dollar a month, which is, you know, more than they would ever get from me clicking on ads. I could click ads every day for a week. And wouldn't give them a book. And it goes a lot further than you would think. And it, it's funny, I've been kind of thinking that that's something that belongs in. Almost public profile, like I should be sharing this somewhere and making that a part of the my, my persona, my support for the world. And I think that that's something that we have a, great opportunity to do with projects like Stack A and with other things that we all participate in because it also creates that social pressure and that. Impression that expectation that part of being a, a good citizen as a developer when you can and if you can, and if you have, you know, the, honestly the mountains of privilege that I'm sitting on top of, like, you should be giving back. I really like that. And I, one of the things that I like about STACK is honestly the, the tree view of the dependencies and seeing the amount of impact that, you know, even a few bucks a month can have is like visceral. You really feel like you, you see that not only are you using this cascade of things to power whatever project you're working on, but you can also give back to them fairly directly. And, there's infrastructure in place to do that for you. I think that's really exciting and I think it's a noble cause and I'm hoping it's something that a lot of the folks who are listening to the podcast will be able to jump into and go ahead long into supporting, but also benefiting from. Dudley Carr: Yeah. No, I appreciate that. I, I think what you're saying really resonates with us in that how you spend your money matters. You know, we are in a position of privilege where, you know, we we have discretionary money that we can funnel towards things. And I think, I think you nailed it. You know, a lot of these developers are, you know, at the moment maybe a couple of bucks per month. You know, we're still small, but I think it, it really matters to those developers partly because it is a real recognition of what they're doing and they know that someone took the time and their money, you know, to do that. And I think that's super powerful. I think it's easy to dismiss it as, oh, it's, you know, it's a trivial sum of money or something of the. But you know, when you are working on something, and a lot of times, you know, you can look at your MPM install numbers, like, oh yeah, that's through the roof. But this is, you know, getting an email from someone saying like, I like your project. That's really visceral as well. Mike Bifulco: Yeah. Dudley Carr: like people actually just paying. I think that's an incredible way. And so hopefully people are not put off by, you know, initially like, oh, the, the dollar amounts are not significant. It, it, it supports that individual at so many different levels. And so yeah, how you spend your money matters and and it has a really great upside on the other other side of it. Mike Bifulco: Yeah. , it's pretty profound and an energizing thing for me. Well, Dudley, thanks so much for coming and hanging out today. I have two important questions for you before I let you go. One is I wanna know how APIs you won't hate listeners can find you and talk to you if they're interested. And where can they go to get started with? Dudley Carr: Absolutely. Yeah. So you can email me at dudley dod e y stack.us and our website is stack a.us. I think if you search for Stack Google, we're number one. And you know, as we were chatting earlier, it's, it's super simple to get started. If you run into any issues please reach out and we're, we're happy to answer questions. But yeah, it's pretty self-service at the moment. Just click on the button o off and then hopefully you're off to the races and, you know, always looking for more feedback and, Yeah. No, we, we appreciate every, every person who signs up and happy to answer questions. Mike Bifulco: Great. Wonderful. Dudley, thanks so much for hanging out today. It's been a pleasure having you. And I'd love to catch up again you know, maybe in a few months or ear down the line to see how things are going. Dudley Carr: Absolutely. Thanks so much for having me. Really appreciate it. Mike Bifulco: Yeah, of course. Take care. Dudley Carr: Bye-bye. All audio, artwork, episode descriptions and notes are property of APIs You Won't Hate, for APIs You Won't Hate, and published with permission by Transistor, Inc. Broadcast by | 2026-01-13T08:48:41 |
https://open.forem.com/t/beginners#main-content | Beginners - Open 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 Open Forem Close Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 1 2 3 4 5 6 7 8 9 … 75 … 3379 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu digital marketing Junaid Rana Junaid Rana Junaid Rana Follow Jan 9 digital marketing # ai # programming # beginners # productivity Comments Add Comment 5 min read How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) Yogendra Prajapati Yogendra Prajapati Yogendra Prajapati Follow Jan 9 How to Build a website in 2026: Complete Beginner’s Guide (The Smartest Way to Launch Online This Year) # webdev # beginners # tools # business Comments Add Comment 8 min read What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning emmma emmma emmma Follow Jan 6 What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning # beginners # design # hardware Comments Add Comment 3 min read Science behind Mountain Formation Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Jan 4 Science behind Mountain Formation # beginners # learning # science Comments Add Comment 5 min read My Journey: Technology, Knowledge, and Building Meaningful Platforms ARVIND GUPTA ARVIND GUPTA ARVIND GUPTA Follow Dec 22 '25 My Journey: Technology, Knowledge, and Building Meaningful Platforms # technology # software # softwaredevelopment # beginners Comments Add Comment 2 min read Abrir Propriedades do Sistema via CMD (Windows) Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Follow Dec 22 '25 Abrir Propriedades do Sistema via CMD (Windows) # beginners # learning # productivity Comments Add Comment 2 min read The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence Abdulla A Abdulla A Abdulla A Follow Dec 23 '25 The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence # beginners # learning # motivation 1 reaction Comments Add Comment 7 min read 🌿 5 Simple Habits to Improve Your Daily Life Dharmikk Baria Dharmikk Baria Dharmikk Baria Follow Dec 23 '25 🌿 5 Simple Habits to Improve Your Daily Life # watercooler # beginners # motivation Comments Add Comment 1 min read Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Rajguru Yadav Rajguru Yadav Rajguru Yadav Follow Dec 27 '25 Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story # discuss # programming # ai # beginners 10 reactions Comments Add Comment 3 min read My North Star as an AI Founder (And Why I’m Not Changing It) Jaideep Parashar Jaideep Parashar Jaideep Parashar Follow Dec 18 '25 My North Star as an AI Founder (And Why I’m Not Changing It) # webdev # ai # beginners # productivity 15 reactions Comments 3 comments 3 min read Why is Displacement a straight line from the starting point to the ending point? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Why is Displacement a straight line from the starting point to the ending point? # beginners # learning # science Comments Add Comment 2 min read Scalar vs Vector Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Scalar vs Vector # beginners # learning # science Comments Add Comment 2 min read What Is Displacement? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 What Is Displacement? # beginners # learning # science Comments Add Comment 2 min read Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market Isabel Rayn Isabel Rayn Isabel Rayn Follow Dec 11 '25 Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market # watercooler # beginners # learning Comments Add Comment 4 min read 4.4 ऋग्वैदिक काल Anil Anil Anil Follow Dec 5 '25 4.4 ऋग्वैदिक काल # beginners # education # learning Comments Add Comment 1 min read 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short Menula De Silva Menula De Silva Menula De Silva Follow Dec 4 '25 🚀 How I Got 25,000+ Views in 2 Days on a YouTube Short # socialmedia # webdev # productivity # beginners 1 reaction Comments Add Comment 3 min read Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning Aparnaa Jadhav Aparnaa Jadhav Aparnaa Jadhav Follow Dec 4 '25 Starting Over in 2026? Here’s How to Create a Vision Board That Supports a Fresh New Beginning # beginners # motivation # productivity Comments Add Comment 4 min read Best Courses to Learn AI for 2026 Hameed Ansari Hameed Ansari Hameed Ansari Follow Dec 8 '25 Best Courses to Learn AI for 2026 # ai # programming # productivity # beginners 5 reactions Comments Add Comment 1 min read All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Amelia Hartley Amelia Hartley Amelia Hartley Follow Dec 4 '25 All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark # beginners # learning Comments Add Comment 4 min read How to Search Non-Patent Literature for Prior Art Alisha Raza Alisha Raza Alisha Raza Follow for PatentScanAI Dec 1 '25 How to Search Non-Patent Literature for Prior Art # beginners # learning # productivity Comments Add Comment 7 min read Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Bella Stewart Bella Stewart Bella Stewart Follow Dec 1 '25 Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies # beginners # learning Comments Add Comment 3 min read Running Without a Plan and Learning Who I Am Miles Hensley Miles Hensley Miles Hensley Follow Nov 29 '25 Running Without a Plan and Learning Who I Am # watercooler # beginners # motivation Comments Add Comment 11 min read A Beginner’s Guide to Power Yoga for Weight Loss and Strength bhaktimeshakti bhaktimeshakti bhaktimeshakti Follow Nov 30 '25 A Beginner’s Guide to Power Yoga for Weight Loss and Strength # watercooler # motivation # learning # beginners Comments Add Comment 6 min read Beginner’s Guide to IT Support Ticketing Systems Amit khan Amit khan Amit khan Follow Nov 27 '25 Beginner’s Guide to IT Support Ticketing Systems # beginners # career # helpedesk # productivity Comments 1 comment 3 min read ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past Jean Klebert de A Modesto Jean Klebert de A Modesto Jean Klebert de A Modesto Follow Nov 27 '25 ## ⏳ From Dot-Com Bubble to Digital Hype: Learning from the Past # discuss # productivity # career # beginners 3 reactions Comments Add Comment 2 min read loading... trending guides/resources Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Abrir Propriedades do Sistema via CMD (Windows) How to Organize Your Notes Using Printable Lined Paper — A Simple Productivity Hack How to Find Patent Prior Art in Research Papers Understanding the All Ordinaries Index: Structure, Purpose, and Market Role Science behind Mountain Formation Understanding ASX 200 Futures and Their Role in Market Observation Understanding the Basics of Pay-Per-Click (PPC) Advertising A Beginner’s Guide to Power Yoga for Weight Loss and Strength All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark Decoding Startup Success: Understanding Burn Rate, Runway, and Churn Metrics Understanding the FTSE AIM 100 Index and the Growth Potential of Its Companies Creating a Physical Wired Network in Cisco Packet Tracer - My Experience | Israh Binoj Best Courses to Learn AI for 2026 Yelken Eğitiminde Hissetmenin Bilgiyi Geçtiği An: Teknenin Sizinle Konuştuğu O An Yelken Eğitiminde Sabır: Rüzgarın Öğrettiği En Değerli Ders How We Process Information Using The DIKW Model How to fix: “less than 1MB free space" Warning 📍Un Viaje Continuo: De Córdoba a Barcelona A Beginner’s Guide to Channel Attribution Modeling in Marketing 💎 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 Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here 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 . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:41 |
https://share.transistor.fm/s/940dfccb/transcript | APIs You Won't Hate | The State of the API Address APIs You Won't Hate 40 ? 30 : 10)" @keyup.document.left="seekBySeconds(-10)" @keyup.document.m="toggleMute" @keyup.document.s="toggleSpeed" @play="play(false, true)" @loadedmetadata="handleLoadedMetadata" @pause="pause(true)" preload="none" @timejump.window="seekToSeconds($event.detail.timestamp); shareTimeFormatted = formatTime($event.detail.timestamp)" > Trailer Bonus 10 40 ? 30 : 10)" class="seek-seconds-button" > 40 ? 30 : 10"> Subscribe Share More Info Download More episodes Subscribe newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyFeedUrl()" class="form-input-group" > Copied to clipboard Apple Podcasts Spotify Pocket Casts Overcast Castro YouTube Goodpods Goodpods Metacast Amazon Music Pandora CastBox Anghami Anghami Fountain JioSaavn Gaana iHeartRadio TuneIn TuneIn Player FM SoundCloud SoundCloud Deezer Podcast Addict Share newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyShareUrl()" class="form-input-group" > Share Copied to clipboard newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyEmbedHtml()" class="form-input-group" > Embed Copied to clipboard Start at Trailer Bonus Full Transcript View the website updateDescriptionLinks($el))" class="episode-description" > Chapters December 1, 2021 by APIs You Won't Hate View the website Listen On Apple Podcasts Listen On Spotify Listen On YouTube RSS Feed Subscribe RSS Feed RSS Feed URL Copied! Follow Episode Details / Transcript Matt and Phil are joined by Matthew Reinbold, director of API Ecosystems and Digital Transformations at Postman, to talk about Postman's State of the API 2021. Show Notes Matt and Phil are joined by Matthew Reinbold, director of API Ecosystems and Digital Transformations to discuss Postman's State of the API 2021 report, detailing various data points from around the API world from which specification people turn to, to how confident people feel deploying their APIs. They also discuss various topics around remote work, how APIs enable more remote work and what will happen in the next few years for APIs. Notes: Matthew on twitter: https://twitter.com/libel_vox Postman's State of the API Creators and Guests Host Mike Bifulco Cofounder and host of APIs You Won't Hate. Blogs at https://mikebifulco.com Into 🚴♀️, espresso ☕, looking after 🌍. ex @Stripe @Google @Microsoft What is APIs You Won't Hate? A no-nonsense (well, some-nonsense) podcast about API design & development, new features in the world of HTTP, service-orientated architecture, microservices, and probably bikes. Matt Trask: Cool. Welcome back to APS. You won't hate episode 17. I have Phil with me and we're joined by a very special guest today. Matthew Reinbold, fresh from postman, who is a director of API ecosystems and digital transformations here to talk about their report, the 2021 state of the API ecosystem. Matthew, how's it going? Matthew Reinbold: It is going. I am happy to be here first time, caller, long time listener. Is that how we say that? Matt Trask: I think that's yeah. It's how you say it. Yeah. So I mean, for those of you, like in the off chance that someone doesn't know who you are in the API ecosystem world can you give us a little bit kind of about yourself? Like you manage two different newsletters, at least as well as a pretty prolific Twitter presence as well. But if someone hasn't run into you, like. Matthew Reinbold: Well, yeah, well, first off, thanks for calling it prolific. Some people would call it annoying, but yeah, I I manage a fair number of tweets over at Twitter slash L I B E L underscore Vox, reliable Vox. That's where I talk about digital transformation and APIs and a lot of technology stuff. Occasionally. Fights with blockchain and NFT enthusiastic. But then I also manage, I also manage a newsletter called net API notes, where for almost 200 issues, going back to 2015, I've covered the landscape. I've shared essential bits of information. I've tried to boil down the, the. Current climate and get it right into just the most essential things that decision makers need to know and care about. And then I do a fair amount of blogging on a blog. That's very imaginatively named Matthew reinbold.com. In there, I talk about a fair number of things as well, but in, in, in short my passion is really about coaching people, helping people, teaching people to get better with their API ecosystem. Matt Trask: That's really cool. So one thing that kinda stuck out to me cause it's, so we're going to be talking about the 20, 21 Sidi APR report. However, I'm curious since you've been doing it now since 2015, you've been keeping notes on. The API world. How does your kind of, I hate to say this phrase, the 30,000 foot view of everything that, you know, from 2015, how does that kind of line up to what you saw with the 2021 state of the API report? Matthew Reinbold: Oh, that's interesting. So there's definitely. Maturing as a industry, we've gone through a number of phases. Those of us that have been around the block a few times, see trends come. And most often they, they tend to roll away. And over that time we have to develop models so that we can kind of. Pick the, the, the wheat from the chaff, you know, what, what are the properties of something new, some kind of buzzword, some kind of hyperbole that we can latch onto and say, yes, this is worth investing in. This is worth our interest in our effort versus, yeah, this is some marketing system, some spin as I'm looking at the 20, 21 postman report. I see. Where we've come. It's gone from being single point to point integrations. One-off bespoke API APIs to where we're now talking about things as ecosystems. We're now talking about collections of these things and how entire organizations. Manage these as, as something that's beneficial, something that's collaborative and, and managed as a separate entity rather than, than each individual unit I've got Phil here. So I have to use the forest for the trees analogy rather than just managing the individual API trees. There's now a greater awareness of what the forest, what the forest role is in the company and how to manage that. In a unique way, as opposed to the individual pieces. I will say for those that are listening, like I'm one of the things I want to highlight right up front here is that you don't have to enter an email address. It's not behind the page. We really felt strongly at postman that we had to get this information out to the most number of decision-makers so that they could make better decisions so that they could be informed as they're developing their strategies and roadmaps. So if you go to postman.com/state-of-api, you'll be able to download. With out any worry about having somebody from sales follow up with you later, or getting spam in your inbox, it's free for all. We want this information to be used. We want the dialogues to happen. We want the discourse to be rich and for me and frothy. And so please, you know, don't let past marketing spam. Stop you from checking this out. We want this in the hands of people. Phil Sturgeon: Fantastic. That's good to hear. I mean, that's I haven't got around to reading it as you might have seen from Twitter. Life has been a bit of a mess recently just spending far too much time in the field, as opposed to in the field doing APA stuff. But, yeah, that's definitely always been a concern of mine, of, you know, you hear about these white papers and reports and you just know so many of them like should have just be in the blog post, but instead that like a PDF that and you've got to enter information and then you just get like that fifth email, like, why didn't you reply to my previous four? I was like, I don't know who you are. I just want to read this thing. So yeah, I'm glad you folks are going in a different direction, but Maybe just taking a step back. Like, what is the state of API is report all about where are you getting your information from? What sort of research is being done? And what's the hospital. Matthew Reinbold: Great question. So this is, as far as I know, the largest survey of its kind, we had more than 28,000 people respond to our latest in a series. What we tend to do is try and track where the industry is at. And typically that's been around certain areas. Like how much time do you spend developing API APIs? What kind of tools are you using? Really good stuff there tracking the growth of, of the industry and the maturation of the industry. What I brought to the table this year. Was an interest on finding the behaviors that lead to sustainable, healthy API ecosystems. Like so much of what we talk about when it comes to API ecosystems is still very anecdotal. We tell stories about the Bezos Amazon memo, where we talk about like Twilio or Stripe, but when it comes to decision makers in large organizations, they're still. Trying to pull at what are decent KPIs, what are the behaviors I should be grooming or promoting within my company to make sure that I can keep producing quality API experiences again and again and again. And so what we did with this report that I'm really proud of is dig deep and discover, like, what are the correlating behaviors in organizations that lead to good things happening for companies? Phil Sturgeon: Okay. That's interesting. Cause I think. There's always this question around, like, what's a good API and what's a bad API. Right. And that's just such a nebulous, almost pointless topic so often, because you're just going to end up with opinions about camel case versus kebab case and opinions about rest versus graph UI, and all the nonsense that we love to fight about. And there's going to be someone with a fever at HTTP status code. And none of that actually matters, but you're talking about more of the business level stuff or what, what sort of things have come up as like. Really interesting results from, from your survey about how to build a good API what's what's, what's new and what's interesting. Matthew Reinbold: Right. Well, one of the things I wanted to look at was some of the insights that popped out to me when I was reading accelerate. So accelerate is like from. The previous decade, but it was written by Nicole Forsgren, Jess humble, Jean Kim, they came together and tried to figure out like, what was it about dev ops? That was so powerful. And they wanted to do it in a, in a way that quantified things, not just like, Hey, this is awesome. You should be doing it, but like get to the meat and potatoes of why is this powerful and why should businesses adopt dev ops? And as they went through their research they ended up discovering that there was really four things, four metrics that showed how dev. Made for better organizational performance. And those things were lead time, deployment, frequency, meantime to restore, or how quickly you recover and the change fail percentage. And I thought, huh, that's really interesting. Now that's for dev ops, but if these things are so instrumental in having organizations outperform. Their peers. Can we find the same correlation with API APIs? If we have the same behaviors, can we therefore then draw a line and say, if you have these things, if you have positive aspects of these four attributes, can you then have a more sustainable, more powerful API program? And based on our survey results, the answer is yes. So I can, I can go in and how we, how we drew that correlation. Phil Sturgeon: I'm curious, what sort of metrics are We, looking at? Matthew Reinbold: yeah. So first off we asked people on a 10 point scale. What, how, how well do you think that you've become API first? So out of our 28,000 respondents, they looked at this 10 point scale and they, they put themselves, you know, how they felt approximately 8% of the people that responded said, yes, we are either a nine or a 10 on the scale for API first, we said fine. And then we went through and we said, okay, you know, how long does it take you to make an API? Are we talking hours, days, weeks, so on and so forth. And we also said, okay, you know, not just time to produce, but how frequently you deploy and how many times do you have a deployment failure? Meaning like you put something in production, but it didn't work. Right. So you have to roll back and then like, what was your time to recovery? Like when an outage does occur and let's be. And outage always occurs at some point. Like how, how quickly can you recover from those things? So we got these nice, you know, bell curves and everybody kind of clumped toward the center on these things. And then we said, okay, Now the magic is we go back to that first question, the people that say their API first that have some kind of strong belief that they're doing API first, let's see how they compare to their peers on these metrics. And again, and again, all for these items, API, first people perform better. So, you know, taking one example here. API first people were able to deploy 17% faster than their peers and you know, in a day or less. So if you are API first and granted, there, there might be some subtlety in how a company defines that. But bottom line, if you are API first, you perform better on these metrics than your counterparts. Phil Sturgeon: Interesting. And yeah. Seeing, seeing as you raised it, what is API first? There's, there's a lot of different definitions floating around. Right. And so just for listeners that might not have listened to everything we've ever talked about and read every blog post we've ever read ref ever wrote how do you define it? Matthew Reinbold: Sure. Well, first for people that haven't heard this and haven't listened to every episode, shame on you. Second, I define I defined API first and. Making the API experience or the interface, the primary means for the functionality exchange. So not viewing, like I'm going to create this functionality and then subsequently go and some other team or, or some other project we'll be wrapping this thing in an API. It's thinking of creating an API experience as the primary exchange mechanism with dysfunctional. Not a library, not a module, not a class, the API. So this is slightly different than API design first, which is, I am going to subsequently talk to stakeholders, create a model, whether that's in an open API document or some other means, but I'm going to sketch that out. Test my assumptions, and then subsequently only begin code after. That's API design. First, I do draw a line between those two. They are very copacetic. They, they work together like peanut butter and chocolate, but there, there is a difference. You can, you can do API first without necessarily being API design first. Phil Sturgeon: For sure. Oh, well, we've got you on a roll. You're doing these really well. What is API as a product? Matthew Reinbold: Ooh, API API as a product. So that is creating an API with the. Awareness that it will have a roadmap. It will have ownership beyond just being put into a production environment that it will grow and change and subsequently necessitates the kind of modeling responsibilities and, and awareness that it will be growing and changing over time. Phil Sturgeon: Okay. So instead of, yeah, API first is your product should have an API. And that will be managed by the team who was making this product. And API as a product is a slight variant of API. First, that kind of takes that API out of that generic functionality team and says the API itself is the product. And another team potentially on the same team will be making a product using that Matthew Reinbold: Right. I, I would, I would, I would venture there's a lot of large enterprise environments for which API for. It's about a project that gets the thing into production. And then that thing is left to operate and run on its own. Perhaps there's some monitoring, perhaps some observability, but the actual team that made it is off doing the next thing and the next thing and the next thing there's not the idea that. This is a long lived item that, that produces some kind of business functionality value that is competing in a complex dynamic marketplace like that. That's the API product side of the house. Phil Sturgeon: Hm. Matt Trask: So the, I guess like the, the big question to bring up, I think right now is what did the pandemic do for the API ecosystem? Matthew Reinbold: Well, you know, first of all, I want to just stress that, that this thing that we kind of hand wave is the pandemic was actually like multiple congenital. Crises all at once. Right. You know, I, I want to, for the audience, like we're talking social unrest and political upheaval and supply chain disruption, and the, the pandemic was really a catch all for a tremendous amount of business stress. And what we've seen in the report is the usage of APIs, the number of API APIs the. Amount of focus and care on API. APIs has increased tremendously with that pandemic because business leaders, technology leaders are struggling with this amount of change, this amount of disruption. And so having architectures that are slow to change, difficult to change is just not cutting it in this. Set of multiple crises. So any kind of architectural advantage that allows them to change rapidly change quickly to do different things with how their development investment is deployed. So, you know, for example, taking that one dev team that was altogether in the office and being able to break it down into microservices to allow for greater asynchronous operation, greater flexibility. Those are the architectures that are being sought right now. Matt Trask: Yeah, that makes sense. I mean, it always here in America, I don't know if it feels sing, but you know, like there's. At the core level there. So like the whole, did we go back to the office and be Sandy the office upheaval as well. So it makes sense that there is kind of like a, a struggle on rapping, like getting non-technical CEOs, CTOs, CFOs their heads around the game-changing, this of APIs that doesn't surprise me at all to hear that they're still kind of, I don't want to say struggling, but unsure. Maybe like, Matthew Reinbold: Well, and, and, well, I, I think that's an interesting perspective because it assumes that leaders were in command and control positions of how the labor was divided anyway. And I would actually, I would actually posit that it's the opposite. It was everybody immediately going and running to their home offices and working in a remote work environment. The change in the communication paths changed the architectures that were subsequently produced by those teams. It's Conway's law in effect. And therefore, as we, as we look forward, as we look forward to what's going to happen, I would, I would venture that the organizations that pull people back to centralized locations, for whatever reason, I'm not going to debate whether that's good or bad, but the people that pull the development teams back to. see, like the Terminator two bad guy they'll reform remold because there will be more efficient communication patterns when everybody's face to face. Whereas those organizations that continue to have a distributed workforce will have more distributed architectural patterns because that's how communication is happening. Phil Sturgeon: That's really interesting. I haven't really thought about it before, but I, I, I bet there's been an uptick in kind of API design first, specifically due to this as well. Right? Because my experience working we work was, was pretty awful as far as like API planning goes and as a result, APA architecture and API performance and Matthew Reinbold: You don't say you should blog about that. Fail. Matt Trask: Yeah. Phil Sturgeon: 25. I'm going to do a book about that shit. Matt Trask: Have you tweeted about this yet? Phil? I'm not sure if anyone knows your true Phil Sturgeon: I did a talk. I did a talk recently. But yeah, there was, there was such an element of like, we're real in an open plan office, playing ping pong together and shooting each other with nerves that there was never any effort on API contract being written down in any shape or form because you're all sitting about. And you're just like, what's that end point? Cool mate. Oh, if slash whatever. Oh, is that a, is that property of booty? It's a string called true with QuoteWerks and then you didn't have a need to write it down because you just show it over, over the top of Nerf fire. And I, I do wonder if remote work, well, not necessarily remote work, but quarantine remote work has helped push people more towards it because if you can all be sitting around asking each other, you're going to be typing. The contract over slack. And if you're going to be typing it out over slack, which is inherently ephemeral, then you might as well type it into a Yammel file and commit that in the repo. And then you can have design reviews around the board request or other tools that the offer, that sort of thing. So, yeah, that's, that's just completely a hypothetical and something I'm thinking the second night and check that, but I'm sure it's happening. Matthew Reinbold: I completely agree. And, and let me throw in something that's not in the report, but something that's got me totally geeked out and I'm watching for on my radar, we are going to see the greatest Renaissance of API design documentation that we've ever seen in the next couple of years. Now, granted, you know, as far as Renaissance goes, maybe Renaissance. Documentation are not that great. So, you know, let's put the party hats back in the closet, but what we're seeing with the great resignation right now is all of that knowledge that people acquired in their heads is leaving. It's headed out the door and I've read reports like up to 80% of how to do things with API APIs is in people's heads. Like at we work. If you needed to know how API has worked. You know, you knew Phil was the guy that could get you straightened and Phil Sturgeon: I didn't have a clue. That was the problem. I was trying to find out how to do it. Matthew Reinbold: Okay. So I wasn't, it was somebody, it was somebody on the other end of a, of a Nerf battle away Phil Sturgeon: Someone who quit already is the person that you. Matthew Reinbold: But right now in organizations like you have this phenomenon where a tremendous number of people are leaving organizations and they might've been the sole person who knew where the end points were or knew how that particular tricky function worked. And as organizations are trying to deal with this and recover and still be productive, there's going to be a greater emphasis on having that crap written down, having things documented. Organizations don't have aren't left on their back foot like they are right now. So whether that's heavy handed processes, whether that's just a greater appreciation for documentation among the staff, that's left, whatever that manifests as there's going to be an increasing amount of emphasis on documentation, because people have seen that too much was stuck in people's heads and it's not sustained. Phil Sturgeon: Yeah, that's a really good point. I mean, and not just kind of documentation, but the whole open API as a source of truth earlier on. And I figured it has to be, has to become more noticeably important when Yeah. They've, they've lost the whole team. How the API works and you know what it's like, code's always a bloody mess. Cause you just hacked up within about what over the place and patch things and fix things. And what about and yeah, when they find themselves rewrite in the API, cause no one can really take it over and no one remembers how it works and there's no documentation for it. And it's just too hard to figure out when they just make a brand new one. And they have a whole brand new team doing it. Cause they've already lost all that stuff. Matthew Reinbold: Yeah. Phil Sturgeon: That's a situation that a lot of managers and business people are going to say, how can we go about avoiding doing this? And I just hope there's someone in the room that says, well, APA designed first would really help avoid this problem because otherwise they'll just repeat all the same mistakes again. Matthew Reinbold: Right. Absolutely. Whether it's design first or tools that help analyze existing traffic and write the document afterwards, like whatever you got to do, get that written down and start taking some notes against it because. It's it, I believe right now with the great resignation. It's an Achilles heel. That's probably hampering a lot of organizational ecosystems right now. Matt Trask: Yeah, I would definitely agree. I mean, it shows in the report under open API three dot oh, 44% of people are aware of it, but they don't use it 28% say they use it. 12% said they use it, the love it. So even just combining use it and use it in love. It still does not match aware of we're not using it. Which means that there is definitely a. A river to jump over. So to speak, to getting more people on, to open API, which is probably currently like the standard for API documentation right now which comes back to your point, which allows them to start writing things down and start documenting things. And Phil gets it by bus tomorrow. We work is still going to be okay. It very well could happen. Which is exactly why I use that example. And it, it, yeah, it it'll give the organization a little bit more or a little less reliance on what's in people's heads a little bit more stability in case great races, nation three Datto happens in three years. You know, you don't know what's gonna happen. Phil Sturgeon: Is that when everyone resigns from web three point now, Matt Trask: please. Don't don't threaten me with a good time. Like I've already, I've already muted those web three and NFD on my Twitter and it cleaned it up so Phil Sturgeon: Why do you hate progress, man? Matt Trask: A lot of reasons. I'm a combustion at heart? No. Matthew Reinbold: Hey, if you don't, Phil Sturgeon: particular messages of this progress that are the problem. Matthew Reinbold: if you, don't stand for something, you'll fall for anything. Good for you, Matt. Matt Trask: yes, I've always wanted my life to be attributed to a, a Hamilton quote. So I am glad I did. I can check that one off to get back onto the actual topic and not just bashing NFTs for an hour and a half, which sounds like a lot of fun. What you the most about this report? Like what was something that you read that just you weren't expecting? Matthew Reinbold: I, I think there was two things that when you combine them together it made me tilt my head and go, huh? The, the first is that more than anything else? Including speed to production. People want quality API APIs. They want stability. They want some other things reliability. But the primary thing that people want out of their, their API APIs is quality. And yet when it came to whether or not people had time to test. Everybody acknowledged that testing was good. Tested was valid, but nobody had enough time for testing and it's like, huh? These two things kind of seem like. The, the two sides of a coin, right. You know, people aren't getting the quality that they want, but everybody acknowledges that they don't have enough time to do testing, even though they recognize the testing is an extremely valuable type thing. So I think when it comes to socializing this report and talking to decision-makers and doing the kind of coaching that I so often do, I, this is one of those things too, to bring up, like how in your program are you supporting. Testing and ensuring that enough is being done there so that your developers feel like you're, you're reaching the kind of quality goals that, that you're, you're promising to the rest of the world. Phil Sturgeon: Hm, do you, is the survey broken down by role? So can you, can you look to see if. Managers and engineers have a rule, very interested in, in high quality. And engineers are going, but we don't have enough time, but the manager's like, oh, they definitely have enough time. Matthew Reinbold: Right. So we do have a breakdown by role and job title, but I don't have the numbers in front of me that, that combined, and show me how to break down the quality question. Phil Sturgeon: Yeah, that'd be an interesting one. Cause yeah, so many roles, so many organizations, I just take it as like a universal truth is that companies are just, you know, business and product are demanding feature, feature, feature, feature, feature, and engineers are just like screaming, just keyboards on fire, trying to try to hit them goals. And everything's just wonky as hell. And it seems to be everywhere I go. There's not enough to have. There's not enough time for QA. They might've got rid of the QA team because it's slowed down product and slowed down delivery of features. Yeah, everyone wants high-quality API has, but no one wants to put the time in to testing because testing is inherently hard and slow. Matthew Reinbold: Right. And kind of along those same lines, another stat that jumped out at me was that 76% of the people building API APIs have less than five years experience doing. I mean, you know, as far as restful APIs now, we're, we're more than a decade into that journey. So that stat leaps out at me, like what is it about API development, where we're getting people with zero to five years experience like what's happening. There are the successful API builders, aging out and becoming management. it, are they moving on to web three O and NFTs? Like, like what is, where are our experienced API builders and why are these critical pieces of business infrastructure? In the hands of relatively younger people. That's not to say that they can't be doing a good job, that, that it's impossible to build a great web experience at your first time at bat. But it's also something where I think everybody on this call would probably agree. Experience counts, experience matters. Ha being around the block once or twice, you pick up a feel for what's beneficial, what's maybe a little wonky and you can imbue that into a better design at launch. So, you know, where are the. 10 year, the 12 year, the 15 year veterans. And why are they not the primary source of API infrastructure development? Phil Sturgeon: Yeah. Some that I've seen so much, again, just, I love complaining about we work. Pretty much everyone that was a junior developer, Right. Like the vast majority, what, what you need developers and their role responsible for creating you know, there's like a hundred API APIs and, you know more than a hundred junior developers with just a sprinkling of seniors who were more on the cowboy coder end of things. Not, not to be rude, you know, like startup, you need to be super agile, super fast, not, not a perfectionist. And so, so many of the problems where this is, this person's first rails app, like they know how to accept incoming Jason parameters and they know how to spit something back from the database. And. That's that, and they know how to make a web request. So he talks to . He talks to F talks to G in the thread, and then no, one's got a timer anyway. So everything falls over, like, things like that. The sort of thing you realize, if you've been doing APIs for five years, or for 10 years, you've been doing it for 10 years, you wouldn't do that. You just wouldn't do that. You'd put something in a sidekick job and then implement a web socket or a web hook, or literally anything else. But. That's the sort of thing you do when you consider like HTP failures or server downtime, to be an edge case that is like some weird scenario that probably won't happen. And when you've been doing it for a longer time, you're like you, you change your mindset to this web requests probably won't work. And on the off chance that it. This is what should happen. And you just get really defensive and paranoid and have like 25 different guard statements and, you know, 25 different types of ex exception catching and, and every single circuit breaker and trigger warning that you can possibly put on this thing. And there is, yeah, there is a change in mind. Around around that kind of it doesn't, I'm not being a gatekeeper or at least they're saying you've got to be doing EPS for 10 years until you're good. But when you start out, you you're such, you're more of an optimist. You haven't seen it go wrong in as many ways. You haven't had cascading failures and you haven't had all these terrifying things that happen. So that, that is definitely a concern for me is that I think, yeah. Happy, happy path development. When you go from having one AP. To having 20 or a hundred, the, the the chance of straying off the happy path gets exponentially worse. Right. And, and that's just something, I think a lot of these younger developers on experience with. Matthew Reinbold: Right. Even, even when it comes to design, having used API APIs, having to incorporate the API APIs, you better understand what makes a good description and what is just a reiteration of the, the name itself. Yeah. Yeah. If I have a field called date of birth and the description is just the birth, that, the date that the person was born on, like, well, what was the. do I need to refresh it? Or is it cashed? You know, like, can I store it or is it part of some kind of regulatory PII? And I shouldn't, you know, I can use it, but I shouldn't store, like, there's so many issues that once you've been down that road, and then you're asked to produce an API, you bring that experience with you and you put it into the description that adds so much that yeah. I, I, I, I don't know. How we continue to get that, that experience circulating and get that in front of people. But I think it's really important. Matt Trask: Well, I must wonder too, like how many of those, like experienced API builders are getting swallowed up into Stripe? Twilio, Google. And kind of almost locked away working on their API APIs and not able to share their experiences down the road to junior developers in their own companies or interim networks, things like that too, because it feels like you do your five, seven years as developer, you get pulled into the management game and then all of your knowledge is still there, but you're having to balance both managing a development team, hitting your goals. Pushing out products because you've got to make money for the business. And all of your knowledge that you've worked so hard to gain is kind of sidelined in the name of profits or KPIs or whatever it might be. Matthew Reinbold: Possibly there's, there's certainly exceptions that spring to mind. One of which is Tim Burks and the team over at Google and with the number of resources that they put out there. For their APIs. It's, it's kind of a mouthful, but if you do a Google search for that, they've produced a tremendous amount of documentation about how they support API APIs at scale, how they do their design reviews, how they think about consistency and cohesion across their entire footprint. So that certainly what you described could be the case in some places. You know, I, I, I do think that it's not necessarily the default that's people go off to these big organizations and then just disappear because the folks at Google around Tim and his crew they're doing some great work. Phil Sturgeon: So I've been sat in the room with you having these sort of conversations your last job, Right, Like a center of excellence type stuff. You, you get a bunch of smart people and me together and start talking about what, what would help with these various different problems? Like how do we do APA design reviews? How do we do governance? What standards should we be interested in? So I think sometimes yeah. Experienced developers can get sucked up into these companies and kind of finish and end up having that scale was used for something else. But I, I think companies that have those governance processes, like they're sharing their experience back by creating style guides, by creating programs that they explain how these, how these like API designed life cycles or API life cycle should work. And that's a way that they can essentially. Distribute their experience. So instead of like, I know what to look for when I'm reviewing a poor request, they can create a style guide. That means that everyone will do that. I think the danger there is that when style goes focus on what, instead of why then, then you kind of lose some of that experience because it just seems like arbitrary decisions delivered from upon high. Right. You just get. Do it this way, but, but Y I've read loads of style guides recently. And, and some of them, I should probably show the examples. It's just like, do this. Like, why you don't tell me what to do? You don't my dad, like, it just, I couldn't figure out what they possibly could have meant by it. Cause usually I can look at something. Why might they mean that? Oh, that reminds me of a thing that happened along these lines. They probably got burned by that before, and they want to avoid it, but if you don't see why it just sounds arbitrary and you're not actually teaching anyone on anything, but if you do it right. that that can be really helpful. Matthew Reinbold: Right. And it's also essential that if you're designing these systems like a governance or like a center of excellence that you have the feedback process that you have, the, the communication cycles so that when people do have that kind of. That they have a recourse. It's not a dead end. It's not either you do this or you're punished for it, but oh, if this doesn't make sense, here's who you talk to. Here's how you can escalate your concern here is how you elevate your edge case. And we can have a discussion about it and you can help co-evolve this thing, because you own this as much as somebody else, the, the phenomenon that you described, where it's a dead end. It's thrust upon you. You don't have ownership of that. And as a developer, that does not feel good, that does not invest you in seeing the long-term growth of, of that system. You want to burn that system. You want to be the rebels flying through the death star trench. You want to take that thing down? So what's essential is to realize. You provide the avenues for people to, to voice their concerns, voice their questions, and make them feel heard in such a way that their process, the process is theirs. It's not something done to them. It's it's their process. Phil Sturgeon: I'm just laughing about the death star rebel situation. Now I'm completely distracted. I need to go rewatch some star wars. I don't know. Matt Trask: I mean, your, your thought on the ownership thing is also interesting cause And we like watching the junior Twitter, the junior developer Twitter circles, which is not the end all be all of it all, but there is a large emphasis on if you want to make more money, you need to jump ship every two years on average. And that kind of removes the does or not the desire, but like the, the ownership of any sort of product from a junior developer, because in two years, they're going to be onto another thing. They're going to be onto another system. Codebase, maybe another language and it, it does kind of bring back, like, how do you entice people to have ownership, even if they only are going to plan to say somewhere for a short period? Because we all know that like having, like you said, having that ownership is going to kind of make you more invested, more caring, more thoughtful, more empathetic towards whatever it is that you're building. Matthew Reinbold: Right. I mean, we're veering into management territory, which I'm happy to talk about. I, I know. Matt Trask: very allergic to management. So. Matthew Reinbold: But I, I was just reading Harvard business review. Hey, I'm fun at parties too. So I was reading Harvard business review talking about COVID and the great resignation and the, the management challenges that, that come with that and what we need more. In all companies is a feeling of belonging, a feeling like we have a career progression feeling like our, our, our work has impact and all too often management, just as about making sure people don't do dumpster. Right. You know, I'm, I'm here to police you because the organization doesn't trust you. And it leads to all kinds of weird effects. Like, Hey, if you actually want to grow your career, you need to leave. You need to hop companies every two years and let's be clear that may work, but it's still very disruptive, not just for the company, but for the individual. 'cause they're having to rebuild all of those social structures, their relationships, their patterns, the routines it, it's not, it doesn't come for free. And so from a management standpoint, if you can show people how to have that fulfilling career, how to fulfill those needs. They don't have to jump ship every two years. There's no reason that that has to be the default blueprint. And from a company standpoint, you actually benefit from that accrued experience rather than having a developer. That's done the same thing. Five times you get five years of experience. That's really powerful, really tremendous. And that, that ultimately not only leads to better APIs, but leads to a better employee. So there is a disconnect we need to work with our management layers. It shouldn't just be the technician that has some headcount is by default manager. There needs to be an appreciation for how those are unique skill sets. Those are unique muscles that need to be exercised, but. If we can create that fulfilling sense of duty then, and that the career path for these individuals, we can get them off of this kind of binge and purge career treadmill. Matt Trask: So that's a really, yeah, that's a really good way to put the whole two year turn. And I mean, it comes back full circle to what you just said earlier, which is, you know, 75% of API has been developed now or done by people with less than five years experience. And that's probably because of the same, people are jumping, jumping, jumping. Whereas if you can keep them around, make them happy, make them feel like they belong. We might actually start seeing that number. Dropped significantly to more experienced API developers building more thoughtful API design with, with years of knowledge built up. So I think it'll be really interesting to see kind of what happens with this great resignation how that all shapes up. And then it'll be interesting to see to kind of the 2022 say the API report. How does that. How, how will things change from a year in a year going forward? And what can we expect possibly looking at these two years, the next five years after that, the next 10 years growing on different trends, you know, we might see NFTs ruling the world. We might see graph QL. Rolling. Phil Sturgeon: No comment. Matt Trask: Matthew is kind of shrugging Phil Sturgeon: we're all sad. Now, rural sat now, NFTs powered by graft UL, problem solved. Can you, can you still right click that? No, you can't. It's like a post. So. Matt Trask: Well, there goes Matthew Reinbold: Each unique query is published as an innovator. And you can put the ownership of that query in a blockchain so that you don't have the centralized point of failure. Phil Sturgeon: I was going to thank you for being for, for making this podcast sound intelligent for once. And, Matthew Reinbold: And then I ruined it. Sorry. Phil Sturgeon: and then you. Matt Trask: no, no, no, you didn't ruin it. You just brought it back down to its normal level of ridiculousness. Phil Sturgeon: Fantastic. No. Do you have any predictions for what we're going to see in the, in next year's state of this report? Because then we can play that clip back and laugh at how wrong you were. Matthew Reinbold: Oh, lovely. All right, well, let me have a few minutes to sandbag my answer. No, I think there's a tremendous amount of, of areas where we can take this correlation that I talked about before behaviors. You know how the question immediately becomes well, okay. If these four behaviors are so good and are present in high-performing API companies, how do we get there? And this year we had a little bit around leadership and what leaders do. To get an API first company. I think there is a lot of exploration we can do there to really dial in and say, okay, we know these things are good. How do you get there? How do you promote these things? How do you, how do you get it so that you are able to deploy in a minimal amount of time or recover faster? What are leaders in those organizations doing? That's one of the things I'd love to dig into obviously. A lot of post pandemic aftermath. There's been a tremendous amount of published about how this digital transformation and, you know, we're so much more flexible and adaptable because we, we are now doing all our conversations over zoom. And I look at that and I, I scratch my head because. Digital transformation, at least in the non buzzword compliant way is a whole lot more difficult than just moving everything to a slack conversation or a, or a zoom conversation. Like it means fundamentally dismantling your policies and procedures and reinventing them in a way that digital technology lends itself to. So figuring out what that post pandemic landscape looks like and how we're still feeling the knock on effect. Is going to be something that's also going to be very interesting to explore. Matt Trask: Yeah, that's definitely true. I mean, I think one thing I would like to see is, is that number of people who know open API, but don't use it start to gradually shift down and people who are using open. Start to shift up, which, you know, from a silver right back to having documentation and some sort of notes about their API. So when the, the knowledge people do eventually leave because everyone leaves the company at some point, the knowledge isn't necessarily leaving. And instead we're, we're kind of leaving a better legacy to the people following us. Yeah, definitely. Matthew Reinbold: Here here. Matt Trask: Cool. Matthew, thank you so much for taking some time out of your, your, your day to talk to us. We really appreciate it. Look forward to having you back in roughly a year's time to talk 20, 22. Say the API report Matthew Reinbold: I love it. Let's do it. Pencil it in right now. Matt Trask: Yep. It's it's on my calendar. I don't know what I'll be doing in a year from today, but I know for a fact we'll be talking again. If you want to get. Matthew on Twitter. He is at libel Vox, L I B E L underscore V O X M. And we'll throw the link to your blog and Twitter in the show notes as well as everything else. Awesome. Cool. Thank you so much. We appreciate it. Phil Sturgeon: Yeah. All audio, artwork, episode descriptions and notes are property of APIs You Won't Hate, for APIs You Won't Hate, and published with permission by Transistor, Inc. Broadcast by | 2026-01-13T08:48:41 |
https://stackoverflow.com/questions?tab=Active#content | Recently Active Questions - Stack Overflow Skip to main content Stack Overflow About Products For Teams Stack Internal Implement a knowledge platform layer to power your enterprise and AI tools. Stack Data Licensing Get access to top-class technical expertise with trusted & attributed content. Stack Ads Connect your brand to the world’s most trusted technologist communities. Releases Keep up-to-date on features we add to Stack Overflow and Stack Internal. About the company Visit the blog s-popover#show" data-s-popover-placement="bottom-start" /> Loading… current community Stack Overflow help chat Meta Stack Overflow your communities Sign up or log in to customize your list. more stack exchange communities company blog Log in Sign up Home Questions AI Assist Tags Challenges Chat Articles Users Companies Collectives Communities for your favorite technologies. Explore all Collectives Stack Internal Stack Overflow for Teams is now called Stack Internal . Bring the best of human thought and AI automation together at your work. Try for free Learn more Stack Internal Bring the best of human thought and AI automation together at your work. Learn more Collectives™ on Stack Overflow Find centralized, trusted content and collaborate around the technologies you use most. Learn more about Collectives Stack Internal Knowledge at work Bring the best of human thought and AI automation together at your work. Explore Stack Internal Recently Active Questions Ask Question 24,179,897 questions se-uql#toggleEditor"> Newest Active Bountied 12 Unanswered More Bountied 12 Unanswered Frequent Score Trending Week Month Unanswered (my tags) Filter Filter by No answers No upvoted or accepted answers No Staging Ground Has bounty Days old Sorted by Newest Recent activity Highest score Most frequent Bounty ending soon Trending Most activity Tagged with My watched tags The following tags: Apply filter Cancel 0 votes 0 answers 7 views Proto encoding for message with packed repeated elements Quite new to protobuf so hope the question isn't too basic. Can someone please help explain the example that is used in https://protobuf.dev/programming-guides/encoding/ repeated elements which I can'... encoding protocol-buffers proto3 packed Atilla Mete Turedi 1 asked 3 mins ago 1 vote 1 answer 225 views AppImage updates conflicts with its .desktop file I have a couple of AppImage files in my system (Fedora38). I need all of those AppImage icons in my app tray. I manually created the .desktop files, and it works fine. But when an app gets updated, ... linux package appimage Florian Kusche 173 answered 3 mins ago 2 votes 1 answer 391 views uint64_t: Division with rounding I'm trying to create a code which divides a uint64_t by another uint64_t plus it applies rounding to the result. The code should be as fast as possible and work for all inputs (e.g. I would prefer it ... c gcc rounding division integer-division phuclv 43.3k modified 5 mins ago 0 votes 0 answers 11 views Is it a bad practice to have a Scaffold as a child of a ListenableBuilder I am currently building a Flutter app for a company I am working for, and I was doing some code refactoring that implied moving a Scaffold as a child of a ListenableBuilder . And I was wondering if it ... flutter Code Error 1 modified 6 mins ago 17 votes 2 answers 6k views How can get READY, STATUS, RESTARTS, AGE,etc in kubectl as custom-columns? I just want to list pods with their .status.podIP as an extra column. It seems that as soon as I specify -o=custom-colums= the default columns NAME, READY, STATUS, RESTARTS, AGE will disappear. The ... kubernetes kubectl Ivan 7,540 answered 8 mins ago 0 votes 0 answers 14 views removing inline javascript failing A rails 7.1 view file runs with in-line javascript as follows. <script> var autoComplete = (function(){ [ ... contents of .js file. see below] </script> <%= javascript_tag do %> ... javascript ruby-on-rails stimulus-rails Jerome 6,357 asked 8 mins ago 0 votes 0 answers 11 views Claude AI suddenly can’t read files inside folders from GitHub repos I’ve been using Claude AI daily for the past ~2 months to analyze GitHub repositories with similar structure (Android/Gradle projects), and it worked fine. Today, Claude can still see the repo and ... github claude Ho Quang Lam 130 asked 9 mins ago 175 votes 9 answers 189k views How to unfork a GitHub repository? How can I unfork a GitHub repository? I have never seen unfork option — is it possible to do that? github Aryan Bhasein 1 answered 10 mins ago 0 votes 2 answers 1k views Run two applications in Heroku and connect them using the PostgreSQL database I am trying to build a full-stack web application using Python and Heroku. There are two apps and they are connected using a common database (Heroku Postgres). The backend app streams live tweets from ... python postgresql heroku tweepy plotly-dash Ashwith kunder 1 answered 11 mins ago 1 vote 0 answers 9 views Shared Preferences lost on flutter edge browser I save my filters in sharedPreferences, in the app and in web-browser daily use its fine , it gets save even on browser/app close. But overnight it gets lost on edge in all mobile device : final prefs ... flutter sharedpreferences flutter-sharedpreference Munsif Ali 8,034 modified 12 mins ago 1 vote 0 answers 30 views Push notifications no longer appear in IntelliJ IntelliJ IDEA no longer shows push status notifications. No balloon, no item in the notification panel. Commit notifications are still listed in the panel. It's inconvenient since I have to manually ... git intellij-idea Sergey Zolotarev 2,745 modified 12 mins ago 2 votes 0 answers 10 views Vue/Element Plus - Keyboard navigation in El-Tree I am trying to make use of the Vue content library Element Plus, more specifically of its El-Tree component, but I need to make it functional with a keyboard and this has proven more challenging than ... vue.js vuejs3 accessibility element-plus Avaloja 11 asked 15 mins ago -1 votes 2 answers 86 views Why do we need 1=1 in URL SQL injection? I was doing the first PortSwigger SQL injection lab, where the goal is to display all “Gifts” products regardless of whether they are released or not. The official solution is to inject the following ... sql oracle-database security sql-injection Jonathan Willcock 5,430 answered 15 mins ago 0 votes 0 answers 7 views Trying to build flutter engine with custom dart sdk I was able to correctly compile the flutter windows engine and get the file (flutter_windows.dll) with the prebuilt dart sdk, but when I try to use --no-prebuilt-dart-sdk when added to the gn tool to ... flutter dart sdk flutter-engine Titoot 120 asked 15 mins ago 17 votes 3 answers 108k views excel vba : selected cells loop Would like to iterate each row in a selection in excel VBA. I have: Dim rng As Range Dim s As String Set rng = Application.Selection Debug.Print "c :" & rng.Address This prints c :$B$22:$C$29 ... vba excel Sybrand De Vries 1 answered 15 mins ago 26 votes 3 answers 25k views Is there a way to call a function when a SwiftUI Picker selection changes? I would like to call a function when selectedOption's value changes. Is there a way to do this in SwiftUI similar to when editing a TextField? Specifically, I would like to save the selected option ... swift onchange swiftui picker davetw12 1,861 modified 17 mins ago 0 votes 1 answer 14 views Use Microsoft Graph 5.0 SDK to get display name from listitem's LookupId field I have retrieved an item in a list and got the field data, several of fields are users but the return value is a LookupId and I need the display name. Looking online it mainly talks about querying the ... c# sharepoint microsoft-graph-api microsoft-graph-sdks martinm 22.2k modified 19 mins ago -8 votes 0 answers 25 views Can anyone solve these very hard Jeroo challenges? [closed] https://docs.google.com/document/d/1_2y2eg8a5dXHW_KA-UYmVhTJ9fA4lJzRcFmuYcBVIoQ/edit?usp=sharing Can somebody solve all 8 of these Jeroo projects. Share your solutions if you solve it java Zack Tudor 1 asked 20 mins ago 0 votes 2 answers 36 views Parsing an XML column in T-SQL with a colon in the XML Structure I have a column of XML data in SQL Server that I'm trying to parse into columns. The start of the XML data looks something like: <DataSet xmlns="google.com"> <diffgr:diffgram ... sql-server xml t-sql Guillaume Outters 7,617 modified 20 mins ago -1 votes 1 answer 36 views Is it necessary your python function should have retun in? def odd_or_even(n): if n % 2 != 0: return "Odd" else: return "Even" #Here I wrote a function which checks wheter the number is odd or even using if ... python adshin21 186 answered 21 mins ago Tooling 0 votes 5 replies 31 views Large build size for Electron app using vite and electron-builder due to node_modules I have an Electron app that I build using webpack + electron-forge. I consider to migrate to vite + electron-builder. The migration succeeded quite smoothly, and dev experience with vite is way better ... webpack electron vite electron-builder electron-forge Arkellys 8,048 answered 24 mins ago 0 votes 0 answers 8 views Houdini not able to pull schema. "ERROR: couldn't pull your schema: resp.text is not a function" I have a SvelteKit project where i am trying to query a GraphQL endpoint and get end to end typesafety using Houdini. I run npx houdini init in my repository and get the following error: ⚠️ Couldn't ... typescript graphql sveltekit Jayant Godse 1 asked 24 mins ago 0 votes 1 answer 2k views libEGL warning: MESA-LOADER: failed to open swrast I am using WSL on Windows 11. Inside WSL, I have created an Anaconda environment, through which I launch Jupyter Lab. I am trying to use OpenCV to load an avi video file into my code and read its ... python ubuntu windows-subsystem-for-linux jupyter-lab Mo_ 2,117 answered 25 mins ago Advice 0 votes 2 replies 5 views Run command (simpleBrowser.show) in response to task output? Is it possible to run a VS Code command in response to the output of an external command run via a task? Specifically, I have a task triggered by a keyboard shortcut which runs an external command, ... visual-studio-code vscode-tasks A. Donda 8,494 answered 27 mins ago 0 votes 1 answer 53 views AttributeError: module 'utils3d' has no attribute 'numpy' when running Microsoft MoGe training I am trying to run the training code for the Microsoft MoGe (Monocular Geometry Estimation) model from their GitHub repository. I have set up my environment and installed dependencies, but when I run ... python machine-learning pip pytorch computer-vision Christoph Rackwitz 16.5k modified 28 mins ago -9 votes 0 answers 52 views Can someone do this project [closed] I have tried it, this is very challenging. Can someone do all eight of these KONG projects. Instructions in the link: Donkey Kong Jeroo. Drop the files below after completing them! java Zack Tudor 1 asked 29 mins ago 0 votes 2 answers 45 views Remove bottom of stack in flutter navigation I need to get this to work for both named and unnamed routes. I would like to remove the bottom of the stack if some specific condition is met. I've looked at suggestions and asked ai, but all answers ... flutter navigation AJJ 197 answered 30 mins ago -1 votes 1 answer 322 views Concatenate string array as a multiple criteria for filter I want to concatenate a string array inside a AutoFilter. I just used macro recorder for this code. I'm trying to get the same output of this and i don't want to brute force all of the possible ... excel vba Qualitcert 1 modified 32 mins ago -2 votes 0 answers 33 views Next/Node stops responding to POST requests after a few minutes I have a Next app deployed on my EC2 paired with nginx, pm2. When my deployment script restarts Next with pm2, all is well, however, after 2-15 minutes, all POST routes stop responding and they ... node.js nginx next.js pm2 Ivan Shatsky 16.2k modified 36 mins ago 3 votes 2 answers 94 views Shorthand to "reuse" object obtained from List? I have a line of code like so: return listOfObjects[Index].param1 == "test1" && listOfObjects[Index].param2 == "test2" ? listOfObjects[Index] : null; Instead of ... c# list wohlstad 36.8k modified 37 mins ago 1 vote 1 answer 9k views Tailwind css hover not changing text color I am completely new to this tailwindcss and I have been stuck at this problem for the entire day. I am so frustrated. Here is my code <button className="bg-yellow-500 px-4 py-2 hover:text-... css colors hover tailwind-css Community Bot 1 modified 39 mins ago 0 votes 3 answers 14k views make an ImageView with rounded corners? rounded corners of cardview I want to make the interface as shown above. The images are not fixed, which means I can transfer images to other. I want to use pakage in xml file. Something like, <... android xml android-layout user-interface rounding Community Bot 1 modified 39 mins ago 7 votes 1 answer 12k views Uncaught Error: [Ext.create] Unrecognized class name / alias: MyApp.store.LibraryFolderTreeStore I'm migrating ext js 4 to ext js 5.1 .I have code in my extjs 4.2.1 which is giving console error after upgrading to extjs 5.1 .It was working good in ExtJs 4.2.1, don't know why it is giving error, ... javascript extjs extjs4 extjs5 Community Bot 1 modified 39 mins ago 6 votes 1 answer 12k views Repeated log : Warn Transport Connection to tcp:<ip> failed: java.net.SocketException: Connection reset I am running ActiveMQ 5.9.0 release on my local machine for dev purposes (Windows 7). I am using AMQP as the protocol and Apache qpid as the client to consume messages (publish subscribe) from ... activemq-classic Community Bot 1 modified 39 mins ago -3 votes 0 answers 69 views Unable to customize styles in borders, colors, selected date, other month days when use inline datepicker [closed] I'm trying to customize the Flowbite inline datepicker using Tailwind CSS in a pure HTML environment, but most of the styles I apply are not taking effect. I'm unable to customize the following: ... javascript html css tailwind-css flowbite rozsazoltan 19.1k modified 41 mins ago -1 votes 0 answers 39 views How to insert the following diagram in MSE? [closed] How to insert the following diagram in a MathStackExchange post ? \begin{tikzcd}[column sep=2cm, row sep=1.8cm] & S \arrow[d,"j_{S}"]\arrow[ddr,"\varphi_S"] \\ T\arrow[r,&... mathjax tikz mkrieger1 24.3k modified 42 mins ago 0 votes 2 answers 7k views Woocommerce Product images not showing on product page Hope you are doing well, my site is www.coutlet.com, it's working fine but when I open any product page, the images are not showing. I've tried enabling disabling almost every plugin but that doesn't ... wordpress woocommerce Suplanus 1,621 answered 42 mins ago 2 votes 1 answer 801 views How use the @c8y/client library I am testing the new @c8y/client library for typescript. I have a very simple code : import { Client } from '@c8y/client'; //const baseUrl = 'https://bismark1.cumulocity.com/'; const baseUrl = '... javascript cumulocity emi 3,108 modified 43 mins ago 7 votes 3 answers 26k views Date object in Cucumber I have a cucumber stepdef like this Given the date of <date> When blah blah Then x y and z Examples: |2015-01-01| |2045-01-01| When I generate stepdefs off of this, I get @Given("^the date of (\... java cucumber gherkin Julien Kronegg 5,396 modified 44 mins ago -3 votes 1 answer 63 views Rescale SVG to a Target size I have a number of SVGs that have been produce, as an example: <?xml version="1.0" encoding="UTF-8"?> <svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 ... svg herrstrietzel 19.6k modified 44 mins ago 2 votes 3 answers 459 views When a canvas path intersects in a certain way, it is not drawn When a path is filled on the canvas, depending on the way the path was created, the path intersections are painted with the fill color or left blank. Here is an example: http://jsfiddle.net/C3Hbb/ //... javascript canvas Normajean 1,323 modified 47 mins ago -1 votes 1 answer 2k views How do I add the Satoshi custom font to my React Native Expo app? (Expo SDK, fonts not loading / error after install) Environment: Expo (state SDK version), React Native, platform(s) affected (Android / iOS / web). What I did: I copied the Satoshi font files into my project and followed a YouTube tutorial to load ... javascript android ios react-native fonts Surendhar S 131 modified 48 mins ago 0 votes 0 answers 40 views Hosting Ansible Playbook using Docker So I been working on an Ansible based project which basically handles the application/firmware upgrade from a Centralised Ansible Server connecting to hundreds of thousands of Linux Application ... linux docker ansible amitk 161 modified 48 mins ago -2 votes 0 answers 32 views Capturing sudoku but Selenium didn't find it with Chrome in HTML I'm trying to capture this sudoku with Selenium and Python after accepting the cookie. With this code I could accept the cookie in the iframe and write the main site to the output.html for debugging: ... python selenium-webdriver cookies iframe jonrsharpe 123k modified 49 mins ago -1 votes 2 answers 69 views Creating employee ID with a fixed prefix and auto-increment number in MySQL (without triggers) Environment: MySQL 8.x (or MySQL-compatible RDBMS) Goal: Generate employee IDs like EMP0001, EMP0002, ... automatically when inserting rows, without using database triggers. What I tried: Considered ... sql mysql database mysql-workbench Surendhar S 131 modified 49 mins ago -5 votes 1 answer 55 views How to inspect DSLContext.select() for what JOIN tables exist? How can I get, for a DSLContext.select() query object, before I fetch the results, what JOIN tables exist, and other metadata like that? Basically I want to have helper functions that will add sorting,... jooq Lukas Eder 224k answered 50 mins ago 1 vote 1 answer 349 views Ugly Fonts in Java Swing - How to set antialiasing? I'm creating a modern-looking program with a cool GUI, but Java prevents me from doing that by showing a eye-burning text presentation. Here's how it looks like: . Look at the numbers, they are shaped ... java swing antialiasing hobbyDude 1 answered 51 mins ago -2 votes 1 answer 312 views Android app receives unreadable BLE characteristic bytes from ESP32 — how to pack and decode correctly? [closed] Environment: Android (Kotlin) central using BluetoothGatt; ESP32 peripheral (Arduino BLE library). What I did: Connected and enabled notifications; receiving data in onCharacteristicChanged(). ... android android-studio bluetooth-lowenergy esp32 arduino-esp32 Surendhar S 131 modified 52 mins ago 0 votes 0 answers 32 views Why do Tkinter apps running under uv have strange fonts? I have a simple Tkinter app: import tkinter as tk from tkinter import ttk def main() -> None: root = tk.Tk() root.title('Hello world') label = ttk.Label(root, text='Hola Mundo') ... python tkinter uv cachyos jonrsharpe 123k modified 53 mins ago Advice 1 vote 3 replies 26 views Why are MCPs needed at all? I've read the anthropic announcement about MCPs where it's supposed to be a protocol that standardizes how agentic software invokes other tooling within the systems so developers would not need to ... model-context-protocol anthropic Stephen C 724k answered 54 mins ago 15 30 50 per page 1 2 3 4 5 … 483598 Next The Overflow Blog Now everyone can chat on Stack Overflow Vibe code anything in a Hanselminute Featured on Meta A proposal for bringing back Community Promotion & Open Source Ads Community Asks Sprint Announcement – January 2026: Custom site-specific badges! Policy: Generative AI (e.g., ChatGPT) is banned Modernizing curation: A proposal for The Workshop and The Archive All users on Stack Overflow can now participate in chat Collectives see all AWS 37k Members Join A collective for developers who utilize Amazon Web Services' infrastructure and platform capabilities. The AWS Collective is organized and managed by the Stack Overflow community as a resource for developers. CI/CD 23k Members Join A collective where developers focused on continuous integration, delivery, and deployment can find, share, and learn about simultaneous development. PHP 17k Members Join A collective where developers working with PHP can learn and connect about the open source scripting language. Hot Network Questions Is training with a coach whose students include a world champion worth it for a 10-year-old compared to FM/IM coaching? Manipulate within another Manipulate: How do I set the initial values of the control variables to reflect the inner Manipulate's last state? I found a paper that basically covers my whole thesis Can you get to 8? Invalid directory left when CreateDirectory fails on bad path Best practices for maintaining and versioning a laboratory notebook? Are the YouTube channel Courts & Crimes's shorts AI-generated deep fakes? (James 2:18b) Was James speaking facetiously to make a spiritual and practical pastoral point? Can we naturally incorporate gravity into a QFT Lagrangian? Eilenberg–Watts for module spectra Detect ssh user@host vs ssh user@host <command> in PAM module during ssh auth The rigor of the definition of higher derivative What is the general problem solving technique to solve this problem? Gender for 3rd person pronoun of a person with nickname Which sefer of Rabbi Elchonon Wasserman is this from How common was the belief in early British India that crossing the sea led to loss of caste? Does this fallacy already exist? Cyrillic script letter el with tail Does a const qualifier inside a struct declaration do anything? Shofars made from rams sacrificed for Eid al-Adha? Why is there no right to a passport in the USA? Does the 22° angle in the right triangle seem to correspond to the maximum of this area ratio? Can a German bicycle tourist use a transit visa to directly cross Suriname from French Guiana to Guyana (400km in 7 days)? Why do some simple/early achievements have a very low unlock percentage? more hot questions Stack Overflow Questions Help Chat Business Stack Internal Stack Data Licensing Stack Ads Company About Press Work Here Legal Privacy Policy Terms of Service Contact Us cookie-settings#toggle" class="s-btn s-btn__link py4 js-gps-track -link" data-gps-track="footer.click({ location: 3, link: 38 })" data-consent-popup-loader="footer"> Cookie Settings Cookie Policy Stack Exchange Network Technology Culture & recreation Life & arts Science Professional Business API Data Blog Facebook Twitter LinkedIn Instagram Site design / logo © 2026 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2026.1.12.38533 | 2026-01-13T08:48:41 |
https://youtube.com/t/contact_us/ | 문의하기 KR YouTube 정보 커뮤니티 가이드 문의하기 채용정보 문의하기 도움이 필요한 경우 YouTube 고객센터 를 방문하세요. 계정 만들기, 동영상 보기 및 업로드, 채널 관리 등 여러 가지 일반적인 질문에 대한 답을 찾을 수 있습니다. 고객센터에서 원하는 내용을 찾을 수 없는 경우 커뮤니티 도움말 포럼 을 방문해 보세요. 버그가 있습니까? 현재 사이트 관련 문제 페이지에서, 이미 알려진 문제 중 현재 수정 작업이 진행되고 있는 문제의 목록을 살펴보세요. 기업 홍보 프레스룸 이 공간 에서는 미디어 연락처 정보, 보도자료, B-Roll 영상 자료, FAQ, 대화식 YouTube 연혁을 제공합니다. 파트너 프로그램 YouTube 파트너 프로그램에 가입하려면 정보 페이지 를 방문하여 자세한 내용을 확인하세요. 광고 AdAge 100 광고주이든 현지 소매상이든 관계없이 누구나 YouTube 광고 프로그램을 이용하면 전 세계에서 가장 큰 온라인 동영상 커뮤니티를 활용하는 것이 됩니다. YouTube에서 광고를 하는 데 대한 기본사항을 알아보세요 . 보안 악용 문제 사이트에 악용 문제가 있는 경우에는 안전센터 를 통해 문의해 주시기 바랍니다. 사이트 보안 문제 YouTube 사이트와 관련된 보안 문제는 여기에서 신고하실 수 있습니다 . 법적 문제 저작권 문제 내가 저작권을 보유한 동영상이 허락 없이 올라와 있는 것을 발견할 경우 다음 안내 에 따라 저작권 침해 신고를 제출하시기 바랍니다. 콘텐츠 확인 프로그램 콘텐츠 확인 프로그램에 참여하려면 콘텐츠 확인 페이지를 방문하세요. 부적절한 콘텐츠 YouTube에 올라온 부적절한 동영상을 신고하려면 동영상 아래에 있는 '신고' 링크를 클릭하세요. YouTube 정책에 대한 자세한 내용은 서비스 약관을 참조 하시기 바랍니다. 기타 개발자 개발자이거나 Google API에 관심이 있는 경우 개발자 페이지 를 방문하세요. Google에 추가 콘텐츠를 제출하세요. 가젯, 쇼핑, 지역 정보, 도서 등 콘텐츠를 Google에 배포할 수 있는 모든 방법 을 확인하세요. 주소 아래 주소로 YouTube에 연락하실 수 있습니다. Google LLC, D/B/A YouTube 901 Cherry Ave. San Bruno, CA 94066 USA 팩스: +1 650-253-0001 | 2026-01-13T08:48:41 |
https://survivejs.com/consulting/ | SurviveJS - Consulting Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Consulting Since officially starting my personal limited company in 2016, I have occasionally worked as a consultant to earn additional income and to develop my competence as consulting cases allow me to stay grounded in reality. In addition, I’ve been pursuing a doctorate since 2022 at Aalto University ↗ . Services I offer a variety of services and I have listed examples below. Custom development Occasionally I have been hired to perform custom development. Example cases include developing a complex table component or building up a new system in collaboration with a design system developer. I understand different aspects of modern frontend development well and work best in the interface between frontend and backend that you might characterize as the backend of the frontend. Workshops To train up staff, I have run several workshops throughout the years in my specialized topics. I have focused mainly on webpack and React although I have given workshops on topics like Deno and Qwik too. These days I prefer a hands-on approach and like to run my workshops through predesigned katas that allow attendees at different levels understand the topic and dive straight into the topic. I can also provide a short lecture on the topic in the beginning if needed. Conference organizing I have been running conferences since 2017 ( React Finland ↗ , GraphQL Finland ↗ , Future Frontend ↗ ) and have gained a strong understanding on how the business works. I have run both physical and online events and have operated mainly as a conference director focused on the big picture (concept, speakers, marketing). In case you have questions related how to build up your own concept, I might some kind of answers to this. Research Since 2022, I have been working as a doctoral researcher for Aalto University. Through my research, I have learned how the world of scientific publishing works. I have not done any commercial research cases but I have not ruled out the option in case a suitable case becomes available. I have done mainly surveys and empirical research so I understand both qualitative and quantitative ends of the spectrum. See my research outputs if you are interested in the academic side. Cleaning up Let's face it, not all development is clean and sometimes you have to go fast and make a mess. That is the situation when you might need someone like me to address your technical debt in a fast and effective manner. I can support your clean-up efforts on different levels by for example doing a superficial review to provide clear points for improvements or dig down into details and for example migrate your webpack configuration to the latest standard or a more effective tool. Coaching These days I tend to work a lot with university students as they learn academic writing. In case you are looking for a personal coach, you could hire me to spend a focused hour or two per week around development and JavaScript related topics in your mind to grow as a professional. I am happy to provide my expertise to you in the form of coaching. References I have worked with numerous companies during my career as a consultant. To mention some, consider the following list: AlphaSense ↗ , eBay ↗ , Kitchen Reklamebyrå ↗ , Kleiner Perkins ↗ , Typeform ↗ , Wix ↗ , Xeneta ↗ . Consulting examples I negotiate each consulting case to fit the needs of the client. For example, with Kapsch ↗ I helped the company to facilitate refactoring of an internal tool including two days of on-site training. With eBay ↗ , I helped the company with internal training and development work. For Typeform ↗ , I did a full week on-site with training on relevant topics as needed. These are only a few cases out of many and the offering is always customized to suit the needs of the client. Testimonials I have listed several of my testimonials below. In some cases I bring needed additional expertise on board through my broad personal networks to complement my own knowledge. Kapsch ↗ - “Great and helpful workshops with @bebraw @filipematossilv and @wSokra Thank you, guys. Great work!” Source ↗ . Namics ↗ - “This will bring our Webpack builds to the next level: great workshop with deep knowledge from @bebraw and @wsokra. Thank you guys!” Quantifio ↗ - “I learned and understood more of webpack in a two-hour masterclass than all previous training combined. Juho has the skills and repertoire to improvise content and fine tune relevancy - he connected the dots on specific topics in an Electron environment and had the answers you wont find online.” How to hire me? In case you are interested in hiring me or collaborating in some manner, please fill my contact form ↗ and I will get back to you. Generally more specialized and intense work tends to be more expensive while lower commitment tends to come with a lower price. I cannot guarantee instant or full-time availability, but the situation can change fast so it is worth sending a query regardless. Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://future.forem.com/t/education/page/3 | Education Page 3 - Future 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 Future 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 Narcissists report high emotional intelligence but perform worse on objective tests, suggests a new study. Science News Science News Science News Follow Aug 7 '25 Narcissists report high emotional intelligence but perform worse on objective tests, suggests a new study. # science # healthtech # productivity # education Comments Add Comment 1 min read Y Combinator Wants to Fund the First ‘10 Person, $100 Billion' Company AI News AI News AI News Follow Aug 5 '25 Y Combinator Wants to Fund the First ‘10 Person, $100 Billion' Company # ai # education # employment # productivity Comments Add Comment 1 min read How to Write Your First Program for a Quantum Computer Quantum News Quantum News Quantum News Follow Aug 5 '25 How to Write Your First Program for a Quantum Computer # quantum # science # education # ai Comments Add Comment 1 min read New Nanodevice can enable Holographic XR Headsets: “we can do everything – holography, beam steering, 3D displays – anything” AR/VR News AR/VR News AR/VR News Follow Aug 5 '25 New Nanodevice can enable Holographic XR Headsets: “we can do everything – holography, beam steering, 3D displays – anything” # education # science # healthtech # energy Comments Add Comment 1 min read Jeff Su: How to Join Google (honest advice from ex-Googler) AI News AI News AI News Follow Aug 1 '25 Jeff Su: How to Join Google (honest advice from ex-Googler) # education # productivity Comments Add Comment 1 min read Jeff Su: ex-Googler: My honest advice for someone who wants to join Google AI News AI News AI News Follow Jul 30 '25 Jeff Su: ex-Googler: My honest advice for someone who wants to join Google # education # productivity Comments Add Comment 1 min read Kurzgesagt - In a Nutshell: Dear Alcohol... Future YouTube Future YouTube Future YouTube Follow Aug 13 '25 Kurzgesagt - In a Nutshell: Dear Alcohol... # education # science 1 reaction Comments Add Comment 1 min read China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility Quantum News Quantum News Quantum News Follow Jul 22 '25 China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility # quantum # science # education # nanotech Comments Add Comment 1 min read Exhausted man defeats AI model in world coding championship AI News AI News AI News Follow Jul 21 '25 Exhausted man defeats AI model in world coding championship # ai # science # education # employment Comments Add Comment 1 min read Don't Get Comfortable: Why Today's Mixed Reality is a Bridge, Not a Destination AR/VR News AR/VR News AR/VR News Follow Jul 14 '25 Don't Get Comfortable: Why Today's Mixed Reality is a Bridge, Not a Destination # productivity # education # security # privacy Comments Add Comment 1 min read Jeff Su: The AI Agent Tutorial That Should've Been Your First (no code) AI News AI News AI News Follow Aug 13 '25 Jeff Su: The AI Agent Tutorial That Should've Been Your First (no code) # ai # productivity # education Comments 1 comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 10 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 10 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read People with short-video addiction show altered brain responses during decision-making Science News Science News Science News Follow Jul 10 '25 People with short-video addiction show altered brain responses during decision-making # science # healthtech # biotech # education Comments Add Comment 1 min read Jeff Su: If you can use ChatGPT, you can build this AI Agent AI News AI News AI News Follow Aug 12 '25 Jeff Su: If you can use ChatGPT, you can build this AI Agent # ai # productivity # education 1 reaction Comments Add Comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 9 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 8 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Leaked Meta Hypernova firmware reveals Photos App zoom and pan instructions AR/VR News AR/VR News AR/VR News Follow Jul 8 '25 Leaked Meta Hypernova firmware reveals Photos App zoom and pan instructions # privacy # security # productivity # education Comments Add Comment 1 min read Laid-off workers should use AI to manage their emotions, says Xbox exec AI News AI News AI News Follow Jul 7 '25 Laid-off workers should use AI to manage their emotions, says Xbox exec # ai # employment # productivity # education 1 reaction Comments Add Comment 1 min read Longer antidepressant use linked to more severe, long-lasting withdrawal symptoms, study finds Science News Science News Science News Follow Jul 2 '25 Longer antidepressant use linked to more severe, long-lasting withdrawal symptoms, study finds # science # healthtech # biotech # education Comments Add Comment 1 min read Earth is trapping much more heat than climate models forecast – and the rate has doubled in 20 years Science News Science News Science News Follow Jul 2 '25 Earth is trapping much more heat than climate models forecast – and the rate has doubled in 20 years # science # energy # solar # education Comments Add Comment 1 min read ChatGPT is bringing back 4o as an option because people missed it AI News AI News AI News Follow Aug 12 '25 ChatGPT is bringing back 4o as an option because people missed it # ai # productivity # education # science 4 reactions Comments 1 comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 7 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science 5 reactions Comments Add Comment 1 min read Veritasium: The Perfect Battery Material Is DANGEROUS Future YouTube Future YouTube Future YouTube Follow Aug 15 '25 Veritasium: The Perfect Battery Material Is DANGEROUS # science # education Comments 1 comment 1 min read OpenAI Scrambles to Update GPT-5 After Users Revolt AI News AI News AI News Follow Aug 12 '25 OpenAI Scrambles to Update GPT-5 After Users Revolt # ai # science # productivity # education Comments 1 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. 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 . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:48:41 |
https://parenting.forem.com/jess/we-started-a-new-routine-called-highs-and-lows-to-get-our-kids-to-open-up-more-3dd8 | We started a new routine called 'highs and lows' to get our kids to open up more! - Parenting 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 Parenting 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 Jess Lee Posted on Oct 22, 2025 We started a new routine called 'highs and lows' to get our kids to open up more! # discuss My two kids are quite different. The younger one is our chatterbox while the older one barely shares a thing. "How was school? Fine." "What did you do today? I don't remember." At 'circle time' in school, every kid is supposed to go around sharing one thing that makes their heart happy. My kid has 'passed' every.single.time. for over a year! Needless to say, this has been a delicate balance in our household of trying to get more but not be pushy about it so we create a safe space. Well, we had a breakthrough over the weekend! Highs and Lows We hosted friends for a few nights and got to witness one of their family rituals - "highs and lows" . Every night, this family shares one high and one low they experienced during the day. Usually done over dinner but if they can't all be present, right before bed time. I think one of the keys is that everyone is involved. Level the playing field. They invited us to do it with them one night and I was sure my kid would pass as she scrambled to hide behind my partner and look away from everyone waiting for a response. To my utter shock, she participated! Enthusiastically. New Daily Routine My partner and I were shocked, and decided this was something we would need to try again. And we have, and it's worked! She will thoughtfully reflect on her day and pull out something that made her happy, and something she was less than pleased about. It's not a super long conversation but it feels special that it's coming honestly from her as opposed to a response to some sort of interrogation by us. I'm hoping this can be a new daily routine...forever? If we can bake it in as just how our family functions , I hope we can hold it through the teenage years and beyond. Anyway, just wanted to share! I know there are a million tricks out there so this is just one of many you could try if you have a quiet kid too. 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 Joanna Duffey Joanna Duffey Joanna Duffey Follow Joined Oct 20, 2025 • Oct 22 '25 Dropdown menu Copy link Hide We do something similar in our house, and I have to say, it’s become a family favorite. Some days it’s not very fruitful, but other days my son really opens up. What’s even more interesting is watching him ask questions about the highs or lows my husband and I mention. I’ve also come to realize that most days are filled with many more high than lows :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Matt Figler Matt Figler Matt Figler Follow Joined Jun 22, 2017 • Oct 22 '25 • Edited on Oct 23 • Edited Dropdown menu Copy link Hide This has shifted the paradigm of sharing feelings with our family, can confirm! Like comment: Like comment: 2 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 Jess Lee Follow Building DEV and Forem with everyone here. Interested in the future. Location USA / TAIWAN Pronouns she/they Work Co-Founder & COO at Forem Joined Jul 29, 2016 More from Jess Lee This...has not worked the last three nights 😒 # discuss International Travel with Toddlers: Car Seat (or vest!) Considerations # travel # gear How do you think about screen time and technology? # technology # 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 Parenting — 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. 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 . Parenting © 2016 - 2026. Navigating the chaos and joy of parenting. Log in Create account | 2026-01-13T08:48:41 |
https://aws.amazon.com/appsync/ | Serverless GraphQL and Pub/Sub APIs – AWS AppSync – Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS AppSync Overview Features Pricing Resources FAQs More Product › Front-End Web and Mobile › AppSync Get started with AWS AppSync with AWS Free Tier AWS AppSync Connect applications to events, data, and AI models Get started with AWS AppSync Contact sales Benefits Access all your data with GraphQL With AppSync GraphQL, give application developers the ability to access data from multiple databases, micro-services, and AI models with a single GraphQL API request. Get started quickly by instantly creating GraphQL APIs from your Amazon DynamoDB and Aurora databases. Combine multiple GraphQL APIs into a federated super-graph as you grow. Real-time experiences with WebSockets With AppSync Events, publish and subscribe to real-time events, like score and location updates, chat messages, inventory and price changes, and support ticket updates. Create your Event API and configure channels, auth rules, and message transformations in minutes. Leverage AppSync to manage millions of connections and billions of messages as you grow. Built-in security and ops Use AppSync auth modes (API key, OIDC, Cognito, IAM, and Lambda), Private APIs, and AWS WAF integration to secure your APIs. Use AppSync managed custom domains to simplify operations, caches to improve API performance, and integration with Amazon CloudWatch and AWS X-Ray for logging, metrics, and traces. Pay-per-use pricing Pay only for AppSync API operations, real-time connection minutes, and data transfer. Let AppSync handle scaling. Leverage the AppSync free tier to get started. How GraphQL drives developer agility AWS AppSync GraphQL APIs enable developers to access exactly the data they need, via a flexible API that securely accesses, manipulates, and combines data from multiple sources. Play Use cases An AI gateway for Amazon Bedrock Use AWS AppSync to simplify integration with AI backends like Amazon Bedrock. Create an AI gateway A federated GraphQL API for all your data Combine multiple GraphQL source APIs into a single Merged GraphQL API “super graph." Build an AppSync managed supergraph Amazon Aurora and DynamoDB APIs Introspect your SQL and NoSQL databases and automatically create an API layer. Instant database APIs Real-time experiences Create a pub/sub solution for your real-time events Build an AppSync Event API How to get started Read the AWS AppSync docs Learn more about AWS AppSync features and functionality Get started with AWS AppSync for free Get 250,000 GraphQL API requests and 250,000 Event API real-time operations for free per month for 12 months Contact an expert From start-ups to enterprise level, get support tailored to your needs Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:41 |
https://survivejs.com/workshops/ | SurviveJS - Workshops Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Workshops I run my workshops using a kata format. In other words, they form of series of smaller tasks that contain exercises to complete to encourage learning through doing. Often I complete my kata workshops with a brief introduction to the topic. Although it is fun to complete them in a workshop format, it is possible to go through them alone and I have listed my katas below. Qwik katas (2023) ↗ Qwik ↗ is a recent web framework that approaches web application from a different angle by eschewing the concept of hydration and replacing it with resumability. This means it provides unique benefits, such as automatic code-splitting, out of the box making it an interesting alternative for web developers that want to develop performant websites and applications out of the box. See Qwik katas ↗ Deno katas (2023) ↗ Deno ↗ is the followup project of Ryan Dahl, the original author of Node.js ↗ . In Deno, Ryan wanted to fix his perceived mistakes of Node.js and Deno could be characterized as a whole toolbox that comes with solutions for common server-side programming problems particularly in terms of tooling. See Deno katas ↗ Web Audio katas (2023) ↗ Web Audio ↗ is a powerful, yet underestimated, web API that allows you to build complex audio-based web application. In this kata, you will build a small Digital Audio Workstation (DAW) while getting acquainted with the relevant APIs and some of the history behind digital audio. See Web Audio katas ↗ Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://docs.python.org/3/license.html#uuencode-and-uudecode-functions | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:48:41 |
https://survivejs.com/books/maintenance/ | SurviveJS – Maintenance Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... SurviveJS – Maintenance The maintenance book captures good practices related to developing and maintaining JavaScript applications or packages at scale. I co-authored the book with Artem Sapegin ↗ and the book is not yet fully complete although completion and a bigger update is planned. Read the maintenance book Buy the maintenance book ↗ Availability Although you can read the book online for free , you can also purchase it in a copy to support the development of the content. See also consulting for other available options. Leanpub (digital, always up to date with the site) ↗ Table of contents Preface Once an initial version of software has been developed, it often becomes the subject of maintenance efforts. You will have to evolve the code to match new requirements. Doing this is challenging when technology keeps changing. Especially web development is prone to this as the stack and standards k… Introduction The popularity of JavaScript and related technologies has exploded. As a result there are now numerous open source projects which rely on the language. JavaScript is widely used for web development and it sees further use beyond the web. The popularity and on-going evolution of the web platform pos… Packaging In this part, you’ll learn how to package your projects for consumption through npm. You will also learn to manage releases, generate standalone builds, and manage dependencies. … Where to Start Packaging npm has become wildly popular for managing JavaScript packages. It started in the backend world but has since grown to include frontend libraries as well. And now we have another issue: it’s hard to find a package your need because there are so many, and you end up creating a new one increasing the… Anatomy of a Package A minimal npm package should contain metadata in a package.json file and an associated source file (usually index.js). In practice, packages contain more than that and you will have at least a license file and the source in various formats. Often projects contain more files than are required to ex… Publishing Packages Publishing npm packages is only a npm publish away. Assuming the package name is still available and everything goes fine, you should have something out there! After this, you can install your package through npm install or npm i. Most of the community follows a specific versioning convention whic… Building Packages While publishing packages, you have a few concerns to worry about: Which browsers and Node versions to support? What to do if we want to use language features that aren’t supported by these targets? What to do if we want to use another language than JavaScript to author our package? How to support… Standalone Builds The scenarios covered in the previous chapter are enough if you consume packages through npm. There may be users that prefer pre-built standalone builds or bundles instead. This comes with a several advantages: Everything is packaged into a single file. You can include the bundle using a `` tag. T… Managing Dependencies Keeping dependencies updated is important to have the latest bugfixes and security updates, but it needs a lot of work: once in a while you need to check which packages have new versions and how to migrate, sometimes you have to rewrite parts of your code. Bigger projects may provide codemods that … Code Quality In this part, you’ll learn about different aspects of code quality. You can use the ideas to evaluate other people’s projects and to improve the quality of your own. … Linting We read code more often then we write it: sometimes we spend hours looking for what caused the bug, only to fix it with a single line of code. That’s why consistent code style is important. Ideally code in a project should look like it was written by a single developer. It makes code easier to read… Code Formatting Usually linters can validate and fix code formatting but there are specialized tools that work better. Achieving Code Consistency Code consistency helps when several people work on the same codebase: code look similar everywhere; programming patterns used consistently across the codebase; naming… Typing A function interface is a contract and depending on the system, it gives you guarantees. JavaScript doesn’t give any guarantees by default and you can pass anything to a function. Doing this may lead to a runtime error and crash your application. In a stricter system it’s difficult, or even impossi… Testing Tests can be seen as a runnable documentation of your code. Automated testing gives you confidence to change the code. Manual testing is the other end of the spectrum. It’s also the most labor intensive and brittle option. What to Verify With Testing Testing can be used to verify at least the fol… Infrastructure In this part, you’ll learn how to set up an infrastructure to support your project. By doing this well, you’ll make it easier for others to contribute to your project and make it grow faster. A good infrastructure becomes particular important as a project grows. … Processes Each project has processes around it. Services like GitHub, GitLab, and Bitbucket provide plenty of tool to manage open source projects: version control for project source, issue tracker, pull requests to accept code from your users, and often hosting your project site. When you think about proces… Continuous Integration Continuous integration (CI) services will run your tests in several environments: different operating systems, browsers or Node versions. It’s would be complicated to setup on your local machine. Usually CI checks every commit to your master or development branch as well as on each pull request — C… Automation Everything that can be done by a machine, will eventually be done by a machine. One of the earliest "computers", the Jacquard machine, achieved this for manufacturing complex textiles. It displaced human effort this way and pushed the difficult and monotonous task to a machine. This is the whole po… Documentation In this part, you’ll learn how to write a good README and a good change log, how to generate documentation for your API and create a site for your project, and about other kind of documentation that may help your users. … README A project README is often the first thing people see when they find the project. The project’s site is another entry point. Often a site is generated from a README file content with nice CSS. A good README can “sell” the project to a potential user. A badly written or formatted one can scare users… Change Logs Change log is an essential part of an open source project: it tells the user what was changed in a new version, about new features and breaking changes, and how to migrate to a new version. Why Not Commit Log Many projects don’t have change logs and ask users to read the commit log. But commit lo… Site Project site isn’t only a marketing tool — it also allows you to show your project to its potential users and give them the opportunity to try the project in their browsers. For many projects GitHub repository would be enough but Markdown pages are the only tool you have there, and a site have som… API Documentation For small project you can write API documentation manually in the README file, but for larger projects it’d be hard to maintain. You will need to generate API documentation from the code. Documenting APIs in Code JavaScript The most popular format for documenting JavaScript APIs is JSDoc. It use… Other Types of Documentation Contribution Guidelines Contribution guidelines explains how to contribute to a project: how to setup the environment; code style; what kind of contributions you want; links to all relevant documentation. GitHub will show a link to contributing guidelines on the new pull request page. Read more… Linting and Formatting Text linting is much less common than code linting, but if you have to maintain a lot of text it may save you a lot of time, and improve quality of your documentation. Linting Markdown With Textlint and Proselint Text linting is less common than code linting but in large projects with many contri… Future In this part, you’ll learn how too consider the longevity of your project and how to market it if popularity is one of the goals of it. … Longevity When developing a project, you should consider its goals and timespan. Some projects are one-off and meant to solve an immediate problem and are then thrown away. Others have more longer term focus and evolve over a long time. The question is, how to enable this long term evolution? You have to co… Marketing Even the technically most excellent project in the world won’t have much impact unless it reaches potential users. Popularity isn’t a goal always, but if it’s, then it’s good to know how to approach marketing the project. The purpose of marketing is to connect the potential user with the project. … Appendices TODO … Managing Packages Using a Monorepo npm packages can be managed in multiple ways. The most common way is to have one package per a source repository. The problems begin when you have to orchestrate changes across multiple related packages. The idea of monorepos was designed for this purpose. Monorepos - What Are They A monorepo all… Customizing ESLint Even though you can get far with vanilla ESLint, there are certain techniques you should know. For instance, sometimes you want to skip specific rules per file. You can even implement rules of your own. Speeding up ESLint Execution One of the most convenient ways to speed up ESLint execution on b… Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://docs.python.org/3/library/trace.html#module-trace | trace — Trace or track Python statement execution — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents trace — Trace or track Python statement execution Command-Line Usage Main options Modifiers Filters Programmatic Interface Previous topic timeit — Measure execution time of small code snippets Next topic tracemalloc — Trace memory allocations This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Debugging and Profiling » trace — Trace or track Python statement execution | Theme Auto Light Dark | trace — Trace or track Python statement execution ¶ Source code: Lib/trace.py The trace module allows you to trace program execution, generate annotated statement coverage listings, print caller/callee relationships and list functions executed during a program run. It can be used in another program or from the command line. See also Coverage.py A popular third-party coverage tool that provides HTML output along with advanced features such as branch coverage. Command-Line Usage ¶ The trace module can be invoked from the command line. It can be as simple as python - m trace -- count - C . somefile . py ... The above will execute somefile.py and generate annotated listings of all Python modules imported during the execution into the current directory. --help ¶ Display usage and exit. --version ¶ Display the version of the module and exit. Added in version 3.8: Added --module option that allows to run an executable module. Main options ¶ At least one of the following options must be specified when invoking trace . The --listfuncs option is mutually exclusive with the --trace and --count options. When --listfuncs is provided, neither --count nor --trace are accepted, and vice versa. -c , --count ¶ Produce a set of annotated listing files upon program completion that shows how many times each statement was executed. See also --coverdir , --file and --no-report below. -t , --trace ¶ Display lines as they are executed. -l , --listfuncs ¶ Display the functions executed by running the program. -r , --report ¶ Produce an annotated list from an earlier program run that used the --count and --file option. This does not execute any code. -T , --trackcalls ¶ Display the calling relationships exposed by running the program. Modifiers ¶ -f , --file =<file> ¶ Name of a file to accumulate counts over several tracing runs. Should be used with the --count option. -C , --coverdir =<dir> ¶ Directory where the report files go. The coverage report for package.module is written to file dir / package / module .cover . -m , --missing ¶ When generating annotated listings, mark lines which were not executed with >>>>>> . -s , --summary ¶ When using --count or --report , write a brief summary to stdout for each file processed. -R , --no-report ¶ Do not generate annotated listings. This is useful if you intend to make several runs with --count , and then produce a single set of annotated listings at the end. -g , --timing ¶ Prefix each line with the time since the program started. Only used while tracing. Filters ¶ These options may be repeated multiple times. --ignore-module =<mod> ¶ Ignore each of the given module names and its submodules (if it is a package). The argument can be a list of names separated by a comma. --ignore-dir =<dir> ¶ Ignore all modules and packages in the named directory and subdirectories. The argument can be a list of directories separated by os.pathsep . Programmatic Interface ¶ class trace. Trace ( count = 1 , trace = 1 , countfuncs = 0 , countcallers = 0 , ignoremods = () , ignoredirs = () , infile = None , outfile = None , timing = False ) ¶ Create an object to trace execution of a single statement or expression. All parameters are optional. count enables counting of line numbers. trace enables line execution tracing. countfuncs enables listing of the functions called during the run. countcallers enables call relationship tracking. ignoremods is a list of modules or packages to ignore. ignoredirs is a list of directories whose modules or packages should be ignored. infile is the name of the file from which to read stored count information. outfile is the name of the file in which to write updated count information. timing enables a timestamp relative to when tracing was started to be displayed. run ( cmd ) ¶ Execute the command and gather statistics from the execution with the current tracing parameters. cmd must be a string or code object, suitable for passing into exec() . runctx ( cmd , globals = None , locals = None ) ¶ Execute the command and gather statistics from the execution with the current tracing parameters, in the defined global and local environments. If not defined, globals and locals default to empty dictionaries. runfunc ( func , / , * args , ** kwds ) ¶ Call func with the given arguments under control of the Trace object with the current tracing parameters. results ( ) ¶ Return a CoverageResults object that contains the cumulative results of all previous calls to run , runctx and runfunc for the given Trace instance. Does not reset the accumulated trace results. class trace. CoverageResults ¶ A container for coverage results, created by Trace.results() . Should not be created directly by the user. update ( other ) ¶ Merge in data from another CoverageResults object. write_results ( show_missing = True , summary = False , coverdir = None , * , ignore_missing_files = False ) ¶ Write coverage results. Set show_missing to show lines that had no hits. Set summary to include in the output the coverage summary per module. coverdir specifies the directory into which the coverage result files will be output. If None , the results for each source file are placed in its directory. If ignore_missing_files is True , coverage counts for files that no longer exist are silently ignored. Otherwise, a missing file will raise a FileNotFoundError . Changed in version 3.13: Added ignore_missing_files parameter. A simple example demonstrating the use of the programmatic interface: import sys import trace # create a Trace object, telling it what to ignore, and whether to # do tracing or line-counting or both. tracer = trace . Trace ( ignoredirs = [ sys . prefix , sys . exec_prefix ], trace = 0 , count = 1 ) # run the new command using the given tracer tracer . run ( 'main()' ) # make a report, placing output in the current directory r = tracer . results () r . write_results ( show_missing = True , coverdir = "." ) Table of Contents trace — Trace or track Python statement execution Command-Line Usage Main options Modifiers Filters Programmatic Interface Previous topic timeit — Measure execution time of small code snippets Next topic tracemalloc — Trace memory allocations This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Debugging and Profiling » trace — Trace or track Python statement execution | 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:48:41 |
https://commission.europa.eu/index_en | European Commission, official website - European Commission Skip to main content en Select your language Close bg български es español cs čeština da dansk de Deutsch et eesti el ελληνικά en English fr français ga Gaeilge hr hrvatski it italiano lv latviešu lt lietuvių hu magyar mt Malti nl Nederlands pl polski pt português ro română sk slovenčina sl slovenščina fi suomi sv svenska Search Search European Commission Menu Back Home About us About us Learn more about the role of the European Commission, its leadership and corporate policies Organisation President Commissioners Departments and executive agencies Staff See all Role In strategy and policy In law In budget and funding In international relations See all Service standards and principles Transparency Ethics and Good Administration Modernising the European Commission The Commission’s use of languages See all Contact Discover more FEATURED 2024-2029 Commission: Priorities and leadership Our priorities Our priorities Learn how the EU is building a sustainable, digital, and inclusive future through its seven key priorities. Competitiveness Implementation tracker See all Security and defence Implementation tracker See all European social fairness Implementation tracker See all Quality of life Implementation tracker See all Democracy and our values Implementation tracker See all A global Europe Implementation tracker See all EU budget and reform Implementation tracker See all Discover more FEATURED Advance your research career in the EU News and media News and media Stay up to date with news from the European Commission. Discover the latest updates, stories, and press and audiovisual material. News Press corner Visual stories Audiovisual portal Discover more Topics Topics from A to Z Discover EU policies designed to bring benefits to citizens, businesses and other stakeholders in the EU Aid, Development cooperation, Fundamental rights Human rights in non-EU countries Your fundamental rights in the EU Recipients and results of EU aid How we provide aid Ensuring aid effectiveness See all Business, Economy, Euro Doing business in the EU Financial services Economic recovery Economic forecasts and surveillance The European Semester Economic and Monetary Union The euro area The benefits of the euro See all Education Skills and qualifications Study or teach abroad Teaching methods and materials Policy on educational issues Set up projects for education and training See all FEATURED Spot and stop information manipulation Energy, Climate change, Environment Overall targets and reporting Implementation in EU countries International cooperation Standards, tools and labels See all EU regional and urban development Financial support for projects Projects and results Countries, regions, cities Cooperation between border regions See all Food, Farming, Fisheries Food safety and quality Farming Oceans and fisheries Forestry Sustainable agriculture Agricultural trade Plants and plant products Animals and animal products See all Law Law-making process Tracking law-making Search law Law by topic Application of EU law Cross-border cases Judicial training and professional networks Find a legal professional See all FEATURED How EU laws are made Live, work, travel in the EU Living in another EU country Consumer rights and complaints Culture, Heritage, Sport in the EU Working in another EU country Employment opportunities Travelling in the EU Travelling for non-EU nationals Emigrating to the EU See all Research and innovation Strategy on research and innovation Law and regulations Knowledge: publications, tools and data Funding Projects Partners, networking Research by area See all FEATURED Advance your research career in the EU Discover more Resources Resources Access a range of resources, including publications, statistics, learning material, and tools for stakeholders. Publications Statistics Search Eurostat statistics Economic forecasts and trends Tracking EU policy performance and recovery Public opinion survey EU open data portal Guide to European statistics See all Eurobarometer EU law Learning corner Europa Web Guide European Commission visual identity Discover more Europe and you Get involved Share your views on EU laws and policies, debate Europe's future and find funding for your EU projects. Engage in EU policymaking Have your say European Citizens’ Panels European Citizens' Initiative Petition the EU See all Jobs Funding and tenders Events Visit us Visitors' Centre Experience Europe exhibition centre See all European Commission on social media Discover more 10 ways the EU makes your life easier Homepage Welcome to the world's biggest free trade zone Partnership agreement with Mercosur Learn more News 9 January 2026 President von der Leyen strengthens EU partnerships in the Middle East 3 min read 31 December 2025 Bulgaria adopts the euro 1 min read 23 December 2025 2025: Europe in 10 snapshots 6 min read 19 December 2025 Agreement reached to support Ukraine with €90 billion 3 min read Read more news Agenda 14 January College meeting 15 and 16 January College visit to the Cyprus presidency of the Council 20 January College meeting Follow us In focus From promise to progress A budget for Europeans Choose Europe for science About the European Commission The European Commission is the EU’s main executive body. It proposes legislation, upholds EU treaties and ensures Member States apply EU law and policies. The Commission manages the EU's budget and negotiates international agreements on behalf of the EU. President Ursula von der Leyen (2024-2029) College 27 Commissioners tasked with specific policy priorities Our work EU strategy, policies, and initiatives Our priorities Discover our seven priorities for 2024–29 Europe and you Your Europe Information, help and advice on EU rights, life, travel and doing business in the EU Funding and tenders EU funding, grants, tenders, and how to apply European Youth Portal Information and opportunities for young people Visit the European Commission How to visit the Commission and other EU institutions in Brussels and beyond Jobs Job vacancies in the Commission Have your say Be an active participant in shaping European policies and share your views with us Share this page This site is managed by: Directorate-General for Communication About us Contact us Priorities Topics Funding and tenders Jobs Press corner Events Follow us Facebook Instagram X LinkedIn Other networks Report an IT vulnerability Languages on our websites Cookies Privacy policy Legal notice Accessibility | 2026-01-13T08:48:41 |
https://docs.python.org/3/tutorial/controlflow.html#keyword-only-arguments | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | 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:48:41 |
https://survivejs.com/workshops/ | SurviveJS - Workshops Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Workshops I run my workshops using a kata format. In other words, they form of series of smaller tasks that contain exercises to complete to encourage learning through doing. Often I complete my kata workshops with a brief introduction to the topic. Although it is fun to complete them in a workshop format, it is possible to go through them alone and I have listed my katas below. Qwik katas (2023) ↗ Qwik ↗ is a recent web framework that approaches web application from a different angle by eschewing the concept of hydration and replacing it with resumability. This means it provides unique benefits, such as automatic code-splitting, out of the box making it an interesting alternative for web developers that want to develop performant websites and applications out of the box. See Qwik katas ↗ Deno katas (2023) ↗ Deno ↗ is the followup project of Ryan Dahl, the original author of Node.js ↗ . In Deno, Ryan wanted to fix his perceived mistakes of Node.js and Deno could be characterized as a whole toolbox that comes with solutions for common server-side programming problems particularly in terms of tooling. See Deno katas ↗ Web Audio katas (2023) ↗ Web Audio ↗ is a powerful, yet underestimated, web API that allows you to build complex audio-based web application. In this kata, you will build a small Digital Audio Workstation (DAW) while getting acquainted with the relevant APIs and some of the history behind digital audio. See Web Audio katas ↗ Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://survivejs.com/books/maintenance/ | SurviveJS – Maintenance Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... SurviveJS – Maintenance The maintenance book captures good practices related to developing and maintaining JavaScript applications or packages at scale. I co-authored the book with Artem Sapegin ↗ and the book is not yet fully complete although completion and a bigger update is planned. Read the maintenance book Buy the maintenance book ↗ Availability Although you can read the book online for free , you can also purchase it in a copy to support the development of the content. See also consulting for other available options. Leanpub (digital, always up to date with the site) ↗ Table of contents Preface Once an initial version of software has been developed, it often becomes the subject of maintenance efforts. You will have to evolve the code to match new requirements. Doing this is challenging when technology keeps changing. Especially web development is prone to this as the stack and standards k… Introduction The popularity of JavaScript and related technologies has exploded. As a result there are now numerous open source projects which rely on the language. JavaScript is widely used for web development and it sees further use beyond the web. The popularity and on-going evolution of the web platform pos… Packaging In this part, you’ll learn how to package your projects for consumption through npm. You will also learn to manage releases, generate standalone builds, and manage dependencies. … Where to Start Packaging npm has become wildly popular for managing JavaScript packages. It started in the backend world but has since grown to include frontend libraries as well. And now we have another issue: it’s hard to find a package your need because there are so many, and you end up creating a new one increasing the… Anatomy of a Package A minimal npm package should contain metadata in a package.json file and an associated source file (usually index.js). In practice, packages contain more than that and you will have at least a license file and the source in various formats. Often projects contain more files than are required to ex… Publishing Packages Publishing npm packages is only a npm publish away. Assuming the package name is still available and everything goes fine, you should have something out there! After this, you can install your package through npm install or npm i. Most of the community follows a specific versioning convention whic… Building Packages While publishing packages, you have a few concerns to worry about: Which browsers and Node versions to support? What to do if we want to use language features that aren’t supported by these targets? What to do if we want to use another language than JavaScript to author our package? How to support… Standalone Builds The scenarios covered in the previous chapter are enough if you consume packages through npm. There may be users that prefer pre-built standalone builds or bundles instead. This comes with a several advantages: Everything is packaged into a single file. You can include the bundle using a `` tag. T… Managing Dependencies Keeping dependencies updated is important to have the latest bugfixes and security updates, but it needs a lot of work: once in a while you need to check which packages have new versions and how to migrate, sometimes you have to rewrite parts of your code. Bigger projects may provide codemods that … Code Quality In this part, you’ll learn about different aspects of code quality. You can use the ideas to evaluate other people’s projects and to improve the quality of your own. … Linting We read code more often then we write it: sometimes we spend hours looking for what caused the bug, only to fix it with a single line of code. That’s why consistent code style is important. Ideally code in a project should look like it was written by a single developer. It makes code easier to read… Code Formatting Usually linters can validate and fix code formatting but there are specialized tools that work better. Achieving Code Consistency Code consistency helps when several people work on the same codebase: code look similar everywhere; programming patterns used consistently across the codebase; naming… Typing A function interface is a contract and depending on the system, it gives you guarantees. JavaScript doesn’t give any guarantees by default and you can pass anything to a function. Doing this may lead to a runtime error and crash your application. In a stricter system it’s difficult, or even impossi… Testing Tests can be seen as a runnable documentation of your code. Automated testing gives you confidence to change the code. Manual testing is the other end of the spectrum. It’s also the most labor intensive and brittle option. What to Verify With Testing Testing can be used to verify at least the fol… Infrastructure In this part, you’ll learn how to set up an infrastructure to support your project. By doing this well, you’ll make it easier for others to contribute to your project and make it grow faster. A good infrastructure becomes particular important as a project grows. … Processes Each project has processes around it. Services like GitHub, GitLab, and Bitbucket provide plenty of tool to manage open source projects: version control for project source, issue tracker, pull requests to accept code from your users, and often hosting your project site. When you think about proces… Continuous Integration Continuous integration (CI) services will run your tests in several environments: different operating systems, browsers or Node versions. It’s would be complicated to setup on your local machine. Usually CI checks every commit to your master or development branch as well as on each pull request — C… Automation Everything that can be done by a machine, will eventually be done by a machine. One of the earliest "computers", the Jacquard machine, achieved this for manufacturing complex textiles. It displaced human effort this way and pushed the difficult and monotonous task to a machine. This is the whole po… Documentation In this part, you’ll learn how to write a good README and a good change log, how to generate documentation for your API and create a site for your project, and about other kind of documentation that may help your users. … README A project README is often the first thing people see when they find the project. The project’s site is another entry point. Often a site is generated from a README file content with nice CSS. A good README can “sell” the project to a potential user. A badly written or formatted one can scare users… Change Logs Change log is an essential part of an open source project: it tells the user what was changed in a new version, about new features and breaking changes, and how to migrate to a new version. Why Not Commit Log Many projects don’t have change logs and ask users to read the commit log. But commit lo… Site Project site isn’t only a marketing tool — it also allows you to show your project to its potential users and give them the opportunity to try the project in their browsers. For many projects GitHub repository would be enough but Markdown pages are the only tool you have there, and a site have som… API Documentation For small project you can write API documentation manually in the README file, but for larger projects it’d be hard to maintain. You will need to generate API documentation from the code. Documenting APIs in Code JavaScript The most popular format for documenting JavaScript APIs is JSDoc. It use… Other Types of Documentation Contribution Guidelines Contribution guidelines explains how to contribute to a project: how to setup the environment; code style; what kind of contributions you want; links to all relevant documentation. GitHub will show a link to contributing guidelines on the new pull request page. Read more… Linting and Formatting Text linting is much less common than code linting, but if you have to maintain a lot of text it may save you a lot of time, and improve quality of your documentation. Linting Markdown With Textlint and Proselint Text linting is less common than code linting but in large projects with many contri… Future In this part, you’ll learn how too consider the longevity of your project and how to market it if popularity is one of the goals of it. … Longevity When developing a project, you should consider its goals and timespan. Some projects are one-off and meant to solve an immediate problem and are then thrown away. Others have more longer term focus and evolve over a long time. The question is, how to enable this long term evolution? You have to co… Marketing Even the technically most excellent project in the world won’t have much impact unless it reaches potential users. Popularity isn’t a goal always, but if it’s, then it’s good to know how to approach marketing the project. The purpose of marketing is to connect the potential user with the project. … Appendices TODO … Managing Packages Using a Monorepo npm packages can be managed in multiple ways. The most common way is to have one package per a source repository. The problems begin when you have to orchestrate changes across multiple related packages. The idea of monorepos was designed for this purpose. Monorepos - What Are They A monorepo all… Customizing ESLint Even though you can get far with vanilla ESLint, there are certain techniques you should know. For instance, sometimes you want to skip specific rules per file. You can even implement rules of your own. Speeding up ESLint Execution One of the most convenient ways to speed up ESLint execution on b… Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://survivejs.com/presentations/ | SurviveJS - Presentations Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Presentations I have given many presentations and lectures through the years and I have included some of the most recent ones below. Web application development - The past, the present, the future (2025) ↗ In this lecture, I take a look at the history of web application development to understand where we are coming, what’s the current state, and where we are heading. By understanding the past constraints, also current struggles and the need for new solutions makes sense. See web application development slides ↗ Emergence of hybrid rendering models in web application development (2025) ↗ In this doctoral lecture, I go through the main points related to my thesis. See my doctoral slides ↗ ECMAScript - From an idea to a major standard (2023) ↗ In this brief presentation held at EURAS2023, I discuss how ECMAScript became a major standard having concrete impact on our daily lives. See ECMAScript slides ↗ Quick introduction to Qwik (2023) ↗ In this presentation, I give a quick introduction to Qwik, an upcoming full stack JavaScript framework. See Qwik slides ↗ JavaScript frameworks of tomorrow (2023) ↗ Expect to learn a lot about the direction of the frontend. See JavaScript slides ↗ The future is mostly static (2022) ↗ In this brief presentation, I go through the main trends of web development in 2022 and share my views on where we are going. See future related slides ↗ Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://survivejs.com/about-me/ | SurviveJS - About me Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... About me I am Juho Vepsäläinen, a DSc and a seasoned web developer. I developed my first website around 1996 although it has been lost to the history and I was not serious about web development back then. It was only in early 2000s that I started to become more serious about programming as I became involved with the Blender ↗ project for several years starting from 2005 as I contributed to the project by coding and improving documentation. I was one of the founders of webpack ↗ core team and helped to establish the project to a broader public through my webpack book . I have also authored numerous open source projects primarily for my own purposes, although several have become popular on their own as other people and companies have found my work useful. I established my own company in 2016 to support my publishing efforts. I use the company for occasional consulting while giving workshops and presentations as opportunities arise. I have been organizing conferences primarily in Finland starting from 2018 as the first React Finland ↗ conference took place then. Since that time, we have pivoted into a new brand called Future Frontend ↗ to allow discussion about future-oriented web topics beyond React. You can consider this site as my collection of web related knowledge. It is primarily a learning resource for beginner to intermediate developers although especially the research portions cover advanced, bleeding edge material. I am not overly active on social media, but you can find me in the following places: Find me at GitHub ↗ See my LinkedIn ↗ Check my Slideshare slides ↗ Follow me on X (Twitter) ↗ Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://dev.to/codemouse92/updated-opensource-tag-guidelines-55m5#guideline-enforcement | Updated #opensource Tag Guidelines - 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 Jason C. McDonald Posted on Jul 17, 2019 • Edited on Apr 8, 2020 Updated #opensource Tag Guidelines # opensource # meta Updated 8 April 2020 The #opensource tag is awesome, but it's also been lacking a lot of focus. Is it for promoting projects? Talking about open source? Posting lists of the top 20 open source Javascript modules? It's hard to tell. In a way, because the lion's share of our technologies, libraries, tools, and projects are open source, nearly everything qualified for this tag before. It was becoming our site's junk drawer as it were - lots of nifty and useful stuff, but no semblance of organization to any of it. Since DEV.to rolled out Listings , I'm taking the opportunity to narrow the tag focus a bit. The goal is to give the #opensource tag clear topic boundaries, so Following it doesn't lead to a bunch of irrelevant posts leaking into your feed. New Guidelines I've updated the tag guidelines, but I wanted to lay out the changes here. Posts promoting a single project should go on Listings , or on #showdev or #news if it qualifies. Posts using or mentioning one or more open source projects should go on the appropriate tags for the relevant languages and technologies. This includes tutorials, "round ups", guides, comparisons, reviews, and the like. These typically land in #opensource, and are the main reason for the tag clutter. Announcements relating to your awesome project, including new features, releases, versions, and the like, should go on #news or Listings , or should be expanded out into a proper article (tutorial, maybe?) and posted on the appropriate technology tags. Open source contributor requests should go on #contributorswanted or Listings . If you're just bursting with pride at something you built, use the #showdev tag instead. "Roundups" and other lists of cool open source projects belong on #githunt . What Changed? All this mainly means the #opensource tag is no longer valid merely if the project(s) being discusses happen to be open source! To put that another way, here's a few theoretical topics which would have been #opensource material before, but aren't now. "Top 10 Open Source Python Data Modules" ( #python ) "My Awesome Data Visualizer in Go" ( #go , #showdev ) "Looking for contributors to Supercoolproject" (Listings or #contributorswanted ) "What I did on my Perl project this week" ( #perl , #devjournal , possibly #showdev ) "Installing Epictool on Ubuntu" ( #ubuntu ) "5 Open Source Alternatives to AWS" ( #cloud ) What SHOULD It Be? Articles in this tag should be about at least one of these three broad topics: Organizing, managing, running, contributing to, or working in an Open Source project. Open Source philosophy, licensing, and/or practical and legal topics thereof. Advocacy and adoption of Open Source philosophy . Aliases #foss and #freesoftware have been aliased over to #opensource (thanks @michaeltharrington !) and the tag info updated to account for that. I know that Free Software is culturally distinct from Open Source, but as the former is always compliant to a subset of the latter, having one tag for all just makes sense. Guideline Enforcement I won't be applying this to any posts before July 17th 2019 (retroactive guidelines just aren't fair). If the #opensource tag is used incorrectly in new posts, I'll remove it and provide a friendly reminder, along with suggestions on better tags to use. I know it'll take a while to get used to the updated rules, so don't worry if you miss it a few dozen times. Top comments (8) 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 • Jul 17 '19 Dropdown menu Copy link Hide Well thought out Jason. I'll be following along. We'll have some more easily accessible tag guidelines adjacent to the editor coming soon so folks can understand the instructions without being caught off guard by doing it wrong. As more folks define their guidelines, my biggest worry is what a lot of forums become when mods are overbearing. So I'm glad this is well thought out and well described. @michaeltharrington let's Jason well with this and we'll coordinate on functionality that needs to ship. Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Michael Tharrington Michael Tharrington Michael Tharrington Follow I'm a friendly, non-dev, cisgender guy from NC who enjoys playing music/making noise, hiking, eating veggies, and hanging out with my best friend/wife + our 3 kitties + 1 greyhound. Email mct3545@gmail.com Location North Carolina Education BFA in Creative Writing Pronouns he/him Work Senior Community Manager at DEV Joined Oct 24, 2017 • Jul 17 '19 Dropdown menu Copy link Hide Agreed! This is very well thought out. I think this tag will definitely benefit from more focus. Jason, feel free to hit me up if you need a hand with anything. I'm happy to help! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Email codemouse92@outlook.com Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 • Jul 17 '19 Dropdown menu Copy link Hide Thanks, Michael and Ben! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand William Antonelli William Antonelli William Antonelli Follow Joined Mar 7, 2019 • Jul 18 '19 Dropdown menu Copy link Hide This is a list of what not to use the tag for. Can you give some examples of what we would use it for? I think that would be easier to understand. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Email codemouse92@outlook.com Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 • Jul 18 '19 Dropdown menu Copy link Hide No problem. From the tag info: To keep this tag clean and meaningful, please ensure your post fits into at least one of the following categories: * Organizing, managing, running, or working in an Open Source project. * Open Source philosophy, licensing, and/or practical and legal topics thereof. * Advocacy and adoption of Open Source technology. I'll add that to the post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Frederik 👨💻➡️🌐 Creemers Frederik 👨💻➡️🌐 Creemers 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! Email frederikcreemers@gmail.com Location Maastricht, the Netherlands Education Knowledge Engineering & Data Science at Maastricht University Pronouns he/him Work Developer at TalkJS Joined Mar 22, 2017 • Jul 17 '19 Dropdown menu Copy link Hide I think the #githunt tag is also relevant here. Looking at some of its recent posts, it could also use some enforcement of its guidelines. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Email codemouse92@outlook.com Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 • Aug 3 '19 • Edited on Aug 3 • Edited Dropdown menu Copy link Hide Y'know, they're always looking for more tag moderators, and I agree that #githunt needs some love. Maybe that'd be something you'd be good at? (Contact yo@dev.to if you're interested.) Like comment: Like comment: 1 like Like Comment button Reply Some comments may only be visible to logged-in visitors. Sign in to view all comments. Some comments have been hidden by the post's author - find out more 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 Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 More from Jason C. McDonald 5 Ways to Retain Open Source Contributors # opensource # culture # projectmanagement Social Lifespan of Posts # meta # discuss Introducing #devjournal # devjournal # meta 💎 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:48:41 |
https://dev.to/t/mentalhealth/page/7 | Mental Health Page 7 - 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth posts 4 5 6 7 8 9 10 11 12 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 🧠 How Small Daily Habits Improve Mental Health (NIMH-Backed Self-Care Strategies) NVelUp NVelUp NVelUp Follow Oct 11 '25 🧠 How Small Daily Habits Improve Mental Health (NIMH-Backed Self-Care Strategies) # mentalhealth # productivity # selfcare # wellness Comments Add Comment 4 min read I Built an AI Prompt to Debug My Post-Holiday Brain Fog—Here's How It Works Hui Hui Hui Follow Oct 8 '25 I Built an AI Prompt to Debug My Post-Holiday Brain Fog—Here's How It Works # ai # productivity # mentalhealth # promptengineering 2 reactions Comments Add Comment 8 min read Burnout in Tech: How to recognize it and build a sustainable career Gonzalo Terzano Gonzalo Terzano Gonzalo Terzano Follow Sep 1 '25 Burnout in Tech: How to recognize it and build a sustainable career # worklife # mentalhealth # career # developers Comments Add Comment 4 min read Coping After Trauma: Practical Strategies to Rebuild Resilience 🌱 NVelUp NVelUp NVelUp Follow Sep 30 '25 Coping After Trauma: Practical Strategies to Rebuild Resilience 🌱 # mentalhealth # burnout # trauma # resilience Comments Add Comment 2 min read Work hard, ship code, go home: Why hustle culture is cringe <devtips/> <devtips/> <devtips/> Follow Sep 29 '25 Work hard, ship code, go home: Why hustle culture is cringe # discuss # career # mentalhealth # productivity 4 reactions Comments 1 comment 25 min read Migraine Awareness Week 2025: Living With New Daily Persistent Headache (NDPH) Dumebi Okolo Dumebi Okolo Dumebi Okolo Follow Sep 24 '25 Migraine Awareness Week 2025: Living With New Daily Persistent Headache (NDPH) # watercooler # mentalhealth # wellbeing # devhealth 17 reactions Comments 9 comments 4 min read 🏆003. Brainstorming is key Valacor Valacor Valacor Follow Sep 26 '25 🏆003. Brainstorming is key # softwareengineering # learning # mentalhealth # tooling Comments Add Comment 1 min read Why Your Relationships Matter as Much as Code Reviews: Social Connection & Mental Health NVelUp NVelUp NVelUp Follow Sep 23 '25 Why Your Relationships Matter as Much as Code Reviews: Social Connection & Mental Health # mentalhealth # productivity # wellness # developer Comments 1 comment 2 min read Building Aliō: How I Shipped an App with AI Tools Evgeniy Molozhenko Evgeniy Molozhenko Evgeniy Molozhenko Follow Sep 21 '25 Building Aliō: How I Shipped an App with AI Tools # vibecoding # ios # mobile # mentalhealth 4 reactions Comments 3 comments 2 min read Detecting Depression Using Deep Learning on Facial Expression Images -Mini Project Michael Quelazar Michael Quelazar Michael Quelazar Follow Aug 19 '25 Detecting Depression Using Deep Learning on Facial Expression Images -Mini Project # deeplearning # tensorflow # cnn # mentalhealth Comments Add Comment 5 min read The Feeling of Momentum Can Be a Trap (Bite-size Article) koshirok096 koshirok096 koshirok096 Follow Aug 15 '25 The Feeling of Momentum Can Be a Trap (Bite-size Article) # mentalhealth # productivity Comments Add Comment 3 min read How a Simple Dashboard Can Transform TMS Therapy Management OlhaStfn OlhaStfn OlhaStfn Follow Aug 15 '25 How a Simple Dashboard Can Transform TMS Therapy Management # ai # tms # mentalhealth # healthtech Comments Add Comment 2 min read Common Challenges for developers and learners davinceleecode davinceleecode davinceleecode Follow Aug 19 '25 Common Challenges for developers and learners # developer # learning # career # mentalhealth 6 reactions Comments Add Comment 1 min read StrangEars Pratham Dhyani Pratham Dhyani Pratham Dhyani Follow Aug 14 '25 StrangEars # kiro # mentalhealth # webdev # ai Comments Add Comment 3 min read 🧠 5 Evidence-Based Anxiety Coping Strategies (For Developers & Tech Professionals) NVelUp NVelUp NVelUp Follow Sep 17 '25 🧠 5 Evidence-Based Anxiety Coping Strategies (For Developers & Tech Professionals) # mentalhealth # wellness # productivity # career Comments 1 comment 2 min read 🧠 When to Seek Help: 5 Clear Signs You Might Need a Therapist NVelUp NVelUp NVelUp Follow Sep 15 '25 🧠 When to Seek Help: 5 Clear Signs You Might Need a Therapist # mentalhealth # productivity # career # burnout Comments 1 comment 2 min read How to get a job without losing your mind! JEstebanDev JEstebanDev JEstebanDev Follow Sep 14 '25 How to get a job without losing your mind! # career # mentalhealth # motivation Comments Add Comment 5 min read New Angle : Serious Games cutieyunny-tech cutieyunny-tech cutieyunny-tech Follow Sep 14 '25 New Angle : Serious Games # showdev # mentalhealth # gamedev # discuss Comments Add Comment 1 min read 🔥 Leading Through Burnout: What They Don’t Tell You Yusuf Saifurahman Yusuf Saifurahman Yusuf Saifurahman Follow Aug 24 '25 🔥 Leading Through Burnout: What They Don’t Tell You # mentalhealth # webdev # programming 5 reactions Comments 1 comment 3 min read The Future of Self-Care: How AI is Revolutionizing Personalized Affirmations with Affirmi WolfOf420Stret WolfOf420Stret WolfOf420Stret Follow Aug 10 '25 The Future of Self-Care: How AI is Revolutionizing Personalized Affirmations with Affirmi # ai # mentalhealth # buildinpublic # startup Comments Add Comment 6 min read WorryBox Andrew Hewitt Andrew Hewitt Andrew Hewitt Follow Sep 12 '25 WorryBox # ai # opensource # mentalhealth # kiro Comments Add Comment 8 min read 🧠Too much on my mind🧠 Valacor Valacor Valacor Follow Sep 11 '25 🧠Too much on my mind🧠 # softwaredevelopment # sideprojects # mentalhealth 1 reaction Comments Add Comment 2 min read 🧠 Sleep Your Way to Mental Wellness: A Developer’s Guide NVelUp NVelUp NVelUp Follow Sep 11 '25 🧠 Sleep Your Way to Mental Wellness: A Developer’s Guide # mentalhealth # productivity # selfcare # wellness 1 reaction Comments Add Comment 2 min read Boost Your Productivity: A Sleep Debt Calculator for Devs Chirag Patel Chirag Patel Chirag Patel Follow Sep 11 '25 Boost Your Productivity: A Sleep Debt Calculator for Devs # productivity # mentalhealth # webdev # developer Comments Add Comment 3 min read Mentorship in Motion: How a Summer Break Sparked a Pivot Bala Madhusoodhanan Bala Madhusoodhanan Bala Madhusoodhanan Follow Sep 8 '25 Mentorship in Motion: How a Summer Break Sparked a Pivot # mentorship # mentalhealth # womenintech 5 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:48:41 |
https://survivejs.com/blog/impressions-on-web-summit-2024/ | Impressions on Web Summit 2024 Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Thank you to the Serbian Chamber of Commerce for making the trip possible Web Summit - What was it about? MEO Arena - the massive venue Catering from your pocket A lot of content, meetups, and night summit Observed trends Conclusion Thank you to the Serbian Chamber of Commerce for making the trip possible Web Summit - What was it about? MEO Arena - the massive venue Catering from your pocket A lot of content, meetups, and night summit Observed trends Conclusion Loading... Impressions on Web Summit 2024 Author: Juho Vepsäläinen Topics Conference Published: 21.11.2024 Impressions on Web Summit 2024 Web Summit ↗ 2024 occurred from 11 to 14.11 in Lisbon, Portugal. Despite its name, the summit does not focus on the web. Instead, it is the largest startup fair in the world, boasting 70.000 yearly visitors. I had the chance to visit the event for the first time this year, and I will share my impressions in this post. TLDR: To get the most out of Web Summit, you must know what you are looking for and prepare accordingly. Thank you to the Serbian Chamber of Commerce for making the trip possible # I would not have made this trip unless the Serbian Chamber of Commerce and Industry had invited me (thank you, Dejan in particular!) as they took care of the arrangements. I brought Janne Kalliola ↗ from Finland, and we spoke about sustainability at the Serbian booth and participated in a panel discussion on the topic. Although the countries are far from each other geographically, they share certain similarities, and the trip allowed for cultural exchange on multiple levels. Me taking part in a sustainability panel Web Summit - What was it about? # From what I understand, the primary function of Web Summit is to connect startups with investors while catering to an audience interested in technology and current trends. Web Summit started as a web startup-focused event in Ireland, which grew in scope and eventually moved to Lisbon, Portugal. I believe this is one of the ways the local government can highlight the status of Portugal as a startup nation and attract investments. It might be a good tactic, and Finland is doing something similar with its Slush ↗ event, which is scoped at 13.000 people while being more focused on connecting startups with investors than Web Summit, which has broader scope. One way to define Web Summit would be to say that it is an antithesis to a small conference like Future Frontend ↗ that I help to organize. While Future Frontend is small (about 200 people) and focused on its single-track program over two days, Web Summit is anything but. One way to describe Web Summit would be to say it is a sea ten centimeters (a couple of inches) deep, while Future Frontend is a small pool that is maybe ten meters deep (about 30 feet). In practice, you must make your program intentionally or get washed up by the waves. Due to its sheer scope, Web Summit has likely everything for everyone working with technology. Participating in an event like this is a bit like a random walk, and you will never know who you will meet. I made some of my most exciting contacts through sheer luck by being in the right place at the right time. I believe each conference experience is different; to some part, it is about what you make out of it as a participant. The conference offered a mobile application for building your program and connecting with other participants to keep it manageable. Paddy Cosgrave at the main stage MEO Arena - the massive venue # To say that the event had a lot of space would be an understatement. Web Summit was held at MEO Arena ↗ , one of the largest indoor arenas in Europe apparently, and it also occupied the nearby exhibition halls. While the arena hosted the main track with the biggest names, the rest of the conference was spread along the exhibition space. Multiple tracks focused on specific topics, such as marketing, running parallel. Apart from one track, the rest ran in the same space with booths, meaning there was constant ambient noise even during presentations. Although that was not too distracting, it was perhaps a bit draining. Serbian booth at Web Summit 2024 Startups had smaller stands where a person could showcase what their business was doing. More established companies and some countries even rented bigger booths with ample space for branding and attracting visitors. Some countries and companies invested a lot of money into their booths. However, several ran with lighter setups and were happy to be present and approachable. Startup booths at Web Summit Catering from your pocket # In addition, the conference ran food and wine expos. Unlike in many other conferences I have visited, in this case, you had to pay for your food; in my experience, the quality tended to vary. The prices were higher than you might pay outside of the venue, and you received less. Usually, it was a good sign if people were queuing at a specific food stand, as that meant you would likely get decent value for your money. Overall, Portugal is a surprisingly good food country if you know where to look. It is easy to find reasonably priced fish food in a coastal city like Lisbon. I was pleasantly surprised many times by the local restaurants, and I found out that a chain restaurant called Honest Greens had good vegetarian offerings. Honorable mention goes to Timeout Market with its unique concept of buying plates to eat from different vendors. For a particular sweet, I would check out Pasteis de Nata. Dorade portuguese style A lot of content, meetups, and night summit # Web Summit 2024 had stunning ten parallel tracks running in addition to what they call a startup university. On top of this, there were what they called meetups and a night summit at the event. In addition, third parties organized their events on top of the official program. This meant there was enough content, and you had to prioritize what to follow. Given the venue was so big, I learned early on that I should reserve enough time to move from one track to another since that could take a while. The tracks were filled with short talks and panels with twenty-minute slots. That felt a bit too short for me, given that many topics are enough to get started but not enough to delve deep. The time felt short for panels as well, and occasionally, there was not enough contrast between the people being interviewed for my tastes to spark interesting conversations. For 2024, the event organized meetups alongside the main program. The idea was to connect people within a specific topic, such as research, and let them meet in a particular context speed-dating style. The meetups were limited to twenty minutes, and I found them quite effective for generating contacts quickly. However, the time went too short for the more interesting ones, and perhaps the speed dating aspect could have been more organized, as now it was up to your social skills to move around and meet people. In addition, Web Summit organized a night summit after the main content for 12.11 and 13.11. Again, these were themed as meetups but were arranged around Lisbon. I participated in one, and their Web Summit organized one free drink for each participant, which was a nice touch. I did find it interesting, however, that there was no night summit after the last day of the conference. Given the sheer number of people, I understand an afterparty would have been too much to ask, but it would have been nice to have some distributed events even after the event’s last day. Beyond the official program, there were many unofficial events, and I participated in a couple. For example, Finland organized a “Finland Afterworks” event explicitly aimed at people who considered Finland a work destination. I also noticed that some companies organized events explicitly aimed at startups, and I believe they were marketed expressly at them. Finland Afterworks Observed trends # A conference as broad as Web Summit gave me an excellent chance to observe several more significant trends. However, I am sure I missed many due to my limited personal bandwidth, which prevented me from consuming them all. Perhaps the thing that stood out the most was the prevalence of Artificial Intelligence (AI) across content and booths. Many startups have taken AI to its core and presented it as a part of their pitch in one way or another. What was perhaps more surprising to me was the limited number of startups oriented around sustainability. However, we are feeling the impact of the climate crisis more concretely year by year, and there is a clear need for more sustainable solutions. In some way, AI and sustainability may be at odds as the former is pushing our energy consumption, and simultaneously, there is a need to use our resources more innovatively to be sustainable in the long term. Another thing that stood out was the need for hyper-personalization, especially in the web context. The talks I followed confirmed my belief that we are headed towards more personalized experiences, and building them will require new levels of expertise from web developers. By personalizing, we can serve our audiences better while attaining better business results. I can imagine this comes with technical challenges, and new ways of thinking about web experiences are needed to move beyond what we currently have. I found the polar bear Conclusion # I can only imagine how difficult it is to organize an event at the scale of Web Summit, and I am happy to run small, focused conferences in Finland. I can see how both models can work in their favor. However, larger conferences, like Web Summit, push a chunk of effort on their attendees as they have to be mindful of how they spend their time. There is less thinking to do in a minor event, and they feel more relaxed for me as an attendee. It would be interesting to visit a smaller conference, such as Slush, similar to Web Summit, to see what difference scale makes for an event aimed specifically at startups. It is difficult to tell whether I will attend the Web Summit again. The city of Lisbon is quite lovely, although you have to be mindful of your belongings. It should be a safe city if you keep your wits with you. It is worth researching before heading there so you know what to do and what not, where to go and not, and so on. The locals seem friendly, and it helps to know at least a few words of Portuguese to show that you are trying. Lisbon tourist trams Author: Juho Vepsäläinen Topics Conference Published: 21.11.2024 ← Previous state-ref - Easy to integrate state management library - Interview with Kim Jinwoo ← Previous state-ref - Easy to integrate state management library - Interview with Kim Jinwoo Comments # Show comments Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://share.transistor.fm/s/940dfccb#copya | APIs You Won't Hate | The State of the API Address APIs You Won't Hate 40 ? 30 : 10)" @keyup.document.left="seekBySeconds(-10)" @keyup.document.m="toggleMute" @keyup.document.s="toggleSpeed" @play="play(false, true)" @loadedmetadata="handleLoadedMetadata" @pause="pause(true)" preload="none" @timejump.window="seekToSeconds($event.detail.timestamp); shareTimeFormatted = formatTime($event.detail.timestamp)" > Trailer Bonus 10 40 ? 30 : 10)" class="seek-seconds-button" > 40 ? 30 : 10"> Subscribe Share More Info Download More episodes Subscribe newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyFeedUrl()" class="form-input-group" > Copied to clipboard Apple Podcasts Spotify Pocket Casts Overcast Castro YouTube Goodpods Goodpods Metacast Amazon Music Pandora CastBox Anghami Anghami Fountain JioSaavn Gaana iHeartRadio TuneIn TuneIn Player FM SoundCloud SoundCloud Deezer Podcast Addict Share newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyShareUrl()" class="form-input-group" > Share Copied to clipboard newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyEmbedHtml()" class="form-input-group" > Embed Copied to clipboard Start at Trailer Bonus Full Transcript View the website updateDescriptionLinks($el))" class="episode-description" > Chapters December 1, 2021 by APIs You Won't Hate View the website Listen On Apple Podcasts Listen On Spotify Listen On YouTube RSS Feed Subscribe RSS Feed RSS Feed URL Copied! Follow Episode Details / Transcript Matt and Phil are joined by Matthew Reinbold, director of API Ecosystems and Digital Transformations at Postman, to talk about Postman's State of the API 2021. Show Notes Matt and Phil are joined by Matthew Reinbold, director of API Ecosystems and Digital Transformations to discuss Postman's State of the API 2021 report, detailing various data points from around the API world from which specification people turn to, to how confident people feel deploying their APIs. They also discuss various topics around remote work, how APIs enable more remote work and what will happen in the next few years for APIs. Notes: Matthew on twitter: https://twitter.com/libel_vox Postman's State of the API Creators and Guests Host Mike Bifulco Cofounder and host of APIs You Won't Hate. Blogs at https://mikebifulco.com Into 🚴♀️, espresso ☕, looking after 🌍. ex @Stripe @Google @Microsoft What is APIs You Won't Hate? A no-nonsense (well, some-nonsense) podcast about API design & development, new features in the world of HTTP, service-orientated architecture, microservices, and probably bikes. Matt Trask: Cool. Welcome back to APS. You won't hate episode 17. I have Phil with me and we're joined by a very special guest today. Matthew Reinbold, fresh from postman, who is a director of API ecosystems and digital transformations here to talk about their report, the 2021 state of the API ecosystem. Matthew, how's it going? Matthew Reinbold: It is going. I am happy to be here first time, caller, long time listener. Is that how we say that? Matt Trask: I think that's yeah. It's how you say it. Yeah. So I mean, for those of you, like in the off chance that someone doesn't know who you are in the API ecosystem world can you give us a little bit kind of about yourself? Like you manage two different newsletters, at least as well as a pretty prolific Twitter presence as well. But if someone hasn't run into you, like. Matthew Reinbold: Well, yeah, well, first off, thanks for calling it prolific. Some people would call it annoying, but yeah, I I manage a fair number of tweets over at Twitter slash L I B E L underscore Vox, reliable Vox. That's where I talk about digital transformation and APIs and a lot of technology stuff. Occasionally. Fights with blockchain and NFT enthusiastic. But then I also manage, I also manage a newsletter called net API notes, where for almost 200 issues, going back to 2015, I've covered the landscape. I've shared essential bits of information. I've tried to boil down the, the. Current climate and get it right into just the most essential things that decision makers need to know and care about. And then I do a fair amount of blogging on a blog. That's very imaginatively named Matthew reinbold.com. In there, I talk about a fair number of things as well, but in, in, in short my passion is really about coaching people, helping people, teaching people to get better with their API ecosystem. Matt Trask: That's really cool. So one thing that kinda stuck out to me cause it's, so we're going to be talking about the 20, 21 Sidi APR report. However, I'm curious since you've been doing it now since 2015, you've been keeping notes on. The API world. How does your kind of, I hate to say this phrase, the 30,000 foot view of everything that, you know, from 2015, how does that kind of line up to what you saw with the 2021 state of the API report? Matthew Reinbold: Oh, that's interesting. So there's definitely. Maturing as a industry, we've gone through a number of phases. Those of us that have been around the block a few times, see trends come. And most often they, they tend to roll away. And over that time we have to develop models so that we can kind of. Pick the, the, the wheat from the chaff, you know, what, what are the properties of something new, some kind of buzzword, some kind of hyperbole that we can latch onto and say, yes, this is worth investing in. This is worth our interest in our effort versus, yeah, this is some marketing system, some spin as I'm looking at the 20, 21 postman report. I see. Where we've come. It's gone from being single point to point integrations. One-off bespoke API APIs to where we're now talking about things as ecosystems. We're now talking about collections of these things and how entire organizations. Manage these as, as something that's beneficial, something that's collaborative and, and managed as a separate entity rather than, than each individual unit I've got Phil here. So I have to use the forest for the trees analogy rather than just managing the individual API trees. There's now a greater awareness of what the forest, what the forest role is in the company and how to manage that. In a unique way, as opposed to the individual pieces. I will say for those that are listening, like I'm one of the things I want to highlight right up front here is that you don't have to enter an email address. It's not behind the page. We really felt strongly at postman that we had to get this information out to the most number of decision-makers so that they could make better decisions so that they could be informed as they're developing their strategies and roadmaps. So if you go to postman.com/state-of-api, you'll be able to download. With out any worry about having somebody from sales follow up with you later, or getting spam in your inbox, it's free for all. We want this information to be used. We want the dialogues to happen. We want the discourse to be rich and for me and frothy. And so please, you know, don't let past marketing spam. Stop you from checking this out. We want this in the hands of people. Phil Sturgeon: Fantastic. That's good to hear. I mean, that's I haven't got around to reading it as you might have seen from Twitter. Life has been a bit of a mess recently just spending far too much time in the field, as opposed to in the field doing APA stuff. But, yeah, that's definitely always been a concern of mine, of, you know, you hear about these white papers and reports and you just know so many of them like should have just be in the blog post, but instead that like a PDF that and you've got to enter information and then you just get like that fifth email, like, why didn't you reply to my previous four? I was like, I don't know who you are. I just want to read this thing. So yeah, I'm glad you folks are going in a different direction, but Maybe just taking a step back. Like, what is the state of API is report all about where are you getting your information from? What sort of research is being done? And what's the hospital. Matthew Reinbold: Great question. So this is, as far as I know, the largest survey of its kind, we had more than 28,000 people respond to our latest in a series. What we tend to do is try and track where the industry is at. And typically that's been around certain areas. Like how much time do you spend developing API APIs? What kind of tools are you using? Really good stuff there tracking the growth of, of the industry and the maturation of the industry. What I brought to the table this year. Was an interest on finding the behaviors that lead to sustainable, healthy API ecosystems. Like so much of what we talk about when it comes to API ecosystems is still very anecdotal. We tell stories about the Bezos Amazon memo, where we talk about like Twilio or Stripe, but when it comes to decision makers in large organizations, they're still. Trying to pull at what are decent KPIs, what are the behaviors I should be grooming or promoting within my company to make sure that I can keep producing quality API experiences again and again and again. And so what we did with this report that I'm really proud of is dig deep and discover, like, what are the correlating behaviors in organizations that lead to good things happening for companies? Phil Sturgeon: Okay. That's interesting. Cause I think. There's always this question around, like, what's a good API and what's a bad API. Right. And that's just such a nebulous, almost pointless topic so often, because you're just going to end up with opinions about camel case versus kebab case and opinions about rest versus graph UI, and all the nonsense that we love to fight about. And there's going to be someone with a fever at HTTP status code. And none of that actually matters, but you're talking about more of the business level stuff or what, what sort of things have come up as like. Really interesting results from, from your survey about how to build a good API what's what's, what's new and what's interesting. Matthew Reinbold: Right. Well, one of the things I wanted to look at was some of the insights that popped out to me when I was reading accelerate. So accelerate is like from. The previous decade, but it was written by Nicole Forsgren, Jess humble, Jean Kim, they came together and tried to figure out like, what was it about dev ops? That was so powerful. And they wanted to do it in a, in a way that quantified things, not just like, Hey, this is awesome. You should be doing it, but like get to the meat and potatoes of why is this powerful and why should businesses adopt dev ops? And as they went through their research they ended up discovering that there was really four things, four metrics that showed how dev. Made for better organizational performance. And those things were lead time, deployment, frequency, meantime to restore, or how quickly you recover and the change fail percentage. And I thought, huh, that's really interesting. Now that's for dev ops, but if these things are so instrumental in having organizations outperform. Their peers. Can we find the same correlation with API APIs? If we have the same behaviors, can we therefore then draw a line and say, if you have these things, if you have positive aspects of these four attributes, can you then have a more sustainable, more powerful API program? And based on our survey results, the answer is yes. So I can, I can go in and how we, how we drew that correlation. Phil Sturgeon: I'm curious, what sort of metrics are We, looking at? Matthew Reinbold: yeah. So first off we asked people on a 10 point scale. What, how, how well do you think that you've become API first? So out of our 28,000 respondents, they looked at this 10 point scale and they, they put themselves, you know, how they felt approximately 8% of the people that responded said, yes, we are either a nine or a 10 on the scale for API first, we said fine. And then we went through and we said, okay, you know, how long does it take you to make an API? Are we talking hours, days, weeks, so on and so forth. And we also said, okay, you know, not just time to produce, but how frequently you deploy and how many times do you have a deployment failure? Meaning like you put something in production, but it didn't work. Right. So you have to roll back and then like, what was your time to recovery? Like when an outage does occur and let's be. And outage always occurs at some point. Like how, how quickly can you recover from those things? So we got these nice, you know, bell curves and everybody kind of clumped toward the center on these things. And then we said, okay, Now the magic is we go back to that first question, the people that say their API first that have some kind of strong belief that they're doing API first, let's see how they compare to their peers on these metrics. And again, and again, all for these items, API, first people perform better. So, you know, taking one example here. API first people were able to deploy 17% faster than their peers and you know, in a day or less. So if you are API first and granted, there, there might be some subtlety in how a company defines that. But bottom line, if you are API first, you perform better on these metrics than your counterparts. Phil Sturgeon: Interesting. And yeah. Seeing, seeing as you raised it, what is API first? There's, there's a lot of different definitions floating around. Right. And so just for listeners that might not have listened to everything we've ever talked about and read every blog post we've ever read ref ever wrote how do you define it? Matthew Reinbold: Sure. Well, first for people that haven't heard this and haven't listened to every episode, shame on you. Second, I define I defined API first and. Making the API experience or the interface, the primary means for the functionality exchange. So not viewing, like I'm going to create this functionality and then subsequently go and some other team or, or some other project we'll be wrapping this thing in an API. It's thinking of creating an API experience as the primary exchange mechanism with dysfunctional. Not a library, not a module, not a class, the API. So this is slightly different than API design first, which is, I am going to subsequently talk to stakeholders, create a model, whether that's in an open API document or some other means, but I'm going to sketch that out. Test my assumptions, and then subsequently only begin code after. That's API design. First, I do draw a line between those two. They are very copacetic. They, they work together like peanut butter and chocolate, but there, there is a difference. You can, you can do API first without necessarily being API design first. Phil Sturgeon: For sure. Oh, well, we've got you on a roll. You're doing these really well. What is API as a product? Matthew Reinbold: Ooh, API API as a product. So that is creating an API with the. Awareness that it will have a roadmap. It will have ownership beyond just being put into a production environment that it will grow and change and subsequently necessitates the kind of modeling responsibilities and, and awareness that it will be growing and changing over time. Phil Sturgeon: Okay. So instead of, yeah, API first is your product should have an API. And that will be managed by the team who was making this product. And API as a product is a slight variant of API. First, that kind of takes that API out of that generic functionality team and says the API itself is the product. And another team potentially on the same team will be making a product using that Matthew Reinbold: Right. I, I would, I would, I would venture there's a lot of large enterprise environments for which API for. It's about a project that gets the thing into production. And then that thing is left to operate and run on its own. Perhaps there's some monitoring, perhaps some observability, but the actual team that made it is off doing the next thing and the next thing and the next thing there's not the idea that. This is a long lived item that, that produces some kind of business functionality value that is competing in a complex dynamic marketplace like that. That's the API product side of the house. Phil Sturgeon: Hm. Matt Trask: So the, I guess like the, the big question to bring up, I think right now is what did the pandemic do for the API ecosystem? Matthew Reinbold: Well, you know, first of all, I want to just stress that, that this thing that we kind of hand wave is the pandemic was actually like multiple congenital. Crises all at once. Right. You know, I, I want to, for the audience, like we're talking social unrest and political upheaval and supply chain disruption, and the, the pandemic was really a catch all for a tremendous amount of business stress. And what we've seen in the report is the usage of APIs, the number of API APIs the. Amount of focus and care on API. APIs has increased tremendously with that pandemic because business leaders, technology leaders are struggling with this amount of change, this amount of disruption. And so having architectures that are slow to change, difficult to change is just not cutting it in this. Set of multiple crises. So any kind of architectural advantage that allows them to change rapidly change quickly to do different things with how their development investment is deployed. So, you know, for example, taking that one dev team that was altogether in the office and being able to break it down into microservices to allow for greater asynchronous operation, greater flexibility. Those are the architectures that are being sought right now. Matt Trask: Yeah, that makes sense. I mean, it always here in America, I don't know if it feels sing, but you know, like there's. At the core level there. So like the whole, did we go back to the office and be Sandy the office upheaval as well. So it makes sense that there is kind of like a, a struggle on rapping, like getting non-technical CEOs, CTOs, CFOs their heads around the game-changing, this of APIs that doesn't surprise me at all to hear that they're still kind of, I don't want to say struggling, but unsure. Maybe like, Matthew Reinbold: Well, and, and, well, I, I think that's an interesting perspective because it assumes that leaders were in command and control positions of how the labor was divided anyway. And I would actually, I would actually posit that it's the opposite. It was everybody immediately going and running to their home offices and working in a remote work environment. The change in the communication paths changed the architectures that were subsequently produced by those teams. It's Conway's law in effect. And therefore, as we, as we look forward, as we look forward to what's going to happen, I would, I would venture that the organizations that pull people back to centralized locations, for whatever reason, I'm not going to debate whether that's good or bad, but the people that pull the development teams back to. see, like the Terminator two bad guy they'll reform remold because there will be more efficient communication patterns when everybody's face to face. Whereas those organizations that continue to have a distributed workforce will have more distributed architectural patterns because that's how communication is happening. Phil Sturgeon: That's really interesting. I haven't really thought about it before, but I, I, I bet there's been an uptick in kind of API design first, specifically due to this as well. Right? Because my experience working we work was, was pretty awful as far as like API planning goes and as a result, APA architecture and API performance and Matthew Reinbold: You don't say you should blog about that. Fail. Matt Trask: Yeah. Phil Sturgeon: 25. I'm going to do a book about that shit. Matt Trask: Have you tweeted about this yet? Phil? I'm not sure if anyone knows your true Phil Sturgeon: I did a talk. I did a talk recently. But yeah, there was, there was such an element of like, we're real in an open plan office, playing ping pong together and shooting each other with nerves that there was never any effort on API contract being written down in any shape or form because you're all sitting about. And you're just like, what's that end point? Cool mate. Oh, if slash whatever. Oh, is that a, is that property of booty? It's a string called true with QuoteWerks and then you didn't have a need to write it down because you just show it over, over the top of Nerf fire. And I, I do wonder if remote work, well, not necessarily remote work, but quarantine remote work has helped push people more towards it because if you can all be sitting around asking each other, you're going to be typing. The contract over slack. And if you're going to be typing it out over slack, which is inherently ephemeral, then you might as well type it into a Yammel file and commit that in the repo. And then you can have design reviews around the board request or other tools that the offer, that sort of thing. So, yeah, that's, that's just completely a hypothetical and something I'm thinking the second night and check that, but I'm sure it's happening. Matthew Reinbold: I completely agree. And, and let me throw in something that's not in the report, but something that's got me totally geeked out and I'm watching for on my radar, we are going to see the greatest Renaissance of API design documentation that we've ever seen in the next couple of years. Now, granted, you know, as far as Renaissance goes, maybe Renaissance. Documentation are not that great. So, you know, let's put the party hats back in the closet, but what we're seeing with the great resignation right now is all of that knowledge that people acquired in their heads is leaving. It's headed out the door and I've read reports like up to 80% of how to do things with API APIs is in people's heads. Like at we work. If you needed to know how API has worked. You know, you knew Phil was the guy that could get you straightened and Phil Sturgeon: I didn't have a clue. That was the problem. I was trying to find out how to do it. Matthew Reinbold: Okay. So I wasn't, it was somebody, it was somebody on the other end of a, of a Nerf battle away Phil Sturgeon: Someone who quit already is the person that you. Matthew Reinbold: But right now in organizations like you have this phenomenon where a tremendous number of people are leaving organizations and they might've been the sole person who knew where the end points were or knew how that particular tricky function worked. And as organizations are trying to deal with this and recover and still be productive, there's going to be a greater emphasis on having that crap written down, having things documented. Organizations don't have aren't left on their back foot like they are right now. So whether that's heavy handed processes, whether that's just a greater appreciation for documentation among the staff, that's left, whatever that manifests as there's going to be an increasing amount of emphasis on documentation, because people have seen that too much was stuck in people's heads and it's not sustained. Phil Sturgeon: Yeah, that's a really good point. I mean, and not just kind of documentation, but the whole open API as a source of truth earlier on. And I figured it has to be, has to become more noticeably important when Yeah. They've, they've lost the whole team. How the API works and you know what it's like, code's always a bloody mess. Cause you just hacked up within about what over the place and patch things and fix things. And what about and yeah, when they find themselves rewrite in the API, cause no one can really take it over and no one remembers how it works and there's no documentation for it. And it's just too hard to figure out when they just make a brand new one. And they have a whole brand new team doing it. Cause they've already lost all that stuff. Matthew Reinbold: Yeah. Phil Sturgeon: That's a situation that a lot of managers and business people are going to say, how can we go about avoiding doing this? And I just hope there's someone in the room that says, well, APA designed first would really help avoid this problem because otherwise they'll just repeat all the same mistakes again. Matthew Reinbold: Right. Absolutely. Whether it's design first or tools that help analyze existing traffic and write the document afterwards, like whatever you got to do, get that written down and start taking some notes against it because. It's it, I believe right now with the great resignation. It's an Achilles heel. That's probably hampering a lot of organizational ecosystems right now. Matt Trask: Yeah, I would definitely agree. I mean, it shows in the report under open API three dot oh, 44% of people are aware of it, but they don't use it 28% say they use it. 12% said they use it, the love it. So even just combining use it and use it in love. It still does not match aware of we're not using it. Which means that there is definitely a. A river to jump over. So to speak, to getting more people on, to open API, which is probably currently like the standard for API documentation right now which comes back to your point, which allows them to start writing things down and start documenting things. And Phil gets it by bus tomorrow. We work is still going to be okay. It very well could happen. Which is exactly why I use that example. And it, it, yeah, it it'll give the organization a little bit more or a little less reliance on what's in people's heads a little bit more stability in case great races, nation three Datto happens in three years. You know, you don't know what's gonna happen. Phil Sturgeon: Is that when everyone resigns from web three point now, Matt Trask: please. Don't don't threaten me with a good time. Like I've already, I've already muted those web three and NFD on my Twitter and it cleaned it up so Phil Sturgeon: Why do you hate progress, man? Matt Trask: A lot of reasons. I'm a combustion at heart? No. Matthew Reinbold: Hey, if you don't, Phil Sturgeon: particular messages of this progress that are the problem. Matthew Reinbold: if you, don't stand for something, you'll fall for anything. Good for you, Matt. Matt Trask: yes, I've always wanted my life to be attributed to a, a Hamilton quote. So I am glad I did. I can check that one off to get back onto the actual topic and not just bashing NFTs for an hour and a half, which sounds like a lot of fun. What you the most about this report? Like what was something that you read that just you weren't expecting? Matthew Reinbold: I, I think there was two things that when you combine them together it made me tilt my head and go, huh? The, the first is that more than anything else? Including speed to production. People want quality API APIs. They want stability. They want some other things reliability. But the primary thing that people want out of their, their API APIs is quality. And yet when it came to whether or not people had time to test. Everybody acknowledged that testing was good. Tested was valid, but nobody had enough time for testing and it's like, huh? These two things kind of seem like. The, the two sides of a coin, right. You know, people aren't getting the quality that they want, but everybody acknowledges that they don't have enough time to do testing, even though they recognize the testing is an extremely valuable type thing. So I think when it comes to socializing this report and talking to decision-makers and doing the kind of coaching that I so often do, I, this is one of those things too, to bring up, like how in your program are you supporting. Testing and ensuring that enough is being done there so that your developers feel like you're, you're reaching the kind of quality goals that, that you're, you're promising to the rest of the world. Phil Sturgeon: Hm, do you, is the survey broken down by role? So can you, can you look to see if. Managers and engineers have a rule, very interested in, in high quality. And engineers are going, but we don't have enough time, but the manager's like, oh, they definitely have enough time. Matthew Reinbold: Right. So we do have a breakdown by role and job title, but I don't have the numbers in front of me that, that combined, and show me how to break down the quality question. Phil Sturgeon: Yeah, that'd be an interesting one. Cause yeah, so many roles, so many organizations, I just take it as like a universal truth is that companies are just, you know, business and product are demanding feature, feature, feature, feature, feature, and engineers are just like screaming, just keyboards on fire, trying to try to hit them goals. And everything's just wonky as hell. And it seems to be everywhere I go. There's not enough to have. There's not enough time for QA. They might've got rid of the QA team because it's slowed down product and slowed down delivery of features. Yeah, everyone wants high-quality API has, but no one wants to put the time in to testing because testing is inherently hard and slow. Matthew Reinbold: Right. And kind of along those same lines, another stat that jumped out at me was that 76% of the people building API APIs have less than five years experience doing. I mean, you know, as far as restful APIs now, we're, we're more than a decade into that journey. So that stat leaps out at me, like what is it about API development, where we're getting people with zero to five years experience like what's happening. There are the successful API builders, aging out and becoming management. it, are they moving on to web three O and NFTs? Like, like what is, where are our experienced API builders and why are these critical pieces of business infrastructure? In the hands of relatively younger people. That's not to say that they can't be doing a good job, that, that it's impossible to build a great web experience at your first time at bat. But it's also something where I think everybody on this call would probably agree. Experience counts, experience matters. Ha being around the block once or twice, you pick up a feel for what's beneficial, what's maybe a little wonky and you can imbue that into a better design at launch. So, you know, where are the. 10 year, the 12 year, the 15 year veterans. And why are they not the primary source of API infrastructure development? Phil Sturgeon: Yeah. Some that I've seen so much, again, just, I love complaining about we work. Pretty much everyone that was a junior developer, Right. Like the vast majority, what, what you need developers and their role responsible for creating you know, there's like a hundred API APIs and, you know more than a hundred junior developers with just a sprinkling of seniors who were more on the cowboy coder end of things. Not, not to be rude, you know, like startup, you need to be super agile, super fast, not, not a perfectionist. And so, so many of the problems where this is, this person's first rails app, like they know how to accept incoming Jason parameters and they know how to spit something back from the database. And. That's that, and they know how to make a web request. So he talks to . He talks to F talks to G in the thread, and then no, one's got a timer anyway. So everything falls over, like, things like that. The sort of thing you realize, if you've been doing APIs for five years, or for 10 years, you've been doing it for 10 years, you wouldn't do that. You just wouldn't do that. You'd put something in a sidekick job and then implement a web socket or a web hook, or literally anything else. But. That's the sort of thing you do when you consider like HTP failures or server downtime, to be an edge case that is like some weird scenario that probably won't happen. And when you've been doing it for a longer time, you're like you, you change your mindset to this web requests probably won't work. And on the off chance that it. This is what should happen. And you just get really defensive and paranoid and have like 25 different guard statements and, you know, 25 different types of ex exception catching and, and every single circuit breaker and trigger warning that you can possibly put on this thing. And there is, yeah, there is a change in mind. Around around that kind of it doesn't, I'm not being a gatekeeper or at least they're saying you've got to be doing EPS for 10 years until you're good. But when you start out, you you're such, you're more of an optimist. You haven't seen it go wrong in as many ways. You haven't had cascading failures and you haven't had all these terrifying things that happen. So that, that is definitely a concern for me is that I think, yeah. Happy, happy path development. When you go from having one AP. To having 20 or a hundred, the, the the chance of straying off the happy path gets exponentially worse. Right. And, and that's just something, I think a lot of these younger developers on experience with. Matthew Reinbold: Right. Even, even when it comes to design, having used API APIs, having to incorporate the API APIs, you better understand what makes a good description and what is just a reiteration of the, the name itself. Yeah. Yeah. If I have a field called date of birth and the description is just the birth, that, the date that the person was born on, like, well, what was the. do I need to refresh it? Or is it cashed? You know, like, can I store it or is it part of some kind of regulatory PII? And I shouldn't, you know, I can use it, but I shouldn't store, like, there's so many issues that once you've been down that road, and then you're asked to produce an API, you bring that experience with you and you put it into the description that adds so much that yeah. I, I, I, I don't know. How we continue to get that, that experience circulating and get that in front of people. But I think it's really important. Matt Trask: Well, I must wonder too, like how many of those, like experienced API builders are getting swallowed up into Stripe? Twilio, Google. And kind of almost locked away working on their API APIs and not able to share their experiences down the road to junior developers in their own companies or interim networks, things like that too, because it feels like you do your five, seven years as developer, you get pulled into the management game and then all of your knowledge is still there, but you're having to balance both managing a development team, hitting your goals. Pushing out products because you've got to make money for the business. And all of your knowledge that you've worked so hard to gain is kind of sidelined in the name of profits or KPIs or whatever it might be. Matthew Reinbold: Possibly there's, there's certainly exceptions that spring to mind. One of which is Tim Burks and the team over at Google and with the number of resources that they put out there. For their APIs. It's, it's kind of a mouthful, but if you do a Google search for that, they've produced a tremendous amount of documentation about how they support API APIs at scale, how they do their design reviews, how they think about consistency and cohesion across their entire footprint. So that certainly what you described could be the case in some places. You know, I, I, I do think that it's not necessarily the default that's people go off to these big organizations and then just disappear because the folks at Google around Tim and his crew they're doing some great work. Phil Sturgeon: So I've been sat in the room with you having these sort of conversations your last job, Right, Like a center of excellence type stuff. You, you get a bunch of smart people and me together and start talking about what, what would help with these various different problems? Like how do we do APA design reviews? How do we do governance? What standards should we be interested in? So I think sometimes yeah. Experienced developers can get sucked up into these companies and kind of finish and end up having that scale was used for something else. But I, I think companies that have those governance processes, like they're sharing their experience back by creating style guides, by creating programs that they explain how these, how these like API designed life cycles or API life cycle should work. And that's a way that they can essentially. Distribute their experience. So instead of like, I know what to look for when I'm reviewing a poor request, they can create a style guide. That means that everyone will do that. I think the danger there is that when style goes focus on what, instead of why then, then you kind of lose some of that experience because it just seems like arbitrary decisions delivered from upon high. Right. You just get. Do it this way, but, but Y I've read loads of style guides recently. And, and some of them, I should probably show the examples. It's just like, do this. Like, why you don't tell me what to do? You don't my dad, like, it just, I couldn't figure out what they possibly could have meant by it. Cause usually I can look at something. Why might they mean that? Oh, that reminds me of a thing that happened along these lines. They probably got burned by that before, and they want to avoid it, but if you don't see why it just sounds arbitrary and you're not actually teaching anyone on anything, but if you do it right. that that can be really helpful. Matthew Reinbold: Right. And it's also essential that if you're designing these systems like a governance or like a center of excellence that you have the feedback process that you have, the, the communication cycles so that when people do have that kind of. That they have a recourse. It's not a dead end. It's not either you do this or you're punished for it, but oh, if this doesn't make sense, here's who you talk to. Here's how you can escalate your concern here is how you elevate your edge case. And we can have a discussion about it and you can help co-evolve this thing, because you own this as much as somebody else, the, the phenomenon that you described, where it's a dead end. It's thrust upon you. You don't have ownership of that. And as a developer, that does not feel good, that does not invest you in seeing the long-term growth of, of that system. You want to burn that system. You want to be the rebels flying through the death star trench. You want to take that thing down? So what's essential is to realize. You provide the avenues for people to, to voice their concerns, voice their questions, and make them feel heard in such a way that their process, the process is theirs. It's not something done to them. It's it's their process. Phil Sturgeon: I'm just laughing about the death star rebel situation. Now I'm completely distracted. I need to go rewatch some star wars. I don't know. Matt Trask: I mean, your, your thought on the ownership thing is also interesting cause And we like watching the junior Twitter, the junior developer Twitter circles, which is not the end all be all of it all, but there is a large emphasis on if you want to make more money, you need to jump ship every two years on average. And that kind of removes the does or not the desire, but like the, the ownership of any sort of product from a junior developer, because in two years, they're going to be onto another thing. They're going to be onto another system. Codebase, maybe another language and it, it does kind of bring back, like, how do you entice people to have ownership, even if they only are going to plan to say somewhere for a short period? Because we all know that like having, like you said, having that ownership is going to kind of make you more invested, more caring, more thoughtful, more empathetic towards whatever it is that you're building. Matthew Reinbold: Right. I mean, we're veering into management territory, which I'm happy to talk about. I, I know. Matt Trask: very allergic to management. So. Matthew Reinbold: But I, I was just reading Harvard business review. Hey, I'm fun at parties too. So I was reading Harvard business review talking about COVID and the great resignation and the, the management challenges that, that come with that and what we need more. In all companies is a feeling of belonging, a feeling like we have a career progression feeling like our, our, our work has impact and all too often management, just as about making sure people don't do dumpster. Right. You know, I'm, I'm here to police you because the organization doesn't trust you. And it leads to all kinds of weird effects. Like, Hey, if you actually want to grow your career, you need to leave. You need to hop companies every two years and let's be clear that may work, but it's still very disruptive, not just for the company, but for the individual. 'cause they're having to rebuild all of those social structures, their relationships, their patterns, the routines it, it's not, it doesn't come for free. And so from a management standpoint, if you can show people how to have that fulfilling career, how to fulfill those needs. They don't have to jump ship every two years. There's no reason that that has to be the default blueprint. And from a company standpoint, you actually benefit from that accrued experience rather than having a developer. That's done the same thing. Five times you get five years of experience. That's really powerful, really tremendous. And that, that ultimately not only leads to better APIs, but leads to a better employee. So there is a disconnect we need to work with our management layers. It shouldn't just be the technician that has some headcount is by default manager. There needs to be an appreciation for how those are unique skill sets. Those are unique muscles that need to be exercised, but. If we can create that fulfilling sense of duty then, and that the career path for these individuals, we can get them off of this kind of binge and purge career treadmill. Matt Trask: So that's a really, yeah, that's a really good way to put the whole two year turn. And I mean, it comes back full circle to what you just said earlier, which is, you know, 75% of API has been developed now or done by people with less than five years experience. And that's probably because of the same, people are jumping, jumping, jumping. Whereas if you can keep them around, make them happy, make them feel like they belong. We might actually start seeing that number. Dropped significantly to more experienced API developers building more thoughtful API design with, with years of knowledge built up. So I think it'll be really interesting to see kind of what happens with this great resignation how that all shapes up. And then it'll be interesting to see to kind of the 2022 say the API report. How does that. How, how will things change from a year in a year going forward? And what can we expect possibly looking at these two years, the next five years after that, the next 10 years growing on different trends, you know, we might see NFTs ruling the world. We might see graph QL. Rolling. Phil Sturgeon: No comment. Matt Trask: Matthew is kind of shrugging Phil Sturgeon: we're all sad. Now, rural sat now, NFTs powered by graft UL, problem solved. Can you, can you still right click that? No, you can't. It's like a post. So. Matt Trask: Well, there goes Matthew Reinbold: Each unique query is published as an innovator. And you can put the ownership of that query in a blockchain so that you don't have the centralized point of failure. Phil Sturgeon: I was going to thank you for being for, for making this podcast sound intelligent for once. And, Matthew Reinbold: And then I ruined it. Sorry. Phil Sturgeon: and then you. Matt Trask: no, no, no, you didn't ruin it. You just brought it back down to its normal level of ridiculousness. Phil Sturgeon: Fantastic. No. Do you have any predictions for what we're going to see in the, in next year's state of this report? Because then we can play that clip back and laugh at how wrong you were. Matthew Reinbold: Oh, lovely. All right, well, let me have a few minutes to sandbag my answer. No, I think there's a tremendous amount of, of areas where we can take this correlation that I talked about before behaviors. You know how the question immediately becomes well, okay. If these four behaviors are so good and are present in high-performing API companies, how do we get there? And this year we had a little bit around leadership and what leaders do. To get an API first company. I think there is a lot of exploration we can do there to really dial in and say, okay, we know these things are good. How do you get there? How do you promote these things? How do you, how do you get it so that you are able to deploy in a minimal amount of time or recover faster? What are leaders in those organizations doing? That's one of the things I'd love to dig into obviously. A lot of post pandemic aftermath. There's been a tremendous amount of published about how this digital transformation and, you know, we're so much more flexible and adaptable because we, we are now doing all our conversations over zoom. And I look at that and I, I scratch my head because. Digital transformation, at least in the non buzzword compliant way is a whole lot more difficult than just moving everything to a slack conversation or a, or a zoom conversation. Like it means fundamentally dismantling your policies and procedures and reinventing them in a way that digital technology lends itself to. So figuring out what that post pandemic landscape looks like and how we're still feeling the knock on effect. Is going to be something that's also going to be very interesting to explore. Matt Trask: Yeah, that's definitely true. I mean, I think one thing I would like to see is, is that number of people who know open API, but don't use it start to gradually shift down and people who are using open. Start to shift up, which, you know, from a silver right back to having documentation and some sort of notes about their API. So when the, the knowledge people do eventually leave because everyone leaves the company at some point, the knowledge isn't necessarily leaving. And instead we're, we're kind of leaving a better legacy to the people following us. Yeah, definitely. Matthew Reinbold: Here here. Matt Trask: Cool. Matthew, thank you so much for taking some time out of your, your, your day to talk to us. We really appreciate it. Look forward to having you back in roughly a year's time to talk 20, 22. Say the API report Matthew Reinbold: I love it. Let's do it. Pencil it in right now. Matt Trask: Yep. It's it's on my calendar. I don't know what I'll be doing in a year from today, but I know for a fact we'll be talking again. If you want to get. Matthew on Twitter. He is at libel Vox, L I B E L underscore V O X M. And we'll throw the link to your blog and Twitter in the show notes as well as everything else. Awesome. Cool. Thank you so much. We appreciate it. Phil Sturgeon: Yeah. All audio, artwork, episode descriptions and notes are property of APIs You Won't Hate, for APIs You Won't Hate, and published with permission by Transistor, Inc. Broadcast by | 2026-01-13T08:48:41 |
https://youtube.com/t/terms | 서비스 약관 KR 서비스 이용약관 유료 서비스 약관 유료 서비스 사용 규칙 저작권 집중관리단체 공지 저작권 고지 커뮤니티 가이드 서비스 약관 다른 언어로 서비스 약관 보기: English 및 한국어 약관의 구성 본 요약은 서비스 약관('약관')을 살펴보는 데 도움을 주기 위해 만들어졌습니다. 이 정보가 유용한 가이드가 되기를 바라며, 약관 전문도 반드시 확인하시기 바랍니다. YouTube에 오신 것을 환영합니다. 이 섹션에서는 YouTube와 사용자의 관계를 설명합니다. 여기에는 서비스에 대한 설명이 포함되며, 계약을 정의하고, 서비스 제공자를 밝힙니다. 서비스 이용 대상 이 섹션에서는 서비스 이용에 대한 특정 요구사항을 설명하고, 사용자 분류를 정의합니다. 서비스의 이용 이 섹션에서는 서비스를 이용할 수 있는 권한과 서비스 이용에 적용되는 조건을 설명합니다. 또한, 서비스가 변경될 수 있음에 대해서도 설명합니다. 귀하의 콘텐츠 및 운영 이 섹션은 서비스에 콘텐츠를 제공하는 사용자에게 적용됩니다. 콘텐츠를 업로드함에 따라 허여하는 권한의 범위를 정의하고, 타인의 권리를 침해하는 콘텐츠를 업로드하지 않겠다는 사용자 동의가 포함됩니다. 계정 정지 및 해지 이 섹션에서는 사용자와 YouTube가 관계를 종료할 수 있는 방법을 설명합니다. 서비스에 포함된 소프트웨어에 대하여 이 섹션에서는 서비스의 소프트웨어에 대한 세부정보를 확인할 수 있습니다. 기타 법적 조항 이 섹션에서는 당사자들의 법적 의무에 대해 설명합니다. YouTube가 책임지지 않는 사항에 대한 설명도 확인할 수 있습니다. 본 계약에 대하여 이 섹션에서는 약관의 변경이나 준거법 등 계약과 관련된 중요한 세부정보를 확인할 수 있습니다. 서비스 약관 날짜: 2022년 1월 5일 서비스 약관 YouTube에 오신 것을 환영합니다. 소개 YouTube 플랫폼과 플랫폼에서 제공되는 제품, 서비스, 기능(이하 통칭하여 ' 서비스 ')을 사용해 주셔서 감사합니다. YouTube 서비스 YouTube 서비스는 사용자가 동영상 및 기타 콘텐츠를 찾아보고, 감상하고, 공유하며, 전 세계 사람들과 소통하고, 정보를 나누며, 아이디어를 주고 받을 수 있는 공간을 제공함은 물론, 규모에 관계없이 모든 독창적인 콘텐츠 크리에이터와 광고주에게 배포 플랫폼의 역할을 합니다. YouTube 고객센터 에서 다양한 제품 정보와 사용 방법을 참고할 수 있습니다. 특히 YouTube Kids , YouTube 파트너 프로그램 , YouTube 유료 멤버십 및 구매 관련 정보가 제공됩니다. TV, 게임 콘솔 또는 Google Home 등의 다른 기기 에서 콘텐츠를 즐기는 방법도 확인할 수 있습니다. 서비스 제공자 서비스를 제공하는 법인은 델라웨어 법률에 따라 운영되며, 1600 Amphitheatre Parkway, Mountain View, CA 94043에 소재한 Google LLC입니다(이하 ' YouTube ' 또는 ' 당사 '). 본 약관에서 YouTube의 ' 계열사 '는 Alphabet Inc. 기업 그룹에 (현재 또는 추후) 소속된 다른 회사를 지칭합니다. 적용 약관 귀하는 서비스 사용 시에 수시로 업데이트될 수 있는 본 약관, YouTube 커뮤니티 가이드 , 정책, 안전 및 저작권 정책 (' 계약 '으로 총칭)을 준수해야 합니다. 본 서비스에 광고 또는 스폰서십을 제공하거나, 콘텐츠에 유료 프로모션을 포함하는 경우 YouTube 광고 정책 도 당사와의 계약에 포함됩니다. 본 약관에 제공된 기타 링크 또는 참조는 정보 참고 목적으로만 제공되며, 계약의 일부가 아닙니다. 본 계약을 주의해서 읽고 숙지하시기 바랍니다. 본 계약에 이해할 수 없거나, 동의하지 않는 내용이 있다면 서비스를 사용하지 마시기 바랍니다. 서비스 이용 대상 연령 요건 서비스를 사용하려면 만 14세 이상이어야 합니다. 하지만 부모나 법정대리인이 사용 설정하면 모든 연령대의 아동이 서비스 또는 YouTube Kids를 사용할 수 있습니다(제공 국가에만 해당). 부모 또는 법정대리인 의 허락 귀하가 거주 국가에서 법률상 미성년자에 해당하는 경우, 귀하는 서비스를 사용할 수 있도록 부모 또는 법정대리인의 허락을 받았음을 진술합니다. 부모 또는 법정대리인과 함께 본 계약을 숙지하시기 바랍니다. 거주 국가에서 법률상 미성년자로 간주되는 사용자의 부모 또는 법정대리인이 사용자의 서비스 사용을 허락한 경우, 부모 또는 법정대리인은 본 계약 조건의 적용을 받게되며, 미성년 사용자의 서비스 이용 활동에 대한 책임을 집니다. 가족의 YouTube 사용을 관리하는 데 도움이 되는 도구와 자료(만 14세 미만의 아동에게 서비스 및 YouTube Kids를 사용 설정하는 방법 포함)가 YouTube 고객센터 와 Google의 Family Link 에서 제공됩니다. 사업자 회사 또는 기관을 위해 서비스를 사용하는 경우, 귀하는 해당 단체를 대신하여 행위할 권한이 귀하에게 있고, 해당 단체가 본 계약에 동의함을 진술합니다. 서비스의 이용 서비스 내 콘텐츠 서비스 내 콘텐츠에는 귀하, YouTube 또는 제3자가 제공하는 동영상, 오디오(예를 들어, 음악 및 기타 음향), 그래픽, 사진, 텍스트(댓글 및 스크립트), 브랜딩(상표 이름, 상표권, 서비스 표시 또는 로고 등), 인터랙티브 기능, 소프트웨어, 측정항목, 기타 자료가 포함됩니다. (이하 통칭하여 ‘ 콘텐츠 ’) 법률에 따라 YouTube가 책임을 지는 경우를 제외하고, 콘텐츠에 대한 책임은 서비스에 콘텐츠를 제공하는 사용자 또는 단체에게 있습니다. YouTube는 콘텐츠를 호스팅하거나 제공할 의무가 없습니다. 커뮤니티 가이드 또는 법률을 위반하는 등 본 약관을 준수하지 않는 콘텐츠를 발견하면 YouTube에 신고 할 수 있습니다. Google 계정 및 YouTube 채널 Google 계정 없이도 콘텐츠 탐색 및 검색 등 일부 서비스를 사용할 수 있습니다. 하지만 Google 계정이 있어야 사용 가능한 기능도 있습니다. Google 계정이 있으면 동영상에 좋아요 표시, 채널 구독, YouTube 채널 만들기 등이 가능합니다. Google 계정 만들기 안내를 따르세요. YouTube 채널을 만들면 동영상 업로드, 댓글 작성, 재생목록 만들기 등의 추가 기능을 이용할 수 있습니다. YouTube 채널을 만드는 방법 에 대한 자세한 내용을 참조하세요. Google 계정을 보호하려면 비밀번호를 공개하지 말아야 합니다. 타사 애플리케이션에서 Google 계정 비밀번호를 재사용하면 안 됩니다. 비밀번호 또는 Google 계정의 무단 사용 사실을 알게 된 경우의 조치 등 Google 계정 보안 유지 에 대해 자세히 알아보세요. 귀하의 정보 당사의 개인정보처리방침 은 서비스를 사용할 때 개인정보가 어떻게 처리되고 보호되는지 설명합니다. YouTube Kids 개인정보처리방침 은 YouTube Kids에만 해당하는 개인정보 보호관행에 대한 추가 정보를 제공합니다. 개인적 용도 또는 가족 활동 과정에서 업로드한 오디오 또는 시청각 콘텐츠인 경우를 제외하고, 귀하가 서비스에 업로드한 오디오 또는 시청각 콘텐츠는 YouTube 정보처리규정 에 따라 처리됩니다. 자세히 알아보기 권한 및 제한사항 귀하는 본 계약 및 관련 법령을 준수하는 한 귀하에게 제공된 서비스에 액세스하여 이를 사용할 수 있습니다. 귀하는 개인적, 비영리적 용도로 콘텐츠를 보고 들을 수 있습니다. 귀하는 내장가능한 YouTube 플레이어를 통해 YouTube 동영상을 표시할 수도 있습니다. 서비스 사용 시 다음 제한사항이 적용됩니다. (a) 서비스의 명시적 승인, 또는 (b) YouTube 및 해당하는 경우 각 권리 소유자의 사전 서면 승인을 받은 경우를 제외하고는, 서비스나 콘텐츠의 어떤 부분에 대해서도 액세스, 복제, 다운로드, 배포, 전송, 방송, 표시, 판매, 라이선스 부여, 변경, 수정 또는 그 밖의 사용을 금지합니다. (a) 콘텐츠의 복사 또는 기타 사용을 방지 또는 제한하거나, (b) 서비스 또는 콘텐츠의 사용을 제한하는 기능 또는 보안 관련 기능을 포함하여 서비스의 어떤 부분에 대해서도 우회, 무력화, 기망적인 관여 또는 그 밖의 방해 행위(또는 이러한 행위들에 대한 시도)를 금지합니다. (a) YouTube의 robots.txt 파일에 따른 공개 검색엔진의 경우, 또는 (b) YouTube의 사전 서면 승인을 받은 경우를 제외하고, 자동화된 수단(로봇, 봇넷 또는 스크래퍼 등)을 사용해 서비스에 액세스하면 안 됩니다. 당사자의 허가를 받거나, 위의 3항에서 허용하지 않는 한, 개인 식별이 가능한 정보(예: 사용자 이름이나 얼굴 모습)를 수집해서는 안 됩니다. 서비스를 사용해 원치 않는 홍보성/상업성 콘텐츠나 그 밖의 원치 않는 대량의 구매 권유 자료를 배포하면 안 됩니다. 동영상 조회수, 좋아요 또는 싫어요 수를 늘리거나, 채널 구독자 수를 늘리기 위해 사람들에게 비용을 지불하거나, 인센티브를 제공하는 등 서비스에 대한 실제 사용자 참여도의 부정확한 측정을 야기 또는 조장하거나, 달리 어떠한 방법으로든 측정항목을 조작하면 안 됩니다. 근거가 없거나, 권한을 남용하거나 또는 사소한 제출 등으로 보고, 신고, 불만 제기, 이의 제기 또는 항소 절차를 남용하면 안 됩니다. 본 서비스에서 또는 본 서비스를 통해 YouTube 컨테스트 정책 및 가이드라인 을 준수하지 않는 컨테스트를 시행하면 안 됩니다. 개인적, 비영리적 용도 외의 목적으로 콘텐츠를 보거나 듣기 위해 서비스를 사용하면 안 됩니다(예를 들어, 공개적으로 서비스의 동영상을 상영하거나, 음악을 스트리밍하면 안 됩니다). (a) YouTube 광 고 정책 에서 허용하는 경우(정책을 준수하는 간접 광고 등)를 제외하고, 서비스나 콘텐츠에 또는 그 주변이나 내부에 배치된 광고, 후원, 홍보물을 판매하거나, (b) 오로지 서비스의 콘텐츠만 포함되거나, 광고, 후원, 홍보물 판매의 주된 이유가 서비스의 콘텐츠인 웹사이트 페이지나 애플리케이션에서 광고, 후원, 홍보물을 판매(예를 들어, 사용자들이 방문하는 주요 목적이 YouTube 동영상인 웹페이지의 광고 판매)하기 위하여 서비스를 사용하면 안 됩니다. 유보 서비스를 사용한다고 해서 본 서비스의 어떠한 요소(예를 들어, 사용자 이름이나 다른 사용자 또는 YouTube가 게시한 다른 콘텐츠 등)에 대해서 소유권이나 권리가 부여되는 것은 아닙니다. 서비스 개발, 개선 업데이트 YouTube는 지속적으로 본 서비스를 변경 및 개선하고 있습니다. 지속적인 발전의 일환으로 기능이나 구성을 추가하거나 삭제하고, 새로운 디지털 콘텐츠 또는 서비스를 제공하거나 기존 서비스의 제공을 중단하는 등 본 서비스 전체 또는 일부를 개선하거나 변경할 수 있습니다. 당사는 성능이나 보안을 개선하거나, 법령을 준수하기 위한 변경을 하거나, YouTube 시스템 상의 불법적인 활동이나 시스템을 악용하는 행위를 방지하기 위해 본 서비스나 그 일부를 변경 또는 중단할 수 있습니다. 이러한 변경사항은 사용자 전체, 일부 또는 특정 개인에게 영향을 미칠 수 있습니다. 본 서비스에 다운로드 가능한 소프트웨어(YouTube 스튜디오 애플리케이션 등)가 필요하거나 포함되는 경우, 소프트웨어에 대한 새로운 버전이나 기능이 제공되면 기기 설정에 따라 소프트웨어가 기기에서 자동으로 업데이트될 수 있습니다. 귀하가 본 서비스를 이용하는 데 부정적인 영향을 미치는 중대한 변경사항이 있을 경우, YouTube는 귀하에게 합당한 사전 통지를 전달합니다. 다만, 합리적으로 통지가 불가능한 경우(예: 사용자가 로그인 없이 본 서비스를 이용하는 경우)이거나 긴급한 상황(예: 악용사례를 방지하거나, 법적 요건에 대응하거나, 보안 및 운용가능성 관련 문제를 해결)에서는 예외로 합니다. 또한 YouTube는 Google 테이크아웃 을 사용해 Google 계정에서 귀하의 콘텐츠를 내보낼 기회를 제공하며, 여기에는 관련 법규 및 정책이 적용됩니다.. 귀하의 콘텐츠 및 운영 콘텐츠 업로드 YouTube 채널을 보유한 경우 귀하는 서비스에 콘텐츠를 업로드할 수 있습니다. 자신의 콘텐츠를 사용해 비즈니스 또는 문화예술 사업을 홍보할 수 있습니다. 콘텐츠를 업로드하기로 했다면, 본 계약 또는 법령을 준수하지 않는 콘텐츠를 서비스에 제출하면 안 됩니다. 예를 들어, 당사자 허가를 받았거나, 법적으로 허용되는 경우가 아니라면 제출한 콘텐츠에 제3자의 지적 재산(예를 들어, 저작권으로 보호되는 자료)이 포함되어서는 안 됩니다. 귀하가 서비스에 제출한 콘텐츠에 대한 법적 책임은 귀하에게 있습니다. 당사는 스팸, 멀웨어, 불법 콘텐츠 등과 같은 침해 및 악용 사례를 감지하기 위해 자동화된 시스템으로 귀하의 콘텐츠를 분석할 수 있습니다. 귀하가 부여하는 권리 귀하의 콘텐츠에 대한 소유권은 귀하에게 있습니다. 하지만 아래에 설명된 바와 같이 귀하는 YouTube 및 서비스의 다른 사용자에게 일정한 권리를 부여해야 합니다. YouTube에 부여하는 라이선스 귀하는 본 서비스에 콘텐츠를 제공함으로써 콘텐츠를 사용(복제, 배포, 수정, 표시, 공연 등)할 수 있는 세계적이고, 비독점적이며, 무상으로 제공되고, 양도가능하며, 서브라이선스를 허여할 수 있는 라이선스를 YouTube에 부여합니다. YouTube는 본 서비스를 운영하고, 홍보 및 개선하기 위한 목적으로만 이러한 라이선스를 사용할 수 있습니다. 본 약관의 어떠한 조항도 법령에서 허용되는 범위를 넘어서는 라이선스를 YouTube에 부여하는 것은 아닙니다. 다른 사용자에게 부여하는 라이선스 또한 귀하는 서비스의 다른 사용자들에게 서비스를 통해 귀하의 콘텐츠에 액세스할 수 있는 세계적이고, 비독점적이며, 무상으로 제공되는 라이선스를 부여하며, 본 서비스에서 제공하는 기능(예를 들어, 비디오 플레이백이나 퍼가기)을 통해 설정된 바에 따라 해당 콘텐츠를 사용할 권리, 즉, 복제, 배포, 수정, 표시, 공연 등을 할 수 있는 권리를 부여합니다. 보다 명확히 설명하자면, 이 라이선스는 다른 사용자가 본 서비스와는 별개로 귀하의 콘텐츠를 활용할 수 있는 어떠한 권리나 권한도 부여하지 않습니다. 라이선스 기간 귀하가 부여한 라이선스는 해당 콘텐츠가 아래에서 설명하는 바에 따라 삭제될 때까지 유지됩니다. 콘텐츠가 삭제되면 라이선스가 종료되지만, 서비스 운영, 삭제 전에 허용한 콘텐츠의 사용, 또는 법령에서 달리 요구하는 경우에는 예외가 인정될 수 있습니다. 예를 들어, 귀하가 콘텐츠를 삭제하더라도 YouTube는 (a) 귀하의 콘텐츠가 포함된 홍보자료를 회수하거나, (b) 서비스의 제한적인 오프라인 시청 기능(예를 들어, 유료가입 서비스에서 이용할 수 있는 기능)에 따라 다른 이용자가 이용하는 콘텐츠를 회수해야 하는 의무가 있는 것은 아니며, (c) YouTube가 법적 필요에 의해 보관할 합리적인 이유가 있는 사본을 삭제해야 하는 것은 아닙니다. 수익 창출 권리 귀하는 서비스에 있는 귀하의 콘텐츠에서 수익을 창출할 권리를 YouTube에 부여합니다. 수익 창출에는 콘텐츠에 광고를 게재하거나 사용자에게 이용료를 청구하는 것도 포함될 수 있습니다. 이 계약으로 귀하에게 수익금을 지급받을 자격이 주어지지는 않습니다. 2021년 6월 1일부터 YouTube와 맺은 기타 계약을 통해 YouTube로부터 지급받을 자격이 있는 수익금(YouTube 파트너 프로그램, 채널 멤버십 또는 Super Chat 수익금 포함)은 모두 로열티로 취급됩니다. 법에서 요구되는 경우 Google이 지급액에서 세금을 원천징수합니다. 귀하의 콘텐츠 삭제 귀하는 언제든지 서비스에서 자신의 콘텐츠를 삭제 할 수 있습니다. 콘텐츠를 삭제하기 전에 콘텐츠 사본 을 만들 수도 있습니다. 만약 귀하가 본 약관에서 요구하는 권한을 더 이상 보유하지 않는 경우 콘텐츠를 삭제해야 합니다. YouTube에 의한 콘텐츠 삭제 귀하의 콘텐츠가 (1) 본 계약을 위반하거나, (2) YouTube, 사용자 또는 제3자에게 위해를 야기한다고 합리적으로 판단되는 경우, 당사는 그러한 콘텐츠를 삭제하거나 차단할 권리를 보유합니다.. YouTube는 통지가 (a) 법적 이유로 금지되거나, (b) 사용자, 기타 제3자, YouTube 또는 그 계열사에게 위해를 야기할 수 있다고 합리적으로 판단되는 경우(예를 들어, 통지하는 것이 법령 또는 규제당국의 명령을 위반하는 경우, 조사를 방해하는 경우, 본 서비스의 보안을 해하는 경우 등)를 제외하고, 귀하에게 해당 조치의 이유를 지체 없이 통지합니다. 항소 방법을 포함한 신고 및 집행에 대한 자세한 내용은 고객센터의 문제해결 페이지에서 확인할 수 있습니다. 커뮤니티 가이드 위반 경고 YouTube는 YouTube 커뮤니티 가이드 를 위반하는 콘텐츠를 대상으로 한 '경고' 시스템을 운영하고 있습니다. 최초 위반인 경우 YouTube는 일반적으로 주의만 주고, 그 이후의 위반의 경우 귀하의 채널에 대해 경고가 적용됩니다. 경고마다 다양한 제한사항이 수반되며 채널이 YouTube에서 영구적으로 삭제될 수도 있습니다. 경고가 채널에 미치는 영향에 대한 자세한 설명은 커뮤니티 가이드 위반 경고 기본사항 페이지 에서 확인할 수 있습니다. 경고가 잘못 주어졌다고 생각되는 경우 여기 에서 항소할 수 있습니다. 경고로 인해 채널에 제한이 적용된 경우 다른 채널을 사용해 제한을 회피하면 안 됩니다. 이 금지 조항을 위반하는 것은 본 계약을 중대하게 위반하는 행위로서 Google은 Google 계정을 해지하거나 본 서비스 전체 또는 일부의 액세스 권한을 해지할 권리를 보유합니다. 저작권 보호 YouTube는 저작권자가 온라인상에서 자신의 지적 재산을 관리하는 데 도움이 되는 정보를 YouTube 저작권 센터 에서 제공하고 있습니다. 본 서비스에서 귀하의 저작권이 침해되었다고 생각하는 경우 YouTube에 신고 해 주시기 바랍니다. YouTube는 YouTube 저작권 센터 의 절차에 따라 저작권 침해 신고에 대응합니다. YouTube 저작권 센터에서는 저작권 위반 경고 해결 방법에 대한 정보도 제공하고 있습니다. 반복적으로 저작권을 침해하는 사용자는 YouTube 정책에 따라 일정한 경우 서비스 액세스가 해지될 수 있습니다. 계정 정지 및 해지 귀하에 의한 해지 귀하는 언제든지 서비스 사용을 중지할 수 있습니다. 안내 에 따라 자신의 Google 계정에서 본 서비스를 삭제하면 됩니다. 삭제 시 귀하의 YouTube 채널이 폐쇄되고, 데이터가 삭제됩니다. 사용을 중지하기 전에 귀하의 데이터 사본을 다운로드할 수도 있습니다. YouTube에 의한 해지 및 정지 YouTube는 (a) 귀하가 본 계약을 중대하게 또는 반복적으로 위반하거나, (b) 법적 요건이나 법원 명령 등의 준수를 위한 경우, 또는 (c) 사용자, 기타 제3자, YouTube 또는 그 계열사에 책임이나 위해를 야기하는 행위가 있다고 합리적으로 판단되는 경우, 귀하의 Google 계정을 정지 또는 해지하거나 본 서비스 전체 또는 일부에 대한 귀하의 액세스를 해지할 권리를 보유합니다. 해지 또는 정지 에 대한 통지 YouTube는 통지가 (a) 법적 이유로 금지되거나, (b) 사용자, 다른 제3자, YouTube 또는 그 계열사에게 위해를 야기할 수 있다고 합리적으로 판단되는 경우(예를 들어, 통지하는 것이 법령 또는 규제당국의 명령을 위반하는 경우, 조사를 방해하는 경우, 본 서비스의 보안을 해하는 경우 등)를 제외하고, 귀하에게 YouTube에 의한 해지 또는 정지의 이유를 지체 없이 통지합니다. 서비스 변경으로 인해 YouTube가 귀하의 액세스를 해지하는 경우, 합리적으로 가능하다면 서비스에서 귀하의 콘텐츠를 가져올 충분한 시간을 귀하에게 제공합니다. 계정 정지 또는 해지의 효과 귀하의 Google 계정이 해지되거나 본 서비스에 대한 액세스가 제한되어도 서비스의 일부(예를 들어, 단순한 시청)는 계정 없이 계속 사용할 수 있으며, 본 계약은 그러한 사용에 대해서 계속 적용됩니다. Google 계정이 잘못 해지 또는 정지되었다고판단되는 경우 이 양식을 사용하여 항소 할 수 있습니다. 서비스에 포함된 소프트웨어에 대하여 다운로드 가능한 소프트웨어 서비스에 다운로드 가능한 소프트웨어(YouTube 스튜디오 애플리케이션 등)가 필요하거나 포함되는 경우, 라이선스를 제공하는 추가 약관의 적용을 받는 소프트웨어가 아니라면, YouTube는 귀하에게 서비스의 일부로 제공한 소프트웨어를 사용할 수 있는 개인적이고, 세계적이며, 무상으로 제공되고, 양도 불가능하며, 비독점적인 라이선스를 제공합니다. 이 라이선스는 귀하가 본 계약에서 허용하는 방법에 따라 YouTube가 제공하는 바대로 본 서비스를 사용하고 혜택을 누릴 수 있도록 하기 위한 목적으로만 제공됩니다. 귀하는 이 소프트웨어의 어느 부분도 복사, 수정, 배포, 판매 또는 대여할 수 없으며, 소프트웨어를 역설계하거나, 소스 코드의 추출을 시도할 수 없습니다. 다만, 법률상 이와 같은 제한이 금지되거나, YouTube의 서면 승인을 받은 경우는 제외합니다. 오픈소스 본 서비스에서 사용되는 일부 소프트웨어는 당사가 귀하에게 부여하는 오픈소스 라이선스 하에서 제공될 수 있습니다. 오픈소스 라이선스에는 명시적으로 본 약관의 일부 규정에 우선하는 규정이 있을 수 있으므로, 그러한 라이선스 내용을 숙지하시기 바랍니다. 기타 법적 조항 보증 의 부인 본 계약에 명시되거나, 법률에서 요구되지 않는 한, 본 서비스는 '있는 그대로' 제공되며 YouTube는 서비스와 관련한 어떤 구체적인 약정이나 보증도 하지 않습니다. 예를 들어, 법률상 허용되는 한도 내에서, 당사는 (a) 서비스를 통해 제공되는 콘텐츠, (b) 서비스의 특정 기능이나 서비스의 정확성, 안정성, 가용성 또는 귀하의 필요를 충족할 능력, 또는 (c) 귀하가 제출하는 어떤 콘텐츠든 서비스에서 액세스할 수 있음을 보증하지 않습니다. 모바일로 YouTube 광고를 시청하는 경우 데이터 요금이 발생할 수 있습니다. 책임의 제한 법률에서 요구되는 경우를 제외하고, YouTube, 그 계열사, 임원, 이사, 직원 및 대리인은 다음 사항을 원인으로 발생한 이익·수입·사업 기회·영업권·예상된 절감 효과의 상실, 데이터의 손실 또는 손상, 간접적 또는 결과적 손실, 징벌적 손해에 대해 책임을 지지 않습니다. 서비스의 오류, 실수 또는 부정확한 내용 귀하의 서비스 사용으로 인한 개인의 상해나 재산 피해 서비스의 무단 액세스 또는 사용 서비스의 중단 또는 중지 제3자에 의해 서비스에 또는 서비스를 통해 전송된 바이러스 또는 악성 코드 귀하의 콘텐츠 사용을 포함해 사용자 또는 YouTube가 제출한 콘텐츠, 및/또는 콘텐츠의 삭제 또는 이용 불가 본 조항은 청구의 근거가 보증, 계약, 불법 행위 또는 기타 법리 등 무엇이든 상관없이 모든 청구에 적용됩니다. 관련 법률이 허용하는 한도 내에서, 본 서비스와 관련된 또는 그로 인한 청구에 대한 YouTube 및 그 계열사의 총 배상 책임은 (a) 귀하가 청구에 관하여 YouTube에 서면 통지하기 전 12개월 동안 YouTube가 귀하의 서비스 사용과 관련해 귀하에게 지급한 수익 금액과, (b) 미달러 $500 중 높은 금액으로 제한됩니다. 면책 관련 법률이 허용하는 한도 내에서, 귀하는 (a) 귀하의 서비스 사용 및 액세스, (b) 귀하의 본 약관 조항 위반, (c) 귀하의 제3자의 저작권, 재산권 또는 프라이버시권 등 권리침해, 또는 (d) 귀하의 콘텐츠로 손해를 입었다는 제3자의 주장으로 발생하는 모든 청구, 손해, 의무, 손실, 책임, 비용 또는 채무, 지출(변호사 비용 등)로부터 YouTube, 그 계열사, 임원, 이사, 직원 및 대리인을 보호하고, 이들의 책임을 면제하며, 이로 인하여 손해를 입지 않도록 하는 데 동의합니다. 이러한 방어 및 면책 의무는 본 계약과 귀하의 본 서비스 사용이 종료된 후에도 유효하게 존속합니다. 제3자 링크 서비스에는 YouTube가 소유하거나 관리하지 않는 제3자 웹사이트 및 온라인 서비스의 링크가 포함될 수 있습니다. YouTube는 해당 웹사이트 및 온라인 서비스에 관여할 수 없으며, 관련 법률이 허용하는 한도 내에서, 이에 대한 책임을 지지 않습니다. 본 서비스에서 떠나는 경우 귀하가 방문하는 각 제3자 웹사이트 및 온라인 서비스의 약관과 개인정보처리방침을 검토하시기 바랍니다. 본 계약에 대하여 본 계약 ' 의 변경 당사는 (1) 서비스 수정 사항을 반영하거나, 사업 방식의 변화를 반영하거나(예: 새 제품 또는 기능을 추가하거나 기존의 것들을 삭제하는 경우) (2) 법령, 규제 또는 보안상 등의 이유가 있거나 (3) 악용 또는 위해를 방지하기 위해 본 계약을 변경할 수 있습니다. 본 계약에 중대한 변경사항이 있을 경우, YouTube는 최소 30일 전에 사전 통지와 변경사항 검토 기회를 제공하지만, (1) 사용자에게 유리한 신규 제품 또는 기능을 출시하는 경우 또는 (2) 발생 중인 악용사례를 방지하거나 법적 요건에 대응해야 하는 등 긴급한 상황인 경우는 예외입니다. 새로운 약관에 동의하지 않으면 업로드한 콘텐츠를 삭제하고 본 서비스 이용을 중지해야 합니다. 본 계약의 지속 귀하의 서비스 사용이 종료되어도 본 계약의 '기타 법적 조항', '본 계약에 대하여' 부분은 계속 귀하에게 적용되며, 귀하가 부여한 라이선스는 '라이선스 기간'에서 설명된 바에 따라 지속됩니다. 분리 어떤 이유로든 본 계약의 특정 조항이 집행 불가능한 것으로 판명되는 경우, 이는 다른 조항에 영향을 미치지 않습니다.. 권리 포기 귀하가 본 계약을 준수하지 않았을 때 당사가 즉시 조치를 취하지 않더라도, 이는 당사가 보유하는 권리(향후 조치를 취할 권리 등)를 포기하는 것을 의미하지 않습니다. 해석 본 약관에 사용된 ' 포함 ' 또는 ‘ 등 '이란 표현은 '포함하되 한정되지 않음'이란 의미이며, 당사가 제시한 예시는 설명을 위한 목적으로 사용된 것입니다. 준거법 일부 국가의 법원에서는 분정 유형에 따라 미국 캘리포니아주 법률을 적용하지 않을 수 있습니다. 귀하가 이러한 국가에 거주하고, 미국 캘리포니아주 법률의 적용이 배제되는 경우, 거주 국가의 법률이 본 약관과 관련된 분쟁에 적용됩니다. 그렇지 않은 경우, 귀하는 본 약관 또는 서비스와 관련되거나, 이로부터 야기된 일체의 분쟁에 대해 미국 캘리포니아주 법률이 적용되며, 캘리포니아주 국제사법의 적용은 배제된다는 것에 동의합니다. 마찬가지로, 거주 국가의 법원이 귀하가 미국 캘리포니아주 산타클라라 카운티 법원의 관할에 합의하는 것을 허용하지 않는 경우, 본 약관과 관련된 분쟁에 관하여 귀하의 거주지 재판관할이나 법정지가 적용됩니다. 그렇지 않은 경우, 본 약관 또는 서비스와 관련되거나, 이로부터 야기된 모든 청구는 미국 캘리포니아주 산타클라라 카운티의 연방 또는 주 법원이 전속관할을 가지며, 귀하와 YouTube는 해당 법원이 인적 관할을 갖는 것에 동의합니다. 발효일: 2022년 1월 5일( 이전 버전 보기 ) | 2026-01-13T08:48:41 |
https://survivejs.com/open-source/ | SurviveJS - Open source Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Open source I have been working with open source since 2004 as I started contributing to Blender ↗ . Later on I was a part of the group that established the core team of webpack ↗ . Besides working on well-known projects, I have developed numerous small projects of my own. Given there are too many to mention, I have highlighted several I consider interesting on this page. You can find more behind my GitHub profile ↗ . Frameworks Gustwind (2021) ↗ As I realized the approach of Antwar is too constraining and I wanted to learn Deno ↗ , I decided to start working on Tailspin ↗ . The initial idea was to combine the ideas of a static site generator with a design system tool but the initial attempt was a technical dead end. In Gustwind, I started from a JSON definition for components due to its simplicity. Later on I understood it’s not fun to author and ended up developing a HTML dialect called HTMLisp ↗ . This site has been rewritten using the approach and likely there are still many fun features to add (interactive editing on web etc.). See the project website ↗ Antwar (2015) ↗ Antwar was my first serious static site generator. I developed it around React and webpack to develop this website and other smaller projects. The unique feature at the time had to do with interactive components which could include small pieces of React code to avoid the problem of having to hydrate the whole webpage. Later on this idea has been formalized as the idea of islands architecture. See the project website ↗ Reactabular (2014) ↗ Reactabular was perhaps the first headless table component built for React. It was built during the time when headless didn’t exist at a time. Although the project started from my personal interest, its development was later funded by Kenandy ↗ . If funding appeared, I would be happy to modernize the library. See the project website ↗ Libraries Sidewind (2019) ↗ After getting exposed to Tailwind ↗ , I started thinking it would be a good idea to do the same but for state. Sidewind was born out of this experiment and it includes a small (~5k) runtime for managing state. As a unique feature, it implements the basic idea of resumability. In other words, it is able to construct its state from the initial HTML markup. It is possible I’ll rewrite the project as a compiler one day. See the project website ↗ webpack-merge (2015) ↗ As I was writing my webpack book , I realized it is difficult to explain how to construct webpack configurations in a simple way. To allow composition, I wrote webpack-merge. I consider the project feature complete and I am thankful to Google for supporting my efforts with a one-time $3000 grant from their infrastructure fund. See the project website ↗ Colorjoe (2012) ↗ The development of colorjoe color picker was motivated by a need to find a light picker that doesn’t rely on static images. The solution was to use CSS to generate gradients and let the browser compose them. Although the project is old, it is still somehow relevant even today. See the project website ↗ Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://aws.amazon.com/blogs/developer/tag/windows-phone/ | Windows Phone | AWS Developer Tools Blog Skip to Main Content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Blogs Home Blogs Editions AWS Developer Tools Blog Tag: Windows Phone AWS SDK for .NET v3.5 Preview by Aaron Costley on 06 FEB 2020 in .NET , AWS .NET Development , AWS SDK for .NET , Developer Tools Permalink Share Today, we have published a preview release of version 3.5 of the AWS SDK for .NET. This primary objective of this version is to transition support for all non-Framework versions of the SDK to .NET Standard 2.0. If you are currently using a .NET Framework or .NET Core target, no changes are required. We are […] Caching Amazon Cognito Identity IDs by Norm Johanson on 05 JAN 2015 in .NET Permalink Share Amazon Cognito is a service that you can use to get AWS credentials to your mobile and desktop applications without embedding them in your code. A few months ago, we added a credentials provider for Cognito. In version 2.3.14 of the AWS SDK for .NET, we updated the credentials provider to support caching the identity […] Supporting Windows Phone 8.1 by Norm Johanson on 22 JUL 2014 in .NET Permalink Share When we introduced version 2 of AWS SDK for .NET, it included support for Windows Store 8 and Windows Phone 8. With the release of Windows Phone 8.1, the runtime environment has changed to make it similar to Windows Store apps and to support Universal Apps. This means that when you create a new Windows […] {"data":{"items":[{"fields":{"footer":"{\n \"createAccountButtonLabel\": \"Create an AWS account\",\n \"createAccountButtonURL\": \"https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc1=f_ct&src=footer_signup\",\n \"backToTopText\": \"Back to top\",\n \"eoeText\": \"Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age.\",\n \"copyrightText\": \"© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.\",\n \"items\": [\n {\n \"name\": \"Learn\",\n \"linkURL\": \"\",\n \"items\": [\n {\n \"heading\": \"What Is AWS?\",\n \"linkURL\": \"/what-is-aws/?nc1=f_cc\"\n },\n {\n \"heading\": \"What Is Cloud Computing?\",\n \"linkURL\": \"/what-is-cloud-computing/?nc1=f_cc\"\n },\n {\n \"heading\": \"What Is Agentic AI?\",\n \"linkURL\": \"/what-is/agentic-ai/?nc1=f_cc\"\n },\n {\n \"heading\": \"Cloud Computing Concepts Hub\",\n \"linkURL\": \"/what-is/?nc1=f_cc\"\n },\n {\n \"heading\": \"AWS Cloud Security\",\n \"linkURL\": \"/security/?nc1=f_cc\"\n },\n {\n \"heading\": \"What's New\",\n \"linkURL\": \"/new/?nc1=f_cc\"\n },\n {\n \"heading\": \"Blogs\",\n \"linkURL\": \"/blogs/?nc1=f_cc\"\n },\n {\n \"heading\": \"Press Releases\",\n \"linkURL\": \"https://press.aboutamazon.com/press-releases/aws\"\n }\n ]\n },\n {\n \"name\": \"Resources\",\n \"linkURL\": \"\",\n \"items\": [\n {\n \"heading\": \"Getting Started\",\n \"linkURL\": \"/getting-started/?nc1=f_cc\"\n },\n {\n \"heading\": \"Training\",\n \"linkURL\": \"/training/?nc1=f_cc\"\n },\n {\n \"heading\": \"AWS Trust Center\",\n \"linkURL\": \"/trust-center/?nc1=f_cc\"\n },\n {\n \"heading\": \"AWS Solutions Library\",\n \"linkURL\": \"/solutions/?nc1=f_cc\"\n },\n {\n \"heading\": \"Architecture Center\",\n \"linkURL\": \"/architecture/?nc1=f_cc\"\n },\n {\n \"heading\": \"Product and Technical FAQs\",\n \"linkURL\": \"/faqs/?nc1=f_dr\"\n },\n {\n \"heading\": \"Analyst Reports\",\n \"linkURL\": \"/resources/analyst-reports/?nc1=f_cc\"\n },\n {\n \"heading\": \"AWS Partners\",\n \"linkURL\": \"/partners/work-with-partners/?nc1=f_dr\"\n }\n ]\n },\n {\n \"nam | 2026-01-13T08:48:41 |
https://dev.to/t/mentalhealth/page/9 | Mental Health Page 9 - 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth posts 6 7 8 9 10 11 12 13 14 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How do you protect your peace and mental health in an industry that never sleeps? JASMINE DANIEL JASMINE DANIEL JASMINE DANIEL Follow Jun 13 '25 How do you protect your peace and mental health in an industry that never sleeps? # discuss # mentalhealth # career Comments Add Comment 1 min read Why I Can’t Quit Tech (Even When I Want To) Accio by Alibaba Group Accio by Alibaba Group Accio by Alibaba Group Follow Jul 20 '25 Why I Can’t Quit Tech (Even When I Want To) # discuss # career # programming # mentalhealth 11 reactions Comments 14 comments 2 min read The Dumb Little Project That Saved My Sanity Accio by Alibaba Group Accio by Alibaba Group Accio by Alibaba Group Follow Jul 12 '25 The Dumb Little Project That Saved My Sanity # mentalhealth 1 reaction Comments Add Comment 1 min read Fact-Checking the Fear Behind “The Dark Side of AI”: The Real Story Ashley Childress Ashley Childress Ashley Childress Follow Jul 20 '25 Fact-Checking the Fear Behind “The Dark Side of AI”: The Real Story # ai # mentalhealth # chatgpt # technology 4 reactions Comments 5 comments 6 min read The Rituals That Remain: Love, Distance, and the Plate No One Clears versiqcontent versiqcontent versiqcontent Follow Jun 3 '25 The Rituals That Remain: Love, Distance, and the Plate No One Clears # discuss # mentalhealth # mlhgrad Comments Add Comment 1 min read The Rituals That Remain: Love, Distance, and the Plate No One Clears versiqcontent versiqcontent versiqcontent Follow Jun 3 '25 The Rituals That Remain: Love, Distance, and the Plate No One Clears # mentalhealth # life # family # mlhgrad Comments Add Comment 1 min read When You're Too Tired to Relax: Just Look at the Sky Accio by Alibaba Group Accio by Alibaba Group Accio by Alibaba Group Follow Jul 7 '25 When You're Too Tired to Relax: Just Look at the Sky # mentalhealth # worklifebalance # developers # rest 3 reactions Comments 2 comments 1 min read Overcoming Impostor Syndrome in Tech: My Personal Story and Real-World Tips Nirmit Kotadiya Nirmit Kotadiya Nirmit Kotadiya Follow Jul 6 '25 Overcoming Impostor Syndrome in Tech: My Personal Story and Real-World Tips # mentalhealth # softwaredevelopment # impostersyndrome # techcareer 1 reaction Comments 1 comment 4 min read How to Identify and Heal Burnout from Work Jelloeater 👉jelloeater.me Jelloeater 👉jelloeater.me Jelloeater 👉jelloeater.me Follow Jul 6 '25 How to Identify and Heal Burnout from Work # mentalhealth # selfcare # burnout Comments Add Comment 6 min read How Developers Can Find Their Rhythm in a Fast-Changing Industry Accio by Alibaba Group Accio by Alibaba Group Accio by Alibaba Group Follow Jul 5 '25 How Developers Can Find Their Rhythm in a Fast-Changing Industry # career # productivity # learning # mentalhealth Comments Add Comment 2 min read Do You Ever Feel Like Your Mind Is Running on Someone Else’s Code? versiqcontent versiqcontent versiqcontent Follow May 31 '25 Do You Ever Feel Like Your Mind Is Running on Someone Else’s Code? # productivity # mentalhealth # opensource # motivation Comments Add Comment 1 min read Debugging My Life: What It Takes (Bite-size Article) koshirok096 koshirok096 koshirok096 Follow Jun 13 '25 Debugging My Life: What It Takes (Bite-size Article) # mentalhealth 1 reaction Comments Add Comment 4 min read The Unfinished Project: Why Aging Means Becoming Possible Again versiqcontent versiqcontent versiqcontent Follow May 30 '25 The Unfinished Project: Why Aging Means Becoming Possible Again # challenge # beginners # mentalhealth # aging Comments Add Comment 1 min read When Anger Takes Over: The Silent Struggles No One Sees Phoebe Smith Phoebe Smith Phoebe Smith Follow May 31 '25 When Anger Takes Over: The Silent Struggles No One Sees # mentalhealth # struggles # anger # growth Comments Add Comment 3 min read When Success Feels Full, but Something’s Still Missing versiqcontent versiqcontent versiqcontent Follow May 29 '25 When Success Feels Full, but Something’s Still Missing # career # mentalhealth # productivity # beginners Comments Add Comment 1 min read Day 4 of my Daily Blog Siddham Negi Siddham Negi Siddham Negi Follow May 29 '25 Day 4 of my Daily Blog # discuss # productivity # mentalhealth Comments Add Comment 1 min read I Went on a 90-Day Dopamine Detox as a Dev Student — Here’s What Happened Syed Ahmer Shah Syed Ahmer Shah Syed Ahmer Shah Follow Jul 1 '25 I Went on a 90-Day Dopamine Detox as a Dev Student — Here’s What Happened # programming # webdev # productivity # mentalhealth 52 reactions Comments Add Comment 3 min read Decoding the Crash Beth (Beza) Meeker Beth (Beza) Meeker Beth (Beza) Meeker Follow May 28 '25 Decoding the Crash # devjournal # career # mentalhealth # webdev Comments Add Comment 2 min read How the Aussie Trades Are Prioritising Mental Health Trusted Tradie Network Trusted Tradie Network Trusted Tradie Network Follow May 28 '25 How the Aussie Trades Are Prioritising Mental Health # mentalhealth # tradies Comments Add Comment 4 min read How We Detect Digital Overload and Emotional Residue: A New Era of Proactive Digital Wellness Gaofenngwe Kabubi Gaofenngwe Kabubi Gaofenngwe Kabubi Follow Jun 29 '25 How We Detect Digital Overload and Emotional Residue: A New Era of Proactive Digital Wellness # digitalwellness # emotionalresidue # mentalhealth # ai Comments Add Comment 3 min read When Illness Moves In and You Still Have to Ship Code versiqcontent versiqcontent versiqcontent Follow Jun 12 '25 When Illness Moves In and You Still Have to Ship Code # discuss # mentalhealth # community Comments 1 comment 1 min read The Body Slows Down but the Dream Still Breathes versiqcontent versiqcontent versiqcontent Follow May 24 '25 The Body Slows Down but the Dream Still Breathes # productivity # agentaichallenge # mentalhealth # selfgrowth Comments Add Comment 1 min read Engineered Addiction: How Silicon Valley Monetizes Emotion and Destroys Mental Health Zain Ul Abdeen Zain Ul Abdeen Zain Ul Abdeen Follow Jun 26 '25 Engineered Addiction: How Silicon Valley Monetizes Emotion and Destroys Mental Health # mentalhealth # socialmedia # webdev # programming 1 reaction Comments 4 comments 4 min read "Every Developer I Meet Is My Superior": How Emerson's Wisdom Transformed My Code Reviews Marty Roque Marty Roque Marty Roque Follow Jun 26 '25 "Every Developer I Meet Is My Superior": How Emerson's Wisdom Transformed My Code Reviews # coding # development # mentalhealth # mentorship Comments 1 comment 5 min read People Who Only Exist in Group Chats versiqcontent versiqcontent versiqcontent Follow May 21 '25 People Who Only Exist in Group Chats # digitalculture # reflection # relationships # mentalhealth 1 reaction 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:48:41 |
https://aws.amazon.com/blogs/developer/tag/c/ | C# | AWS Developer Tools Blog Skip to Main Content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Blogs Home Blogs Editions AWS Developer Tools Blog Tag: C# Tips & Tricks: Delaying AWS Service configuration when using .NET Dependency Injection by Philip Pittle on 18 APR 2022 in .NET , AWS .NET Development , AWS SDK for .NET , Best Practices Permalink Share Tips & Tricks: Delaying AWS Service configuration when using .NET Dependency Injection The AWSSDK.Extensions.NETCore.Setup package provides extensions for enabling AWS Service Client creation to work with native .NET Dependency Injection. Bindings for one or more services can be registered via the included AddAWSService<TService> method and a shared configuration can be added and customized via the […] Introducing .NET Annotations Lambda Framework (Preview) by Norm Johanson on 13 APR 2022 in .NET , Announcements , AWS Lambda Permalink Share Recently we released the .NET 6 managed runtime for Lambda. Along with the new Lambda runtime we have also been working on a new framework for writing .NET 6 Lambda functions called Lambda Annotations. The Annotations framework makes the experience of writing Lambda feel more natural in C#. It also takes care of synchronizing the […] Build and Deploy a Microsoft .NET Core Web API application to AWS App Runner using CloudFormation by Naveen Balaraman and Siva Ramani on 11 MAR 2022 in .NET , Amazon Aurora , Amazon CloudWatch , AWS .NET Development , AWS CloudFormation , AWS CodeBuild , AWS CodeCommit , AWS SDK for .NET , AWS Systems Manager , Containers Permalink Share In this blog we show you how to build a Microsoft.NET Web API application with Amazon Aurora Database using AWS App Runner. AWS App Runner makes it easy for developers to quickly deploy containerized web applications and APIs, and helps us start with our source code or a container image. Container workload management tasks, such […] Run Blazor-based .NET Web applications on AWS Serverless by Pratip Bagchi on 30 JUL 2020 in .NET , *Post Types , AWS Toolkit for Visual Studio , Programing Language , Technical How-to , Visual Studio Permalink Share Blazor WebAssembly is a new client-side web development framework that lets developers to use C# to create application front end. Blazor can run client-side C# code directly in the browser, using WebAssembly. Blazor WebAssembly runs on .NET Core and it is an open source and cross-platform web framework for building single-page application using .NET and […] AWS SDK for C++ Version 1.8 is Now Generally Available by Pushen Wang on 29 MAY 2020 in Announcements , AWS SDK for C++ , C++ Permalink Share We’re happy to share that version 1.8 of AWS SDK for C++ is now generally available. AWS SDK for C++ provides a modern C++ (version C++ 11 or later) interface for Amazon Web Services (AWS). It is performant and fully functioning with low- and high-level SDKs, and minimizes dependencies. The AWS SDK for C++ also […] Centralize Amazon CloudWatch Logs using AWS CDK by Naveen Balaraman on 27 MAY 2020 in *Post Types , Amazon CloudWatch , Amazon Data Firehose , Amazon Kinesis , Architecture , AWS .NET Development , AWS Cloud Development Kit , AWS Lambda , Developer Tools , DevOps , Technical How-to Permalink Share September 8, 2021: Amazon Elasticsearch Service has been renamed to Amazon OpenSearch Service. See details. One of the most common use cases that customers try to implement is to centralize various types of logs in their AWS infrastructure so that these logs can be utilized for security, monitoring or analytics purposes. Centralizing AWS services logs […] AWS SDK for .NET v3.5 Preview by Aaron Costley on 06 FEB 2020 in .NET , AWS .NET Development , AWS SDK for .NET , Developer Tools Permalink Share Today, we have published a preview release of version 3.5 of the AWS SDK for .NET. This primary objective of this version is to transition support for all non-Framework versions of the SDK to .NET Standard 2.0. If you are currently using a .NET Framework or .NET Core target, no changes are required. We are […] Announcing Amazon.Lambda.RuntimeSupport by John Vellozzi on 18 MAR 2019 in .NET , AWS Lambda Permalink Share We’ve received many requests to include more versions of .NET Core in AWS Lambda. Customers want the flexibility to write Lambda functions in LTS, current, and preview versions of .NET Core. Until now, you could use only LTS versions. The new Amazon.Lambda.RuntimeSupport library changes that. Today we’ve released the Amazon.Lambda.RuntimeSupport library that enables you to […] AWS SSM ASP.NET Core Data Protection Provider by John Vellozzi on 14 DEC 2018 in .NET , AWS Systems Manager Permalink Share The antiforgery framework is a critical part of ASP.NET Core. It ensures web forms and login pages haven’t been tampered with by storing crypto data with the form and then validating the form with a key created by the Data Protection framework. An ASP.NET Core Data Protection Provider is the building block that provides encryption […] Working with dependency injection in .NET Standard: inject your AWS clients – part 2 by Aaron Costley on 12 NOV 2018 in .NET , AWS SDK for .NET , How-To Permalink Share In part 1 of this blog post, we explored using the lightweight dependency injection (DI) provided by Microsoft.Extensions.DependencyInjection. By itself, this is great for libraries and small programs, but if you’re building a nontrivial application, you have other problems to contend with: You might have complex configuration needs (development versus production, multiple sources, etc.) How […] ← Older posts @charset "UTF-8";[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4{position:relative;transition:box-shadow .3s ease}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover{box-shadow:var(--rg-shadow-gray-elevation-1, 1px 1px 20px rgba(0, 0, 0, .1))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0.rgft_e79955da,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003.rgft_e79955da,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover.rgft_e79955da{box-shadow:var(--rg-shadow-gray-elevation-2, 1px 1px 24px rgba(0, 0, 0, .25))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:hover{box-shadow:none}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde{position:relative;transform-style:preserve-3d;overflow:unset!important}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:before{content:"";position:absolute;inset:0;border-radius:inherit;transform:translateZ(-1px);pointer-events:none;transition-property:filter,inset;transition-duration:.3s;transition-timing-function:ease;background-clip:content-box!important;padding:1px}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0.rgft_4df65418:hover:before{filter:blur(20px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:hover:before{filter:none}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_e90ac70d:active:before{filter:blur(8px)!important}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_a4f580d2:before{filter:blur(8px)!important}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #fa6f00 0%, #e433ff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #d14600 0%, #c300e0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #0099ff 0%, #5c7fff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #006ce0 0%, #295eff 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #ff1ae0 0%, #ff386a 50%, #fa6f00 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #d600ba 0%, #eb003b 50%, #d14600 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #00bd6b 0%, #00a4bd 50%, #0099ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #008559 0%, #007e94 50%, #006ce0 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #00bd6b 0%, #0099ff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #008559 0%, #006ce0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #ad5cff 0%, #0099ff 50%, #00a4bd 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #962eff 0%, #006ce0 50%, #007e94 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #ff1ae0 0%, #8575ff 50%, #00a4bd 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #d600ba 0%, #6842ff 50%, #007e94 100%))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:linear-gradient(123deg,#d14600,#c300e0,#6842ff)}[data-eb-6a8f3296] [data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #d14600 0%, #c300e0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #006ce0 0%, #295eff 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #d600ba 0%, #eb003b 50%, #d14600 100%))}[data-eb-6a8f3296] [data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #008559 0%, #007e94 50%, #006ce0 100%))}[data-eb-6a8f3296] [data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #008559 0%, #006ce0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #962eff 0%, #006ce0 50%, #007e94 100%))}[data-eb-6a8f3296] [data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #d600ba 0%, #6842ff 50%, #007e94 100%))}[data-eb-6a8f3296] a.rgft_f7822e54,[data-eb-6a8f3296] button.rgft_f7822e54{--button-size: 44px;--button-pad-h: 24px;--button-pad-borderless-h: 26px;border:2px solid var(--rg-color-background-page-inverted, #0F141A);padding:8px var(--button-pad-h, 24px);border-radius:40px!important;align-items:center;justify-content:center;display:inline-flex;height:var(--button-size, 44px);text-decoration:none!important;text-wrap:nowrap;cursor:pointer;position:relative;transition:all .3s ease}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_094d67e1,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_094d67e1{--button-size: 32px;--button-pad-h: 14px;--button-pad-borderless-h: 16px}[data-eb-6a8f3296] a.rgft_f7822e54>span,[data-eb-6a8f3296] button.rgft_f7822e54>span{color:var(--btn-text-color, inherit)!important}[data-eb-6a8f3296] a.rgft_f7822e54:focus-visible,[data-eb-6a8f3296] button.rgft_f7822e54:focus-visible{outline:2px solid var(--rg-color-focus-ring, #006CE0)!important;outline-offset:4px!important;transition:outline 0s}[data-eb-6a8f3296] a.rgft_f7822e54:focus:not(:focus-visible),[data-eb-6a8f3296] button.rgft_f7822e54:focus:not(:focus-visible){outline:none!important}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_303c672b,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_303c672b{--btn-text-color: var(--rg-color-text-utility-inverted, #FFFFFF);background-color:var(--rg-color-btn-primary-bg, #161D26);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_18409398{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF);border-color:var(--rg-color-background-page-inverted, #0F141A)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_090951dc{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-background-object, #F3F3F7);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_15529d9f{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{--btn-text-color: var(--rg-color-text-utility, #161D26);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{background-image:linear-gradient(97deg,#ffc0ad,#f8c7ff 37.79%,#d2ccff 75.81%,#c2d1ff)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a, linear-gradient(120deg, #f8c7ff 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_bb950a4e{background-image:var(--rg-gradient-a, linear-gradient(120deg, #78008a 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678{--btn-text-color: var(--rg-color-text-utility-inverted, #FFFFFF);background-color:var(--rg-color-btn-visited-bg, #656871);border-color:var(--rg-color-btn-visited-bg, #656871)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678.rgft_18409398,[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678.rgft_15529d9f{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-visited-bg, #FFFFFF)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5{--btn-text-color: var(--rg-color-btn-disabled-text, #B4B4BB);background-color:var(--rg-color-btn-disabled-bg, #F3F3F7);border-color:var(--rg-color-btn-disabled-bg, #F3F3F7);cursor:default}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_18409398,[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_15529d9f{border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_090951dc{--btn-text-color: var(--rg-color-btn-tertiary-disabled-text, #B4B4BB);background-color:#0000}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_18409398:not(.rgft_bb950a4e),[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_15529d9f:not(.rgft_bb950a4e),[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_18409398:not(.rgft_bb950a4e),[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_15529d9f:not(.rgft_bb950a4e){--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF)}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{box-shadow:none}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{background-image:linear-gradient(97deg,#ffc0ad80,#f8c7ff80 37.79%,#d2ccff80 75.81%,#c2d1ff80)}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a-50, linear-gradient(120deg, #f8c7ff 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:hover:not(.rgft_badebaf5),[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:hover:not(.rgft_badebaf5){background-image:var(--rg-gradient-a-50, linear-gradient(120deg, #78008a 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{box-shadow:none}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{background-image:linear-gradient(97deg,#ffc0ad,#f8c7ff 37.79%,#d2ccff 75.81%,#c2d1ff)}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a-pressed, linear-gradient(120deg, rgba(248, 199, 255, .5) 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:active:not(.rgft_badebaf5),[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:active:not(.rgft_badebaf5){background-image:var(--rg-gradient-a-pressed, linear-gradient(120deg, rgba(120, 0, 138, .5) 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] .rgft_8711ccd9{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;background:#0000;border:none;margin:0}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_5e58a6df{text-align:center}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_b7ada98b{display:block}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_beb26dc7{font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}[data-eb-6a8f3296] .rgft_8711ccd9 a{display:inline;position:relative;cursor:pointer;text-decoration:none!important;color:var(--rg-color-link-default, #006CE0);background:linear-gradient(to right,currentcolor,currentcolor);background-size:100% .1em;background-position:0 100%;background-repeat:no-repeat}[data-eb-6a8f3296] .rgft_8711ccd9 a:focus-visible{color:var(--rg-color-link-focus, #006CE0)}[data-eb-6a8f3296] .rgft_8711ccd9 a:hover{color:var(--rg-color-link-hover, #003B8F);animation:rgft_d72bdead .3s cubic-bezier(0,0,.2,1)}[data-eb-6a8f3296] .rgft_8711ccd9 a:visited{color:var(--rg-color-link-visited, #6842FF)}@keyframes rgft_d72bdead{0%{background-size:0 .1em}to{background-size:100% .1em}}[data-eb-6a8f3296] .rgft_8711ccd9 b,[data-eb-6a8f3296] b.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 strong,[data-eb-6a8f3296] strong.rgft_8711ccd9{font-weight:700}[data-eb-6a8f3296] i.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 i,[data-eb-6a8f3296] em.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 em{font-style:italic}[data-eb-6a8f3296] u.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 u{text-decoration:underline}[data-eb-6a8f3296] code.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 code{font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace;border-radius:4px;border:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);color:var(--rg-color-text-secondary, #232B37);padding-top:var(--rg-padding-8);padding-right:var(--rg-padding-8);padding-bottom:var(--rg-padding-8);padding-left:var(--rg-padding-8)}[data-eb-6a8f3296] .rgft_12e1c6fa{display:inline!important;vertical-align:middle}[data-eb-6a8f3296] .rgft_8711ccd9 p img{aspect-ratio:16/9;height:100%;object-fit:cover;width:100%;border-radius:8px;order:1;margin-bottom:var(--rg-margin-4)}[data-eb-6a8f3296] .rgft_8711ccd9 table{table-layout:fixed;border-spacing:0;width:100%}[data-eb-6a8f3296] .rgft_8711ccd9 table td{font-size:14px;border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);padding-top:var(--rg-padding-6);padding-right:var(--rg-padding-6);padding-bottom:var(--rg-padding-6);padding-left:var(--rg-padding-6)}[data-eb-6a8f3296] .rgft_8711ccd9 table td:first-of-type{border-left:1px solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table thead tr:first-of-type>*:first-of-type,[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead)) tr:first-of-type>*:first-of-type{border-top-left-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table thead tr:first-of-type>*:last-of-type,[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead)) tr:first-of-type>*:last-of-type{border-top-right-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table tr:last-of-type td:first-of-type{border-bottom-left-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table tr:last-of-type td:last-of-type{border-bottom-right-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead),:has(th)) tr:first-of-type td{border-top:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th{color:var(--rg-color-text-primary-inverted, #FFFFFF);min-width:280px;max-width:400px;padding:0;text-align:left;vertical-align:top;background-color:var(--rg-color-background-object-inverted, #232B37);border-left:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);padding-top:var(--rg-padding-6);padding-right:var(--rg-padding-6);padding-bottom:var(--rg-padding-6);padding-left:var(--rg-padding-6);row-gap:var(--rg-margin-5);column-gap:var(--rg-margin-5);max-width:100%;min-width:150px}@media (min-width: 480px) and (max-width: 767px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:100%;min-width:150px}}@media (min-width: 768px) and (max-width: 1023px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:240px;min-width:180px}}@media (min-width: 1024px) and (max-width: 1279px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:350px;min-width:240px}}@media (min-width: 1280px) and (max-width: 1599px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:400px;min-width:280px}}@media (min-width: 1600px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:400px;min-width:280px}}[data-eb-6a8f3296] .rgft_8711ccd9 table th:first-of-type{border-top-left-radius:16px;border-top:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-left:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th:nth-of-type(n+3){border-left:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th:last-of-type{border-top-right-radius:16px;border-top:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_a1b66739{display:inline-flex;flex-direction:column;align-items:center;justify-content:center;color:var(--rg-color-text-primary, #161D26);--icon-color: currentcolor}[data-eb-6a8f3296] .rgft_a1b66739.rgft_bc1a8743{height:16px;width:16px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_c0cbb35d{height:20px;width:20px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_bd40fe12{height:32px;width:32px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_27320e58{height:48px;width:48px}[data-eb-6a8f3296] .rgft_a1b66739 svg{fill:none;stroke:none}[data-eb-6a8f3296] .rgft_a1b66739 path[data-fill]:not([fill]){fill:var(--icon-color)}[data-eb-6a8f3296] .rgft_a1b66739 path[data-stroke]{stroke-width:2}[data-eb-6a8f3296] .rgft_a1b66739 path[data-stroke]:not([stroke]){stroke:var(--icon-color)}[data-eb-6a8f3296] .rgft_3ed66ff4{display:inline-flex;flex-direction:column;align-items:center;justify-content:center;color:var(--rg-color-text-primary, #161D26)}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_9124b200{height:10px;width:10px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_bc1a8743{height:16px;width:16px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_c0cbb35d{height:20px;width:20px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_bd40fe12{height:32px;width:32px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_27320e58{height:48px;width:48px}[data-eb-6a8f3296] .rgft_98b54368{color:var(--rg-color-text-body, #232B37)}[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_275611e5{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_275611e5{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_275611e5{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_275611e5{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_275611e5{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_007aef8b{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_007aef8b{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_ff19c5f9{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_ff19c5f9{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368 ul{list-style-type:disc;margin-top:2rem}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee{display:inline;position:relative;cursor:pointer;text-decoration:none!important;color:var(--rg-color-link-default, #006CE0);background:linear-gradient(to right,currentcolor,currentcolor);background-size:100% .1em;background-position:0 100%;background-repeat:no-repeat}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:focus-visible{color:var(--rg-color-link-focus, #006CE0)}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:hover{color:var(--rg-color-link-hover, #003B8F);animation:rgft_9beb7cc5 .3s cubic-bezier(0,0,.2,1)}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:visited{color:var(--rg-color-link-visited, #6842FF)}@keyframes rgft_9beb7cc5{0%{background-size:0 .1em}to{background-size:100% .1em}}[data-eb-6a8f3296] .rgft_d835af5c{color:var(--rg-color-text-title, #161D26)}[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(4.5rem * var(--font-size-multiplier, 1.6));line-height:1.111;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(3.75rem * var(--font-size-multiplier, 1.6));line-height:1.133;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_3e9243e1{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_3e9243e1{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(3.75rem * var(--font-size-multiplier, 1.6));line-height:1.133;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_54816d41{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_54816d41{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(2rem * var(--font-size-multiplier, 1.6));line-height:1.25;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_852a8b78{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_852a8b78{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_286fbc8d{letter-spacing:1.6px;text-transform:uppercase;color:var(--rg-color-text-eyebrow, #161D26)}[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.714;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:2;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_286fbc8d.rgft_cf5cdf86{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_286fbc8d.rgft_cf5cdf86{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.714;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:2;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:2.4;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_286fbc8d.rgft_c6f92487{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_286fbc8d.rgft_c6f92487{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751{color:var(--rg-color-text-utility, #161D26)}[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_927d7fd1{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_927d7fd1{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_100c8a76{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_100c8a76{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_453dc601{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_453dc601{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_949ed5ce{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_949ed5ce{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_5d220f64{color:var(--rg-color-text-heading, #161D26)}[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.1;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(2rem * var(--font-size-multiplier, 1.6));line-height:1.25;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(1.75rem * var(--font-size-multiplier, 1.6));line-height:1.286;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_5d220f64.rgft_94339b09{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_5d220f64.rgft_94339b09{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_5d220f64.rgft_94339b09{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [dat | 2026-01-13T08:48:41 |
https://aws.amazon.com/blogs/developer/tag/unity/ | Unity | AWS Developer Tools Blog Skip to Main Content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Blogs Home Blogs Editions AWS Developer Tools Blog Tag: Unity AWS SDK for .NET v3.5 Preview by Aaron Costley on 06 FEB 2020 in .NET , AWS .NET Development , AWS SDK for .NET , Developer Tools Permalink Share Today, we have published a preview release of version 3.5 of the AWS SDK for .NET. This primary objective of this version is to transition support for all non-Framework versions of the SDK to .NET Standard 2.0. If you are currently using a .NET Framework or .NET Core target, no changes are required. We are […] Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New <a data-rg-n="Link" href="/blogs/?nc1=f_cc" data- | 2026-01-13T08:48:41 |
https://survivejs.com/books/react/ | SurviveJS – React Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... SurviveJS – React React ↗ is a popular library for developing JavaScript applications and websites. In this book, you will implement a simple Kanban application step-wise. Note that the book is still using old class-based syntax and needs an update to the latest. You can follow the book with the help of the official documentation for now, however. Read the React book Buy the React book ↗ Availability Although you can read the book online for free , you can also purchase it in a copy to support the development of the content. See also consulting for other available options. Leanpub (digital, always up to date with the site) ↗ Table of contents Introduction Front-end development moves forward fast. A good indication of this is the pace at which new technologies appear to the scene. React is one of these recent newcomers. Even though the technology itself is simple, there's a lot going on around it. The purpose of this book is to help you get started … Getting Started React, despite being a young library, has had a significant impact on the front-end development community. It introduced concepts, such as the virtual DOM, and made the community understand the power of components. Its component oriented design approach works well for the web. But React isn't limit… Introduction to React Facebook's React has changed the way we think about web applications and user interface development. Due to its design, you can use it beyond web. A feature known as the Virtual DOM enables this. In this chapter we'll go through some of the basic ideas behind the library so you understand React a … Setting Up the Project To make it easier to get started, I've set up a simple Webpack based boilerplate that allows us to dig into React straight away. The boilerplate includes a development mode with a feature known as hot loading enabled. Hot loading allows Webpack to patch the code running in the browser without a fu… Implementing a Note Application Now that we have a nice development setup, we can actually get some work done. Our goal here is to end up with a crude note-taking application. It will have basic manipulation operations. We will grow our application from scratch and get into some trouble. This way you will understand why architect… Deleting Notes One easy way to handle deleting notes is to render a "x" button for each Note. When it's clicked we will simply delete the note in question from our data structure. As before, we can start by adding stubs in place. This might be a good place to separate the concept of a Note from the current Notes … Understanding React Components As we have seen so far, React components are fairly simple. They can have internal state. They can also accept props. Beyond this React provides escape hatches that allow you to handle advanced use cases. These include lifecycle methods and refs. There are also a set of custom properties and method… Editing Notes Editing notes is a similar problem as deleting them. The data flow is exactly the same. We'll need to define an onEdit callback and bind an id of the note being edited at Notes. What makes this scenario difficult is the user interface requirement. It's not enough just to have a button. We'll need… Styling the Notes Application Aesthetically, our current application is very barebones. As pretty applications are more fun to use, we can do a little something about that. In this case we'll be sticking to an old skool way of styling. In other words, we'll sprinkle some CSS classes around and then apply CSS selectors based on… Implementing Kanban In this part, we will turn our Notes application into a Kanban application. During the process, you will learn the basics of React. As React is just a view library we will also discuss supporting technology. We will set up a state management solution to our application. We will also see how to use … React and Flux You can get pretty far by keeping everything in components. That's an entirely valid way to get started. The problems begin as you add state to your application and need to share it across different parts. This is the reason why various state management solutions have emerged. Each one of those tri… Implementing NoteStore and NoteActions Now that we have pushed data management related concerns in the right places, we can focus on implementing the remaining portions - NoteStore and NoteActions. These will encapsulate the application data and logic. No matter what state management solution you end up using, there is usually somethin… Implementing Persistency over localStorage Currently our application cannot retain its state if refreshed. One neat way to get around this problem is to store the application state to localStorage and then restore it when we run the application again. If you were working against a back-end, this wouldn't be a problem. Even then having a te… Handling Data Dependencies So far we have developed an application for keeping track of notes in localStorage. To get closer to Kanban, we need to model the concept of Lane. A Lane is something that should be able to contain many Notes within itself and track their order. One way to model this is simply to make a Lane point … Editing Lanes Kanban board We still have work to do to turn this into a real Kanban as pictured above. The application is still missing some logic and styling. That's what we'll focus on here. The Editable component we implemented earlier will come in handy. We can use it to make it possible to alter Lane name… Implementing Drag and Drop Our Kanban application is almost usable now. It looks alright and there's basic functionality in place. In this chapter, we will integrate drag and drop functionality to it as we set up React DnD. After this chapter, you should be able to sort notes within a lane and drag them from one lane to ano… Advanced Techniques There are a variety of advanced React techniques that are good to be aware of. By testing and typing your code well, you can make it more robust against change. It will be easier to develop if you have the right scaffolding in place supporting your application. Styling React is a complicated topic… Testing React In order to encourage people to support my work, I've decided to publish a TL;DR version of this chapter for the community. This will allow me to develop more content, so it's a win-win really. You can access the full chapter by buying a copy through Leanpub. It goes into detail, whereas the follo… Typing with React In order to encourage people to support my work, I've decided to publish a TL;DR version of this chapter for the community. This will allow me to develop more content, so it's a win-win really. You can access the full chapter by buying a copy through Leanpub. It goes into detail, whereas the follo… Styling React Traditionally, web pages have been split up into markup (HTML), styling (CSS), and logic (JavaScript). Thanks to React and similar approaches, we've begun to question this split. We still may want to separate our concerns somehow. But the split can be on different axes. This change in the mindset … Structuring React Projects React doesn't enforce any particular project structure. The good thing about this is that it allows you to make up a structure to suit your needs. The bad thing is that it is not possible to provide you an ideal structure that would work for every project. Instead, I'm going to give you some inspir… Appendices As not everything that's worth discussing fits a book like this, I've compiled related material into brief appendices. These support the main material and explain certain topics, such as language features, in greater detail. There are also troubleshooting tips in the end. … Language Features ES6 (or ES2015) was arguably the biggest change to JavaScript in a long time. As a result, we received a wide variety of new functionality. The purpose of this appendix is to illustrate the features used in the book in isolation to make it clearer to understand how they work. Rather than going thro… Understanding Decorators If you have used languages, such as Java or Python before, you might be familiar with the idea. Decorators are syntactic sugar that allow us to wrap and annotate classes and functions. In their current proposal (stage 1) only class and method level wrapping is supported. Functions may become suppor… Troubleshooting I've tried to cover some common issues here. This chapter will be expanded as common issues are found. EPEERINVALID It is possible you may see a message like this: npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] No README data npm WARN peerDepen… Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://dev.to/szabgab/perl-weekly-604-p-in-lamp-1j9a | Perl Weekly #604 - P in LAMP? - 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 Gabor Szabo Posted on Feb 20, 2023 • Originally published at perlweekly.com Perl Weekly #604 - P in LAMP? # perl # news # programming # webdev perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Originally published at Perl Weekly 604 Hi there, Depending who you ask the question, you might get different answer. As I am native Perl speaker, I would say it stands for Perl . I first came to know about LAMP in the year 1999 when I was first introduced to Perl . Although the term was first coined by Michael Kunze in the year 1998 . During that time, Perl and PHP were the only two contenders. Many years later, Python joined the gang. That makes it good fun discussion on what P stands for in LAMP . Those days, Web Development was mostly around Perl and good old friend CGI . Things have changed for good in all these years. We now have plenty of choices to pick from, like Catalyst , Mojolicious , Dancer2 etc etc. Most of my time with Perl spent on Web Development. At one place, we had inhouse Web Framework, which worked like a charm but recently when I moved to Oleeo , I got the opportunity to work with Catalyst . I am a big fan of Dancer2 , so getting on with Catalyst was a little difficult. Having said, I did find some similarities between the two. Going back to the topic, LAMP , I remember a blog post on the same subject going into fine details and variations. It was fun read. I also came across this question, Why Perl is included into lamp-server? . I loved the reply to the question. I never thought about it before. Last but not the least, I let you explore this Stackoverflow Q&A on the similar topic. My twins always say "My dad is the best", so I borrow their pet statement and say "Perl is the best language ever" . So go on and play with it. Enjoy the rest of the newsletter and please keep supporting us as always. -- Your editor: Mohammad S. Anwar. Announcements This Week in PSC (098) Quick recaps of what discussed. PayProp supports the German Perl/Raku Workshop 2023 So now we have one more sponsor for Perl/Raku Workshop 2023. Congratulations. Articles ChatGPT suggests new keywords for Perl Have you played with ChatGPT? Please checkout how Perl behaves with ChatGPT. What does ChatGPT think about improving Perl? ChatGPT helping with role and inheritance in Perl. Fun. Outstanding GitHub Items Do you use GitHub? If yes then you should checkout this post, Discussion Main reasons for Perl's loss of popularity ... Interesting points raised and discussed in this thread. Why not join and share your views too. Code csv2json Handy tool to convert csv file to JSON. You get plenty of examples to play with. Web A quick look at Skate The personal key value store with a simple, powerful command line user interface. You can also sync it across all your machines to access your data anywhere. CPAN Using Type::Params Effectively Well defined tutorials on CPAN module Type::Params sharing with nice examples. PDF::Collage on CPAN Short and sweet introduction to PDF::Collage. Reflections after a couple of weeks of Data::Resolver Sharing the feedback on recently uploaded module Data::Resolver. The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 205 Welcome to a new week with a couple of fun tasks: "Third Highest" and "Maximum XOR". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 204 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Monotonic Array" and "Reshape Matrix" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Monotonically Reshaped I noticed one pattern in Arne's solution is that you get more than just one solution for each task. Keep it up great work. PWC204 - Monotonic Array Raku solution is more impressive than the Perl one. The one-liners solution is full of jargons. Thanks for keeping us entertained. PWC204 - Reshape Matrix Turning Perl version to Raku can be fun. The end result is very impressive. Good job. The Weekly Challenge 204 I just fall in love with this code every week. Elegantly crafted code, very inspiring. Well done. Perl Weekly Challenge 204: Monotonic Arrays and Reshape Matrix Cool use of meta-operator in Raku makes the end result one-liner. Smart solutions both in Perl and Raku. Thanks for sharing the knowledge. Arrays everywhere! Pure logical solutions in Raku without the use of any special features. One can easily port it to Perl. Easy Peasy. Perl Weekly Challenge 204 As expected we got yet another classic one-liner in Perl. Keep it up great work. Climbing or falling and reshaping the matrix I would give full marks for clean blog style. The discussion and code side-by-side makes life so simple. Well done, keep it up. The Weekly Challenge #204 One should learn from Robbie how to get job done with little effort. Incredible. Thanks for sharing. Reshape the Monotony The solution to the task "Reshape Matrix" turned out to be easy peasy for Roger. Above all, it is easy to follow too, well done. Weekly Challenge 204 Clever use of procesing matrix data as input. Getting the best result using the available choices isn't easy. Python solution is always the bonus for us. Rakudo 2023.07 Core Class Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Perl to Node Cross-training? Yes Please! UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. Bold, beautiful, and… brainy? Senior Perl roles in Malaysia, Dubai and Malta With all the knowledge in your big, beautiful brain, it’s time to join a company that appreciates your breadth of experience. Our client provides online trading services and with offices in Dubai, Malta, and Malaysia, they’ve got the global reach that may provide the challenge you’re looking for. They know that a seasoned Perl pro is just what their team needs, and that’s where you come in. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. UK Remote Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming Perl 🐪 Weekly #752 - Marlin - OOP Framework # perl # news # programming 💎 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:48:41 |
https://survivejs.com/books/react/ | SurviveJS – React Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... SurviveJS – React React ↗ is a popular library for developing JavaScript applications and websites. In this book, you will implement a simple Kanban application step-wise. Note that the book is still using old class-based syntax and needs an update to the latest. You can follow the book with the help of the official documentation for now, however. Read the React book Buy the React book ↗ Availability Although you can read the book online for free , you can also purchase it in a copy to support the development of the content. See also consulting for other available options. Leanpub (digital, always up to date with the site) ↗ Table of contents Introduction Front-end development moves forward fast. A good indication of this is the pace at which new technologies appear to the scene. React is one of these recent newcomers. Even though the technology itself is simple, there's a lot going on around it. The purpose of this book is to help you get started … Getting Started React, despite being a young library, has had a significant impact on the front-end development community. It introduced concepts, such as the virtual DOM, and made the community understand the power of components. Its component oriented design approach works well for the web. But React isn't limit… Introduction to React Facebook's React has changed the way we think about web applications and user interface development. Due to its design, you can use it beyond web. A feature known as the Virtual DOM enables this. In this chapter we'll go through some of the basic ideas behind the library so you understand React a … Setting Up the Project To make it easier to get started, I've set up a simple Webpack based boilerplate that allows us to dig into React straight away. The boilerplate includes a development mode with a feature known as hot loading enabled. Hot loading allows Webpack to patch the code running in the browser without a fu… Implementing a Note Application Now that we have a nice development setup, we can actually get some work done. Our goal here is to end up with a crude note-taking application. It will have basic manipulation operations. We will grow our application from scratch and get into some trouble. This way you will understand why architect… Deleting Notes One easy way to handle deleting notes is to render a "x" button for each Note. When it's clicked we will simply delete the note in question from our data structure. As before, we can start by adding stubs in place. This might be a good place to separate the concept of a Note from the current Notes … Understanding React Components As we have seen so far, React components are fairly simple. They can have internal state. They can also accept props. Beyond this React provides escape hatches that allow you to handle advanced use cases. These include lifecycle methods and refs. There are also a set of custom properties and method… Editing Notes Editing notes is a similar problem as deleting them. The data flow is exactly the same. We'll need to define an onEdit callback and bind an id of the note being edited at Notes. What makes this scenario difficult is the user interface requirement. It's not enough just to have a button. We'll need… Styling the Notes Application Aesthetically, our current application is very barebones. As pretty applications are more fun to use, we can do a little something about that. In this case we'll be sticking to an old skool way of styling. In other words, we'll sprinkle some CSS classes around and then apply CSS selectors based on… Implementing Kanban In this part, we will turn our Notes application into a Kanban application. During the process, you will learn the basics of React. As React is just a view library we will also discuss supporting technology. We will set up a state management solution to our application. We will also see how to use … React and Flux You can get pretty far by keeping everything in components. That's an entirely valid way to get started. The problems begin as you add state to your application and need to share it across different parts. This is the reason why various state management solutions have emerged. Each one of those tri… Implementing NoteStore and NoteActions Now that we have pushed data management related concerns in the right places, we can focus on implementing the remaining portions - NoteStore and NoteActions. These will encapsulate the application data and logic. No matter what state management solution you end up using, there is usually somethin… Implementing Persistency over localStorage Currently our application cannot retain its state if refreshed. One neat way to get around this problem is to store the application state to localStorage and then restore it when we run the application again. If you were working against a back-end, this wouldn't be a problem. Even then having a te… Handling Data Dependencies So far we have developed an application for keeping track of notes in localStorage. To get closer to Kanban, we need to model the concept of Lane. A Lane is something that should be able to contain many Notes within itself and track their order. One way to model this is simply to make a Lane point … Editing Lanes Kanban board We still have work to do to turn this into a real Kanban as pictured above. The application is still missing some logic and styling. That's what we'll focus on here. The Editable component we implemented earlier will come in handy. We can use it to make it possible to alter Lane name… Implementing Drag and Drop Our Kanban application is almost usable now. It looks alright and there's basic functionality in place. In this chapter, we will integrate drag and drop functionality to it as we set up React DnD. After this chapter, you should be able to sort notes within a lane and drag them from one lane to ano… Advanced Techniques There are a variety of advanced React techniques that are good to be aware of. By testing and typing your code well, you can make it more robust against change. It will be easier to develop if you have the right scaffolding in place supporting your application. Styling React is a complicated topic… Testing React In order to encourage people to support my work, I've decided to publish a TL;DR version of this chapter for the community. This will allow me to develop more content, so it's a win-win really. You can access the full chapter by buying a copy through Leanpub. It goes into detail, whereas the follo… Typing with React In order to encourage people to support my work, I've decided to publish a TL;DR version of this chapter for the community. This will allow me to develop more content, so it's a win-win really. You can access the full chapter by buying a copy through Leanpub. It goes into detail, whereas the follo… Styling React Traditionally, web pages have been split up into markup (HTML), styling (CSS), and logic (JavaScript). Thanks to React and similar approaches, we've begun to question this split. We still may want to separate our concerns somehow. But the split can be on different axes. This change in the mindset … Structuring React Projects React doesn't enforce any particular project structure. The good thing about this is that it allows you to make up a structure to suit your needs. The bad thing is that it is not possible to provide you an ideal structure that would work for every project. Instead, I'm going to give you some inspir… Appendices As not everything that's worth discussing fits a book like this, I've compiled related material into brief appendices. These support the main material and explain certain topics, such as language features, in greater detail. There are also troubleshooting tips in the end. … Language Features ES6 (or ES2015) was arguably the biggest change to JavaScript in a long time. As a result, we received a wide variety of new functionality. The purpose of this appendix is to illustrate the features used in the book in isolation to make it clearer to understand how they work. Rather than going thro… Understanding Decorators If you have used languages, such as Java or Python before, you might be familiar with the idea. Decorators are syntactic sugar that allow us to wrap and annotate classes and functions. In their current proposal (stage 1) only class and method level wrapping is supported. Functions may become suppor… Troubleshooting I've tried to cover some common issues here. This chapter will be expanded as common issues are found. EPEERINVALID It is possible you may see a message like this: npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] No README data npm WARN peerDepen… Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://dev.to/t/mentalhealth/page/5 | Mental Health Page 5 - 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth posts 2 3 4 5 6 7 8 9 10 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Khủng hoảng nghề nghiệp tuổi 30 Kelvyn Thai Kelvyn Thai Kelvyn Thai Follow Oct 22 '25 Khủng hoảng nghề nghiệp tuổi 30 # crisis # career # mentalhealth Comments Add Comment 4 min read I use AI when I code. And sometimes it makes me feel like I’m cheating. Christoffer Madsen Christoffer Madsen Christoffer Madsen Follow Nov 10 '25 I use AI when I code. And sometimes it makes me feel like I’m cheating. # ai # selfimprovement # webdev # mentalhealth 83 reactions Comments 57 comments 2 min read Pourquoi changer sera difficile… (Réflexion personnelle) Elvis Ansima Elvis Ansima Elvis Ansima Follow Nov 25 '25 Pourquoi changer sera difficile… (Réflexion personnelle) # mentalhealth Comments 1 comment 2 min read October Taught Me to Show Up Hamzat Abdul-muizz Hamzat Abdul-muizz Hamzat Abdul-muizz Follow Nov 2 '25 October Taught Me to Show Up # devjournal # mentalhealth # motivation 6 reactions Comments Add Comment 4 min read The Beginning : Hello World! cz writes cz writes cz writes Follow Oct 25 '25 The Beginning : Hello World! # codenewbie # motivation # devjournal # mentalhealth 1 reaction Comments 1 comment 2 min read 🌱La maternidad, la pausa laboral… y un clic Laura Montironi Laura Montironi Laura Montironi Follow Nov 20 '25 🌱La maternidad, la pausa laboral… y un clic # career # devjournal # mentalhealth 5 reactions Comments Add Comment 4 min read Sleep Patterns Predict Mental Health Episodes 3-7 Days Ahead: Building SleepMind.ai Alex Chen Alex Chen Alex Chen Follow Oct 21 '25 Sleep Patterns Predict Mental Health Episodes 3-7 Days Ahead: Building SleepMind.ai # mentalhealth # ai # python # opensource Comments Add Comment 2 min read Has AI made programming less satisfying for you? Ava Nichols Ava Nichols Ava Nichols Follow Nov 6 '25 Has AI made programming less satisfying for you? # discuss # ai # productivity # mentalhealth 4 reactions Comments 4 comments 1 min read Lesson 25: Risk Control and Psychology Management Henry Lin Henry Lin Henry Lin Follow Nov 20 '25 Lesson 25: Risk Control and Psychology Management # management # mentalhealth # productivity Comments Add Comment 14 min read From Imposter Syndrome to Confidence: My Journey as a Senior Angular Developer Gouranga Das Samrat Gouranga Das Samrat Gouranga Das Samrat Follow Nov 16 '25 From Imposter Syndrome to Confidence: My Journey as a Senior Angular Developer # angular # career # mentalhealth 4 reactions Comments 2 comments 9 min read The Commit I Almost Didn't Push Evan Lausier Evan Lausier Evan Lausier Follow Nov 18 '25 The Commit I Almost Didn't Push # beginners # career # mentalhealth 1 reaction Comments Add Comment 2 min read Turning emotional struggles into “bug reports” — my side project, Life.exe SoulInMind Labs SoulInMind Labs SoulInMind Labs Follow Oct 26 '25 Turning emotional struggles into “bug reports” — my side project, Life.exe # showdev # webdev # sideprojects # mentalhealth 1 reaction Comments Add Comment 1 min read Building Eunoia: A Mental Wellbeing Companion Oluwadahunsi Ifeoluwa Oluwadahunsi Ifeoluwa Oluwadahunsi Ifeoluwa Follow Nov 3 '25 Building Eunoia: A Mental Wellbeing Companion # gemini # ai # mentalhealth # go Comments 3 comments 9 min read We Need to Stop Calling It 'Imposter Syndrome' Tombri Bowei Tombri Bowei Tombri Bowei Follow Nov 6 '25 We Need to Stop Calling It 'Imposter Syndrome' # discuss # career # mentalhealth # programming 21 reactions Comments 12 comments 4 min read I Reduced My Panic Attacks by 90% With Data—Here's How I Built the Tool Alex Chen Alex Chen Alex Chen Follow Oct 20 '25 I Reduced My Panic Attacks by 90% With Data—Here's How I Built the Tool # wellbeing # mentalhealth # productivity # data Comments Add Comment 2 min read Stuck Between Studies and Career Manasvi Pal Manasvi Pal Manasvi Pal Follow Oct 31 '25 Stuck Between Studies and Career # help # beginners # mentalhealth # career Comments 1 comment 1 min read The Thirst of Learning Everything Mourya Vamsi Modugula Mourya Vamsi Modugula Mourya Vamsi Modugula Follow Nov 7 '25 The Thirst of Learning Everything # webdev # programming # career # mentalhealth Comments Add Comment 2 min read 🎧 The Silent Crisis: Using Speech Recognition and Sentiment AI for Real-Time Emotional Support shambhavi525-sudo shambhavi525-sudo shambhavi525-sudo Follow Nov 6 '25 🎧 The Silent Crisis: Using Speech Recognition and Sentiment AI for Real-Time Emotional Support # showdev # ai # mentalhealth # machinelearning 1 reaction Comments 2 comments 2 min read Developing Secure Healthcare Apps in 2026: Standards, Tech & Best Practices CHILLICODE CHILLICODE CHILLICODE Follow Oct 6 '25 Developing Secure Healthcare Apps in 2026: Standards, Tech & Best Practices # mentalhealth # mobile # development Comments Add Comment 7 min read Reflections on Learning, Mentorship, and Growth Fredrick Ogutu Fredrick Ogutu Fredrick Ogutu Follow Oct 13 '25 Reflections on Learning, Mentorship, and Growth # learning # mentalhealth # career # productivity Comments Add Comment 5 min read MoodFeed: Building an AI-Powered Social Feed That Actually Gets You Nadim Chowdhury Nadim Chowdhury Nadim Chowdhury Follow Nov 1 '25 MoodFeed: Building an AI-Powered Social Feed That Actually Gets You # showdev # sideprojects # mentalhealth # ai 1 reaction Comments Add Comment 6 min read What Keeps Me Coding When It Gets Tough Churchill Emmanuel Churchill Emmanuel Churchill Emmanuel Follow Sep 29 '25 What Keeps Me Coding When It Gets Tough # discuss # coding # mentalhealth Comments Add Comment 2 min read What I See When I Watch You Build Dev TNG Dev TNG Dev TNG Follow Oct 30 '25 What I See When I Watch You Build # discuss # mentalhealth # startup 7 reactions Comments 1 comment 2 min read Enhancing Critical Thinking Skills: The Power of Online Learning Platforms for Students Ghumman Tech Ghumman Tech Ghumman Tech Follow Oct 12 '25 Enhancing Critical Thinking Skills: The Power of Online Learning Platforms for Students # ghummantech # mentalhealth # financialliteracy Comments Add Comment 3 min read 1% 0 — Sobre la improbabilidad estadística de conservar la conciencia en un sistema que la penaliza Bernard Uriza Bernard Uriza Bernard Uriza Follow Oct 31 '25 1% 0 — Sobre la improbabilidad estadística de conservar la conciencia en un sistema que la penaliza # webdev # security # mentalhealth # analytics 1 reaction Comments Add Comment 4 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:48:41 |
https://docs.python.org/3/library/decimal.html#decimal.Decimal | decimal — Decimal fixed-point and floating-point arithmetic — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents decimal — Decimal fixed-point and floating-point arithmetic Quick-start tutorial Decimal objects Logical operands Context objects Constants Rounding modes Signals Floating-point notes Mitigating round-off error with increased precision Special values Working with threads Recipes Decimal FAQ Previous topic cmath — Mathematical functions for complex numbers Next topic fractions — Rational numbers This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Numeric and Mathematical Modules » decimal — Decimal fixed-point and floating-point arithmetic | Theme Auto Light Dark | decimal — Decimal fixed-point and floating-point arithmetic ¶ Source code: Lib/decimal.py The decimal module provides support for fast correctly rounded decimal floating-point arithmetic. It offers several advantages over the float datatype: Decimal “is based on a floating-point model which was designed with people in mind, and necessarily has a paramount guiding principle – computers must provide an arithmetic that works in the same way as the arithmetic that people learn at school.” – excerpt from the decimal arithmetic specification. Decimal numbers can be represented exactly. In contrast, numbers like 1.1 and 2.2 do not have exact representations in binary floating point. End users typically would not expect 1.1 + 2.2 to display as 3.3000000000000003 as it does with binary floating point. The exactness carries over into arithmetic. In decimal floating point, 0.1 + 0.1 + 0.1 - 0.3 is exactly equal to zero. In binary floating point, the result is 5.5511151231257827e-017 . While near to zero, the differences prevent reliable equality testing and differences can accumulate. For this reason, decimal is preferred in accounting applications which have strict equality invariants. The decimal module incorporates a notion of significant places so that 1.30 + 1.20 is 2.50 . The trailing zero is kept to indicate significance. This is the customary presentation for monetary applications. For multiplication, the “schoolbook” approach uses all the figures in the multiplicands. For instance, 1.3 * 1.2 gives 1.56 while 1.30 * 1.20 gives 1.5600 . Unlike hardware based binary floating point, the decimal module has a user alterable precision (defaulting to 28 places) which can be as large as needed for a given problem: >>> from decimal import * >>> getcontext () . prec = 6 >>> Decimal ( 1 ) / Decimal ( 7 ) Decimal('0.142857') >>> getcontext () . prec = 28 >>> Decimal ( 1 ) / Decimal ( 7 ) Decimal('0.1428571428571428571428571429') Both binary and decimal floating point are implemented in terms of published standards. While the built-in float type exposes only a modest portion of its capabilities, the decimal module exposes all required parts of the standard. When needed, the programmer has full control over rounding and signal handling. This includes an option to enforce exact arithmetic by using exceptions to block any inexact operations. The decimal module was designed to support “without prejudice, both exact unrounded decimal arithmetic (sometimes called fixed-point arithmetic) and rounded floating-point arithmetic.” – excerpt from the decimal arithmetic specification. The module design is centered around three concepts: the decimal number, the context for arithmetic, and signals. A decimal number is immutable. It has a sign, coefficient digits, and an exponent. To preserve significance, the coefficient digits do not truncate trailing zeros. Decimals also include special values such as Infinity , -Infinity , and NaN . The standard also differentiates -0 from +0 . The context for arithmetic is an environment specifying precision, rounding rules, limits on exponents, flags indicating the results of operations, and trap enablers which determine whether signals are treated as exceptions. Rounding options include ROUND_CEILING , ROUND_DOWN , ROUND_FLOOR , ROUND_HALF_DOWN , ROUND_HALF_EVEN , ROUND_HALF_UP , ROUND_UP , and ROUND_05UP . Signals are groups of exceptional conditions arising during the course of computation. Depending on the needs of the application, signals may be ignored, considered as informational, or treated as exceptions. The signals in the decimal module are: Clamped , InvalidOperation , DivisionByZero , Inexact , Rounded , Subnormal , Overflow , Underflow and FloatOperation . For each signal there is a flag and a trap enabler. When a signal is encountered, its flag is set to one, then, if the trap enabler is set to one, an exception is raised. Flags are sticky, so the user needs to reset them before monitoring a calculation. See also IBM’s General Decimal Arithmetic Specification, The General Decimal Arithmetic Specification . Quick-start tutorial ¶ The usual start to using decimals is importing the module, viewing the current context with getcontext() and, if necessary, setting new values for precision, rounding, or enabled traps: >>> from decimal import * >>> getcontext () Context(prec=28, rounding=ROUND_HALF_EVEN, Emin=-999999, Emax=999999, capitals=1, clamp=0, flags=[], traps=[Overflow, DivisionByZero, InvalidOperation]) >>> getcontext () . prec = 7 # Set a new precision Decimal instances can be constructed from integers, strings, floats, or tuples. Construction from an integer or a float performs an exact conversion of the value of that integer or float. Decimal numbers include special values such as NaN which stands for “Not a number”, positive and negative Infinity , and -0 : >>> getcontext () . prec = 28 >>> Decimal ( 10 ) Decimal('10') >>> Decimal ( '3.14' ) Decimal('3.14') >>> Decimal ( 3.14 ) Decimal('3.140000000000000124344978758017532527446746826171875') >>> Decimal (( 0 , ( 3 , 1 , 4 ), - 2 )) Decimal('3.14') >>> Decimal ( str ( 2.0 ** 0.5 )) Decimal('1.4142135623730951') >>> Decimal ( 2 ) ** Decimal ( '0.5' ) Decimal('1.414213562373095048801688724') >>> Decimal ( 'NaN' ) Decimal('NaN') >>> Decimal ( '-Infinity' ) Decimal('-Infinity') If the FloatOperation signal is trapped, accidental mixing of decimals and floats in constructors or ordering comparisons raises an exception: >>> c = getcontext () >>> c . traps [ FloatOperation ] = True >>> Decimal ( 3.14 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> decimal.FloatOperation : [<class 'decimal.FloatOperation'>] >>> Decimal ( '3.5' ) < 3.7 Traceback (most recent call last): File "<stdin>" , line 1 , in <module> decimal.FloatOperation : [<class 'decimal.FloatOperation'>] >>> Decimal ( '3.5' ) == 3.5 True Added in version 3.3. The significance of a new Decimal is determined solely by the number of digits input. Context precision and rounding only come into play during arithmetic operations. >>> getcontext () . prec = 6 >>> Decimal ( '3.0' ) Decimal('3.0') >>> Decimal ( '3.1415926535' ) Decimal('3.1415926535') >>> Decimal ( '3.1415926535' ) + Decimal ( '2.7182818285' ) Decimal('5.85987') >>> getcontext () . rounding = ROUND_UP >>> Decimal ( '3.1415926535' ) + Decimal ( '2.7182818285' ) Decimal('5.85988') If the internal limits of the C version are exceeded, constructing a decimal raises InvalidOperation : >>> Decimal ( "1e9999999999999999999" ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> decimal.InvalidOperation : [<class 'decimal.InvalidOperation'>] Changed in version 3.3. Decimals interact well with much of the rest of Python. Here is a small decimal floating-point flying circus: >>> data = list ( map ( Decimal , '1.34 1.87 3.45 2.35 1.00 0.03 9.25' . split ())) >>> max ( data ) Decimal('9.25') >>> min ( data ) Decimal('0.03') >>> sorted ( data ) [Decimal('0.03'), Decimal('1.00'), Decimal('1.34'), Decimal('1.87'), Decimal('2.35'), Decimal('3.45'), Decimal('9.25')] >>> sum ( data ) Decimal('19.29') >>> a , b , c = data [: 3 ] >>> str ( a ) '1.34' >>> float ( a ) 1.34 >>> round ( a , 1 ) Decimal('1.3') >>> int ( a ) 1 >>> a * 5 Decimal('6.70') >>> a * b Decimal('2.5058') >>> c % a Decimal('0.77') Decimals can be formatted (with format() built-in or f-strings ) in fixed-point or scientific notation, using the same formatting syntax (see Format Specification Mini-Language ) as builtin float type: >>> format ( Decimal ( '2.675' ), "f" ) '2.675' >>> format ( Decimal ( '2.675' ), ".2f" ) '2.68' >>> f " { Decimal ( '2.675' ) : .2f } " '2.68' >>> format ( Decimal ( '2.675' ), ".2e" ) '2.68e+0' >>> with localcontext () as ctx : ... ctx . rounding = ROUND_DOWN ... print ( format ( Decimal ( '2.675' ), ".2f" )) ... 2.67 And some mathematical functions are also available to Decimal: >>> getcontext () . prec = 28 >>> Decimal ( 2 ) . sqrt () Decimal('1.414213562373095048801688724') >>> Decimal ( 1 ) . exp () Decimal('2.718281828459045235360287471') >>> Decimal ( '10' ) . ln () Decimal('2.302585092994045684017991455') >>> Decimal ( '10' ) . log10 () Decimal('1') The quantize() method rounds a number to a fixed exponent. This method is useful for monetary applications that often round results to a fixed number of places: >>> Decimal ( '7.325' ) . quantize ( Decimal ( '.01' ), rounding = ROUND_DOWN ) Decimal('7.32') >>> Decimal ( '7.325' ) . quantize ( Decimal ( '1.' ), rounding = ROUND_UP ) Decimal('8') As shown above, the getcontext() function accesses the current context and allows the settings to be changed. This approach meets the needs of most applications. For more advanced work, it may be useful to create alternate contexts using the Context() constructor. To make an alternate active, use the setcontext() function. In accordance with the standard, the decimal module provides two ready to use standard contexts, BasicContext and ExtendedContext . The former is especially useful for debugging because many of the traps are enabled: >>> myothercontext = Context ( prec = 60 , rounding = ROUND_HALF_DOWN ) >>> setcontext ( myothercontext ) >>> Decimal ( 1 ) / Decimal ( 7 ) Decimal('0.142857142857142857142857142857142857142857142857142857142857') >>> ExtendedContext Context(prec=9, rounding=ROUND_HALF_EVEN, Emin=-999999, Emax=999999, capitals=1, clamp=0, flags=[], traps=[]) >>> setcontext ( ExtendedContext ) >>> Decimal ( 1 ) / Decimal ( 7 ) Decimal('0.142857143') >>> Decimal ( 42 ) / Decimal ( 0 ) Decimal('Infinity') >>> setcontext ( BasicContext ) >>> Decimal ( 42 ) / Decimal ( 0 ) Traceback (most recent call last): File "<pyshell#143>" , line 1 , in -toplevel- Decimal ( 42 ) / Decimal ( 0 ) DivisionByZero : x / 0 Contexts also have signal flags for monitoring exceptional conditions encountered during computations. The flags remain set until explicitly cleared, so it is best to clear the flags before each set of monitored computations by using the clear_flags() method. >>> setcontext ( ExtendedContext ) >>> getcontext () . clear_flags () >>> Decimal ( 355 ) / Decimal ( 113 ) Decimal('3.14159292') >>> getcontext () Context(prec=9, rounding=ROUND_HALF_EVEN, Emin=-999999, Emax=999999, capitals=1, clamp=0, flags=[Inexact, Rounded], traps=[]) The flags entry shows that the rational approximation to pi was rounded (digits beyond the context precision were thrown away) and that the result is inexact (some of the discarded digits were non-zero). Individual traps are set using the dictionary in the traps attribute of a context: >>> setcontext ( ExtendedContext ) >>> Decimal ( 1 ) / Decimal ( 0 ) Decimal('Infinity') >>> getcontext () . traps [ DivisionByZero ] = 1 >>> Decimal ( 1 ) / Decimal ( 0 ) Traceback (most recent call last): File "<pyshell#112>" , line 1 , in -toplevel- Decimal ( 1 ) / Decimal ( 0 ) DivisionByZero : x / 0 Most programs adjust the current context only once, at the beginning of the program. And, in many applications, data is converted to Decimal with a single cast inside a loop. With context set and decimals created, the bulk of the program manipulates the data no differently than with other Python numeric types. Decimal objects ¶ class decimal. Decimal ( value = '0' , context = None ) ¶ Construct a new Decimal object based from value . value can be an integer, string, tuple, float , or another Decimal object. If no value is given, returns Decimal('0') . If value is a string, it should conform to the decimal numeric string syntax after leading and trailing whitespace characters, as well as underscores throughout, are removed: sign : := '+' | '-' digit : := '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' indicator : := 'e' | 'E' digits : := digit [ digit ] ... decimal - part : := digits '.' [ digits ] | [ '.' ] digits exponent - part : := indicator [ sign ] digits infinity : := 'Infinity' | 'Inf' nan : := 'NaN' [ digits ] | 'sNaN' [ digits ] numeric - value : := decimal - part [ exponent - part ] | infinity numeric - string : := [ sign ] numeric - value | [ sign ] nan Other Unicode decimal digits are also permitted where digit appears above. These include decimal digits from various other alphabets (for example, Arabic-Indic and Devanāgarī digits) along with the fullwidth digits '\uff10' through '\uff19' . Case is not significant, so, for example, inf , Inf , INFINITY , and iNfINity are all acceptable spellings for positive infinity. If value is a tuple , it should have three components, a sign ( 0 for positive or 1 for negative), a tuple of digits, and an integer exponent. For example, Decimal((0, (1, 4, 1, 4), -3)) returns Decimal('1.414') . If value is a float , the binary floating-point value is losslessly converted to its exact decimal equivalent. This conversion can often require 53 or more digits of precision. For example, Decimal(float('1.1')) converts to Decimal('1.100000000000000088817841970012523233890533447265625') . The context precision does not affect how many digits are stored. That is determined exclusively by the number of digits in value . For example, Decimal('3.00000') records all five zeros even if the context precision is only three. The purpose of the context argument is determining what to do if value is a malformed string. If the context traps InvalidOperation , an exception is raised; otherwise, the constructor returns a new Decimal with the value of NaN . Once constructed, Decimal objects are immutable. Changed in version 3.2: The argument to the constructor is now permitted to be a float instance. Changed in version 3.3: float arguments raise an exception if the FloatOperation trap is set. By default the trap is off. Changed in version 3.6: Underscores are allowed for grouping, as with integral and floating-point literals in code. Decimal floating-point objects share many properties with the other built-in numeric types such as float and int . All of the usual math operations and special methods apply. Likewise, decimal objects can be copied, pickled, printed, used as dictionary keys, used as set elements, compared, sorted, and coerced to another type (such as float or int ). There are some small differences between arithmetic on Decimal objects and arithmetic on integers and floats. When the remainder operator % is applied to Decimal objects, the sign of the result is the sign of the dividend rather than the sign of the divisor: >>> ( - 7 ) % 4 1 >>> Decimal ( - 7 ) % Decimal ( 4 ) Decimal('-3') The integer division operator // behaves analogously, returning the integer part of the true quotient (truncating towards zero) rather than its floor, so as to preserve the usual identity x == (x // y) * y + x % y : >>> - 7 // 4 -2 >>> Decimal ( - 7 ) // Decimal ( 4 ) Decimal('-1') The % and // operators implement the remainder and divide-integer operations (respectively) as described in the specification. Decimal objects cannot generally be combined with floats or instances of fractions.Fraction in arithmetic operations: an attempt to add a Decimal to a float , for example, will raise a TypeError . However, it is possible to use Python’s comparison operators to compare a Decimal instance x with another number y . This avoids confusing results when doing equality comparisons between numbers of different types. Changed in version 3.2: Mixed-type comparisons between Decimal instances and other numeric types are now fully supported. In addition to the standard numeric properties, decimal floating-point objects also have a number of specialized methods: adjusted ( ) ¶ Return the adjusted exponent after shifting out the coefficient’s rightmost digits until only the lead digit remains: Decimal('321e+5').adjusted() returns seven. Used for determining the position of the most significant digit with respect to the decimal point. as_integer_ratio ( ) ¶ Return a pair (n, d) of integers that represent the given Decimal instance as a fraction, in lowest terms and with a positive denominator: >>> Decimal ( '-3.14' ) . as_integer_ratio () (-157, 50) The conversion is exact. Raise OverflowError on infinities and ValueError on NaNs. Added in version 3.6. as_tuple ( ) ¶ Return a named tuple representation of the number: DecimalTuple(sign, digits, exponent) . canonical ( ) ¶ Return the canonical encoding of the argument. Currently, the encoding of a Decimal instance is always canonical, so this operation returns its argument unchanged. compare ( other , context = None ) ¶ Compare the values of two Decimal instances. compare() returns a Decimal instance, and if either operand is a NaN then the result is a NaN: a or b is a NaN ==> Decimal ( 'NaN' ) a < b ==> Decimal ( '-1' ) a == b ==> Decimal ( '0' ) a > b ==> Decimal ( '1' ) compare_signal ( other , context = None ) ¶ This operation is identical to the compare() method, except that all NaNs signal. That is, if neither operand is a signaling NaN then any quiet NaN operand is treated as though it were a signaling NaN. compare_total ( other , context = None ) ¶ Compare two operands using their abstract representation rather than their numerical value. Similar to the compare() method, but the result gives a total ordering on Decimal instances. Two Decimal instances with the same numeric value but different representations compare unequal in this ordering: >>> Decimal ( '12.0' ) . compare_total ( Decimal ( '12' )) Decimal('-1') Quiet and signaling NaNs are also included in the total ordering. The result of this function is Decimal('0') if both operands have the same representation, Decimal('-1') if the first operand is lower in the total order than the second, and Decimal('1') if the first operand is higher in the total order than the second operand. See the specification for details of the total order. This operation is unaffected by context and is quiet: no flags are changed and no rounding is performed. As an exception, the C version may raise InvalidOperation if the second operand cannot be converted exactly. compare_total_mag ( other , context = None ) ¶ Compare two operands using their abstract representation rather than their value as in compare_total() , but ignoring the sign of each operand. x.compare_total_mag(y) is equivalent to x.copy_abs().compare_total(y.copy_abs()) . This operation is unaffected by context and is quiet: no flags are changed and no rounding is performed. As an exception, the C version may raise InvalidOperation if the second operand cannot be converted exactly. conjugate ( ) ¶ Just returns self, this method is only to comply with the Decimal Specification. copy_abs ( ) ¶ Return the absolute value of the argument. This operation is unaffected by the context and is quiet: no flags are changed and no rounding is performed. copy_negate ( ) ¶ Return the negation of the argument. This operation is unaffected by the context and is quiet: no flags are changed and no rounding is performed. copy_sign ( other , context = None ) ¶ Return a copy of the first operand with the sign set to be the same as the sign of the second operand. For example: >>> Decimal ( '2.3' ) . copy_sign ( Decimal ( '-1.5' )) Decimal('-2.3') This operation is unaffected by context and is quiet: no flags are changed and no rounding is performed. As an exception, the C version may raise InvalidOperation if the second operand cannot be converted exactly. exp ( context = None ) ¶ Return the value of the (natural) exponential function e**x at the given number. The result is correctly rounded using the ROUND_HALF_EVEN rounding mode. >>> Decimal ( 1 ) . exp () Decimal('2.718281828459045235360287471') >>> Decimal ( 321 ) . exp () Decimal('2.561702493119680037517373933E+139') classmethod from_float ( f , / ) ¶ Alternative constructor that only accepts instances of float or int . Note Decimal.from_float(0.1) is not the same as Decimal('0.1') . Since 0.1 is not exactly representable in binary floating point, the value is stored as the nearest representable value which is 0x1.999999999999ap-4 . That equivalent value in decimal is 0.1000000000000000055511151231257827021181583404541015625 . Note From Python 3.2 onwards, a Decimal instance can also be constructed directly from a float . >>> Decimal . from_float ( 0.1 ) Decimal('0.1000000000000000055511151231257827021181583404541015625') >>> Decimal . from_float ( float ( 'nan' )) Decimal('NaN') >>> Decimal . from_float ( float ( 'inf' )) Decimal('Infinity') >>> Decimal . from_float ( float ( '-inf' )) Decimal('-Infinity') Added in version 3.1. classmethod from_number ( number , / ) ¶ Alternative constructor that only accepts instances of float , int or Decimal , but not strings or tuples. >>> Decimal . from_number ( 314 ) Decimal('314') >>> Decimal . from_number ( 0.1 ) Decimal('0.1000000000000000055511151231257827021181583404541015625') >>> Decimal . from_number ( Decimal ( '3.14' )) Decimal('3.14') Added in version 3.14. fma ( other , third , context = None ) ¶ Fused multiply-add. Return self*other+third with no rounding of the intermediate product self*other. >>> Decimal ( 2 ) . fma ( 3 , 5 ) Decimal('11') is_canonical ( ) ¶ Return True if the argument is canonical and False otherwise. Currently, a Decimal instance is always canonical, so this operation always returns True . is_finite ( ) ¶ Return True if the argument is a finite number, and False if the argument is an infinity or a NaN. is_infinite ( ) ¶ Return True if the argument is either positive or negative infinity and False otherwise. is_nan ( ) ¶ Return True if the argument is a (quiet or signaling) NaN and False otherwise. is_normal ( context = None ) ¶ Return True if the argument is a normal finite number. Return False if the argument is zero, subnormal, infinite or a NaN. is_qnan ( ) ¶ Return True if the argument is a quiet NaN, and False otherwise. is_signed ( ) ¶ Return True if the argument has a negative sign and False otherwise. Note that zeros and NaNs can both carry signs. is_snan ( ) ¶ Return True if the argument is a signaling NaN and False otherwise. is_subnormal ( context = None ) ¶ Return True if the argument is subnormal, and False otherwise. is_zero ( ) ¶ Return True if the argument is a (positive or negative) zero and False otherwise. ln ( context = None ) ¶ Return the natural (base e) logarithm of the operand. The result is correctly rounded using the ROUND_HALF_EVEN rounding mode. log10 ( context = None ) ¶ Return the base ten logarithm of the operand. The result is correctly rounded using the ROUND_HALF_EVEN rounding mode. logb ( context = None ) ¶ For a nonzero number, return the adjusted exponent of its operand as a Decimal instance. If the operand is a zero then Decimal('-Infinity') is returned and the DivisionByZero flag is raised. If the operand is an infinity then Decimal('Infinity') is returned. logical_and ( other , context = None ) ¶ logical_and() is a logical operation which takes two logical operands (see Logical operands ). The result is the digit-wise and of the two operands. logical_invert ( context = None ) ¶ logical_invert() is a logical operation. The result is the digit-wise inversion of the operand. logical_or ( other , context = None ) ¶ logical_or() is a logical operation which takes two logical operands (see Logical operands ). The result is the digit-wise or of the two operands. logical_xor ( other , context = None ) ¶ logical_xor() is a logical operation which takes two logical operands (see Logical operands ). The result is the digit-wise exclusive or of the two operands. max ( other , context = None ) ¶ Like max(self, other) except that the context rounding rule is applied before returning and that NaN values are either signaled or ignored (depending on the context and whether they are signaling or quiet). max_mag ( other , context = None ) ¶ Similar to the max() method, but the comparison is done using the absolute values of the operands. min ( other , context = None ) ¶ Like min(self, other) except that the context rounding rule is applied before returning and that NaN values are either signaled or ignored (depending on the context and whether they are signaling or quiet). min_mag ( other , context = None ) ¶ Similar to the min() method, but the comparison is done using the absolute values of the operands. next_minus ( context = None ) ¶ Return the largest number representable in the given context (or in the current thread’s context if no context is given) that is smaller than the given operand. next_plus ( context = None ) ¶ Return the smallest number representable in the given context (or in the current thread’s context if no context is given) that is larger than the given operand. next_toward ( other , context = None ) ¶ If the two operands are unequal, return the number closest to the first operand in the direction of the second operand. If both operands are numerically equal, return a copy of the first operand with the sign set to be the same as the sign of the second operand. normalize ( context = None ) ¶ Used for producing canonical values of an equivalence class within either the current context or the specified context. This has the same semantics as the unary plus operation, except that if the final result is finite it is reduced to its simplest form, with all trailing zeros removed and its sign preserved. That is, while the coefficient is non-zero and a multiple of ten the coefficient is divided by ten and the exponent is incremented by 1. Otherwise (the coefficient is zero) the exponent is set to 0. In all cases the sign is unchanged. For example, Decimal('32.100') and Decimal('0.321000e+2') both normalize to the equivalent value Decimal('32.1') . Note that rounding is applied before reducing to simplest form. In the latest versions of the specification, this operation is also known as reduce . number_class ( context = None ) ¶ Return a string describing the class of the operand. The returned value is one of the following ten strings. "-Infinity" , indicating that the operand is negative infinity. "-Normal" , indicating that the operand is a negative normal number. "-Subnormal" , indicating that the operand is negative and subnormal. "-Zero" , indicating that the operand is a negative zero. "+Zero" , indicating that the operand is a positive zero. "+Subnormal" , indicating that the operand is positive and subnormal. "+Normal" , indicating that the operand is a positive normal number. "+Infinity" , indicating that the operand is positive infinity. "NaN" , indicating that the operand is a quiet NaN (Not a Number). "sNaN" , indicating that the operand is a signaling NaN. quantize ( exp , rounding = None , context = None ) ¶ Return a value equal to the first operand after rounding and having the exponent of the second operand. >>> Decimal ( '1.41421356' ) . quantize ( Decimal ( '1.000' )) Decimal('1.414') Unlike other operations, if the length of the coefficient after the quantize operation would be greater than precision, then an InvalidOperation is signaled. This guarantees that, unless there is an error condition, the quantized exponent is always equal to that of the right-hand operand. Also unlike other operations, quantize never signals Underflow, even if the result is subnormal and inexact. If the exponent of the second operand is larger than that of the first then rounding may be necessary. In this case, the rounding mode is determined by the rounding argument if given, else by the given context argument; if neither argument is given the rounding mode of the current thread’s context is used. An error is returned whenever the resulting exponent is greater than Emax or less than Etiny() . radix ( ) ¶ Return Decimal(10) , the radix (base) in which the Decimal class does all its arithmetic. Included for compatibility with the specification. remainder_near ( other , context = None ) ¶ Return the remainder from dividing self by other . This differs from self % other in that the sign of the remainder is chosen so as to minimize its absolute value. More precisely, the return value is self - n * other where n is the integer nearest to the exact value of self / other , and if two integers are equally near then the even one is chosen. If the result is zero then its sign will be the sign of self . >>> Decimal ( 18 ) . remainder_near ( Decimal ( 10 )) Decimal('-2') >>> Decimal ( 25 ) . remainder_near ( Decimal ( 10 )) Decimal('5') >>> Decimal ( 35 ) . remainder_near ( Decimal ( 10 )) Decimal('-5') rotate ( other , context = None ) ¶ Return the result of rotating the digits of the first operand by an amount specified by the second operand. The second operand must be an integer in the range -precision through precision. The absolute value of the second operand gives the number of places to rotate. If the second operand is positive then rotation is to the left; otherwise rotation is to the right. The coefficient of the first operand is padded on the left with zeros to length precision if necessary. The sign and exponent of the first operand are unchanged. same_quantum ( other , context = None ) ¶ Test whether self and other have the same exponent or whether both are NaN . This operation is unaffected by context and is quiet: no flags are changed and no rounding is performed. As an exception, the C version may raise InvalidOperation if the second operand cannot be converted exactly. scaleb ( other , context = None ) ¶ Return the first operand with exponent adjusted by the second. Equivalently, return the first operand multiplied by 10**other . The second operand must be an integer. shift ( other , context = None ) ¶ Return the result of shifting the digits of the first operand by an amount specified by the second operand. The second operand must be an integer in the range -precision through precision. The absolute value of the second operand gives the number of places to shift. If the second operand is positive then the shift is to the left; otherwise the shift is to the right. Digits shifted into the coefficient are zeros. The sign and exponent of the first operand are unchanged. sqrt ( context = None ) ¶ Return the square root of the argument to full precision. to_eng_string ( context = None ) ¶ Convert to a string, using engineering notation if an exponent is needed. Engineering notation has an exponent which is a multiple of 3. This can leave up to 3 digits to the left of the decimal place and may require the addition of either one or two trailing zeros. For example, this converts Decimal('123E+1') to Decimal('1.23E+3') . to_integral ( rounding = None , context = None ) ¶ Identical to the to_integral_value() method. The to_integral name has been kept for compatibility with older versions. to_integral_exact ( rounding = None , context = None ) ¶ Round to the nearest integer, signaling Inexact or Rounded as appropriate if rounding occurs. The rounding mode is determined by the rounding parameter if given, else by the given context . If neither parameter is given then the rounding mode of the current context is used. to_integral_value ( rounding = None , context = None ) ¶ Round to the nearest integer without signaling Inexact or Rounded . If given, applies rounding ; otherwise, uses the rounding method in either the supplied context or the current context. Decimal numbers can be rounded using the round() function: round(number) round(number, ndigits) If ndigits is not given or None , returns the nearest int to number , rounding ties to even, and ignoring the rounding mode of the Decimal context. Raises OverflowError if number is an infinity or ValueError if it is a (quiet or signaling) NaN. If ndigits is an int , the context’s rounding mode is respected and a Decimal representing number rounded to the nearest multiple of Decimal('1E-ndigits') is returned; in this case, round(number, ndigits) is equivalent to self.quantize(Decimal('1E-ndigits')) . Returns Decimal('NaN') if number is a quiet NaN. Raises InvalidOperation if number is an infinity, a signaling NaN, or if the length of the coefficient after the quantize operation would be greater than the current context’s precision. In other words, for the non-corner cases: if ndigits is positive, return number rounded to ndigits decimal places; if ndigits is zero, return number rounded to the nearest integer; if ndigits is negative, return number rounded to the nearest multiple of 10**abs(ndigits) . For example: >>> from decimal import Decimal , getcontext , ROUND_DOWN >>> getcontext () . rounding = ROUND_DOWN >>> round ( Decimal ( '3.75' )) # context rounding ignored 4 >>> round ( Decimal ( '3.5' )) # round-ties-to-even 4 >>> round ( Decimal ( '3.75' ), 0 ) # uses the context rounding Decimal('3') >>> round ( Decimal ( '3.75' ), 1 ) Decimal('3.7') >>> round ( Decimal ( '3.75' ), - 1 ) Decimal('0E+1') Logical operands ¶ The logical_and() , logical_invert() , logical_or() , and logical_xor() methods expect their arguments to be logical operands . A logical operand is a Decimal instance whose exponent and sign are both zero, and whose digits are all either 0 or 1 . Context objects ¶ Contexts are environments for arithmetic operations. They govern precision, set rules for rounding, determine which signals are treated as exceptions, and limit the range for exponents. Each thread has its own current context which is accessed or changed using the getcontext() and setcontext() functions: decimal. getcontext ( ) ¶ Return the current context for the active thread. decimal. setcontext ( c , / ) ¶ Set the current context for the active thread to c . You can also use the with statement and the localcontext() function to temporarily change the active context. decimal. localcontext ( ctx = None , ** kwargs ) ¶ Return a context manager that will set the current context for the active thread to a copy of ctx on entry to the with-statement and restore the previous context when exiting the with-statement. If no context is specified, a copy of the current context is used. The kwargs argument is used to set the attributes of the new context. For example, the following code sets the current decimal precision to 42 places, performs a calculation, and then automatically restores the previous context: from decimal import localcontext with localcontext () as ctx : ctx . prec = 42 # Perform a high precision calculation s = calculate_something () s = + s # Round the final result back to the default precision Using keyword arguments, the code would be the following: from decimal import localcontext with localcontext ( prec = 42 ) as ctx : s = calculate_something () s = + s Raises TypeError if kwargs supplies an attribute that Context doesn’t support. Raises either TypeError or ValueError if kwargs supplies an invalid value for an attribute. Changed in version 3.11: localcontext() now supports setting context attributes through the use of keyword arguments. decimal. IEEEContext ( bits ) ¶ Return a context object initialized to the proper values for one of the IEEE interchange formats. The argument must be a multiple of 32 and less than IEEE_CONTEXT_MAX_BITS . Added in version 3.14. New contexts can also be created using the Context constructor described below. In addition, the module provides three pre-made contexts: decimal. BasicContext ¶ This is a standard context defined by the General Decimal Arithmetic Specification. Precision is set to nine. Rounding is set to ROUND_HALF_UP . All flags are cleared. All traps are enabled (treated as exceptions) except Inexact , Rounded , and Subnormal . Because many of the traps are enabled, this context is useful for debugging. decimal. ExtendedContext ¶ This is a standard context defined by the General Decimal Arithmetic Specification. Precision is set to nine. Rounding is set to ROUND_HALF_EVEN . All flags are cleared. No traps are enabled (so that exceptions are not raised during computations). Because the traps are disabled, this context is useful for applications that prefer to have result value of NaN or Infinity instead of raising exceptions. This allows an application to complete a run in the presence of conditions that would otherwise halt the program. decimal. DefaultContext ¶ This context is used by the Context constructor as a prototype for new contexts. Changing a field (such a precision) has the effect of changing the default for new contexts created by the Context constructor. This context is most useful in multi-threaded environments. Changing one of the fields before threads are started has the effect of setting system-wide defaults. Changing the fields after threads have started is not recommended as it would require thread synchronization to prevent race conditions. In single threaded environments, it is preferable to not use this context at all. Instead, simply create contexts explicitly as described below. The default values are Context.prec = 28 , Context.rounding = ROUND_HALF_EVEN , and enabled traps for Overflow , InvalidOperation , and DivisionByZero . In addition to the three supplied contexts, new contexts can be created with the Context constructor. class decimal. Context ( prec = None , rounding = None , Emin = None , Emax = None , capitals = None , clamp = None , flags = None , traps = None ) ¶ Creates a new context. If a field is not specified or is None , the default values are copied from the DefaultContext . If the flags field is not specified or is None , all flags are cleared. prec ¶ An integer in the range [ 1 , MAX_PREC ] that sets the precision for arithmetic operations in the context. rounding ¶ One of the constants listed in the section Rounding Modes . traps ¶ flags ¶ Lists of any signals to be set. Generally, new contexts should only set traps and leave the flags clear. Emin ¶ Emax ¶ Integers specifying the outer limits allowable for exponents. Emin must be in the range [ MIN_EMIN , 0 ], Emax in the range [ 0 , MAX_EMAX ]. capitals ¶ Either 0 or 1 (the default). If set to 1 , exponents are printed with a capital E ; otherwise, a lowercase e is used: Decimal('6.02e+23') . clamp ¶ Either 0 (the default) or 1 . If set to 1 , the exponent e of a Decimal instance representable in this context is strictly limited to the range Emin - prec + 1 <= e <= Emax - prec + 1 . If clamp is 0 then a weaker condition holds: the adjusted exponent of the Decimal instance is at most Emax . When clamp is 1 , a large normal number will, where possible, have its exponent reduced and a corresponding number of zeros added to its coefficient, in order to fit the exponent constraints; this preserves the value of the number but loses information about significant trailing zeros. For example: >>> Context ( prec = 6 , Emax = 999 , clamp = 1 ) . create_decimal ( '1.23e999' ) Decimal('1.23000E+999') A clamp value of 1 allows compatibility with the fixed-width decimal interchange formats specified in IEEE 754. The Context class defines several general purpose methods as well as a large number of methods for doing arithmetic directly in a given context. In addition, for each of the Decimal methods described above (with the exception of the adjusted() and as_tuple() methods) there is a corresponding Context method. For example, for a Context instance C and Decimal instance x , C.exp(x) is equivalent to x.exp(context=C) . Each Context method accepts a Python integer (an instance of int ) anywhere that a Decimal instance is accepted. clear_flags ( ) ¶ Resets all of the flags to 0 . clear_traps ( ) ¶ Resets all of the traps to 0 . Added in version 3.3. copy ( ) ¶ Return a duplicate of the context. copy_decimal ( num , / ) ¶ Return a copy of the Decimal instance num. create_decimal ( num = '0' , / ) ¶ Creates a new Decimal instance from num but using self as context. Unlike the Decimal constructor, the context precision, rounding method, flags, and traps are applied to the conversion. This is useful because constants are often given to a greater precision than is needed by the application. Another benefit is that rounding immediately eliminates unintended effects from digits beyond the current precision. In the following example, using unrounded inputs means that adding zero to a sum can change the result: >>> getcontext () . prec = 3 >>> Decimal ( '3.4445' ) + Decimal ( '1.0023' ) Decimal('4.45') >>> Decimal ( '3.4445' ) + Decimal ( 0 ) + Decimal ( '1.0023' ) Decimal('4.44') This method implements the to-number operation of the IBM specification. If the argument is a string, no leading or trailing whitespace or underscores are permitted. create_decimal_from_float ( f , / ) ¶ Creates a new Decimal instance from a float f but rounding using self as the context. Unlike the Decimal.from_float() class method, the context precision, rounding method, flags, and traps are applied to the conversion. >>> context = Context ( prec = 5 , rounding = ROUND_DOWN ) >>> context . create_decimal_from_float ( math . pi ) Decimal('3.1415') >>> context = Context ( prec = 5 , traps = [ Inexact ]) >>> context . create_decimal_from_float ( math . pi ) Traceback (most recent call last): ... decimal.Inexact : None Added in version 3.1. Etiny ( ) ¶ Returns a value equal to Emin - prec + 1 which is the minimum exponent value for subnormal results. When underflow occurs, the exponent is set to Etiny . Etop ( ) ¶ Returns a value equal to Emax - prec + 1 . The usual approach to working with decimals is to create Decimal instances and then apply arithmetic operations which take place within the current context for the active thread. An alternative approach is to use context methods for calculating within a specific context. The methods are similar to those for the Decimal class and are only briefly recounted here. abs ( x , / ) ¶ Returns the absolute value of x . add ( x , y , / ) ¶ Return the sum of x and y . canonical ( x , / ) ¶ Returns the same Decimal object x . compare ( x , y , / ) ¶ Compares x and y numerically. compare_signal ( x , y , / ) ¶ Compares the values of the two operands numerically. compare_total ( x , y , / ) ¶ Compares two operands using their abstract representation. compare_total_mag ( x , y , / ) ¶ Compares two operands using their abstract representation, ignoring sign. copy_abs ( x , / ) ¶ Returns a copy of x with the sign set to 0. copy_negate ( x , / ) ¶ Returns a copy of x with the sign inverted. copy_sign ( x , y , / ) ¶ Copies the sign from y to x . divide ( x , y , / ) ¶ Return x divided by y . divide_int ( x , y , / ) ¶ Return x divided by y , truncated to an integer. divmod ( x , y , / ) ¶ Divides two numbers and returns the integer part of the result. exp ( x , / ) ¶ Returns e ** x . fma ( x , y , z , / ) ¶ Returns x multiplied by y , plus z . is_canonical ( x , / ) ¶ Returns True if x is canonical; otherwise returns False . is_finite ( x , / ) ¶ Returns True if x is finite; otherwise returns False . is_infinite ( x , / ) ¶ Returns True if x is infinite; otherwise returns False . is_nan ( x , / ) ¶ Returns True if x is a qNaN or sNaN; otherwise returns False . is_normal ( x , / ) ¶ Returns True if x is a normal number; otherwise returns False . is_qnan ( x , / ) ¶ Returns True if x is a quiet NaN; otherwise returns False . is_signed ( x , / ) ¶ Returns True if x is negative; otherwise returns False . is_snan ( x , / ) ¶ Returns True if x is a signaling NaN; otherwise returns False . is_subnormal ( x , / ) ¶ Returns True if x is subnormal; otherwise returns False . is_zero ( x , / ) ¶ Returns True if x is a zero; otherwise returns False . ln ( x , / ) ¶ Returns the natural (base e) logarithm of x . log10 ( x , / ) ¶ Returns the base 10 logarithm of x . logb ( x , / ) ¶ Returns the exponent of the magnitude of the operand’s MSD. logical_and ( x , y , / ) ¶ Applies the logical operation and between each operand’s digits. logical_invert ( x , / ) ¶ Invert all the digits in x . logical_or ( x , y , / ) ¶ Applies the logical operation or between each operand’s digits. logical_xor ( x , y , / ) ¶ Applies the logical operation xor between each operand’s digits. max ( x , y , / ) ¶ Compares two values numerically and returns the maximum. max_mag ( x , y , / ) ¶ Compares the values numerically with their sign ignored. min ( x , y , / ) ¶ Compares two values numerically and returns the minimum. min_mag ( x , y , / ) ¶ Compares the values numerically with their sign ignored. minus ( x , / ) ¶ Minus corresponds to the unary prefix minus operator in Python. multiply ( x , y , / ) ¶ Return the product of x and y . next_minus ( x , / ) ¶ Returns the largest representable number smaller than x . next_plus ( x , / ) ¶ Returns the smallest representable number larger than x . next_toward ( x , y , / ) ¶ Returns the number closest to x , in direction towards y . normalize ( x , / ) ¶ Reduces x to its simplest form. number_class ( x , / ) ¶ Returns an indication of the class of x . plus ( x , / ) ¶ Plus corresponds to the unary prefix plus operator in Python. This operation applies the context precision and rounding, so it is not an identity operation. power ( x , y , modulo = None ) ¶ Return x to the power of y , reduced modulo modulo if given. With two arguments, compute x**y . If x is negative then y must be integral. The result will be inexact unless y is integral and the result is finite and can be expressed exactly in ‘precision’ digits. The rounding mode of the context is used. Results are always correctly rounded in the Python version. Decimal(0) ** Decimal(0) results in InvalidOperation , and if InvalidOperation is not trapped, then results in Decimal('NaN') . Changed in version 3.3: The C module computes power() in terms of the correctly rounded exp() and ln() functions. The result is well-defined but only “almost always correctly rounded”. With three arguments, compute (x**y) % modulo . For the three argument form, the following restrictions on the arguments hold: all three arguments must be integral y must be nonnegative at least one of x or y must be nonzero modulo must be nonzero and have at most ‘precision’ digits The value resulting from Context.power(x, y, modulo) is equal to the value that would be obtained by computing (x**y) % modulo with unbounded precision, but is computed more efficiently. The exponent of the result is zero, regardless of the exponents of x , y and modulo . The result is always exact. quantize ( x , y , / ) ¶ Returns a value equal to x (rounded), having the exponent of y . radix ( ) ¶ Just returns 10, as this is Decimal, :) remainder ( x , y , / ) ¶ Returns the remainder from integer division. The sign of the result, if non-zero, is the same as that of the original dividend. remainder_ne | 2026-01-13T08:48:41 |
https://dev.to/t/mentalhealth/page/2 | Mental Health 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 Mental Health Follow Hide Mental health matters! Break the stigma. We can empower ourselves and each other to invest in our mental health. We can give support and care to ourselves and each other while we struggle. Let's talk about making our mental health priority. Create Post about #mentalhealth Posts should be related to mental health. This is a pretty wide category but some things that are included are: Managing mental health as a developer Living with mental illness and how it affects your work Ways to cope with mental health issues Avoiding burn out Tools, apps, and methods that help you with your mental health ...and more “Your mental health is a priority. Your happiness is an essential. Your self-care is a necessity.” Struggling? Help is out there. Click here to find a list of global mental health resources and hotlines. Older #mentalhealth 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 How to Reduce AI Dependency While Still Using It Daily James Patterson James Patterson James Patterson Follow Jan 2 How to Reduce AI Dependency While Still Using It Daily # ai # mentalhealth # productivity Comments Add Comment 2 min read How to Stay Connected as a Couple During High-Stress Seasons Daily Dose Of Dee Daily Dose Of Dee Daily Dose Of Dee Follow Jan 2 How to Stay Connected as a Couple During High-Stress Seasons # watercooler # mentalhealth # motivation Comments Add Comment 2 min read Voice Journaling for Mental Clarity: How to Build Your Own AI-Powered Reflection Tool wellallyTech wellallyTech wellallyTech Follow Jan 6 Voice Journaling for Mental Clarity: How to Build Your Own AI-Powered Reflection Tool # ai # openai # node # mentalhealth Comments Add Comment 2 min read I Built a Mental Health SaaS for Entrepreneurs - Here's the Tech Stack Ben Stone Ben Stone Ben Stone Follow Jan 1 I Built a Mental Health SaaS for Entrepreneurs - Here's the Tech Stack # startup # nextjs # saas # mentalhealth Comments Add Comment 1 min read Best Buddhist Temples in the World: A Journey Through Global Spiritual Heritage Naman Saxena Naman Saxena Naman Saxena Follow Jan 3 Best Buddhist Temples in the World: A Journey Through Global Spiritual Heritage # watercooler # mentalhealth # resources 1 reaction Comments Add Comment 4 min read Il Bug della Dignità: Cronaca di un’illusione ereditaria Michele Carino Michele Carino Michele Carino Follow Dec 30 '25 Il Bug della Dignità: Cronaca di un’illusione ereditaria # discuss # career # mentalhealth Comments Add Comment 2 min read Human dignity bug: chronicles of an inherited delusion Michele Carino Michele Carino Michele Carino Follow Dec 30 '25 Human dignity bug: chronicles of an inherited delusion # discuss # career # mentalhealth Comments Add Comment 2 min read Why Gamification Actually Works for Developer Productivity (And Why I Was Wrong to Dismiss It) Lux Seminare Lux Seminare Lux Seminare Follow Dec 31 '25 Why Gamification Actually Works for Developer Productivity (And Why I Was Wrong to Dismiss It) # developer # motivation # mentalhealth # productivity Comments Add Comment 9 min read How I Stay Healthy While Working 250 Hours a Month as a Software Engineer ryo ariyama ryo ariyama ryo ariyama Follow Dec 30 '25 How I Stay Healthy While Working 250 Hours a Month as a Software Engineer # webdev # programming # mentalhealth # softwareengineering Comments Add Comment 3 min read Why SWEs are afraid of making mistakes TechPreneur: lesswork&earnmore TechPreneur: lesswork&earnmore TechPreneur: lesswork&earnmore Follow Jan 2 Why SWEs are afraid of making mistakes # beginners # career # mentalhealth Comments Add Comment 13 min read I Tried a 7-Day Dopamine Detox: The Hardest Part Wasn’t What I Expected yusuf yonturk yusuf yonturk yusuf yonturk Follow Dec 29 '25 I Tried a 7-Day Dopamine Detox: The Hardest Part Wasn’t What I Expected # discuss # productivity # mentalhealth # devlife Comments Add Comment 4 min read How to Build Stability With Variable Income Brian Davies Brian Davies Brian Davies Follow Jan 2 How to Build Stability With Variable Income # career # mentalhealth # productivity Comments Add Comment 3 min read Not Everything Is Late. Zainab Zainab Zainab Follow Dec 28 '25 Not Everything Is Late. # discuss # career # learning # mentalhealth Comments Add Comment 3 min read Standing Alone Before God -Into a New Year Congo Musah Congo Musah Congo Musah Follow Dec 31 '25 Standing Alone Before God -Into a New Year # discuss # mentalhealth # watercooler 1 reaction Comments Add Comment 2 min read 7 Breakup Recovery App Strategies to Heal Faster in 2026 Anas Kayssi Anas Kayssi Anas Kayssi Follow Jan 9 7 Breakup Recovery App Strategies to Heal Faster in 2026 # mentalhealth # digitalwellbeing # selfimprovement # techtools Comments Add Comment 8 min read 7 AI Girlfriend App Strategies to Overcome Social Anxiety in 2026 Anas Kayssi Anas Kayssi Anas Kayssi Follow Jan 9 7 AI Girlfriend App Strategies to Overcome Social Anxiety in 2026 # ai # mentalhealth # techethics # developercommunity Comments Add Comment 7 min read Choosing Yourself Without Guilt: A Lesson I Learned the Hard Way as a Developer Zainab Zainab Zainab Follow for CareerByteCode Dec 28 '25 Choosing Yourself Without Guilt: A Lesson I Learned the Hard Way as a Developer # devjournal # career # productivity # mentalhealth 1 reaction Comments Add Comment 3 min read Developer Burnout: How Your Git History Can Improve Your Well-Beinga wellallyTech wellallyTech wellallyTech Follow Dec 24 '25 Developer Burnout: How Your Git History Can Improve Your Well-Beinga # python # datascience # mentalhealth # machinelearning Comments Add Comment 2 min read Suffering = Pain * Resistance (and the Role of Self-Compassion) munyoki_kilyungi munyoki_kilyungi munyoki_kilyungi Follow Jan 6 Suffering = Pain * Resistance (and the Role of Self-Compassion) # discuss # mentalhealth # watercooler Comments Add Comment 3 min read 2025 Yearly Recap Dany Paredes Dany Paredes Dany Paredes Follow Dec 28 '25 2025 Yearly Recap # devjournal # mentalhealth # writing 1 reaction Comments Add Comment 2 min read Why I Built Eunonix: From Chaos to Clarity Aniket Sharma Aniket Sharma Aniket Sharma Follow Dec 18 '25 Why I Built Eunonix: From Chaos to Clarity # productivity # startup # mentalhealth Comments Add Comment 2 min read Why Mental Health Issues Are Rising (And What Modern Life Is Doing to Our Brains) NVelUp NVelUp NVelUp Follow Dec 17 '25 Why Mental Health Issues Are Rising (And What Modern Life Is Doing to Our Brains) # mentalhealth Comments Add Comment 3 min read In Defense of Rudolph (and Against State-Sanctioned Reindeer Bullying) John Napiorkowski John Napiorkowski John Napiorkowski Follow Dec 14 '25 In Defense of Rudolph (and Against State-Sanctioned Reindeer Bullying) # watercooler # leadership # mentalhealth # discuss Comments Add Comment 3 min read Refactoring Legacy Code in the Human OS: Why Developers Need a Different Kind of Debugger Aleksei Sergeevich Aleksei Sergeevich Aleksei Sergeevich Follow Dec 12 '25 Refactoring Legacy Code in the Human OS: Why Developers Need a Different Kind of Debugger # productivity # career # mentalhealth # softskills Comments Add Comment 1 min read Ready to Quit LeetCode? Here's How to Push Through Alex Hunter Alex Hunter Alex Hunter Follow Dec 11 '25 Ready to Quit LeetCode? Here's How to Push Through # mentalhealth # motivation # studytips # anxiety Comments Add Comment 8 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:48:41 |
https://docs.python.org/3/library/ssl.html#module-ssl | ssl — TLS/SSL wrapper for socket objects — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents ssl — TLS/SSL wrapper for socket objects Functions, Constants, and Exceptions Socket creation Context creation Exceptions Random generation Certificate handling Constants SSL Sockets SSL Contexts Certificates Certificate chains CA certificates Combined key and certificate Self-signed certificates Examples Testing for SSL support Client-side operation Server-side operation Notes on non-blocking sockets Memory BIO Support SSL session Security considerations Best defaults Manual settings Verifying certificates Protocol versions Cipher selection Multi-processing TLS 1.3 Previous topic socket — Low-level networking interface Next topic select — Waiting for I/O completion This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Networking and Interprocess Communication » ssl — TLS/SSL wrapper for socket objects | Theme Auto Light Dark | ssl — TLS/SSL wrapper for socket objects ¶ Source code: Lib/ssl.py This module provides access to Transport Layer Security (often known as “Secure Sockets Layer”) encryption and peer authentication facilities for network sockets, both client-side and server-side. This module uses the OpenSSL library. This is an optional module . If it is missing from your copy of CPython, look for documentation from your distributor (that is, whoever provided Python to you). If you are the distributor, see Requirements for optional modules . Note Some behavior may be platform dependent, since calls are made to the operating system socket APIs. The installed version of OpenSSL may also cause variations in behavior. For example, TLSv1.3 comes with OpenSSL version 1.1.1. Warning Don’t use this module without reading the Security considerations . Doing so may lead to a false sense of security, as the default settings of the ssl module are not necessarily appropriate for your application. Availability : not WASI. This module does not work or is not available on WebAssembly. See WebAssembly platforms for more information. This section documents the objects and functions in the ssl module; for more general information about TLS, SSL, and certificates, the reader is referred to the documents in the “See Also” section at the bottom. This module provides a class, ssl.SSLSocket , which is derived from the socket.socket type, and provides a socket-like wrapper that also encrypts and decrypts the data going over the socket with SSL. It supports additional methods such as getpeercert() , which retrieves the certificate of the other side of the connection, cipher() , which retrieves the cipher being used for the secure connection or get_verified_chain() , get_unverified_chain() which retrieves certificate chain. For more sophisticated applications, the ssl.SSLContext class helps manage settings and certificates, which can then be inherited by SSL sockets created through the SSLContext.wrap_socket() method. Changed in version 3.5.3: Updated to support linking with OpenSSL 1.1.0 Changed in version 3.6: OpenSSL 0.9.8, 1.0.0 and 1.0.1 are deprecated and no longer supported. In the future the ssl module will require at least OpenSSL 1.0.2 or 1.1.0. Changed in version 3.10: PEP 644 has been implemented. The ssl module requires OpenSSL 1.1.1 or newer. Use of deprecated constants and functions result in deprecation warnings. Functions, Constants, and Exceptions ¶ Socket creation ¶ Instances of SSLSocket must be created using the SSLContext.wrap_socket() method. The helper function create_default_context() returns a new context with secure default settings. Client socket example with default context and IPv4/IPv6 dual stack: import socket import ssl hostname = 'www.python.org' context = ssl . create_default_context () with socket . create_connection (( hostname , 443 )) as sock : with context . wrap_socket ( sock , server_hostname = hostname ) as ssock : print ( ssock . version ()) Client socket example with custom context and IPv4: hostname = 'www.python.org' # PROTOCOL_TLS_CLIENT requires valid cert chain and hostname context = ssl . SSLContext ( ssl . PROTOCOL_TLS_CLIENT ) context . load_verify_locations ( 'path/to/cabundle.pem' ) with socket . socket ( socket . AF_INET , socket . SOCK_STREAM , 0 ) as sock : with context . wrap_socket ( sock , server_hostname = hostname ) as ssock : print ( ssock . version ()) Server socket example listening on localhost IPv4: context = ssl . SSLContext ( ssl . PROTOCOL_TLS_SERVER ) context . load_cert_chain ( '/path/to/certchain.pem' , '/path/to/private.key' ) with socket . socket ( socket . AF_INET , socket . SOCK_STREAM , 0 ) as sock : sock . bind (( '127.0.0.1' , 8443 )) sock . listen ( 5 ) with context . wrap_socket ( sock , server_side = True ) as ssock : conn , addr = ssock . accept () ... Context creation ¶ A convenience function helps create SSLContext objects for common purposes. ssl. create_default_context ( purpose = Purpose.SERVER_AUTH , * , cafile = None , capath = None , cadata = None ) ¶ Return a new SSLContext object with default settings for the given purpose . The settings are chosen by the ssl module, and usually represent a higher security level than when calling the SSLContext constructor directly. cafile , capath , cadata represent optional CA certificates to trust for certificate verification, as in SSLContext.load_verify_locations() . If all three are None , this function can choose to trust the system’s default CA certificates instead. The settings are: PROTOCOL_TLS_CLIENT or PROTOCOL_TLS_SERVER , OP_NO_SSLv2 , and OP_NO_SSLv3 with high encryption cipher suites without RC4 and without unauthenticated cipher suites. Passing SERVER_AUTH as purpose sets verify_mode to CERT_REQUIRED and either loads CA certificates (when at least one of cafile , capath or cadata is given) or uses SSLContext.load_default_certs() to load default CA certificates. When keylog_filename is supported and the environment variable SSLKEYLOGFILE is set, create_default_context() enables key logging. The default settings for this context include VERIFY_X509_PARTIAL_CHAIN and VERIFY_X509_STRICT . These make the underlying OpenSSL implementation behave more like a conforming implementation of RFC 5280 , in exchange for a small amount of incompatibility with older X.509 certificates. Note The protocol, options, cipher and other settings may change to more restrictive values anytime without prior deprecation. The values represent a fair balance between compatibility and security. If your application needs specific settings, you should create a SSLContext and apply the settings yourself. Note If you find that when certain older clients or servers attempt to connect with a SSLContext created by this function that they get an error stating “Protocol or cipher suite mismatch”, it may be that they only support SSL3.0 which this function excludes using the OP_NO_SSLv3 . SSL3.0 is widely considered to be completely broken . If you still wish to continue to use this function but still allow SSL 3.0 connections you can re-enable them using: ctx = ssl . create_default_context ( Purpose . CLIENT_AUTH ) ctx . options &= ~ ssl . OP_NO_SSLv3 Note This context enables VERIFY_X509_STRICT by default, which may reject pre- RFC 5280 or malformed certificates that the underlying OpenSSL implementation otherwise would accept. While disabling this is not recommended, you can do so using: ctx = ssl . create_default_context () ctx . verify_flags &= ~ ssl . VERIFY_X509_STRICT Added in version 3.4. Changed in version 3.4.4: RC4 was dropped from the default cipher string. Changed in version 3.6: ChaCha20/Poly1305 was added to the default cipher string. 3DES was dropped from the default cipher string. Changed in version 3.8: Support for key logging to SSLKEYLOGFILE was added. Changed in version 3.10: The context now uses PROTOCOL_TLS_CLIENT or PROTOCOL_TLS_SERVER protocol instead of generic PROTOCOL_TLS . Changed in version 3.13: The context now uses VERIFY_X509_PARTIAL_CHAIN and VERIFY_X509_STRICT in its default verify flags. Exceptions ¶ exception ssl. SSLError ¶ Raised to signal an error from the underlying SSL implementation (currently provided by the OpenSSL library). This signifies some problem in the higher-level encryption and authentication layer that’s superimposed on the underlying network connection. This error is a subtype of OSError . The error code and message of SSLError instances are provided by the OpenSSL library. Changed in version 3.3: SSLError used to be a subtype of socket.error . library ¶ A string mnemonic designating the OpenSSL submodule in which the error occurred, such as SSL , PEM or X509 . The range of possible values depends on the OpenSSL version. Added in version 3.3. reason ¶ A string mnemonic designating the reason this error occurred, for example CERTIFICATE_VERIFY_FAILED . The range of possible values depends on the OpenSSL version. Added in version 3.3. exception ssl. SSLZeroReturnError ¶ A subclass of SSLError raised when trying to read or write and the SSL connection has been closed cleanly. Note that this doesn’t mean that the underlying transport (read TCP) has been closed. Added in version 3.3. exception ssl. SSLWantReadError ¶ A subclass of SSLError raised by a non-blocking SSL socket when trying to read or write data, but more data needs to be received on the underlying TCP transport before the request can be fulfilled. Added in version 3.3. exception ssl. SSLWantWriteError ¶ A subclass of SSLError raised by a non-blocking SSL socket when trying to read or write data, but more data needs to be sent on the underlying TCP transport before the request can be fulfilled. Added in version 3.3. exception ssl. SSLSyscallError ¶ A subclass of SSLError raised when a system error was encountered while trying to fulfill an operation on a SSL socket. Unfortunately, there is no easy way to inspect the original errno number. Added in version 3.3. exception ssl. SSLEOFError ¶ A subclass of SSLError raised when the SSL connection has been terminated abruptly. Generally, you shouldn’t try to reuse the underlying transport when this error is encountered. Added in version 3.3. exception ssl. SSLCertVerificationError ¶ A subclass of SSLError raised when certificate validation has failed. Added in version 3.7. verify_code ¶ A numeric error number that denotes the verification error. verify_message ¶ A human readable string of the verification error. exception ssl. CertificateError ¶ An alias for SSLCertVerificationError . Changed in version 3.7: The exception is now an alias for SSLCertVerificationError . Random generation ¶ ssl. RAND_bytes ( num , / ) ¶ Return num cryptographically strong pseudo-random bytes. Raises an SSLError if the PRNG has not been seeded with enough data or if the operation is not supported by the current RAND method. RAND_status() can be used to check the status of the PRNG and RAND_add() can be used to seed the PRNG. For almost all applications os.urandom() is preferable. Read the Wikipedia article, Cryptographically secure pseudorandom number generator (CSPRNG) , to get the requirements of a cryptographically strong generator. Added in version 3.3. ssl. RAND_status ( ) ¶ Return True if the SSL pseudo-random number generator has been seeded with ‘enough’ randomness, and False otherwise. You can use ssl.RAND_egd() and ssl.RAND_add() to increase the randomness of the pseudo-random number generator. ssl. RAND_add ( bytes , entropy , / ) ¶ Mix the given bytes into the SSL pseudo-random number generator. The parameter entropy (a float) is a lower bound on the entropy contained in string (so you can always use 0.0 ). See RFC 1750 for more information on sources of entropy. Changed in version 3.5: Writable bytes-like object is now accepted. Certificate handling ¶ ssl. cert_time_to_seconds ( cert_time ) ¶ Return the time in seconds since the Epoch, given the cert_time string representing the “notBefore” or “notAfter” date from a certificate in "%b %d %H:%M:%S %Y %Z" strptime format (C locale). Here’s an example: >>> import ssl >>> timestamp = ssl . cert_time_to_seconds ( "Jan 5 09:34:43 2018 GMT" ) >>> timestamp 1515144883 >>> from datetime import datetime >>> print ( datetime . utcfromtimestamp ( timestamp )) 2018-01-05 09:34:43 “notBefore” or “notAfter” dates must use GMT ( RFC 5280 ). Changed in version 3.5: Interpret the input time as a time in UTC as specified by ‘GMT’ timezone in the input string. Local timezone was used previously. Return an integer (no fractions of a second in the input format) ssl. get_server_certificate ( addr , ssl_version=PROTOCOL_TLS_CLIENT , ca_certs=None [ , timeout ] ) ¶ Given the address addr of an SSL-protected server, as a ( hostname , port-number ) pair, fetches the server’s certificate, and returns it as a PEM-encoded string. If ssl_version is specified, uses that version of the SSL protocol to attempt to connect to the server. If ca_certs is specified, it should be a file containing a list of root certificates, the same format as used for the cafile parameter in SSLContext.load_verify_locations() . The call will attempt to validate the server certificate against that set of root certificates, and will fail if the validation attempt fails. A timeout can be specified with the timeout parameter. Changed in version 3.3: This function is now IPv6-compatible. Changed in version 3.5: The default ssl_version is changed from PROTOCOL_SSLv3 to PROTOCOL_TLS for maximum compatibility with modern servers. Changed in version 3.10: The timeout parameter was added. ssl. DER_cert_to_PEM_cert ( der_cert_bytes ) ¶ Given a certificate as a DER-encoded blob of bytes, returns a PEM-encoded string version of the same certificate. ssl. PEM_cert_to_DER_cert ( pem_cert_string ) ¶ Given a certificate as an ASCII PEM string, returns a DER-encoded sequence of bytes for that same certificate. ssl. get_default_verify_paths ( ) ¶ Returns a named tuple with paths to OpenSSL’s default cafile and capath. The paths are the same as used by SSLContext.set_default_verify_paths() . The return value is a named tuple DefaultVerifyPaths : cafile - resolved path to cafile or None if the file doesn’t exist, capath - resolved path to capath or None if the directory doesn’t exist, openssl_cafile_env - OpenSSL’s environment key that points to a cafile, openssl_cafile - hard coded path to a cafile, openssl_capath_env - OpenSSL’s environment key that points to a capath, openssl_capath - hard coded path to a capath directory Added in version 3.4. ssl. enum_certificates ( store_name ) ¶ Retrieve certificates from Windows’ system cert store. store_name may be one of CA , ROOT or MY . Windows may provide additional cert stores, too. The function returns a list of (cert_bytes, encoding_type, trust) tuples. The encoding_type specifies the encoding of cert_bytes. It is either x509_asn for X.509 ASN.1 data or pkcs_7_asn for PKCS#7 ASN.1 data. Trust specifies the purpose of the certificate as a set of OIDS or exactly True if the certificate is trustworthy for all purposes. Example: >>> ssl . enum_certificates ( "CA" ) [(b'data...', 'x509_asn', {'1.3.6.1.5.5.7.3.1', '1.3.6.1.5.5.7.3.2'}), (b'data...', 'x509_asn', True)] Availability : Windows. Added in version 3.4. ssl. enum_crls ( store_name ) ¶ Retrieve CRLs from Windows’ system cert store. store_name may be one of CA , ROOT or MY . Windows may provide additional cert stores, too. The function returns a list of (cert_bytes, encoding_type, trust) tuples. The encoding_type specifies the encoding of cert_bytes. It is either x509_asn for X.509 ASN.1 data or pkcs_7_asn for PKCS#7 ASN.1 data. Availability : Windows. Added in version 3.4. Constants ¶ All constants are now enum.IntEnum or enum.IntFlag collections. Added in version 3.6. ssl. CERT_NONE ¶ Possible value for SSLContext.verify_mode . Except for PROTOCOL_TLS_CLIENT , it is the default mode. With client-side sockets, just about any cert is accepted. Validation errors, such as untrusted or expired cert, are ignored and do not abort the TLS/SSL handshake. In server mode, no certificate is requested from the client, so the client does not send any for client cert authentication. See the discussion of Security considerations below. ssl. CERT_OPTIONAL ¶ Possible value for SSLContext.verify_mode . In client mode, CERT_OPTIONAL has the same meaning as CERT_REQUIRED . It is recommended to use CERT_REQUIRED for client-side sockets instead. In server mode, a client certificate request is sent to the client. The client may either ignore the request or send a certificate in order perform TLS client cert authentication. If the client chooses to send a certificate, it is verified. Any verification error immediately aborts the TLS handshake. Use of this setting requires a valid set of CA certificates to be passed to SSLContext.load_verify_locations() . ssl. CERT_REQUIRED ¶ Possible value for SSLContext.verify_mode . In this mode, certificates are required from the other side of the socket connection; an SSLError will be raised if no certificate is provided, or if its validation fails. This mode is not sufficient to verify a certificate in client mode as it does not match hostnames. check_hostname must be enabled as well to verify the authenticity of a cert. PROTOCOL_TLS_CLIENT uses CERT_REQUIRED and enables check_hostname by default. With server socket, this mode provides mandatory TLS client cert authentication. A client certificate request is sent to the client and the client must provide a valid and trusted certificate. Use of this setting requires a valid set of CA certificates to be passed to SSLContext.load_verify_locations() . class ssl. VerifyMode ¶ enum.IntEnum collection of CERT_* constants. Added in version 3.6. ssl. VERIFY_DEFAULT ¶ Possible value for SSLContext.verify_flags . In this mode, certificate revocation lists (CRLs) are not checked. By default OpenSSL does neither require nor verify CRLs. Added in version 3.4. ssl. VERIFY_CRL_CHECK_LEAF ¶ Possible value for SSLContext.verify_flags . In this mode, only the peer cert is checked but none of the intermediate CA certificates. The mode requires a valid CRL that is signed by the peer cert’s issuer (its direct ancestor CA). If no proper CRL has been loaded with SSLContext.load_verify_locations , validation will fail. Added in version 3.4. ssl. VERIFY_CRL_CHECK_CHAIN ¶ Possible value for SSLContext.verify_flags . In this mode, CRLs of all certificates in the peer cert chain are checked. Added in version 3.4. ssl. VERIFY_X509_STRICT ¶ Possible value for SSLContext.verify_flags to disable workarounds for broken X.509 certificates. Added in version 3.4. ssl. VERIFY_ALLOW_PROXY_CERTS ¶ Possible value for SSLContext.verify_flags to enables proxy certificate verification. Added in version 3.10. ssl. VERIFY_X509_TRUSTED_FIRST ¶ Possible value for SSLContext.verify_flags . It instructs OpenSSL to prefer trusted certificates when building the trust chain to validate a certificate. This flag is enabled by default. Added in version 3.4.4. ssl. VERIFY_X509_PARTIAL_CHAIN ¶ Possible value for SSLContext.verify_flags . It instructs OpenSSL to accept intermediate CAs in the trust store to be treated as trust-anchors, in the same way as the self-signed root CA certificates. This makes it possible to trust certificates issued by an intermediate CA without having to trust its ancestor root CA. Added in version 3.10. class ssl. VerifyFlags ¶ enum.IntFlag collection of VERIFY_* constants. Added in version 3.6. ssl. PROTOCOL_TLS ¶ Selects the highest protocol version that both the client and server support. Despite the name, this option can select both “SSL” and “TLS” protocols. Added in version 3.6. Deprecated since version 3.10: TLS clients and servers require different default settings for secure communication. The generic TLS protocol constant is deprecated in favor of PROTOCOL_TLS_CLIENT and PROTOCOL_TLS_SERVER . ssl. PROTOCOL_TLS_CLIENT ¶ Auto-negotiate the highest protocol version that both the client and server support, and configure the context client-side connections. The protocol enables CERT_REQUIRED and check_hostname by default. Added in version 3.6. ssl. PROTOCOL_TLS_SERVER ¶ Auto-negotiate the highest protocol version that both the client and server support, and configure the context server-side connections. Added in version 3.6. ssl. PROTOCOL_SSLv23 ¶ Alias for PROTOCOL_TLS . Deprecated since version 3.6: Use PROTOCOL_TLS instead. ssl. PROTOCOL_SSLv3 ¶ Selects SSL version 3 as the channel encryption protocol. This protocol is not available if OpenSSL is compiled with the no-ssl3 option. Warning SSL version 3 is insecure. Its use is highly discouraged. Deprecated since version 3.6: OpenSSL has deprecated all version specific protocols. Use the default protocol PROTOCOL_TLS_SERVER or PROTOCOL_TLS_CLIENT with SSLContext.minimum_version and SSLContext.maximum_version instead. ssl. PROTOCOL_TLSv1 ¶ Selects TLS version 1.0 as the channel encryption protocol. Deprecated since version 3.6: OpenSSL has deprecated all version specific protocols. ssl. PROTOCOL_TLSv1_1 ¶ Selects TLS version 1.1 as the channel encryption protocol. Available only with openssl version 1.0.1+. Added in version 3.4. Deprecated since version 3.6: OpenSSL has deprecated all version specific protocols. ssl. PROTOCOL_TLSv1_2 ¶ Selects TLS version 1.2 as the channel encryption protocol. Available only with openssl version 1.0.1+. Added in version 3.4. Deprecated since version 3.6: OpenSSL has deprecated all version specific protocols. ssl. OP_ALL ¶ Enables workarounds for various bugs present in other SSL implementations. This option is set by default. It does not necessarily set the same flags as OpenSSL’s SSL_OP_ALL constant. Added in version 3.2. ssl. OP_NO_SSLv2 ¶ Prevents an SSLv2 connection. This option is only applicable in conjunction with PROTOCOL_TLS . It prevents the peers from choosing SSLv2 as the protocol version. Added in version 3.2. Deprecated since version 3.6: SSLv2 is deprecated ssl. OP_NO_SSLv3 ¶ Prevents an SSLv3 connection. This option is only applicable in conjunction with PROTOCOL_TLS . It prevents the peers from choosing SSLv3 as the protocol version. Added in version 3.2. Deprecated since version 3.6: SSLv3 is deprecated ssl. OP_NO_TLSv1 ¶ Prevents a TLSv1 connection. This option is only applicable in conjunction with PROTOCOL_TLS . It prevents the peers from choosing TLSv1 as the protocol version. Added in version 3.2. Deprecated since version 3.7: The option is deprecated since OpenSSL 1.1.0, use the new SSLContext.minimum_version and SSLContext.maximum_version instead. ssl. OP_NO_TLSv1_1 ¶ Prevents a TLSv1.1 connection. This option is only applicable in conjunction with PROTOCOL_TLS . It prevents the peers from choosing TLSv1.1 as the protocol version. Available only with openssl version 1.0.1+. Added in version 3.4. Deprecated since version 3.7: The option is deprecated since OpenSSL 1.1.0. ssl. OP_NO_TLSv1_2 ¶ Prevents a TLSv1.2 connection. This option is only applicable in conjunction with PROTOCOL_TLS . It prevents the peers from choosing TLSv1.2 as the protocol version. Available only with openssl version 1.0.1+. Added in version 3.4. Deprecated since version 3.7: The option is deprecated since OpenSSL 1.1.0. ssl. OP_NO_TLSv1_3 ¶ Prevents a TLSv1.3 connection. This option is only applicable in conjunction with PROTOCOL_TLS . It prevents the peers from choosing TLSv1.3 as the protocol version. TLS 1.3 is available with OpenSSL 1.1.1 or later. When Python has been compiled against an older version of OpenSSL, the flag defaults to 0 . Added in version 3.6.3. Deprecated since version 3.7: The option is deprecated since OpenSSL 1.1.0. It was added to 2.7.15 and 3.6.3 for backwards compatibility with OpenSSL 1.0.2. ssl. OP_NO_RENEGOTIATION ¶ Disable all renegotiation in TLSv1.2 and earlier. Do not send HelloRequest messages, and ignore renegotiation requests via ClientHello. This option is only available with OpenSSL 1.1.0h and later. Added in version 3.7. ssl. OP_CIPHER_SERVER_PREFERENCE ¶ Use the server’s cipher ordering preference, rather than the client’s. This option has no effect on client sockets and SSLv2 server sockets. Added in version 3.3. ssl. OP_SINGLE_DH_USE ¶ Prevents reuse of the same DH key for distinct SSL sessions. This improves forward secrecy but requires more computational resources. This option only applies to server sockets. Added in version 3.3. ssl. OP_SINGLE_ECDH_USE ¶ Prevents reuse of the same ECDH key for distinct SSL sessions. This improves forward secrecy but requires more computational resources. This option only applies to server sockets. Added in version 3.3. ssl. OP_ENABLE_MIDDLEBOX_COMPAT ¶ Send dummy Change Cipher Spec (CCS) messages in TLS 1.3 handshake to make a TLS 1.3 connection look more like a TLS 1.2 connection. This option is only available with OpenSSL 1.1.1 and later. Added in version 3.8. ssl. OP_NO_COMPRESSION ¶ Disable compression on the SSL channel. This is useful if the application protocol supports its own compression scheme. Added in version 3.3. class ssl. Options ¶ enum.IntFlag collection of OP_* constants. ssl. OP_NO_TICKET ¶ Prevent client side from requesting a session ticket. Added in version 3.6. ssl. OP_IGNORE_UNEXPECTED_EOF ¶ Ignore unexpected shutdown of TLS connections. This option is only available with OpenSSL 3.0.0 and later. Added in version 3.10. ssl. OP_ENABLE_KTLS ¶ Enable the use of the kernel TLS. To benefit from the feature, OpenSSL must have been compiled with support for it, and the negotiated cipher suites and extensions must be supported by it (a list of supported ones may vary by platform and kernel version). Note that with enabled kernel TLS some cryptographic operations are performed by the kernel directly and not via any available OpenSSL Providers. This might be undesirable if, for example, the application requires all cryptographic operations to be performed by the FIPS provider. This option is only available with OpenSSL 3.0.0 and later. Added in version 3.12. ssl. OP_LEGACY_SERVER_CONNECT ¶ Allow legacy insecure renegotiation between OpenSSL and unpatched servers only. Added in version 3.12. ssl. HAS_ALPN ¶ Whether the OpenSSL library has built-in support for the Application-Layer Protocol Negotiation TLS extension as described in RFC 7301 . Added in version 3.5. ssl. HAS_NEVER_CHECK_COMMON_NAME ¶ Whether the OpenSSL library has built-in support not checking subject common name and SSLContext.hostname_checks_common_name is writeable. Added in version 3.7. ssl. HAS_ECDH ¶ Whether the OpenSSL library has built-in support for the Elliptic Curve-based Diffie-Hellman key exchange. This should be true unless the feature was explicitly disabled by the distributor. Added in version 3.3. ssl. HAS_SNI ¶ Whether the OpenSSL library has built-in support for the Server Name Indication extension (as defined in RFC 6066 ). Added in version 3.2. ssl. HAS_NPN ¶ Whether the OpenSSL library has built-in support for the Next Protocol Negotiation as described in the Application Layer Protocol Negotiation . When true, you can use the SSLContext.set_npn_protocols() method to advertise which protocols you want to support. Added in version 3.3. ssl. HAS_SSLv2 ¶ Whether the OpenSSL library has built-in support for the SSL 2.0 protocol. Added in version 3.7. ssl. HAS_SSLv3 ¶ Whether the OpenSSL library has built-in support for the SSL 3.0 protocol. Added in version 3.7. ssl. HAS_TLSv1 ¶ Whether the OpenSSL library has built-in support for the TLS 1.0 protocol. Added in version 3.7. ssl. HAS_TLSv1_1 ¶ Whether the OpenSSL library has built-in support for the TLS 1.1 protocol. Added in version 3.7. ssl. HAS_TLSv1_2 ¶ Whether the OpenSSL library has built-in support for the TLS 1.2 protocol. Added in version 3.7. ssl. HAS_TLSv1_3 ¶ Whether the OpenSSL library has built-in support for the TLS 1.3 protocol. Added in version 3.7. ssl. HAS_PSK ¶ Whether the OpenSSL library has built-in support for TLS-PSK. Added in version 3.13. ssl. HAS_PHA ¶ Whether the OpenSSL library has built-in support for TLS-PHA. Added in version 3.14. ssl. CHANNEL_BINDING_TYPES ¶ List of supported TLS channel binding types. Strings in this list can be used as arguments to SSLSocket.get_channel_binding() . Added in version 3.3. ssl. OPENSSL_VERSION ¶ The version string of the OpenSSL library loaded by the interpreter: >>> ssl . OPENSSL_VERSION 'OpenSSL 1.0.2k 26 Jan 2017' Added in version 3.2. ssl. OPENSSL_VERSION_INFO ¶ A tuple of five integers representing version information about the OpenSSL library: >>> ssl . OPENSSL_VERSION_INFO (1, 0, 2, 11, 15) Added in version 3.2. ssl. OPENSSL_VERSION_NUMBER ¶ The raw version number of the OpenSSL library, as a single integer: >>> ssl . OPENSSL_VERSION_NUMBER 268443839 >>> hex ( ssl . OPENSSL_VERSION_NUMBER ) '0x100020bf' Added in version 3.2. ssl. ALERT_DESCRIPTION_HANDSHAKE_FAILURE ¶ ssl. ALERT_DESCRIPTION_INTERNAL_ERROR ¶ ALERT_DESCRIPTION_* Alert Descriptions from RFC 5246 and others. The IANA TLS Alert Registry contains this list and references to the RFCs where their meaning is defined. Used as the return value of the callback function in SSLContext.set_servername_callback() . Added in version 3.4. class ssl. AlertDescription ¶ enum.IntEnum collection of ALERT_DESCRIPTION_* constants. Added in version 3.6. Purpose. SERVER_AUTH ¶ Option for create_default_context() and SSLContext.load_default_certs() . This value indicates that the context may be used to authenticate web servers (therefore, it will be used to create client-side sockets). Added in version 3.4. Purpose. CLIENT_AUTH ¶ Option for create_default_context() and SSLContext.load_default_certs() . This value indicates that the context may be used to authenticate web clients (therefore, it will be used to create server-side sockets). Added in version 3.4. class ssl. SSLErrorNumber ¶ enum.IntEnum collection of SSL_ERROR_* constants. Added in version 3.6. class ssl. TLSVersion ¶ enum.IntEnum collection of SSL and TLS versions for SSLContext.maximum_version and SSLContext.minimum_version . Added in version 3.7. TLSVersion. MINIMUM_SUPPORTED ¶ TLSVersion. MAXIMUM_SUPPORTED ¶ The minimum or maximum supported SSL or TLS version. These are magic constants. Their values don’t reflect the lowest and highest available TLS/SSL versions. TLSVersion. SSLv3 ¶ TLSVersion. TLSv1 ¶ TLSVersion. TLSv1_1 ¶ TLSVersion. TLSv1_2 ¶ TLSVersion. TLSv1_3 ¶ SSL 3.0 to TLS 1.3. Deprecated since version 3.10: All TLSVersion members except TLSVersion.TLSv1_2 and TLSVersion.TLSv1_3 are deprecated. SSL Sockets ¶ class ssl. SSLSocket ( socket.socket ) ¶ SSL sockets provide the following methods of Socket Objects : accept() bind() close() connect() detach() fileno() getpeername() , getsockname() getsockopt() , setsockopt() gettimeout() , settimeout() , setblocking() listen() makefile() recv() , recv_into() (but passing a non-zero flags argument is not allowed) send() , sendall() (with the same limitation) sendfile() (but os.sendfile will be used for plain-text sockets only, else send() will be used) shutdown() However, since the SSL (and TLS) protocol has its own framing atop of TCP, the SSL sockets abstraction can, in certain respects, diverge from the specification of normal, OS-level sockets. See especially the notes on non-blocking sockets . Instances of SSLSocket must be created using the SSLContext.wrap_socket() method. Changed in version 3.5: The sendfile() method was added. Changed in version 3.5: The shutdown() does not reset the socket timeout each time bytes are received or sent. The socket timeout is now the maximum total duration of the shutdown. Deprecated since version 3.6: It is deprecated to create a SSLSocket instance directly, use SSLContext.wrap_socket() to wrap a socket. Changed in version 3.7: SSLSocket instances must to created with wrap_socket() . In earlier versions, it was possible to create instances directly. This was never documented or officially supported. Changed in version 3.10: Python now uses SSL_read_ex and SSL_write_ex internally. The functions support reading and writing of data larger than 2 GB. Writing zero-length data no longer fails with a protocol violation error. SSL sockets also have the following additional methods and attributes: SSLSocket. read ( len = 1024 , buffer = None ) ¶ Read up to len bytes of data from the SSL socket and return the result as a bytes instance. If buffer is specified, then read into the buffer instead, and return the number of bytes read. Raise SSLWantReadError or SSLWantWriteError if the socket is non-blocking and the read would block. As at any time a re-negotiation is possible, a call to read() can also cause write operations. Changed in version 3.5: The socket timeout is no longer reset each time bytes are received or sent. The socket timeout is now the maximum total duration to read up to len bytes. Deprecated since version 3.6: Use recv() instead of read() . SSLSocket. write ( data ) ¶ Write data to the SSL socket and return the number of bytes written. The data argument must be an object supporting the buffer interface. Raise SSLWantReadError or SSLWantWriteError if the socket is non-blocking and the write would block. As at any time a re-negotiation is possible, a call to write() can also cause read operations. Changed in version 3.5: The socket timeout is no longer reset each time bytes are received or sent. The socket timeout is now the maximum total duration to write data . Deprecated since version 3.6: Use send() instead of write() . Note The read() and write() methods are the low-level methods that read and write unencrypted, application-level data and decrypt/encrypt it to encrypted, wire-level data. These methods require an active SSL connection, i.e. the handshake was completed and SSLSocket.unwrap() was not called. Normally you should use the socket API methods like recv() and send() instead of these methods. SSLSocket. do_handshake ( block = False ) ¶ Perform the SSL setup handshake. If block is true and the timeout obtained by gettimeout() is zero, the socket is set in blocking mode until the handshake is performed. Changed in version 3.4: The handshake method also performs match_hostname() when the check_hostname attribute of the socket’s context is true. Changed in version 3.5: The socket timeout is no longer reset each time bytes are received or sent. The socket timeout is now the maximum total duration of the handshake. Changed in version 3.7: Hostname or IP address is matched by OpenSSL during handshake. The function match_hostname() is no longer used. In case OpenSSL refuses a hostname or IP address, the handshake is aborted early and a TLS alert message is sent to the peer. SSLSocket. getpeercert ( binary_form = False ) ¶ If there is no certificate for the peer on the other end of the connection, return None . If the SSL handshake hasn’t been done yet, raise ValueError . If the binary_form parameter is False , and a certificate was received from the peer, this method returns a dict instance. If the certificate was not validated, the dict is empty. If the certificate was validated, it returns a dict with several keys, amongst them subject (the principal for which the certificate was issued) and issuer (the principal issuing the certificate). If a certificate contains an instance of the Subject Alternative Name extension (see RFC 3280 ), there will also be a subjectAltName key in the dictionary. The subject and issuer fields are tuples containing the sequence of relative distinguished names (RDNs) given in the certificate’s data structure for the respective fields, and each RDN is a sequence of name-value pairs. Here is a real-world example: { 'issuer' : ((( 'countryName' , 'IL' ),), (( 'organizationName' , 'StartCom Ltd.' ),), (( 'organizationalUnitName' , 'Secure Digital Certificate Signing' ),), (( 'commonName' , 'StartCom Class 2 Primary Intermediate Server CA' ),)), 'notAfter' : 'Nov 22 08:15:19 2013 GMT' , 'notBefore' : 'Nov 21 03:09:52 2011 GMT' , 'serialNumber' : '95F0' , 'subject' : ((( 'description' , '571208-SLe257oHY9fVQ07Z' ),), (( 'countryName' , 'US' ),), (( 'stateOrProvinceName' , 'California' ),), (( 'localityName' , 'San Francisco' ),), (( 'organizationName' , 'Electronic Frontier Foundation, Inc.' ),), (( 'commonName' , '*.eff.org' ),), (( 'emailAddress' , 'hostmaster@eff.org' ),)), 'subjectAltName' : (( 'DNS' , '*.eff.org' ), ( 'DNS' , 'eff.org' )), 'version' : 3 } If the binary_form parameter is True , and a certificate was provided, this method returns the DER-encoded form of the entire certificate as a sequence of bytes, or None if the peer did not provide a certificate. Whether the peer provides a certificate depends on the SSL socket’s role: for a client SSL socket, the server will always provide a certificate, regardless of whether validation was required; for a server SSL socket, the client will only provide a certificate when requested by the server; therefore getpeercert() will return None if you used CERT_NONE (rather than CERT_OPTIONAL or CERT_REQUIRED ). See also SSLContext.check_hostname . Changed in version 3.2: The returned dictionary includes additional items such as issuer and notBefore . Changed in version 3.4: ValueError is raised when the handshake isn’t done. The returned dictionary includes additional X509v3 extension items such as crlDistributionPoints , caIssuers and OCSP URIs. Changed in version 3.9: IPv6 address strings no longer have a trailing new line. SSLSocket. get_verified_chain ( ) ¶ Returns verified certificate chain provided by the other end of the SSL channel as a list of DER-encoded bytes. If certificate verification was disabled method acts the same as get_unverified_chain() . Added in version 3.13. SSLSocket. get_unverified_chain ( ) ¶ Returns raw certificate chain provided by the other end of the SSL channel as a list of DER-encoded bytes. Added in version 3.13. SSLSocket. cipher ( ) ¶ Returns a three-value tuple containing the name of the cipher being used, the version of the SSL protocol that defines its use, and the number of secret bits being used. If no connection has been established, returns None . SSLSocket. shared_ciphers ( ) ¶ Return the list of ciphers available in both the client and server. Each entry of the returned list is a three-value tuple containing the name of the cipher, the version of the SSL protocol that defines its use, and the number of secret bits the cipher uses. shared_ciphers() returns None if no connection has been established or the socket is a client socket. Added in version 3.5. SSLSocket. compression ( ) ¶ Return the compression algorithm being used as a string, or None if the connection isn’t compressed. If the higher-level protocol supports its own compression mechanism, you can use OP_NO_COMPRESSION to disable SSL-level compression. Added in version 3.3. SSLSocket. get_channel_binding ( cb_type = 'tls-unique' ) ¶ Get channel binding data for current connection, as a bytes object. Returns None if not connected or the handshake has not been completed. The cb_type parameter allow selection of the desired channel binding type. Valid channel binding types are listed in the CHANNEL_BINDING_TYPES list. Currently only the ‘tls-unique’ channel binding, defined by RFC 5929 , is supported. ValueError will be raised if an unsupported channel binding type is requested. Added in version 3.3. SSLSocket. selected_alpn_protocol ( ) ¶ Return the protocol that was selected during the TLS handshake. If SSLContext.set_alpn_protocols() was not called, if the other party does not support ALPN, if this socket does not support any of the client’s proposed protocols, or if the handshake has not happened yet, None is returned. Added in version 3.5. SSLSocket. selected_npn_protocol ( ) ¶ Return the higher-level protocol that was selected during the TLS/SSL handshake. If SSLContext.set_npn_protocols() was not called, or if the other party does not support NPN, or if the handshake has not yet happened, this will return None . Added in version 3.3. Deprecated since version 3.10: NPN has been superseded by ALPN SSLSocket. unwrap ( ) ¶ Performs the SSL shutdown handshake, which removes the TLS layer from the underlying socket, and returns the underlying socket object. This can be used to go from encrypted operation over a connection to unencrypted. The returned socket should always be used for further communication with the other side of the connection, rather than the original socket. SSLSocket. verify_client_post_handshake ( ) ¶ Requests post-handshake authentication (PHA) from a TLS 1.3 client. PHA can only be initiated for a TLS 1.3 connection from a server-side socket, after the initial TLS handshake and with PHA enabled on both sides, see SSLContext.post_handshake_auth . The method does not perform a cert exchange immediately. The server-side sends a CertificateRequest during the next write event and expects the client to respond with a certificate on the next read event. If any precondition isn’t met (e.g. not TLS 1.3, PHA not enabled), an SSLError is raised. Note Only available with OpenSSL 1.1.1 and TLS 1.3 enabled. Without TLS 1.3 support, the method raises NotImplementedError . Added in version 3.8. SSLSocket. version ( ) ¶ Return the actual SSL protocol version negotiated by the connection as a string, or None if no secure connection is established. As of this writing, possible return values include "SSLv2" , "SSLv3" , "TLSv1" , "TLSv1.1" and "TLSv1.2" . Recent OpenSSL versions may define more return values. Added in version 3.5. SSLSocket. pending ( ) ¶ Returns the number of already decrypted bytes available for read, pending on the connection. SSLSocket. context ¶ The SSLContext object this SSL socket is tied to. Added in version 3.2. SSLSocket. server_side ¶ A boolean which is True for server-side sockets and False for client-side sockets. Added in version 3.2. SSLSocket. server_hostname ¶ Hostname of the server: str type, or None for server-side socket or if the hostname was not specified in the constructor. Added in version 3.2. Changed in version 3.7: The attribute is now always ASCII text. When server_hostname is an internationalized domain name (IDN), this attribute now stores the A-label form ( "xn--pythn-mua.org" ), rather than the U-label form ( "pythön.org" ). SSLSocket. session ¶ The SSLSession for this SSL connection. The session is available for client and server side sockets after the TLS handshake has been performed. For client sockets the session can be set before do_handshake() has been called to reuse a session. Added in version 3.6. SSLSocket. session_reused ¶ Added in version 3.6. SSL Contexts ¶ Added in version 3.2. An SSL context holds various data longer-lived than single SSL connections, such as SSL configuration options, certificate(s) and private key(s). It also manages a cache of SSL sessions for server-side sockets, in order to speed up repeated connections from the same clients. class ssl. SSLContext ( protocol = None ) ¶ Create a new SSL context. You may pass protocol which must be one of the PROTOCOL_* constants defined in this module. The parameter specifies which version of the SSL protocol to use. Typically, the server chooses a particular protocol version, and the client must adapt to the server’s choice. Most of the versions are not interoperable with the other versions. If not specified, the default is PROTOCOL_TLS ; it provides the most compatibility with other versions. Here’s a table showing which versions in a client (down the side) can connect to which versions in a server (along the top): client / server SSLv2 SSLv3 TLS [ 3 ] TLSv1 TLSv1.1 TLSv1.2 SSLv2 yes no no [ 1 ] no no no SSLv3 no yes no [ 2 ] no no no TLS ( SSLv23 ) [ 3 ] no [ 1 ] no [ 2 ] yes yes yes yes TLSv1 no no yes yes no no TLSv1.1 no no yes no yes no TLSv1.2 no no yes no no yes Footnotes [ 1 ] ( 1 , 2 ) SSLContext disables SSLv2 with OP_NO_SSLv2 by default. [ 2 ] ( 1 , 2 ) SSLContext disables SSLv3 with OP_NO_SSLv3 by default. [ 3 ] ( 1 , 2 ) TLS 1.3 protocol will be available with PROTOCOL_TLS in OpenSSL >= 1.1.1. There is no dedicated PROTOCOL constant for just TLS 1.3. See also create_default_context() lets the ssl module choose security settings for a given purpose. Changed in version 3.6: The context is created with secure default values. The options OP_NO_COMPRESSION , OP_CIPHER_SERVER_PREFERENCE , OP_SINGLE_DH_USE , OP_SINGLE_ECDH_USE , OP_NO_SSLv2 , and OP_NO_SSLv3 (except for PROTOCOL_SSLv3 ) are set by default. The initial cipher suite list contains only HIGH ciphers, no NULL ciphers and no MD5 ciphers. Deprecated since version 3.10: SSLContext without protocol argument is deprecated. The context class will either require PROTOCOL_TLS_CLIENT or PROTOCOL_TLS_SERVER protocol in the future. Changed in version 3.10: The default cipher suites now include only secure AES and ChaCha20 ciphers with forward secrecy and security level 2. RSA and DH keys with less than 2048 bits and ECC keys with less than 224 bits are prohibited. PROTOCOL_TLS , PROTOCOL_TLS_CLIENT , and PROTOCOL_TLS_SERVER use TLS 1.2 as minimum TLS version. Note SSLContext only supports limited mutation once it has been used by a connection. Adding new certificates to the internal trust store is allowed, but changing ciphers, verification settings, or mTLS certificates may result in surprising behavior. Note SSLContext is designed to be shared and used by multiple connections. Thus, it is thread-safe as long as it is not reconfigured after being used by a connection. SSLContext objects have the following methods and attributes: SSLContext. cert_store_stats ( ) ¶ Get statistics about quantities of loaded X.509 certificates, count of X.509 certificates flagged as CA certificates and certificate revocation lists as dictionary. Example for a context with one CA cert and one other cert: >>> context . cert_store_stats () {'crl': 0, 'x509_ca': 1, 'x509': 2} Added in version 3.4. SSLContext. load_cert_chain ( certfile , keyfile = None , password = None ) ¶ Load a private key and the corresponding certificate. The certfile string must be the path to a single file in PEM format containing the certificate as well as any number of CA certificates needed to establish the certificate’s authenticity. The keyfile string, if present, must point to a file containing the private key. Otherwise the private key will be taken from certfile as well. See the discussion of Certificates for more information on how the certificate is stored in the certfile . The password argument may be a function to call to get the password for decrypting the private key. It will only be called if the private key is encrypted and a password is necessary. It will be called with no arguments, and it should return a string, bytes, or bytearray. If the return value is a string it will be encoded as UTF-8 before using it to decrypt the key. Alternatively a string, bytes, or bytearray value may be supplied directly as the password argument. It will be ignored if the private key is not encrypted and no password is needed. If the password argument is not specified and a password is required, OpenSSL’s built-in password prompting mechanism will be used to interactively prompt the user for a password. An SSLError is raised if the private key doesn’t match with the certificate. Changed in version 3.3: New optional argument password . SSLContext. load_default_certs ( purpose = Purpose.SERVER_AUTH ) ¶ Load a set of default “certification authority” (CA) certificates from default locations. On Windows it loads CA certs from the CA and ROOT system stores. On all systems it calls SSLContext.set_default_verify_paths() . In the future the method may load CA certificates from other locations, too. The purpose flag specifies what kind of CA certificates are loaded. The default settings Purpose.SERVER_AUTH loads certificates, that are flagged and trusted for TLS web server authentication (client side sockets). Purpose.CLIENT_AUTH loads CA certificates for client certificate verification on the server side. Added in version 3.4. SSLContext. load_verify_locations ( cafile = None , capath = None , cadata = None ) ¶ Load a set of “certification authority” (CA) certificates used to validate other peers’ certificates when verify_mode is other than CERT_NONE . At least one of cafile or capath must be specified. This method can also load certification revocation lists (CRLs) in PEM or DER format. In order to make use of CRLs, SSLContext.verify_flags must be configured properly. The cafile string, if present, is the path to a file of concatenated CA certificates in PEM format. See the discussion of Certificates for more information about how to arrange the certificates in this file. The capath string, if present, is the path to a directory containing several CA certificates in PEM format, following an OpenSSL specif | 2026-01-13T08:48:41 |
https://dev.to/szabgab/perl-weekly-593-perl-on-devto-g5k | Perl Weekly #593 - Perl on DEV.to - 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 Gabor Szabo Posted on Dec 5, 2022 • Originally published at perlweekly.com Perl Weekly #593 - Perl on DEV.to # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 593 Hi there! I registered to DEV.to in 2017, more than 5 years ago. Posted a few articles with rather limited success: less than 10 people looked at the articles. Then in 2020 I posted a few more articles. On one of them Tests are awesome! I got as many as 300 readers, but the others have not received much love so I did not continue publishing. In 2021 I had another experiment when I published Perl modules with their own web site on which there were some 600 visitors. Primarily the readers of the Perl Weekly newsletter. I published a few more articles with readers in the low 10s. A few weeks ago I started to publish again. This time several of my articles got above 100 viewers and one, Open Source Development Courses is already above 1100 viewers. I started to get around 600 readers a day. That's already really valuable! So what happened? There were a couple of changes: 1. There are more people on DEV. 2. I publish a lot more articles that appeal to a wider range of people. 3. There is a sort-of network effect. The more people up-vote and bookmark (the two kinds of reactions on DEV) my articles the more people will see it. The nice thing about DEV is that I can republish the articles I published elsewhere (e.g. on PerlMaven , on Code-Maven , or blogs.perl.org ), and also I can set the canonical URL of each article on DEV to the original one on my blog. That way I get the visitors on DEV as well, but the 'Google juice' the articles receive will flow over to my sites. It seems like a win-win for DEV and authors who have blogs elsewhere. You can even configure DEV to pull your RSS feed and create drafts from your articles published elsewhere. I even started to republish the content of the Perl Weekly . So here is what I suggest. If you already write about Perl elsewhere, republish those articles on DEV and tag them with perl . If you are primarily a reader of articles, then register on DEV and start up-voting the Perl-related posts you like. You can even follow a few authors there, get notified when they have new posts, and up-vote those to encourage them to write even more. Alternatively, you can watch the Perl Planetarium . It already follows the perl tag on DEV. Enjoy your week! -- Your editor: Gabor Szabo. Announcements German Perl/Raku Workshop 2023 Call for Papers New feature: HTTPS support blogs.perl.org now has HTTPS support Articles Advent of Code puzzle input downloader SPVM 0.9663 is released JSON Pure Perl Pretty Print SPVM::IO 0.14 is released on Perl/CPAN AoC 2022/1 - Caloric snacks AoC 2022/2 - Rock Paper Scissors cheat guide Day 5: CI for Win32-Wlan Perl module Perl is Actually Portable Discussion The Perl outlook for next year is favorable Testing The 2022 December CI Challenge You probably already know that I think having CI for any project is valuable. I started a series of blog posts in which every day during December 2022 I am going to describe a pull-request I sent to an open source project adding Continuous Integration to it. Add GitHub Action CI to the Net-Async-Redis-XS Perl module This is a nice example where you can see how to configure the GitHub Action for some Perl code that uses Redis. The module author ended up accepting my PR and then switching over to CircleCI. Check out the CircleCI configuration in the GitHub repository . I think it was a very nice way to handle the situation: accepting the work even though the author already knew it will be replace. Advent Calendars Perl Advent Calendar for 2022 Raku Advent Calendar for 2022 Daily CI in December 2022 7 Advent Calendars in 2022 Advent Planet in 2022 CPAN List of new CPAN distributions – Nov 2022 Perl This Week in PSC (089) The weekly report of the Perl Steering Council The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 194 Welcome to a new week with a couple of fun tasks "Digital Clock" and "Frequency Equalizer". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 193 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Binary String" and "Odd String" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. The Weekly Challenge 193 Cool use of sprintf() to solve the task. Thanks for sharing the knowledge. An Abundance of Strings Line by line code analysis is the USP of Arne's blog. Great source for any Raku fan. Evens and Oddballs Bruce doesn't use many words but every word is worth every penny. Thanks for your contributions. What An Unusual String You Have There! Or Are You Just Glad To Meet Me? Thank you Colin for sharing blog post. You don't miss the opportunity to treat us with surprises. PWC193 - Binary String Nice show of Raku power to get the job done. Keep it up great work. PWC193 - Odd String Creative individual approach one for each, Perl and Raku. Please do checkout. The Weekly Challenge 193 As always every week we get the varieties and this week is no different. Highly recommended. Binary String and Odd String Near identical solutions in Perl and Raku. Keep sharing the knowledge with us every week. Map, map and remap! Great show of Raku one-liner and other gems. Well done and keep it up. Perl Weekly Challenge 193 Master of Perl one-liner, you don't want to miss. Highly recommended. All the binaries and find the odd man out Interesting narration of task analysis. You should definitely check it out. Odd Binary Are you a Kotlin fan? Roger decided to discuss his Kotlin solution in the blog this week. Highly recommended. The odd binary string Simon style of breaking big task into subtasks makes it so easy to follow. Thanks for your contributions. PWC 193 Nice one-liner in Perl and Raku by Stephen. For me the highlight was the discussion of task analysis. Keep it up great work. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Events German Perl/Raku Workshop 2023 Call for Papers Perl Jobs by Perl Careers Modern Perl and positive team vibes. UK Remote Perl role If you’re a Modern Perl developer in the UK with Go-lang experience (or at least a strong desire to learn) and you’re searching for a team of dynamos, we’ve found the perfect place for you. This award-winning company may be newer, but the combined experience of their people is impressive. No doubt this is one of the many reasons their AI recruitment marketing business has taken off! Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role Sure, you’ve got Perl chops for days, but that’s not all you can do — and that’s why our client wants to meet you. They’re looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Cross-trained team members are their sweet spot, and whether you’re cross-trained yourself or are open to the possibility, this may be your perfect role. Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for folks with passion, drive, and an appreciation for new experiences. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. Perl role in the UK A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:41 |
https://docs.suprsend.com/reference/cli-schema-commit | Commit Schema - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Schema Commit Schema Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Schema Commit Schema OpenAI Open in ChatGPT Make schema changes live in a SuprSend workspace. OpenAI Open in ChatGPT Commit a draft schema to live status in your SuprSend workspace. Until a draft is committed, your latest changes remain inactive and are not used for notification validation. You do not need to run this command separately if you already used the --commit=true flag with the schema push command. Syntax Copy Ask AI suprsend schema commit < schema-slu g > [flags] Arguments: <schema-slug> - Slug of the schema to commit (required) Flags Flag Description Default -h, --help Show help for the command – -m, --commit-message string Commit message describing the changes – Example Copy Ask AI # Commit a schema in staging workspace to live status suprsend schema commit my-schema # Commit schema in production workspace with commit message suprsend schema commit notification-schema --workspace production --commit-message "Commit message" Was this page helpful? Yes No Suggest edits Raise issue Previous Generate Types Generate type definitions from all enabled SuprSend schemas in a workspace. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:41 |
https://www.youtube.com/channel/UC3_cJM5UxFUYCi3n39vvvCw | fine - 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, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:41 |
https://dev.to/t/tutorial/page/10 | Tutorial Page 10 - 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 # 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 7 8 9 10 11 12 13 14 15 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Why Markdown Is The Secret To Better AI Karishma Shukla Karishma Shukla Karishma Shukla Follow Jan 8 Why Markdown Is The Secret To Better AI # webdev # ai # tutorial # programming 6 reactions Comments Add Comment 3 min read Solved: Why do project-management refugees think a weekend AWS course makes them engineers? Darian Vance Darian Vance Darian Vance Follow Jan 8 Solved: Why do project-management refugees think a weekend AWS course makes them engineers? # devops # programming # tutorial # cloud Comments Add Comment 7 min read Trigger Logic Causing Recursive Updates or Data Duplication Selavina B Selavina B Selavina B Follow Jan 8 Trigger Logic Causing Recursive Updates or Data Duplication # architecture # backend # codequality # tutorial Comments Add Comment 3 min read Course Launch: Writing Is an Important Part of Coding Prasoon Jadon Prasoon Jadon Prasoon Jadon Follow Jan 8 Course Launch: Writing Is an Important Part of Coding # programming # learning # tutorial # beginners 1 reaction Comments Add Comment 2 min read Best Practices for Training LoRA Models with Z-Image: Complete 2026 Guide Garyvov Garyvov Garyvov Follow Jan 8 Best Practices for Training LoRA Models with Z-Image: Complete 2026 Guide # ai # deeplearning # tutorial Comments Add Comment 6 min read Weather Service Project (Part 1): Building the Data Collector with Python and GitHub Actions or Netlify Daniel Daniel Daniel Follow for Datalaria Jan 12 Weather Service Project (Part 1): Building the Data Collector with Python and GitHub Actions or Netlify # api # automation # python # tutorial 3 reactions Comments Add Comment 9 min read How My Company Automate Meeting Notes to Jira A.I. A.I. A.I. Follow Jan 8 How My Company Automate Meeting Notes to Jira # ai # webdev # tutorial # productivity 1 reaction Comments 1 comment 3 min read Building a Centralized Keyboard Shortcut System in React: A Priority-Based Approach Hasnaat Iftikhar Hasnaat Iftikhar Hasnaat Iftikhar Follow Jan 6 Building a Centralized Keyboard Shortcut System in React: A Priority-Based Approach # react # typescript # webdev # tutorial Comments Add Comment 17 min read Working with Categorical Data in R: Creating Frequency Tables as Data Frames (Modern Approaches) Anshuman Anshuman Anshuman Follow Jan 8 Working with Categorical Data in R: Creating Frequency Tables as Data Frames (Modern Approaches) # programming # ai # javascript # tutorial Comments Add Comment 4 min read Clone Graph: Coding Problem Solution Explained Stack Overflowed Stack Overflowed Stack Overflowed Follow Jan 8 Clone Graph: Coding Problem Solution Explained # programming # coding # tutorial # learning Comments Add Comment 4 min read LLM Data Leaks: Exposing Hidden Risks in ETL/ELT Pipelines Malik Abualzait Malik Abualzait Malik Abualzait Follow Jan 8 LLM Data Leaks: Exposing Hidden Risks in ETL/ELT Pipelines # ai # tech # programming # tutorial Comments Add Comment 4 min read Sliding window (Fixed length) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 6 Sliding window (Fixed length) # programming # beginners # tutorial # learning Comments Add Comment 2 min read 港美主流期货 API 接入全指南：TradingView 看盘策略 San Si wu San Si wu San Si wu Follow Jan 8 港美主流期货 API 接入全指南：TradingView 看盘策略 # tutorial # python # api # github Comments Add Comment 3 min read Rust Macros System Aviral Srivastava Aviral Srivastava Aviral Srivastava Follow Jan 12 Rust Macros System # automation # productivity # rust # tutorial 1 reaction Comments 1 comment 9 min read LTX-2 Prompting Guide: Master AI Video Generation with Expert Techniques Garyvov Garyvov Garyvov Follow Jan 8 LTX-2 Prompting Guide: Master AI Video Generation with Expert Techniques # ai # tooling # tutorial Comments Add Comment 12 min read Solved: Hot take: The outage isn’t the problem everyone going down at once is Darian Vance Darian Vance Darian Vance Follow Jan 8 Solved: Hot take: The outage isn’t the problem everyone going down at once is # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: How are you guys handling extra product options in your WooCommerce store? Darian Vance Darian Vance Darian Vance Follow Jan 6 Solved: How are you guys handling extra product options in your WooCommerce store? # devops # programming # tutorial # cloud Comments Add Comment 10 min read Solved: Any plugins to manage checkout in WooCommerce Checkout Blocks? Darian Vance Darian Vance Darian Vance Follow Jan 6 Solved: Any plugins to manage checkout in WooCommerce Checkout Blocks? # devops # programming # tutorial # cloud Comments Add Comment 8 min read How to Add Randomness to Z-Image Turbo Using Transformers: Complete Seed Control Guide Garyvov Garyvov Garyvov Follow Jan 8 How to Add Randomness to Z-Image Turbo Using Transformers: Complete Seed Control Guide # ai # deeplearning # python # tutorial Comments Add Comment 8 min read AI Automation vs AI Agents: What’s the Real Difference (Explained with Real-Life Examples) Viveka Sharma Viveka Sharma Viveka Sharma Follow Jan 8 AI Automation vs AI Agents: What’s the Real Difference (Explained with Real-Life Examples) # agents # tutorial # beginners # ai 1 reaction Comments 1 comment 3 min read Amazing Z-Image Workflow v3.0: Complete Guide to Enhanced ComfyUI Image Generation Garyvov Garyvov Garyvov Follow Jan 8 Amazing Z-Image Workflow v3.0: Complete Guide to Enhanced ComfyUI Image Generation # ai # machinelearning # tooling # tutorial Comments Add Comment 9 min read How to Add a Contact Form to Your Next.js Site in 5 Minutes H Master (MasterH) H Master (MasterH) H Master (MasterH) Follow Jan 8 How to Add a Contact Form to Your Next.js Site in 5 Minutes # nextjs # react # webdev # tutorial Comments Add Comment 3 min read Passkey Login & Smart Wallet Creation on Solana with React Native and LazorKit — No More Seed Phrases! Onwuka David Onwuka David Onwuka David Follow Jan 7 Passkey Login & Smart Wallet Creation on Solana with React Native and LazorKit — No More Seed Phrases! # reactnative # security # tutorial # web3 Comments Add Comment 9 min read Solved: Recommendations on Hosting Platform, Realtor website Darian Vance Darian Vance Darian Vance Follow Jan 6 Solved: Recommendations on Hosting Platform, Realtor website # devops # programming # tutorial # cloud Comments Add Comment 10 min read Solved: Bitbucket bait-and-switched, now charging $15/month per self-hosted runner Darian Vance Darian Vance Darian Vance Follow Jan 6 Solved: Bitbucket bait-and-switched, now charging $15/month per self-hosted runner # devops # programming # tutorial # cloud Comments Add Comment 9 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:48:41 |
https://survivejs.com/blog/kaibanjs-interview/ | KaibanJS - Open-source framework for building multi-agent AI systems - Interview with Dariel Vila Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Can you tell me a bit about yourself? How would you describe KaibanJS to someone who has never heard of it? How does KaibanJS work? How does KaibanJS differ from other solutions? Why did you develop KaibanJS? What next? What does the future look like for KaibanJS and web development in general? Can you see any particular trends? What advice would you give to programmers getting into AI? Who should I interview next? Any last remarks? Conclusion Can you tell me a bit about yourself? How would you describe KaibanJS to someone who has never heard of it? How does KaibanJS work? How does KaibanJS differ from other solutions? Why did you develop KaibanJS? What next? What does the future look like for KaibanJS and web development in general? Can you see any particular trends? What advice would you give to programmers getting into AI? Who should I interview next? Any last remarks? Conclusion Loading... KaibanJS - Open-source framework for building multi-agent AI systems - Interview with Dariel Vila Author: Juho Vepsäläinen Topics Interview Ai Published: 11.10.2024 Since the launch of ChatGPT, there has been a lot of interest in AI systems. The question is, how do you build your agents, for example? In this interview, we will look into a JavaScript-based solution called KaibanJS ↗ with its author Dariel Vila ↗ . Can you tell me a bit about yourself? # I’m Dariel Vila, Lead Developer at KaibanJS and a passionate advocate for JavaScript. With over 15 years in the tech industry, I’ve worn many hats — Developer, Team Lead, and Entrepreneur. You know, JavaScript has been a game-changer for me. It’s not just a language but my ticket to a whole new life. It helped me leave Cuba, land a job in Venezuela when I had no papers, and even get my first gig in the US. Thanks to JS, I created my first open-source project, AniJS, and later founded my company, FRONT10. It’s pretty wild how a programming language can shape your entire journey, right. These experiences have shaped my perspective and fueled my passion for the JavaScript ecosystem. They’ve also inspired me to give back to the community through projects like KaibanJS, aiming to empower other developers to achieve their goals and push the boundaries of what’s possible with JavaScript. How would you describe KaibanJS to someone who has never heard of it? # Imagine you’re a project manager, but instead of managing a team of people, you’re orchestrating a group of AI agents using a Kanban Board. If you’ve used Trello or Notion, you know how that works. That’s what KaibanJS allows you to do. The JavaScript-native framework lets you build and manage multi-agent AI systems following the Kanban methodology. How does KaibanJS work? # You start by creating your AI agents, each with specific roles and capabilities. These could be agents for data analysis, content creation, customer service – whatever your project needs. Then, just like in a regular sprint planning session, you assign tasks to these agents. The magic happens on what we call the Kaiban Board. Think of it as a Trello or Notion board for AI tasks. You’ve got your columns – maybe “To Do,” “In Progress,” and “Done” – and you can visualize the status of each task in real time. You can drag and drop tasks, set priorities, and watch your AI agents work through their assignments. What’s cool is that you can see the interactions between agents, track their progress, and even step in to make adjustments if needed. It’s like having an agile AI team at your fingertips, all managed through a familiar visual interface. It is important to note that people can easily build their own UIs using the state management system that KaibanJS provides. So, in essence, KaibanJS bridges the gap between JavaScript developers and the world of AI, allowing you to create, manage, and visualize complex AI workflows as quickly as you’d manage a sprint in your regular development process. How does KaibanJS differ from other solutions? # KaibanJS stands out because it’s designed exclusively for JavaScript, unlike most AI frameworks that cater primarily to Python. When you deeply specialize in technology, you understand how to leverage its unique features—such as reactive state management and component-based architecture—providing tools that ensure robust performance and extensive customization. KaibanJS allows developers to build, visualize, and deploy AI workloads effortlessly within a familiar environment. The Kaiban Board is a game-changer in how we interact with and manage AI workflows, making AI development as intuitive as organizing a kanban board for sprint planning. Why did you develop KaibanJS? # The inspiration for KaibanJS arose from frustration with the lack of proper AI tools for the JavaScript community. Having been deeply involved in JavaScript for years, I felt creating a framework enabling developers to harness AI capabilities without the steep learning curve associated with other languages was crucial. I wanted to bridge the gap and make AI accessible to JavaScript developers without requiring them to learn a new language or ecosystem. Additionally, improving user interfaces in AI interactions is vital, and KaibanJS, together with the Kaiban Board, excels. What next? # Looking ahead, we’re excited to gather user feedback as we finalize the framework. Our next steps include: Building a solid community around KaibanJS Keep improving the framework with capabilities that JavaScript developers need in real-world applications. Try to push the boundaries of what’s possible with AI in JavaScript. What does the future look like for KaibanJS and web development in general? Can you see any particular trends? # The future looks incredibly promising! With the increasing demand for AI capabilities across various platforms, KaibanJS is positioning itself at the forefront of this evolution. I envision a trend where AI integration becomes as common in JavaScript frameworks as using a state management library is today. One exciting development is the emergence of smaller, more efficient language models that can run directly in the browser or on devices. This shift is a game-changer for JavaScript developers because it opens up new possibilities for AI-powered applications without constant server communication. Imagine having powerful AI capabilities in your Chrome browser or smartphone, all powered by JavaScript! JavaScript’s ubiquity is a huge advantage here. It’s already everywhere - in browsers, servers, mobile apps, and IoT devices. This versatility means that as AI becomes more integrated into our daily tech, JavaScript developers will be uniquely positioned to create AI-enhanced experiences across various platforms. What advice would you give to programmers getting into AI? # My advice is simple: dive in! It’s easier than you might think. AI development primarily involves consuming APIs and understanding how to interact with them. As with ReactJS, you don’t need to understand the framework’s internals to build software effectively. Many beginners mistakenly believe they must dive deeply into concepts like Neural Networks. Instead, I encourage you to: Grab an LLM API and start experimenting Create something tangible, like a simple chatbot or content generator Use tools like KaibanJS to make the process more engaging and productive Focus on leveraging AI to enhance your JavaScript projects Don’t be afraid to make mistakes – they’re part of the learning process Remember, the goal isn’t to become an AI researcher overnight but to explore how AI can enhance your development skills and projects. Who should I interview next? # I highly recommend interviewing Zeno Rocha, the founder of Resend. I’ve been following his work since I was 26 years old, and he has inspired many frontend developers. Any last remarks? # I’m genuinely excited about the possibility of every JavaScript developer becoming an AI developer, regardless of their prior experience with machine learning or data science. By leveraging the familiar JavaScript environment and providing intuitive tools, we can lower the barrier to entry for AI development. We’re facilitating innovation in this domain and fostering a vibrant community where JavaScript developers can support one another in their AI journey. With KaibanJS, we’re democratizing AI development and opening up a world of possibilities for JavaScript enthusiasts everywhere. We aim to make working with AI as natural for JavaScript developers as building a web application – no specialized knowledge is required. Conclusion # Thanks for the interview, Dariel! It is exciting that you mixed AI with JavaScript in such a creative way. I have been looking into agent development lately, and KaibanJS fits the bill nicely! To get started with your own agent adventures, you can learn more about KaibanJS online ↗ . Author: Juho Vepsäläinen Topics Interview Ai Published: 11.10.2024 ← Previous How to get started with web development in 2024? Next → state-ref - Easy to integrate state management library - Interview with Kim Jinwoo ← Previous How to get started with web development in 2024? Next → state-ref - Easy to integrate state management library - Interview with Kim Jinwoo Comments # Show comments Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://docs.python.org/3/license.html#openssl | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:48:41 |
https://aws.amazon.com/blogs/developer/category/developer-tools/aws-sdk-for-net/ | AWS SDK for .NET | AWS Developer Tools Blog Skip to Main Content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Blogs Home Blogs Editions AWS Developer Tools Blog Category: AWS SDK for .NET What’s New in the AWS Deploy Tool for .NET by Philippe El Asmar on 14 OCT 2025 in .NET , Announcements , AWS .NET Development , AWS SDK for .NET , AWS Toolkit for Visual Studio , Developer Tools , Visual Studio Permalink Share Version 2.0 of the AWS Deploy Tool for .NET is now available. This new major version introduces several foundational upgrades to improve the deployment experience for .NET applications on AWS. The tool comes with new minimum runtime requirements. We have upgraded it to require .NET 8 because the predecessor, .NET 6, is now out of […] AWS .NET Distributed Cache Provider for Amazon DynamoDB now Generally Available by Garrett Beatty on 03 JUL 2025 in .NET , Advanced (300) , Announcements , AWS .NET Development , AWS SDK for .NET , Developer Tools Permalink Share Today, we are excited to announce the general availability of the AWS .NET Distributed Cache Provider for Amazon DynamoDB. This is a seamless, serverless caching solution that enables .NET developers to efficiently manage their caching needs across distributed systems. Consistent caching is a difficult problem in distributed architectures, where maintaining data integrity and performance across […] Deploy to ARM-Based Compute with AWS Deploy Tool for .NET by Philippe El Asmar on 08 MAY 2025 in .NET , Announcements , AWS .NET Development , AWS SDK for .NET , AWS Toolkit for Visual Studio , Developer Tools , Visual Studio Permalink Share We’re excited to announce that the AWS Deploy Tool for .NET now supports deploying .NET applications to select ARM-based compute platforms on AWS! Whether you’re deploying from Visual Studio or using the .NET CLI, you can now target cost-effective ARM infrastructure like AWS Graviton with the same streamlined experience you’re used to. Why deploy to […] Announcing the end of support for AWS DynamoDB Session State Provider by Philippe El Asmar on 07 MAY 2025 in .NET , AWS SDK for .NET Permalink Share We are announcing the deprecation of the AWS DynamoDB Session State Provider for .NET. Support for this library will continue for the next six months and will officially end on November 14, 2025. After that date, we will no longer publish updates to the library, including security or critical bug fixes. Previously published releases will […] General Availability of AWS SDK for .NET V4.0 by Norm Johanson on 28 APR 2025 in .NET , Announcements , AWS SDK for .NET , Foundational (100) Permalink Share Version 4.0 of the AWS SDK for .NET has been released for general availability (GA). V4 has been in development for a little over a year in our SDK’s public GitHub repository with 13 previews being released. This new version contains performance improvements, consistency with other AWS SDKs, and bug and usability fixes that required […] Updating AWS SDK defaults – AWS STS service endpoint and Retry Strategy by Alban Gicquel on 10 FEB 2025 in Announcements , AWS Command Line Interface , AWS SDK for .NET , AWS SDK for C++ , AWS SDK for Java , AWS SDK for PHP , AWS SDK for Python , AWS SDK for Ruby , AWS Tools for PowerShell Permalink Share AWS announces important configuration updates coming July 31st, 2025, affecting AWS SDKs and CLIs default settings. Two key changes include switching the AWS Security Token Service (STS) endpoint to regional and updating the default retry strategy to standard. These updates aim to improve service availability and reliability by implementing regional endpoints to reduce cross-regional dependencies and introducing token-bucket throttling for standardized retry behavior. Organizations should test their applications before the release date and can opt-in early or temporarily opt-out of these changes. These updates align with AWS best practices for optimal service performance and security. Preview 4 of AWS SDK for .NET V4 by Norm Johanson on 11 NOV 2024 in .NET , AWS SDK for .NET Permalink Share In August 2024, we announced the first preview of our upcoming version 4 of the AWS SDK for .NET. Since then we have continued making progress and released new previews as we go. At the time of writing this post, the SDK has released preview 4. In this post, we’ll take a look at some […] Enhancing Observability in the AWS SDK for .NET with OpenTelemetry by Muhammad Othman on 12 SEP 2024 in .NET , AWS SDK for .NET Permalink Share Starting with version 3.7.400, the AWS SDK for .NET added significant observability enhancements. It introduced powerful tracing and metrics capabilities with OpenTelemetry support, an industry-standard for observability. With these enhancements, developers can now gain deeper insights into their applications’ behavior, from tracking API call durations to monitoring system metrics. In this blog post, we’ll guide […] Preview 1 of AWS SDK for .NET V4 by Norm Johanson on 15 AUG 2024 in .NET , AWS SDK for .NET Permalink Share In February 2024, AWS SDK for .NET team announced changes to the minimum .NET target versions the AWS SDK for .NET will support. The major changes announced were ending support for .NET Framework 3.5 and changing the minimum .NET Framework to 4.6.2. In June we revised the blog post with the .NET Framework minimum set […] Important changes coming for .NET Framework 3.5 and 4.5 targets of the AWS SDK for .NET by Norm Johanson on 14 FEB 2024 in .NET , AWS SDK for .NET Permalink Share Update June 20th, 2024: Initially this announcement specified the minimum .NET Framework version would change to 4.6.2. During the development of this work we determined that 4.7.2 would be a better minimum target framework for the long term direction of the SDK. With 4.7.2 the SDK has access to more crypto algorithms that we will […] ← Older posts @charset "UTF-8";[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4{position:relative;transition:box-shadow .3s ease}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover{box-shadow:var(--rg-shadow-gray-elevation-1, 1px 1px 20px rgba(0, 0, 0, .1))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0.rgft_e79955da,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003.rgft_e79955da,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover.rgft_e79955da{box-shadow:var(--rg-shadow-gray-elevation-2, 1px 1px 24px rgba(0, 0, 0, .25))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:hover{box-shadow:none}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde{position:relative;transform-style:preserve-3d;overflow:unset!important}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:before{content:"";position:absolute;inset:0;border-radius:inherit;transform:translateZ(-1px);pointer-events:none;transition-property:filter,inset;transition-duration:.3s;transition-timing-function:ease;background-clip:content-box!important;padding:1px}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0.rgft_4df65418:hover:before{filter:blur(20px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:hover:before{filter:none}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_e90ac70d:active:before{filter:blur(8px)!important}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_a4f580d2:before{filter:blur(8px)!important}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #fa6f00 0%, #e433ff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #d14600 0%, #c300e0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #0099ff 0%, #5c7fff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #006ce0 0%, #295eff 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #ff1ae0 0%, #ff386a 50%, #fa6f00 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #d600ba 0%, #eb003b 50%, #d14600 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #00bd6b 0%, #00a4bd 50%, #0099ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #008559 0%, #007e94 50%, #006ce0 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #00bd6b 0%, #0099ff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #008559 0%, #006ce0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #ad5cff 0%, #0099ff 50%, #00a4bd 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #962eff 0%, #006ce0 50%, #007e94 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #ff1ae0 0%, #8575ff 50%, #00a4bd 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #d600ba 0%, #6842ff 50%, #007e94 100%))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:linear-gradient(123deg,#d14600,#c300e0,#6842ff)}[data-eb-6a8f3296] [data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #d14600 0%, #c300e0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #006ce0 0%, #295eff 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #d600ba 0%, #eb003b 50%, #d14600 100%))}[data-eb-6a8f3296] [data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #008559 0%, #007e94 50%, #006ce0 100%))}[data-eb-6a8f3296] [data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #008559 0%, #006ce0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #962eff 0%, #006ce0 50%, #007e94 100%))}[data-eb-6a8f3296] [data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #d600ba 0%, #6842ff 50%, #007e94 100%))}[data-eb-6a8f3296] a.rgft_f7822e54,[data-eb-6a8f3296] button.rgft_f7822e54{--button-size: 44px;--button-pad-h: 24px;--button-pad-borderless-h: 26px;border:2px solid var(--rg-color-background-page-inverted, #0F141A);padding:8px var(--button-pad-h, 24px);border-radius:40px!important;align-items:center;justify-content:center;display:inline-flex;height:var(--button-size, 44px);text-decoration:none!important;text-wrap:nowrap;cursor:pointer;position:relative;transition:all .3s ease}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_094d67e1,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_094d67e1{--button-size: 32px;--button-pad-h: 14px;--button-pad-borderless-h: 16px}[data-eb-6a8f3296] a.rgft_f7822e54>span,[data-eb-6a8f3296] button.rgft_f7822e54>span{color:var(--btn-text-color, inherit)!important}[data-eb-6a8f3296] a.rgft_f7822e54:focus-visible,[data-eb-6a8f3296] button.rgft_f7822e54:focus-visible{outline:2px solid var(--rg-color-focus-ring, #006CE0)!important;outline-offset:4px!important;transition:outline 0s}[data-eb-6a8f3296] a.rgft_f7822e54:focus:not(:focus-visible),[data-eb-6a8f3296] button.rgft_f7822e54:focus:not(:focus-visible){outline:none!important}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_303c672b,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_303c672b{--btn-text-color: var(--rg-color-text-utility-inverted, #FFFFFF);background-color:var(--rg-color-btn-primary-bg, #161D26);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_18409398{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF);border-color:var(--rg-color-background-page-inverted, #0F141A)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_090951dc{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-background-object, #F3F3F7);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_15529d9f{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{--btn-text-color: var(--rg-color-text-utility, #161D26);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{background-image:linear-gradient(97deg,#ffc0ad,#f8c7ff 37.79%,#d2ccff 75.81%,#c2d1ff)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a, linear-gradient(120deg, #f8c7ff 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_bb950a4e{background-image:var(--rg-gradient-a, linear-gradient(120deg, #78008a 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678{--btn-text-color: var(--rg-color-text-utility-inverted, #FFFFFF);background-color:var(--rg-color-btn-visited-bg, #656871);border-color:var(--rg-color-btn-visited-bg, #656871)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678.rgft_18409398,[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678.rgft_15529d9f{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-visited-bg, #FFFFFF)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5{--btn-text-color: var(--rg-color-btn-disabled-text, #B4B4BB);background-color:var(--rg-color-btn-disabled-bg, #F3F3F7);border-color:var(--rg-color-btn-disabled-bg, #F3F3F7);cursor:default}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_18409398,[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_15529d9f{border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_090951dc{--btn-text-color: var(--rg-color-btn-tertiary-disabled-text, #B4B4BB);background-color:#0000}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_18409398:not(.rgft_bb950a4e),[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_15529d9f:not(.rgft_bb950a4e),[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_18409398:not(.rgft_bb950a4e),[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_15529d9f:not(.rgft_bb950a4e){--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF)}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{box-shadow:none}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{background-image:linear-gradient(97deg,#ffc0ad80,#f8c7ff80 37.79%,#d2ccff80 75.81%,#c2d1ff80)}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a-50, linear-gradient(120deg, #f8c7ff 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:hover:not(.rgft_badebaf5),[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:hover:not(.rgft_badebaf5){background-image:var(--rg-gradient-a-50, linear-gradient(120deg, #78008a 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{box-shadow:none}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{background-image:linear-gradient(97deg,#ffc0ad,#f8c7ff 37.79%,#d2ccff 75.81%,#c2d1ff)}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a-pressed, linear-gradient(120deg, rgba(248, 199, 255, .5) 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:active:not(.rgft_badebaf5),[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:active:not(.rgft_badebaf5){background-image:var(--rg-gradient-a-pressed, linear-gradient(120deg, rgba(120, 0, 138, .5) 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] .rgft_8711ccd9{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;background:#0000;border:none;margin:0}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_5e58a6df{text-align:center}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_b7ada98b{display:block}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_beb26dc7{font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}[data-eb-6a8f3296] .rgft_8711ccd9 a{display:inline;position:relative;cursor:pointer;text-decoration:none!important;color:var(--rg-color-link-default, #006CE0);background:linear-gradient(to right,currentcolor,currentcolor);background-size:100% .1em;background-position:0 100%;background-repeat:no-repeat}[data-eb-6a8f3296] .rgft_8711ccd9 a:focus-visible{color:var(--rg-color-link-focus, #006CE0)}[data-eb-6a8f3296] .rgft_8711ccd9 a:hover{color:var(--rg-color-link-hover, #003B8F);animation:rgft_d72bdead .3s cubic-bezier(0,0,.2,1)}[data-eb-6a8f3296] .rgft_8711ccd9 a:visited{color:var(--rg-color-link-visited, #6842FF)}@keyframes rgft_d72bdead{0%{background-size:0 .1em}to{background-size:100% .1em}}[data-eb-6a8f3296] .rgft_8711ccd9 b,[data-eb-6a8f3296] b.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 strong,[data-eb-6a8f3296] strong.rgft_8711ccd9{font-weight:700}[data-eb-6a8f3296] i.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 i,[data-eb-6a8f3296] em.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 em{font-style:italic}[data-eb-6a8f3296] u.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 u{text-decoration:underline}[data-eb-6a8f3296] code.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 code{font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace;border-radius:4px;border:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);color:var(--rg-color-text-secondary, #232B37);padding-top:var(--rg-padding-8);padding-right:var(--rg-padding-8);padding-bottom:var(--rg-padding-8);padding-left:var(--rg-padding-8)}[data-eb-6a8f3296] .rgft_12e1c6fa{display:inline!important;vertical-align:middle}[data-eb-6a8f3296] .rgft_8711ccd9 p img{aspect-ratio:16/9;height:100%;object-fit:cover;width:100%;border-radius:8px;order:1;margin-bottom:var(--rg-margin-4)}[data-eb-6a8f3296] .rgft_8711ccd9 table{table-layout:fixed;border-spacing:0;width:100%}[data-eb-6a8f3296] .rgft_8711ccd9 table td{font-size:14px;border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);padding-top:var(--rg-padding-6);padding-right:var(--rg-padding-6);padding-bottom:var(--rg-padding-6);padding-left:var(--rg-padding-6)}[data-eb-6a8f3296] .rgft_8711ccd9 table td:first-of-type{border-left:1px solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table thead tr:first-of-type>*:first-of-type,[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead)) tr:first-of-type>*:first-of-type{border-top-left-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table thead tr:first-of-type>*:last-of-type,[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead)) tr:first-of-type>*:last-of-type{border-top-right-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table tr:last-of-type td:first-of-type{border-bottom-left-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table tr:last-of-type td:last-of-type{border-bottom-right-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead),:has(th)) tr:first-of-type td{border-top:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th{color:var(--rg-color-text-primary-inverted, #FFFFFF);min-width:280px;max-width:400px;padding:0;text-align:left;vertical-align:top;background-color:var(--rg-color-background-object-inverted, #232B37);border-left:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);padding-top:var(--rg-padding-6);padding-right:var(--rg-padding-6);padding-bottom:var(--rg-padding-6);padding-left:var(--rg-padding-6);row-gap:var(--rg-margin-5);column-gap:var(--rg-margin-5);max-width:100%;min-width:150px}@media (min-width: 480px) and (max-width: 767px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:100%;min-width:150px}}@media (min-width: 768px) and (max-width: 1023px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:240px;min-width:180px}}@media (min-width: 1024px) and (max-width: 1279px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:350px;min-width:240px}}@media (min-width: 1280px) and (max-width: 1599px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:400px;min-width:280px}}@media (min-width: 1600px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:400px;min-width:280px}}[data-eb-6a8f3296] .rgft_8711ccd9 table th:first-of-type{border-top-left-radius:16px;border-top:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-left:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th:nth-of-type(n+3){border-left:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th:last-of-type{border-top-right-radius:16px;border-top:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_a1b66739{display:inline-flex;flex-direction:column;align-items:center;justify-content:center;color:var(--rg-color-text-primary, #161D26);--icon-color: currentcolor}[data-eb-6a8f3296] .rgft_a1b66739.rgft_bc1a8743{height:16px;width:16px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_c0cbb35d{height:20px;width:20px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_bd40fe12{height:32px;width:32px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_27320e58{height:48px;width:48px}[data-eb-6a8f3296] .rgft_a1b66739 svg{fill:none;stroke:none}[data-eb-6a8f3296] .rgft_a1b66739 path[data-fill]:not([fill]){fill:var(--icon-color)}[data-eb-6a8f3296] .rgft_a1b66739 path[data-stroke]{stroke-width:2}[data-eb-6a8f3296] .rgft_a1b66739 path[data-stroke]:not([stroke]){stroke:var(--icon-color)}[data-eb-6a8f3296] .rgft_3ed66ff4{display:inline-flex;flex-direction:column;align-items:center;justify-content:center;color:var(--rg-color-text-primary, #161D26)}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_9124b200{height:10px;width:10px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_bc1a8743{height:16px;width:16px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_c0cbb35d{height:20px;width:20px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_bd40fe12{height:32px;width:32px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_27320e58{height:48px;width:48px}[data-eb-6a8f3296] .rgft_98b54368{color:var(--rg-color-text-body, #232B37)}[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_275611e5{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_275611e5{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_275611e5{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_275611e5{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_275611e5{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_007aef8b{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_007aef8b{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_ff19c5f9{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_ff19c5f9{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368 ul{list-style-type:disc;margin-top:2rem}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee{display:inline;position:relative;cursor:pointer;text-decoration:none!important;color:var(--rg-color-link-default, #006CE0);background:linear-gradient(to right,currentcolor,currentcolor);background-size:100% .1em;background-position:0 100%;background-repeat:no-repeat}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:focus-visible{color:var(--rg-color-link-focus, #006CE0)}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:hover{color:var(--rg-color-link-hover, #003B8F);animation:rgft_9beb7cc5 .3s cubic-bezier(0,0,.2,1)}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:visited{color:var(--rg-color-link-visited, #6842FF)}@keyframes rgft_9beb7cc5{0%{background-size:0 .1em}to{background-size:100% .1em}}[data-eb-6a8f3296] .rgft_d835af5c{color:var(--rg-color-text-title, #161D26)}[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(4.5rem * var(--font-size-multiplier, 1.6));line-height:1.111;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(3.75rem * var(--font-size-multiplier, 1.6));line-height:1.133;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_3e9243e1{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_3e9243e1{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(3.75rem * var(--font-size-multiplier, 1.6));line-height:1.133;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_54816d41{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_54816d41{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(2rem * var(--font-size-multiplier, 1.6));line-height:1.25;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_852a8b78{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_852a8b78{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_286fbc8d{letter-spacing:1.6px;text-transform:uppercase;color:var(--rg-color-text-eyebrow, #161D26)}[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.714;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:2;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_286fbc8d.rgft_cf5cdf86{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_286fbc8d.rgft_cf5cdf86{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.714;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:2;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:2.4;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_286fbc8d.rgft_c6f92487{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_286fbc8d.rgft_c6f92487{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751{color:var(--rg-color-text-utility, #161D26)}[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_927d7fd1{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_927d7fd1{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_100c8a76{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_100c8a76{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_453dc601{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_453dc601{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_949ed5ce{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_949ed5ce{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_5d220f64{color:var(--rg-color-text-heading, #161D26)}[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.1;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(2rem * var(--font-size-multiplier, 1.6));line-height:1.25;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(1.75rem * var(--font-size-multiplier, 1.6));line-height:1.286;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_5d220f64.rgft_94339b09{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_5d220f64.rgft_94339b09{font-family:ShinGo,\30d2\30e9\30ae\30ce\8 | 2026-01-13T08:48:41 |
https://dev.to/szabgab/perl-weekly-593-perl-on-devto-g5k | Perl Weekly #593 - Perl on DEV.to - 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 Gabor Szabo Posted on Dec 5, 2022 • Originally published at perlweekly.com Perl Weekly #593 - Perl on DEV.to # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 593 Hi there! I registered to DEV.to in 2017, more than 5 years ago. Posted a few articles with rather limited success: less than 10 people looked at the articles. Then in 2020 I posted a few more articles. On one of them Tests are awesome! I got as many as 300 readers, but the others have not received much love so I did not continue publishing. In 2021 I had another experiment when I published Perl modules with their own web site on which there were some 600 visitors. Primarily the readers of the Perl Weekly newsletter. I published a few more articles with readers in the low 10s. A few weeks ago I started to publish again. This time several of my articles got above 100 viewers and one, Open Source Development Courses is already above 1100 viewers. I started to get around 600 readers a day. That's already really valuable! So what happened? There were a couple of changes: 1. There are more people on DEV. 2. I publish a lot more articles that appeal to a wider range of people. 3. There is a sort-of network effect. The more people up-vote and bookmark (the two kinds of reactions on DEV) my articles the more people will see it. The nice thing about DEV is that I can republish the articles I published elsewhere (e.g. on PerlMaven , on Code-Maven , or blogs.perl.org ), and also I can set the canonical URL of each article on DEV to the original one on my blog. That way I get the visitors on DEV as well, but the 'Google juice' the articles receive will flow over to my sites. It seems like a win-win for DEV and authors who have blogs elsewhere. You can even configure DEV to pull your RSS feed and create drafts from your articles published elsewhere. I even started to republish the content of the Perl Weekly . So here is what I suggest. If you already write about Perl elsewhere, republish those articles on DEV and tag them with perl . If you are primarily a reader of articles, then register on DEV and start up-voting the Perl-related posts you like. You can even follow a few authors there, get notified when they have new posts, and up-vote those to encourage them to write even more. Alternatively, you can watch the Perl Planetarium . It already follows the perl tag on DEV. Enjoy your week! -- Your editor: Gabor Szabo. Announcements German Perl/Raku Workshop 2023 Call for Papers New feature: HTTPS support blogs.perl.org now has HTTPS support Articles Advent of Code puzzle input downloader SPVM 0.9663 is released JSON Pure Perl Pretty Print SPVM::IO 0.14 is released on Perl/CPAN AoC 2022/1 - Caloric snacks AoC 2022/2 - Rock Paper Scissors cheat guide Day 5: CI for Win32-Wlan Perl module Perl is Actually Portable Discussion The Perl outlook for next year is favorable Testing The 2022 December CI Challenge You probably already know that I think having CI for any project is valuable. I started a series of blog posts in which every day during December 2022 I am going to describe a pull-request I sent to an open source project adding Continuous Integration to it. Add GitHub Action CI to the Net-Async-Redis-XS Perl module This is a nice example where you can see how to configure the GitHub Action for some Perl code that uses Redis. The module author ended up accepting my PR and then switching over to CircleCI. Check out the CircleCI configuration in the GitHub repository . I think it was a very nice way to handle the situation: accepting the work even though the author already knew it will be replace. Advent Calendars Perl Advent Calendar for 2022 Raku Advent Calendar for 2022 Daily CI in December 2022 7 Advent Calendars in 2022 Advent Planet in 2022 CPAN List of new CPAN distributions – Nov 2022 Perl This Week in PSC (089) The weekly report of the Perl Steering Council The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 194 Welcome to a new week with a couple of fun tasks "Digital Clock" and "Frequency Equalizer". If you are new to the weekly challenge then why not join us and have fun every week. For more information, please read the FAQ . RECAP - The Weekly Challenge - 193 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Binary String" and "Odd String" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. The Weekly Challenge 193 Cool use of sprintf() to solve the task. Thanks for sharing the knowledge. An Abundance of Strings Line by line code analysis is the USP of Arne's blog. Great source for any Raku fan. Evens and Oddballs Bruce doesn't use many words but every word is worth every penny. Thanks for your contributions. What An Unusual String You Have There! Or Are You Just Glad To Meet Me? Thank you Colin for sharing blog post. You don't miss the opportunity to treat us with surprises. PWC193 - Binary String Nice show of Raku power to get the job done. Keep it up great work. PWC193 - Odd String Creative individual approach one for each, Perl and Raku. Please do checkout. The Weekly Challenge 193 As always every week we get the varieties and this week is no different. Highly recommended. Binary String and Odd String Near identical solutions in Perl and Raku. Keep sharing the knowledge with us every week. Map, map and remap! Great show of Raku one-liner and other gems. Well done and keep it up. Perl Weekly Challenge 193 Master of Perl one-liner, you don't want to miss. Highly recommended. All the binaries and find the odd man out Interesting narration of task analysis. You should definitely check it out. Odd Binary Are you a Kotlin fan? Roger decided to discuss his Kotlin solution in the blog this week. Highly recommended. The odd binary string Simon style of breaking big task into subtasks makes it so easy to follow. Thanks for your contributions. PWC 193 Nice one-liner in Perl and Raku by Stephen. For me the highlight was the discussion of task analysis. Keep it up great work. Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Events German Perl/Raku Workshop 2023 Call for Papers Perl Jobs by Perl Careers Modern Perl and positive team vibes. UK Remote Perl role If you’re a Modern Perl developer in the UK with Go-lang experience (or at least a strong desire to learn) and you’re searching for a team of dynamos, we’ve found the perfect place for you. This award-winning company may be newer, but the combined experience of their people is impressive. No doubt this is one of the many reasons their AI recruitment marketing business has taken off! Senior Perl Developer with Cross-Trained Chops. UK Remote Perl Role Sure, you’ve got Perl chops for days, but that’s not all you can do — and that’s why our client wants to meet you. They’re looking for senior Perl developers, Node engineers, and those with mighty Python and SQL skills to lead their team. Cross-trained team members are their sweet spot, and whether you’re cross-trained yourself or are open to the possibility, this may be your perfect role. Adventure! Senior Perl roles in Malaysia, Dubai and Malta Clever folks know that if you’re lucky, you can earn a living and have an adventure at the same time. Enter our international client: online trading is their game, and they’re looking for folks with passion, drive, and an appreciation for new experiences. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. Perl role in the UK A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:41 |
https://parenting.forem.com/jess/international-travel-with-toddlers-car-seat-or-vest-considerations-p51 | International Travel with Toddlers: Car Seat (or vest!) Considerations - Parenting 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 Parenting 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 Jess Lee Posted on Oct 14, 2025 International Travel with Toddlers: Car Seat (or vest!) Considerations # travel # gear After flying from the U.S. to Taiwan (twice) with my toddlers, I've become the go-to person for travel gear recs amongst my friends. Instead of sending the same lengthy text message over and over again, I figured I'd jot everything down in a series of posts for easy sharing. Obviously, every kid and journey is different but this series will give you a few things to can consider. No referral links or anything like that. Let's start with the biggest headache: car seats. Unless you're planning to car share everywhere (and even then), you need a solution. And no, you don't want to lug around your cushy at-home car seat, unless it's one of the ones I'm suggesting below: Option 1: Low Budget Traditional Car Seat - Cosco Scenara Next The Cosco Scenera Next is the lightest weight traditional car seat on the market. It's a bulky shape (like all car seats), but it's cheap and it works for both rear and front facing, so it'll last you a while. The link above might be for their older model. Option 2: The Packable Premium - Wayb Pico If you have the budget and want something that actually packs down, the Wayb Pico is the most packable car seat on the market. It's expensive, but if you're a frequent traveler, it might be worth the investment. Check it out at Wayb . I've seen kids strapped into these on short-haul flights and they seem great. I can't imagine keeping my kids in one of these flights for a 6+ hour flight, though. I've never had the pleasure of owning one but you should know about it as part of your research. Important note: this is only for kids who can front-face. Option 3: The Game Changer - RideSafer Travel Vest Here's what I actually recommend for kids old enough to understand instructions: the car seat vest. This thing passes all the same testing standards that regular car seats do, as long as your child stays in the right position and doesn't mess with the straps . For a kid who can follow directions and understands safety, this is ridiculously convenient and cheap. No lugging a giant plastic contraption through airports. Just a vest. Find it here . Rideshare or Car Rental? Since we did not rent a car in Taiwan and traveled via rideshare, we went with the travel vest for the older kid and cosco for the yougner kid. We only did this because I'd be with my kid in the backseat the entire time to monitor their straps. This is really important! We've done some domestic travel where we did rent a car and have had to buy a last minute car seat (the cosco one) because the 4yo would either fall asleep or slouch in the vest, putting them in an unsafe position. So now I own...two cosco seats and a travel vest. Car Seat Travel Bag If you go with a traditional car seat, you'll also want a car seat travel bag. Some airlines (depending on the airport) will provide a clear plastic bag for you but definitely don't bank on that. Here's the car seat travel bag we use, it's cheap and effective. Note: you can bring your car seat (not the vest) directly onto the plane to strap your kids into. I personally don't do this for long-haul flights because my kids would lose their minds, but it is the safest option for them while in-flight. A Word of Warning About International Cars Here's something nobody tells you: car safety standards vary wildly by country. In Taiwan, 99% of cars didn't have the ratcheting mechanism in the seat belt like they do in the U.S. Brand new Teslas didn't have them. So, if you're paranoid, you might want a car seat that supports lower anchors (both cosco and wayb do). Anyway, be sure to do your research on your destination country before you land so you know what to expect! Next Up My next post will be about gear you'll want while you're 30,000 feet in the air! 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 Peter Kim Frank Peter Kim Frank Peter Kim Frank Follow Doing a bit of everything at DEV / Forem Email peter@dev.to Education Wesleyan University Pronouns He/Him Work Co-Founder Joined Jan 3, 2017 • Oct 15 '25 Dropdown menu Copy link Hide +1 for the Cosco. We normally just use the straps to hook the car seat directly to our stroller which works like a charm. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Matt Figler Matt Figler Matt Figler Follow Joined Jun 22, 2017 • Oct 22 '25 Dropdown menu Copy link Hide This is an awesome breakdown, takes a little bit of stress out of family travel. Like comment: Like comment: 2 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 Jess Lee Follow Building DEV and Forem with everyone here. Interested in the future. Location USA / TAIWAN Pronouns she/they Work Co-Founder & COO at Forem Joined Jul 29, 2016 💎 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 Parenting — 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. 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 . Parenting © 2016 - 2026. Navigating the chaos and joy of parenting. Log in Create account | 2026-01-13T08:48:41 |
https://gustwind.js.org/ | 🐳 "> Gustwind ☰ 🐳💨 Modes Configuration Routing Concepts Templating Deployment Blog GitHub 🐳💨 Gustwind Deno powered website creator Gustwind is a Deno -powered website creator that allows component-oriented development of large-scale sites using HTMLisp, a variant of HTML. Conceptually, it is split as follows: Development mode lets you preview the site and modify page definitions to commit later Production mode generates pure static HTML with CSS inlined to the files HTMLisp is the default option for templating and component definitions Data sources define how information is brought to a site Route definition binds it all together and allows connecting data sources to specific routes Plugin system allows replacing any part of the system to fit custom requirements Please see the documentation to learn more about the concepts. Getting started 🔗 There is a simple GitHub template that has basic features set up. It renders the project readme as index.html , and you should expand/change the project to your liking. Data flow 🔗 Gustwind accepts TypeScript, Markdown, and HTMLisp definitions. Then, the build process emits HTML and JavaScript. Note that you can replace many aspects of the system by using plugins to fit your requirements. The image below describes the basic idea: It's possible to customize the input formats and it can load data from asynchronous sources, say GraphQL APIs, so Gustwind can be used with headless content APIs. Server-Side Rendering (SSR) 🔗 Although Gustwind was designed mainly with Static Site Generation (SSG) in mind, portions of it can be used in a server environment. There's for example a simplified version of the router designed for this purpose, and the default templating solution works both in server and client as it is light by design. Example sites 🔗 Given Gustwind is still in a rapid development phase, the APIs change every once in a while. The source of this site is the most up to date resource, and I've listed other examples below: jster.net - Source sidewind.js.org - Source dragjs - Source Future Frontend - Source SurviveJS - Source Performance 🔗 In my experience, Gustwind is somewhat performant although I haven't benchmarked it. The main factors contributing to speed are its parallelized build process and light rendering engine. There are still ways to push it further by implementing techniques, like incremental compilation to compile only pages affected by a given change. The underlying architecture has been designed with advanced features in mind, so although they aren't trivial to implement, they aren't impossible if there is time and interest. Earlier related work 🔗 Tailspin was an experimental site generator built with partially the same technology. In this project, the ideas have been largely re-implemented and taken further. In some ways, Tailspin went further, though, as it implemented component level introspection (types) and editors while allowing JSX syntax. Antwar was a React-based static site generator. The experiences with Antwar over years, have been put to good use in this project. About Gustwind is a Deno powered website creator. It was written with speed and flexibility in mind. Navigation Modes Configuration Routing Concepts Templating Deployment Credits Gustwind was developed by Juho Vepsäläinen . | 2026-01-13T08:48:41 |
https://survivejs.com/books/webpack/ | SurviveJS – Webpack 5 Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... SurviveJS – Webpack 5 Webpack ↗ is a module bundler meant for building JavaScript applications and sites. In this book, I will go through main features of webpack while teaching you to compose configuration using webpack-merge ↗ . Incidentally, I developed webpack-merge for the purposes of this book and since then it has become a popular solution for taming the complexity of webpack configuration. The book is meant to web developers ranging from beginners to advanced although you should be familiar with the basic ideas behind JavaScript language to get most out of it. The book content was developed during many years with the help of the community and it complements the official documentation. Even if you know webpack well already, I have taken care to include short summaries capturing the main points of the book so you can fill the gaps in your knowledge and understanding of the tool. Read the webpack book Buy the webpack book ↗ Testimonials Clément Paris Front-end Engineer After weeks failing at configuring webpack, I stumbled upon SurviveJS book while looking for yet another tutorial. Since that day, it has been my go-to resource for every single webpack question I ever had. Andrea Chiumenti CEO Red Software Systems ↗ Brilliant! A must have if you want to to learn webpack but also if need an updated reference guide. I always use it as a reference guide when I develop. Gavin Doughtie Senior Software Engineer Google ↗ Before I worked through the SurviveJS webpack book, my own webpack config, cobbled together from random code on the Internet, was a mystery to me. Afterwards, I have route-splitting and parallel-loading superpowers. Neeraj Singh Founder Big Binary ↗ Webpack is powerful but configuring it can be painful. Same goes with React. There are so many ways of configuring React with asset compilation, minification etc that it is easy to get lost. This book provides practical tips on how to proceed. Aaron Harris Software Engineer This guide was a great starter in taming the Wild West of ESNext-era JavaScript development. Its beauty comes from its commitment to not skipping the fundamentals in favor of a fast demo, but making sure you’re understanding what you’re doing as you bootstrap your next JavaScript-based UI project. Julien Castelain Software Engineer Liferay ↗ This guide is a great way to get started with webpack or improve your existing skills. After a detailed introduction, you’ll start working on a webpack project that provides all you need to push your app to production. Highly recommended. Availability Although you can read the book online for free , you can also purchase it in a copy to support the development of the content. See also consulting for other available options. Leanpub (digital, always up to date with the site) ↗ Amazon (paperback, last major revision) ↗ Kindle (digital, last major revision) ↗ Table of contents Foreword It's a funny story how I started with webpack. Before getting addicted to JavaScript, I also developed in Java. I tried GWT (Google Web Toolkit) in that time. GWT is a Java-to-JavaScript Compiler, which has a great feature: code splitting. I liked this feature and missed it in existing JavaScript t… Preface The book you are reading right now goes years back. It all started with a comment I made on Christian Alfoni's blog in 2014. It was when I discovered webpack and React, and I felt there was a need for a cookbook about the topics. The work began with a GitHub wiki in early 2015. After a while, I re… Introduction Webpack simplifies web development by solving a fundamental problem: bundling. It takes in various assets, such as JavaScript, CSS, and HTML, and transforms them into a format that's convenient to consume through a browser. Doing this well takes a significant amount of pain away from web developmen… What is Webpack Webpack is a module bundler. Webpack can take care of bundling alongside a separate task runner. However, the line between bundler and task runner has become blurred thanks to community-developed webpack plugins. Sometimes these plugins are used to perform tasks that are usually done outside of web… Developing In this part, you get up and running with webpack. You will learn to configure webpack-plugin-serve. Finally, you compose the configuration so that it's possible to expand in the following parts of the book. … Getting Started Before getting started, make sure you are using a recent version of Node. You should use at least the most current LTS (long-term support) version as the configuration of the book has been written with modern Node features in mind. You should have node and npm (or yarn) commands available at your … Development Server When developing a frontend without any special tooling, you often end up having to refresh the browser to see changes. Given this gets annoying fast, there's tooling to remedy the problem. The first tools on the market were LiveReload and Browsersync. The point of either is to allow refreshing the… Composing Configuration Even though not a lot has been done with webpack yet, the amount of configuration is starting to feel substantial. Now you have to be careful about the way you compose it as you have separate production and development targets in the project. The situation can only get worse as you want to add more… Styling In this part, you will learn about styling-related concerns in detail including loading styles, separating CSS, eliminating unused CSS, and autoprefixing. … Loading Styles Webpack doesn't handle styling out of the box, and you will have to use loaders and plugins to allow loading style files. In this chapter, you will set up CSS with the project and see how it works out with automatic browser refreshing. When you make a change to the CSS webpack doesn't have to force… Separating CSS Even though there is a nice build set up now, where did all the CSS go? As per configuration, it has been inlined to JavaScript! Although this can be convenient during development, it doesn't sound ideal. The current solution doesn't allow caching CSS. You can also get a Flash of Unstyled Content … Eliminating Unused CSS Frameworks like Bootstrap or Tailwind tend to come with a lot of CSS. Often you use only a small part of it and if you aren't careful, you will bundle the unused CSS. PurgeCSS is a tool that can achieve this by analyzing files. It walks through your code and figures out which CSS classes are being… Autoprefixing It can be challenging to remember which vendor prefixes you have to use for specific CSS rules to support a large variety of users. Autoprefixing solves this problem. It can be enabled through PostCSS and the autoprefixer plugin. autoprefixer uses Can I Use service to figure out which rules should … Loading Assets In this part, you will learn how to load different types of assets using webpack's loaders. Especially images, fonts, and JavaScript receive particular attention. You also learn how webpack's loader definitions work. … Loader Definitions Webpack provides multiple ways to set up module loaders. Each loader is a function accepting input and returning output. They can have side effects as they can emit to the file system and can intercept execution to implement caching. Anatomy of a loader Webpack supports common JavaScript formats … Loading Images Image loading and processing can be a concern when developing sites and applications. The problem can be solved by pushing the images to a separate service that then takes care of optimizing them and provides an interface for consuming them. For smaller scale usage, webpack is a good option as it … Loading Fonts Loading fonts is similar to loading images. It does come with unique challenges, though. How to know what font formats to support? There can be up to four font formats to worry about if you want to provide first class support to each browser. The problem can be solved by deciding a set of browsers… Loading JavaScript Webpack processes ES2015 module definitions by default and transforms them into code. It does not transform specific syntax, such as const, though. The resulting code can be problematic especially in the older browsers. To get a better idea of the default transform, we can generate a build while s… Building In this part, you enable source maps on the build, discuss how to split it into separate bundles in various ways, and learn to tidy up the result. … Source Maps Source maps in Chrome When your source code has gone through transformations, debugging in the browser becomes a problem. Source maps solve this problem by providing a mapping between the original and the transformed source code. In addition to source compiling to JavaScript, this works for stylin… Code Splitting Web applications tend to grow big as features are developed. The longer it takes for your site to load, the more frustrating it's to the user. This problem is amplified in a mobile environment where the connections can be slow. Even though splitting bundles can help a notch, they are not the only … Bundle Splitting Although code splitting gives control over when code is loaded, it's not the only way webpack lets you shape the output. Bundle splitting is a complementary technique that lets you define splitting behavior on the level of configuration. A common use case is extracting so called vendor bundle that… Tidying Up The current setup doesn't clean the build directory between builds. As a result, it keeps on accumulating files as the project changes. Given this can get annoying, you should clean it up in between. Another nice touch would be to include information about the build itself to the generated bundles… Optimizing In this part, you will learn about code minification, setting environment variables, adding hashing to filenames, webpack runtime, analyzing build statistics, and improving webpack performance. … Minifying Since webpack 4, the production output gets minified using terser by default. Terser is an ES2015+ compatible JavaScript-minifier. Compared to UglifyJS, the earlier standard for many projects, it's a future-oriented option. Although webpack minifies the output by default, it's good to understand h… Tree Shaking Tree shaking is a feature enabled by the ES2015 module definition. The idea is that given it's possible to analyze the module definition statically without running it, webpack can tell which parts of the code are being used and which are not. It's possible to verify this behavior by expanding the a… Environment Variables Sometimes a part of your code should execute only during development. Or you could have experimental features in your build that are not ready for production yet. Controlling environment variables becomes valuable as you can toggle functionality using them. Since JavaScript minifiers can remove de… Adding Hashes to Filenames Even though the generated build works, the file names it uses is problematic. It doesn't allow to leverage client level cache efficiently as there's no way tell whether or not a file has changed. Cache invalidation can be achieved by including a hash to the filenames. T> Starting from version 5, w… Separating a Runtime When webpack writes bundles, it maintains a runtime as well. The runtime includes a manifest of the files to be loaded initially. If the names of the files change, then the manifest changes and the change invalidates the file in which it is contained. For this reason, it can be a good idea to write… Build Analysis Analyzing build statistics is a good step towards understanding webpack better. The available tooling helps to answer the following questions: What's the composition of the project bundles? What kind of dependencies do project modules have? How does the size of the project change over time? Which … Performance Webpack's performance out of the box is often enough for small projects. That said, it begins to hit limits as your project grows in scale, and it's a frequent topic in webpack's issue tracker. There are a couple of ground rules when it comes to optimization: Know what to optimize. Perform fast t… Output This part covers different output techniques webpack provides. You see how to manage a multi-page setup, how to implement server-side rendering, and how to use module federation to develop micro frontends. … Build Targets Even though webpack is used most commonly for bundling web applications, it can do more. You can use it to target Node or desktop environments, such as Electron. Webpack can also bundle as a library while writing an appropriate output wrapper making it possible to consume the library. Webpack's ou… Multiple Pages Even though webpack is often used for bundling single-page applications, it's possible to use it with multiple separate pages as well. The idea is similar to the way you generated many output files in the Targets chapter. That's achievable through MiniHtmlWebpackPlugin and a bit of configuration. … Server-Side Rendering Server-Side Rendering (SSR) is a technique that allows you to serve an initial payload with HTML, JavaScript, CSS, and even application state. You serve a fully rendered HTML page that would make sense even without JavaScript enabled. In addition to providing potential performance benefits, this ca… Module Federation Micro frontends take the idea of microservices to frontend development. Instead of developing the application or a site as a monolith, the point is to split it as smaller portions programmed separately that are then tied together during runtime. With the approach, you can use different technologie… Techniques In this part, you will learn to use webpack techniques such as dynamic loading, using web workers, internationalization, testing, deploying, and package consumption. … Dynamic Loading Even though you can get far with webpack's code splitting features covered in the Code Splitting chapter, there's more to it. Webpack provides more dynamic ways to deal with code through require.context. Dynamic loading with require.context require.context provides a general form of code splittin… Web Workers Web workers allow you to push work outside of main execution thread of JavaScript, making them convenient for lengthy computations and background work. Moving data between the main thread and the worker comes with communication-related overhead. The split provides isolation that forces workers to … Internationalization Internationalization (i18n) is a big topic by itself. The broadest definition has to do with translating your user interface to other languages. Localization (l10n) is a more specific term, and it describes how to adapt your application to a particular locale or market. Different locales can have t… Testing Testing is a vital part of development. Even though techniques, such as linting, can help to spot and solve issues, they have their limitations. Testing can be applied to the code and an application on many different levels. You can unit test a specific piece of code, or you can look at the applic… Deploying Applications A project built with webpack can be deployed to a variety of environments. A public project that doesn't rely on a backend can be pushed to GitHub Pages using the gh-pages package. Also, there are a variety of webpack plugins that can target other environments, such as S3. Deploying with gh-pages … Consuming Packages Sometimes packages have not been packaged the way you expect, and you have to tweak the way webpack interprets them. Webpack provides multiple ways to achieve this. resolve.alias Sometimes packages do not follow the standard rules and their package.json contains a faulty main field. It can be mis… Extending Even though there are a lot of available loaders and plugins for webpack, it's good to be able to extend it. In this part, you go through a couple of short examples to understand how to get started. … Extending with Loaders As you have seen so far, loaders are one of the building blocks of webpack. If you want to load an asset, you most likely need to set up a matching loader definition. Even though there are a lot of available loaders, it's possible you are missing one fitting your purposes. You'll learn to develop … Extending with Plugins Compared to loaders, plugins are a more flexible means to extend webpack. You have access to webpack's compiler and compilation processes. It's possible to run child compilers, and plugins can work in tandem with loaders as MiniCssExtractPlugin shows. Plugins allow you to intercept webpack's execu… Conclusion As this book has demonstrated, webpack is a versatile tool. To make it easier to recap the content and techniques, go through the checklists below. General checklist Source maps** allow you to debug your code in the browser during development. They can also give better quality stack traces during… Appendices As not everything that's worth discussing fits into the main content, you can find related material in brief appendices. These support the primary content and explain specific topics, such as Hot Module Replacement, in greater detail. You will also learn to troubleshoot webpack. … Comparison of Build Tools Back in the day, it was enough to concatenate scripts together. Times have changed, though, and distributing your JavaScript code can be a complicated endeavor. This problem has escalated with the rise of single-page applications (SPAs) as they tend to rely on many big libraries. For this reason, m… Hot Module Replacement Hot Module Replacement (HMR) builds on top of the WDS. It enables an interface that makes it possible to swap modules live. For example, style-loader can update your CSS without forcing a refresh. Implementing HMR for styles is ideal because CSS is stateless by design. HMR is possible with JavaScr… CSS Modules Perhaps the most significant challenge of CSS is that all rules exist within global scope, meaning that two classes with the same name will collide. The limitation is inherent to the CSS specification, but projects have workarounds for the issue. CSS Modules introduces local scope for every module … Searching with React Let's say you want to implement a rough little search for an application without a proper backend. You could do it through lunr and generate a static search index to serve. The problem is that the index can be sizable depending on the amount of the content. The good thing is that you don't need th… Troubleshooting Using webpack can lead to a variety of runtime warnings or errors. Often a particular part of the build fails for a reason or another. A basic process can be used to figure out these problems: Enable stats.errorDetails in webpack configuration to get more information. Study the origin of the error… Glossary Given webpack comes with specific terminology, the principal terms and their explanations have been gathered below. Asset** is a general term for the media and source files of a project that are the raw material used by webpack in building a bundle. Bundle** is the result of bundling. Bundling inv… Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://dev.to/t/seniorgolf | Seniorgolf - 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 # seniorgolf Follow Hide Golf for the senior community, focusing on adapted play and gear Create Post 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 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:48:41 |
https://dev.to/souparnika | Souparnika - 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 Organization actions Souparnika A collection of sample projects of my team Joined Joined on Aug 21, 2020 External link icon Meet the team Post 0 posts published Member 1 member 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:48:41 |
https://javascript.info/operators#string-concatenation-with-binary | Basic operators, maths Sorry, Internet Explorer is not supported, please use a newer browser. EN AR عربي EN English ES Español FA فارسی FR Français ID Indonesia IT Italiano JA 日本語 KO 한국어 RU Русский TR Türkçe UK Українська UZ Oʻzbek ZH 简体中文 We want to make this open-source project available for people all around the world. Help to translate the content of this tutorial to your language! Buy EPUB/PDF Search Search Tutorial map Light theme Dark theme Share عربي English Español فارسی Français Indonesia Italiano 日本語 한국어 Русский Türkçe Українська Oʻzbek 简体中文 Tutorial The JavaScript language JavaScript Fundamentals November 14, 2022 Basic operators, maths We know many operators from school. They are things like addition + , multiplication * , subtraction - , and so on. In this chapter, we’ll start with simple operators, then concentrate on JavaScript-specific aspects, not covered by school arithmetic. Terms: “unary”, “binary”, “operand” Before we move on, let’s grasp some common terminology. An operand – is what operators are applied to. For instance, in the multiplication of 5 * 2 there are two operands: the left operand is 5 and the right operand is 2 . Sometimes, people call these “arguments” instead of “operands”. An operator is unary if it has a single operand. For example, the unary negation - reverses the sign of a number: let x = 1; x = -x; alert( x ); // -1, unary negation was applied An operator is binary if it has two operands. The same minus exists in binary form as well: let x = 1, y = 3; alert( y - x ); // 2, binary minus subtracts values Formally, in the examples above we have two different operators that share the same symbol: the negation operator, a unary operator that reverses the sign, and the subtraction operator, a binary operator that subtracts one number from another. Maths The following math operations are supported: Addition + , Subtraction - , Multiplication * , Division / , Remainder % , Exponentiation ** . The first four are straightforward, while % and ** need a few words about them. Remainder % The remainder operator % , despite its appearance, is not related to percents. The result of a % b is the remainder of the integer division of a by b . For instance: alert( 5 % 2 ); // 1, the remainder of 5 divided by 2 alert( 8 % 3 ); // 2, the remainder of 8 divided by 3 alert( 8 % 4 ); // 0, the remainder of 8 divided by 4 Exponentiation ** The exponentiation operator a ** b raises a to the power of b . In school maths, we write that as a b . For instance: alert( 2 ** 2 ); // 2² = 4 alert( 2 ** 3 ); // 2³ = 8 alert( 2 ** 4 ); // 2⁴ = 16 Just like in maths, the exponentiation operator is defined for non-integer numbers as well. For example, a square root is an exponentiation by ½: alert( 4 ** (1/2) ); // 2 (power of 1/2 is the same as a square root) alert( 8 ** (1/3) ); // 2 (power of 1/3 is the same as a cubic root) String concatenation with binary + Let’s meet the features of JavaScript operators that are beyond school arithmetics. Usually, the plus operator + sums numbers. But, if the binary + is applied to strings, it merges (concatenates) them: let s = "my" + "string"; alert(s); // mystring Note that if any of the operands is a string, then the other one is converted to a string too. For example: alert( '1' + 2 ); // "12" alert( 2 + '1' ); // "21" See, it doesn’t matter whether the first operand is a string or the second one. Here’s a more complex example: alert(2 + 2 + '1' ); // "41" and not "221" Here, operators work one after another. The first + sums two numbers, so it returns 4 , then the next + adds the string 1 to it, so it’s like 4 + '1' = '41' . alert('1' + 2 + 2); // "122" and not "14" Here, the first operand is a string, the compiler treats the other two operands as strings too. The 2 gets concatenated to '1' , so it’s like '1' + 2 = "12" and "12" + 2 = "122" . The binary + is the only operator that supports strings in such a way. Other arithmetic operators work only with numbers and always convert their operands to numbers. Here’s the demo for subtraction and division: alert( 6 - '2' ); // 4, converts '2' to a number alert( '6' / '2' ); // 3, converts both operands to numbers Numeric conversion, unary + The plus + exists in two forms: the binary form that we used above and the unary form. The unary plus or, in other words, the plus operator + applied to a single value, doesn’t do anything to numbers. But if the operand is not a number, the unary plus converts it into a number. For example: // No effect on numbers let x = 1; alert( +x ); // 1 let y = -2; alert( +y ); // -2 // Converts non-numbers alert( +true ); // 1 alert( +"" ); // 0 It actually does the same thing as Number(...) , but is shorter. The need to convert strings to numbers arises very often. For example, if we are getting values from HTML form fields, they are usually strings. What if we want to sum them? The binary plus would add them as strings: let apples = "2"; let oranges = "3"; alert( apples + oranges ); // "23", the binary plus concatenates strings If we want to treat them as numbers, we need to convert and then sum them: let apples = "2"; let oranges = "3"; // both values converted to numbers before the binary plus alert( +apples + +oranges ); // 5 // the longer variant // alert( Number(apples) + Number(oranges) ); // 5 From a mathematician’s standpoint, the abundance of pluses may seem strange. But from a programmer’s standpoint, there’s nothing special: unary pluses are applied first, they convert strings to numbers, and then the binary plus sums them up. Why are unary pluses applied to values before the binary ones? As we’re going to see, that’s because of their higher precedence . Operator precedence If an expression has more than one operator, the execution order is defined by their precedence , or, in other words, the default priority order of operators. From school, we all know that the multiplication in the expression 1 + 2 * 2 should be calculated before the addition. That’s exactly the precedence thing. The multiplication is said to have a higher precedence than the addition. Parentheses override any precedence, so if we’re not satisfied with the default order, we can use them to change it. For example, write (1 + 2) * 2 . There are many operators in JavaScript. Every operator has a corresponding precedence number. The one with the larger number executes first. If the precedence is the same, the execution order is from left to right. Here’s an extract from the precedence table (you don’t need to remember this, but note that unary operators are higher than corresponding binary ones): Precedence Name Sign … … … 14 unary plus + 14 unary negation - 13 exponentiation ** 12 multiplication * 12 division / 11 addition + 11 subtraction - … … … 2 assignment = … … … As we can see, the “unary plus” has a priority of 14 which is higher than the 11 of “addition” (binary plus). That’s why, in the expression "+apples + +oranges" , unary pluses work before the addition. Assignment Let’s note that an assignment = is also an operator. It is listed in the precedence table with the very low priority of 2 . That’s why, when we assign a variable, like x = 2 * 2 + 1 , the calculations are done first and then the = is evaluated, storing the result in x . let x = 2 * 2 + 1; alert( x ); // 5 Assignment = returns a value The fact of = being an operator, not a “magical” language construct has an interesting implication. All operators in JavaScript return a value. That’s obvious for + and - , but also true for = . The call x = value writes the value into x and then returns it . Here’s a demo that uses an assignment as part of a more complex expression: let a = 1; let b = 2; let c = 3 - (a = b + 1); alert( a ); // 3 alert( c ); // 0 In the example above, the result of expression (a = b + 1) is the value which was assigned to a (that is 3 ). It is then used for further evaluations. Funny code, isn’t it? We should understand how it works, because sometimes we see it in JavaScript libraries. Although, please don’t write the code like that. Such tricks definitely don’t make code clearer or readable. Chaining assignments Another interesting feature is the ability to chain assignments: let a, b, c; a = b = c = 2 + 2; alert( a ); // 4 alert( b ); // 4 alert( c ); // 4 Chained assignments evaluate from right to left. First, the rightmost expression 2 + 2 is evaluated and then assigned to the variables on the left: c , b and a . At the end, all the variables share a single value. Once again, for the purposes of readability it’s better to split such code into few lines: c = 2 + 2; b = c; a = c; That’s easier to read, especially when eye-scanning the code fast. Modify-in-place We often need to apply an operator to a variable and store the new result in that same variable. For example: let n = 2; n = n + 5; n = n * 2; This notation can be shortened using the operators += and *= : let n = 2; n += 5; // now n = 7 (same as n = n + 5) n *= 2; // now n = 14 (same as n = n * 2) alert( n ); // 14 Short “modify-and-assign” operators exist for all arithmetical and bitwise operators: /= , -= , etc. Such operators have the same precedence as a normal assignment, so they run after most other calculations: let n = 2; n *= 3 + 5; // right part evaluated first, same as n *= 8 alert( n ); // 16 Increment/decrement Increasing or decreasing a number by one is among the most common numerical operations. So, there are special operators for it: Increment ++ increases a variable by 1: let counter = 2; counter++; // works the same as counter = counter + 1, but is shorter alert( counter ); // 3 Decrement -- decreases a variable by 1: let counter = 2; counter--; // works the same as counter = counter - 1, but is shorter alert( counter ); // 1 Important: Increment/decrement can only be applied to variables. Trying to use it on a value like 5++ will give an error. The operators ++ and -- can be placed either before or after a variable. When the operator goes after the variable, it is in “postfix form”: counter++ . The “prefix form” is when the operator goes before the variable: ++counter . Both of these statements do the same thing: increase counter by 1 . Is there any difference? Yes, but we can only see it if we use the returned value of ++/-- . Let’s clarify. As we know, all operators return a value. Increment/decrement is no exception. The prefix form returns the new value while the postfix form returns the old value (prior to increment/decrement). To see the difference, here’s an example: let counter = 1; let a = ++counter; // (*) alert(a); // 2 In the line (*) , the prefix form ++counter increments counter and returns the new value, 2 . So, the alert shows 2 . Now, let’s use the postfix form: let counter = 1; let a = counter++; // (*) changed ++counter to counter++ alert(a); // 1 In the line (*) , the postfix form counter++ also increments counter but returns the old value (prior to increment). So, the alert shows 1 . To summarize: If the result of increment/decrement is not used, there is no difference in which form to use: let counter = 0; counter++; ++counter; alert( counter ); // 2, the lines above did the same If we’d like to increase a value and immediately use the result of the operator, we need the prefix form: let counter = 0; alert( ++counter ); // 1 If we’d like to increment a value but use its previous value, we need the postfix form: let counter = 0; alert( counter++ ); // 0 Increment/decrement among other operators The operators ++/-- can be used inside expressions as well. Their precedence is higher than most other arithmetical operations. For instance: let counter = 1; alert( 2 * ++counter ); // 4 Compare with: let counter = 1; alert( 2 * counter++ ); // 2, because counter++ returns the "old" value Though technically okay, such notation usually makes code less readable. One line does multiple things – not good. While reading code, a fast “vertical” eye-scan can easily miss something like counter++ and it won’t be obvious that the variable increased. We advise a style of “one line – one action”: let counter = 1; alert( 2 * counter ); counter++; Bitwise operators Bitwise operators treat arguments as 32-bit integer numbers and work on the level of their binary representation. These operators are not JavaScript-specific. They are supported in most programming languages. The list of operators: AND ( & ) OR ( | ) XOR ( ^ ) NOT ( ~ ) LEFT SHIFT ( << ) RIGHT SHIFT ( >> ) ZERO-FILL RIGHT SHIFT ( >>> ) These operators are used very rarely, when we need to fiddle with numbers on the very lowest (bitwise) level. We won’t need these operators any time soon, as web development has little use of them, but in some special areas, such as cryptography, they are useful. You can read the Bitwise Operators chapter on MDN when a need arises. Comma The comma operator , is one of the rarest and most unusual operators. Sometimes, it’s used to write shorter code, so we need to know it in order to understand what’s going on. The comma operator allows us to evaluate several expressions, dividing them with a comma , . Each of them is evaluated but only the result of the last one is returned. For example: let a = (1 + 2, 3 + 4); alert( a ); // 7 (the result of 3 + 4) Here, the first expression 1 + 2 is evaluated and its result is thrown away. Then, 3 + 4 is evaluated and returned as the result. Comma has a very low precedence Please note that the comma operator has very low precedence, lower than = , so parentheses are important in the example above. Without them: a = 1 + 2, 3 + 4 evaluates + first, summing the numbers into a = 3, 7 , then the assignment operator = assigns a = 3 , and the rest is ignored. It’s like (a = 1 + 2), 3 + 4 . Why do we need an operator that throws away everything except the last expression? Sometimes, people use it in more complex constructs to put several actions in one line. For example: // three operations in one line for (a = 1, b = 3, c = a * b; a < 10; a++) { ... } Such tricks are used in many JavaScript frameworks. That’s why we’re mentioning them. But usually they don’t improve code readability so we should think well before using them. Tasks The postfix and prefix forms importance: 5 What are the final values of all variables a , b , c and d after the code below? let a = 1, b = 1; let c = ++a; // ? let d = b++; // ? solution The answer is: a = 2 b = 2 c = 2 d = 1 let a = 1, b = 1; alert( ++a ); // 2, prefix form returns the new value alert( b++ ); // 1, postfix form returns the old value alert( a ); // 2, incremented once alert( b ); // 2, incremented once Assignment result importance: 3 What are the values of a and x after the code below? let a = 2; let x = 1 + (a *= 2); solution The answer is: a = 4 (multiplied by 2) x = 5 (calculated as 1 + 4) Type conversions importance: 5 What are results of these expressions? "" + 1 + 0 "" - 1 + 0 true + false 6 / "3" "2" * "3" 4 + 5 + "px" "$" + 4 + 5 "4" - 2 "4px" - 2 " -9 " + 5 " -9 " - 5 null + 1 undefined + 1 " \t \n" - 2 Think well, write down and then compare with the answer. solution "" + 1 + 0 = "10" // (1) "" - 1 + 0 = -1 // (2) true + false = 1 6 / "3" = 2 "2" * "3" = 6 4 + 5 + "px" = "9px" "$" + 4 + 5 = "$45" "4" - 2 = 2 "4px" - 2 = NaN " -9 " + 5 = " -9 5" // (3) " -9 " - 5 = -14 // (4) null + 1 = 1 // (5) undefined + 1 = NaN // (6) " \t \n" - 2 = -2 // (7) The addition with a string "" + 1 converts 1 to a string: "" + 1 = "1" , and then we have "1" + 0 , the same rule is applied. The subtraction - (like most math operations) only works with numbers, it converts an empty string "" to 0 . The addition with a string appends the number 5 to the string. The subtraction always converts to numbers, so it makes " -9 " a number -9 (ignoring spaces around it). null becomes 0 after the numeric conversion. undefined becomes NaN after the numeric conversion. Space characters are trimmed off string start and end when a string is converted to a number. Here the whole string consists of space characters, such as \t , \n and a “regular” space between them. So, similarly to an empty string, it becomes 0 . Fix the addition importance: 5 Here’s a code that asks the user for two numbers and shows their sum. It works incorrectly. The output in the example below is 12 (for default prompt values). Why? Fix it. The result should be 3 . let a = prompt("First number?", 1); let b = prompt("Second number?", 2); alert(a + b); // 12 solution The reason is that prompt returns user input as a string. So variables have values "1" and "2" respectively. let a = "1"; // prompt("First number?", 1); let b = "2"; // prompt("Second number?", 2); alert(a + b); // 12 What we should do is to convert strings to numbers before + . For example, using Number() or prepending them with + . For example, right before prompt : let a = +prompt("First number?", 1); let b = +prompt("Second number?", 2); alert(a + b); // 3 Or in the alert : let a = prompt("First number?", 1); let b = prompt("Second number?", 2); alert(+a + +b); // 3 Using both unary and binary + in the latest code. Looks funny, doesn’t it? Previous lesson Next lesson Share Tutorial map Comments read this before commenting… If you have suggestions what to improve - please submit a GitHub issue or a pull request instead of commenting. If you can't understand something in the article – please elaborate. To insert few words of code, use the <code> tag, for several lines – wrap them in <pre> tag, for more than 10 lines – use a sandbox ( plnkr , jsbin , codepen …) Chapter JavaScript Fundamentals Lesson navigation Terms: “unary”, “binary”, “operand” Maths String concatenation with binary + Numeric conversion, unary + Operator precedence Assignment Modify-in-place Increment/decrement Bitwise operators Comma Tasks (4) Comments Share Edit on GitHub © 2007—2026 Ilya Kantor about the project contact us terms of usage privacy policy | 2026-01-13T08:48:41 |
https://casinoaustraliaonline.net/payid-casinos/ | Safe PayID Casinos in Australia Australian casinos Australian casinos Real Money Casinos New Casinos Best Payout Casinos Instant Payout Casinos Mobile Casinos AU$ Casinos AU$1-5 Minimum Deposit Under 1 hour withdrawal casinos No Verification Casinos Hollycorn N.V. Casinos Dama N.V. Casinos Casino Reviews Casino Reviews Dudespin Casino Lizaro Casino Jokery Casino Millioner Casino Pistolo Casino Spinbara Casino Wyns Casino Online Pokies Casino Bonuses Casino Bonuses Free Spins Cashback Bonuses Mobile Bonuses No Deposit Bonuses Payments Payments PayID Casinos Bitcoin Casinos MiFinity Casinos Tether (USDT) Casinos EcoPayz Casinos Jeton casinos MuchBetter Casinos Neosurf Casinos Interac Casinos PaySafeCard Casinos POLi Casinos Skrill Casinos Search Suggestion for: Popular Casinos LuckyDreams Casino Wazamba Casino Nomini Casino LevelUp Casino Slots Palace Casino 5 Gringos Casino Abo Casino Popular Pages PayID Casinos Casino Cashback Bonuses Australia Mobile Casino Bonuses Australia Casino Bonuses Australia Bitcoin Casinos in Australia Best Payout Casinos Australia Instant Payout Casinos Australia Australian Dollar Casinos (AU$ Casinos) No Verification Casinos In Australia AU$1 Minimum Deposit Casinos New Casinos Australia Interac Casinos Australia Jeton casinos Australia Online Pokies Australia Mobile Casinos Real Money Casinos Australia PayID Casinos Today’s guide is all about PayID casinos in Australia. We explain the legal framework for playing at offshore casinos, detail how PayID works for casino deposits and withdrawals, and review the most trusted sites accepting Australian players. Show more Compare casinos by minimum deposit (from AU$1) , payout time (instant to 72 hours), and licensing (Curacao, Anjouan, Malta, etc.). Where speed and security matter just as much as the games themselves, that’s where PayID comes in. It’s a banking innovation that streamlines the deposit and withdrawal process. You don’t have to juggle long BSB and account numbers. PayID lets you connect your bank account to a simple identifier, like your mobile number or email. The result? Instant transfers, fewer errors, and a smoother gambling experience. See more about this payment method below. Best 7 PayID casinos with Instant PayID withdrawals for Australian players Welcome bonus AU$4,000 + 300 Free Spins 18+ | T&C applies Super Fast Payout Time Bank Transfer Bitcoin CashtoCode ecoPayz iDebit Play Now LuckyDreams Casino Review Welcome bonus AU$4,000 + 300 free spins 18+ | T&C applies Super Fast Payout Time Bank Transfer Bitcoin Bitcoin Cash CashtoCode ecoPayz Play Now Just Casino Review Welcome bonus 100% up to AUD300 + 20 Free Spins 18+ | T&C applies Super Fast Payout Time Bank Transfer Bitcoin CashtoCode ecoPayz Maestro Play Now RickyCasino Review Welcome bonus AU$500 + 200 Free spins + 1 Bonus Crab 18+ | T&C applies Super Fast Payout Time Bank Transfer Bitcoin CashtoCode ecoPayz Ethereum Play Now Wazamba Casino Review Welcome bonus 100% match bonus of up to €500 18+ | T&C applies Good Payout Time AstroPay Card Bank Transfer Bitcoin ecoPayz Ethereum Play Now Neon54 Casino Review Welcome bonus 100% up to AUD750 18+ | T&C applies Good Payout Time Bitcoin ecoPayz Ethereum Interac Litecoin Play Now Slots Palace Casino Review Load More What is PayID? Payment method PayID Launch Year 2018 Parent company Australian Payments Plus (NPP + BPAY + eftpos) Type Bank Transfer Deposit time Instant Withdrawal time 1 to 3 days Casinos with PayID 30+ Minimum deposit AU$20 Fees 0% Website Payid.com.au PayID was introduced in 2018 as part of the New Payment Platform (NPP) in Australia, which aimed to make payment systems more efficient. As such, PayID was developed to reduce the tedious process of using bank account numbers and BSBs for payments. As aforementioned, the payment channel was born from NPP, and the service has evolved over the years. Its headquarters are in Sydney, Australia, and it has over 25 million users as of 2025. NPP’s birth dates back to 2012, when the Reserve Bank of Australia strategically reviewed the Australian payment system. There was a need to adopt a real-time payment system that would make Australian payments more competitive. PayID was among the first initiatives of NPP. Many financial organisations support NPP, which is also supported by the Reserve Bank of Australia. As such, there is a lot of credibility for the payment channel. Besides, PayID transactions are supervised by financial institutions. This makes them safer. In 2021, NPP introduced PayTo. This allowed participating organisations to set up pre-authorised payment agreements for clients. In the same year, NPP revealed that more than 8 million users were already registered to the platform. The upward trajectory in numbers was a huge growth for the company. Impressively, the 10 million mark was reached in March 2022. Since then, growth has accelerated, with 25 million+ PayIDs registered by 2025. This is alongside new functionalities like PayTo, which enable third-party-initiated payments. Safest PayID Casinos Reviewed 6 of the top PayID casinos in Australia reviewed. Slotuna Casino Review Reviewed by: Amelia Taylor Updated: 16-08-2024 Operated by NovaForge Ltd., Slotuna is a 2024-founded PayID online casino. It has an active license from Anjouan Gaming. Over 20 language options, including Australian English, are available. So, navigation shouldn’t be a problem. PayID is among the accepted banking options. The minimum deposit and withdrawal amount is AUD 15, and the maximum is AUD 7800 per transaction. The finance team processes PayID deposits instantly. Meanwhile, payouts take less than 3 business days. You can use the Australian dollar for all transactions. It’s among the 20+ fiat options supported. So, there’s no need to convert currencies. This gambling platform comes with a user-friendly progressive web application. It functions flawlessly on Android and iOS devices. We had an easy time navigating the games department. There are several categories from which you can pick your favourite title. They include game shows, slots, and hot jackpots. New players with PayID can claim a sizable welcome bonus. Meanwhile, returning gamblers are eligible for weekly challenges and tournaments, and reload bonuses. Customer support is available 24/7 in case you need help. You can reach out via email ( [email protected] ) or live chat. For faster feedback, we recommend the latter option. Online since: 2024 License: Anjouan Offshore Finance Authority Website: slotuna3.com/au/ Fantastic selection of pokies and live casino games Sports betting section Lots of reload bonuses Players from Austria accepted. Play Now PayID Casinos Review --> Online since: 2024 License: Curacao Website: slotuna3.com/au/ Welcome Bonus Package and Sports Welcome Package Over 6,000 games VIP Club for top scorers Disclosed licensing and ownership Players from Austria accepted. Play Now Slotuna Casino Review RioAce Casino Review Reviewed by: Amelia Taylor Updated: 16-08-2024 Licensed by the Curacao Gaming Authority, RioAce operates under Altacore N.V. It’s available in 8 languages, including several English dialects. The casino accepts PayID among 15+ other banking options. With this payment method, you can be sure of instant deposits. Even better, the finance team doesn’t charge commissions on PayID transactions. That means you get to keep most of your winnings. Notably, the Australian dollar is on the list of accepted currencies. So, you don’t have to worry about conversions. You can access RioAce via popular browsers or install its progressive web application. The app functions smoothly on Android and iOS devices. There are several game categories from which you can pick your preferred title. They include slots, table games, live casino, and crash. Besides playing for real money with a PayID deposit, you can try games for free. Just tap on a thumbnail and press “Demo”. New players with PayID qualify for a welcome bonus. Meanwhile, returning gamblers can claim reload offers. There are also regular offers on the casino’s Telegram channel. If you need help, check the FAQs page. In case you want to speak with real agents, you can do so via email or live chat. Online since: 2024 License: Costa Rica Website: rioace.com/en Massive selection of 4,000+ casino games Impressive live dealer section with 400+ tables Competitive weekly cashback of up to 15% Excellent tournament variety with substantial prize pools Comprehensive banking options including cryptocurrencies Players from Austria accepted. Play Now PayID Casinos Review --> Online since: 2024 License: Curacao Website: rioace.com/en Fantastic live casino section Players from Austria accepted. Play Now RioAce Casino Review Spinbara Casino Review Reviewed by: Amelia Taylor Updated: 06-07-2025 Operated by Stellar Ltd., Spinbara is an Anjouan-licensed gambling platform. As the name implies, the capybara was the inspiration behind the creation of this PayID casino. Australian English is among the dialects the operator supports. This makes browsing and navigation seamless for Australians. There are over 20 payment methods, including PayID. The minimum deposit amount is AUD 15, and the maximum is AUD 8920 per transaction. Meanwhile, the lowest withdrawal amount with PayID is AUD 50, and the highest is AUD 7800. Spinbara accepts AUD. For Aussie players using PayID, there’s no need for currency conversions. Remarkably, the finance team processes PayID deposits instantly. Withdrawals take less than 3 business days. Game categories include slots, jackpots, and game shows. If you’re unsure of where to start, there are several sections you can check, including new, popular, and exclusive. Here, you’ll find the most-loved titles such as Big Bass Bonanza and Gates of Olympus. All titles are mobile-compatible. You can play them via the casino’s progressive web app on your Android or iOS device. There are plenty of bonus offers, including a one-time welcome package for new PayID players. With a PayID deposit, you can also claim reload offers and join the VIP club. If you encounter any problems, reach out to the support team. The customer care reps are professional and will address your queries promptly. Online since: 2025 License: Costa Rica Website: spinbaracasino.com Massive selection of 4,000+ casino games Impressive live dealer section with 400+ tables Competitive weekly cashback of up to 15% Excellent tournament variety with substantial prize pools Comprehensive banking options including cryptocurrencies Players from Austria accepted. Play Now PayID Casinos Review --> Online since: 2025 License: Anjouan Offshore Finance Authority Website: spinbaracasino.com Exceptional game library Generous three-part welcome package Competitive sportsbook Fast withdrawals, especially for crypto users Excellent mobile experience Players from Austria accepted. Play Now Spinbara Casino Review MyLuck Casino Review Reviewed by: Amelia Taylor Updated: 27-05-2025 Founded in 2025, MyLuck is a new PayID casino operated by 130 Group N.V. It holds a valid license from the Curaçao Gaming Authority. There are over 25 languages, including Australian English. This is the default option if you access the casino from AU. You can, however, change to your preferred dialect at any time. MyLuck supports banks that accept PayID. With this payment method, you can be sure of instant deposits and under 72 hours withdrawals. The minimum deposit and withdrawal amount is AUD 15. Notably, the operator supports the Australian dollar, so no need for currency conversions. This gambling platform is mobile-compatible. You can access it using various devices, including iOS and Android smartphones. Over 115 software providers power the game library. They include Pragmatic Play, Playtech, and NetEnt. Besides the seasoned providers, the operator features titles from upcoming companies for variety. Some of the game categories you can explore include slots, table games, and bonus buy. Crash games, instant win, and live dealer titles are also available. Overall, the casino features over 12,800 titles that you can play for real money with PayID deposits. If you’re a new player using PayID, you qualify for a one-time welcome package. Other bonus offers include cashback, free spins, and a 5-tier VIP program ranging from Opulence to Diamond. Online since: 2025 License: Anjouan Offshore Finance Authority Website: myluck.com Fantastic selection of pokies and live casino games Sports betting section Lots of reload bonuses Players from Austria accepted. Play Now PayID Casinos Review --> Online since: 2025 License: Curacao Website: myluck.com Substantial welcome package Extensive game library Great sportsbook Strong VIP program Multiple payment options Players from Austria accepted. Play Now MyLuck Casino Review Avocasino Review Reviewed by: Amelia Taylor Updated: 25-11-2025 From the name, you can tell this is a fruit-themed PayID casino. The avocado is used as the mascot. There are over 15 languages, including Australian English. So, navigation and understanding the terms and conditions shouldn’t be a headache. Worth mentioning, you must wager your PayID deposit 3x before requesting a withdrawal. This way, the casino prevents money laundering. When it comes to transaction speed, the finance team processes PayID deposits instantly. Meanwhile, withdrawals take less than 2 banking days. There are several ways you can pick your preferred title. A search function is available if you have a game in mind. Alternatively, you can filter titles by software providers and game categories. Some of the game divisions are wager-pokies, crash games, and pokies. A live casino section with baccarat, roulette, and poker is also available. You don’t need an app to access Avocasino’s games and other features. You can use any popular browser, including Safari and Chrome. PayID players are eligible for all bonuses. These include a welcome offer, cashback, free spins, and reload bonuses. A 10-tier VIP program, ranging from Beginner to Legend, is also available. Customer support is available 24/7 in case you get stuck. There’s also a guide with well-explained processes, such as registration and account verification. Online since: 2023 License: Costa Rica Website: avocasino.com Massive selection of 4,000+ casino games Impressive live dealer section with 400+ tables Competitive weekly cashback of up to 15% Excellent tournament variety with substantial prize pools Comprehensive banking options including cryptocurrencies Players from Austria accepted. Play Now PayID Casinos Review --> Online since: 2023 Website: avocasino.com Players from Austria accepted. Play Now Avocasino Review Fortunica Casino Review Reviewed by: Amelia Taylor Updated: 25-11-2025 Operated by Winstar N.V., Fortunica is a 2025-founded PayID casino. It has a valid license from Anjouan Gaming. PayID is on the list of banking options for deposits and withdrawals. The minimum deposit and withdrawal amount is AUD 15 per transaction. A user-friendly progressive web app is available. To install it, head to the menu and tap “App Store if you have an iOS device. If you’re using an Android smartphone or tablet, press “Android”. The registration process is straightforward and takes less than 30 seconds to complete. You only need to enter your email and password, and choose your preferred currency. Speaking of currency, AUD is available. For Aussie gamblers, there’s no need for conversions. Over 60 licensed software providers power the games section. They include powerhouses like Wazdan, KA Gaming, and Yggdrasil. Upcoming providers such as Fa Chai are also available. There are 20 game categories for easy navigation and browsing. They include fishing games, scratch, pokies, and live games. Bonus options include free spins, cashback, and a welcome package for new PayID gamblers. Additionally, a 7-tier VIP program, ranging from Fighter to Immortal, is available. If you have queries, check the casino’s FAQ page. Alternatively, you can reach out via live chat. The player support team responds in Australian English. Online since: 2025 License: Costa Rica Website: fortunica.io Massive selection of 4,000+ casino games Impressive live dealer section with 400+ tables Competitive weekly cashback of up to 15% Excellent tournament variety with substantial prize pools Comprehensive banking options including cryptocurrencies Players from Austria accepted. Play Now PayID Casinos Review --> Online since: 2025 Website: fortunica.io Players from Austria accepted. Play Now Fortunica Casino Review New Pokies to play at PayID Casinos PayID Casinos are great, but even greater are the latest pokies titles available at those casinos. Bellow you can find the hottest pokies available to the Australian Market. Play Now Rise of Atlantis 2 Play Now Cashpot Kegs Megaways Play Now Goat Getter Play Now Forge of Olympus Play Now Enchanted Waters Play Now Pinata Popper Dream Drop Play Now Safari Sun Play Now Ronin StackWays Load More Getting Started With PayID From the foregoing, PayID is a simpler means to an end. Other than going through hectic processes, the technology allows you to make payments within a few minutes. So how exactly can one get started? Here’s how to open a PayID account from the bank: Get Started View more Identify a Bank with PayID Firstly, you need to choose one of the banks that supports PayID. Then, you need to create an account with the bank. If you already have one, you are good to go. Log in to your Bank Next, you need to log into your bank account. From the main menu, you should be able to see ‘ create PayID ’. Click on that option and proceed. Connect your PayID Choose the account you wish to connect to PayID and follow the prompts. You can choose to have memorable information by email or phone. Submit and wait for verification After choosing either your mobile number or email address, the bank will confirm your details. A code will be sent to your phone or email address. Use it for authentication. Make payments After successful activation, the bank will add PayID to your account. You can use the channel to make payments. How To Make a PayID Casino Deposit Now that we have learned how to create a PayID account, we need to know how to use it in casinos. Here’s how to make a PayID casino deposit: Time needed 5 minutes Tools needed Smartphone Software needed Web browser Pick a reliable PayID casino in Australia The first step is to choose a casino that has a payment method. Confirm that the site is licensed and has SSL encryptions before depositing real money. Open an account Next, you will log in or register your account if you don’t have any. You will be required to give your username and password. Open the cashier section After successfully logging in, you should go to the deposit section. Here, you will enter the amount that you wish to deposit. It should not be less than the casino’s minimum deposit requirement. Choose Bank Transfer From the list of available deposit methods, pick bank transfer and simultaneously log in to your online bank account. Then, select payID and confirm the transaction. It’s Play Time PayID casino deposits are near-instant. So, you should have the money in your casino account within a few seconds. PS: For PayID withdrawals, players should choose PayID as the withdrawal method. The casino will need you to enter your PayID details to cash out. Table of contents Choosing The Best PayID Casino – What To Consider Before settling on an online casino, it is good to ensure that you have considered all the necessary factors. You don’t want a casino where your security can be compromised or where games aren’t fair. Here are the key things to consider when choosing the best PayID casino in Australia: Security & Licensing Predominantly, security is an essential factor that should not be overlooked. The best AU PayID casino should have the latest security measures to safeguard your data. That way, scammers cannot access and use your information for fraud. Some of the things to look out for are the SSL certificates that a casino has. Also, it is important to check the validity of the casino’s license. Lastly, the privacy policy and T&Cs reveal some of the ways the site might protect your data. Genuineness of Games For a thrilling time, players should ensure that a PayID gambling site has a variety of original games in their library. If you are a slots fan, then the site should have a wide collection for your amusement. Sports fanatics should look for a casino with competitive odds and multiple sports to bet on.That way, players do not get easily bored. Above all, you need to make sure that the casino games on offer are genuine. They need to be the original products, not just replicas whose payout mechanics have been tampered with. Bonuses A good PayID accepting casino should have lucrative deals for the players. From welcome offers to deposit bonuses and tournaments, the gambling site should have them all. Some PayID casinos even have VIP rewards for their loyal players. Most importantly, the bonus terms should be fair. You don’t want a deal where meeting the wagering requirements will be hard or even impossible. Talking of bonuses… Popular Bonuses in PayID Casinos Casino bonuses can help extend your gameplay at no extra cost. With increased playtime, you get more chances to try your luck. If things work out well, you can increase your winnings as your bet size increases. Thankfully, many PayID casinos have multiple bonuses. The welcome package is common across many platforms. Although the amount and percentage vary, you are sure to get a good deal in many casinos. Wazamba, Nomini, and Neon54 casinos all have welcome bonuses. For Nomini casino, the amount of the welcome bonus is determined by the fruit you picked during registration. Others have a different scheme, so read the terms first. When it comes to deposit bonuses, players will find a vast array. The promotions may range from reload bonuses, cashback bonuses , and bonus spins . In these promotions, the casino rewards you for depositing real money. Of course, there will be roll over to be met before cashing out. Keep an eye on them. PayID Limits, Fees, and Processing Times Each banking solution has its own policies when it comes to fees and limits. Similarly, they all process transactions differently, so timeframes will vary. Let’s see what to expect in PayID payments. PayID Fees Some payment channels charge an arm and a leg for casino deposits and withdrawals. Luckily, PayID does not charge any fees for either. However, some banks might charge fees, and this will vary from one bank to another. These charges by the bank would be for account maintenance. For deposits and withdrawals to the bank account, there are no charges. Limits PayID does not have limits on min/max deposit and withdrawal amounts. However, since the payment mode is linked to banks, the financial institution will impose some limits. There are over 100 banks that support PayID. So, it’s hard to give a specific figure on the daily limits of the bank. Australian PayID casinos will often have a cap on the least and highest you can deposit or withdraw. For instance, the deposit limit at Wazamba casino is AUD 15-7800 if you are using PayID. Check with the casino for these details. Processing Times As an initiative of NPP, PayID is meant to reduce the long and tedious payment process. Its transactions are processed almost instantaneously. Thus, if you are making deposits to an online casino using the channel, you should be able to play in a few minutes. If you are making deposits for the first time, there might be delays due to bank security checks. For withdrawals, players should submit withdrawal requests and wait for the casino’s approval. The payout time for PayID is between 1 and 3 business days due to the approval process. PayID Security Features This casino payment method has advanced security features that make it safe to use. Since users make transactions using their email or phone number, the casino does not store their financial details. Also, PayID is linked to banks, which have extra security measures. Screening of payment details by banks helps minimise cases of fraud. Furthermore, users of PayID can enable two-factor authentication that helps protect their transactions. Although PayID does not have passcode and fingerprint security features, the payment method is pretty safe. Just make sure the casino you choose is protected as well. Also, avoid phishing attempts by fraudsters through vigilance at all times. How to contact PayID support Players who need to reach out to PayID can do so in several ways. The payment method’s official website is payid.com.au. At the bottom of the page, you will find a FAQ section with answers to popular inquiries. You can also get assistance from the bank that supports PayID. This is especially if you are stuck on registration or during payment. If your inquiry is complicated and you need a comprehensive solution, you can contact the team using [email protected] . The team will respond and help you within a short while. PayID On Mobile It is easy to use PayID services on your phone. Depending on the bank you choose, you can install the banking app on your phone. For swift transactions, you should have the latest version of the bank’s app. PayID is not a separate payment method. So, no extra app is required. Find the PayID tab within the banking app, and you are good to go. The process is similar to using online banking on a PC. As soon as you have entered the amount you need to deposit on your mobile casino, you log in to the bank’s mobile app, then initiate the payment. Wait for confirmation, and that’s it! PayID Market Coverage As a revolutionary banking solution, PayID has grown remarkably over the years. The payment channel has a presence in Australia and is backed by financial organisations therein. Therefore, you may not use it in other parts of the world. Its use in the country comes as a result of the urge to make payments simpler. By eliminating the need for a BSB code for payments, PayID helped many Aussies. There are numerous credit unions and banks that support the payment channel. Moreover, there are many PayID accepting casinos in Australia. This makes things easier for Aussie gamblers. No Chargebacks? Understanding PayID Casino Dispute Resolution PayID and traditional card payments at online casinos are different, especially when it comes to dispute resolution. With credit cards, players often rely on chargebacks. This is a process where the bank reverses a transaction in case of erroneous transactions or fraud. PayID, however, doesn’t operate with a built-in chargeback mechanism. This makes dispute resolution a little different. For that reason, Aussie players must understand how it works. When issues arise, say, a failed deposit or a delayed withdrawal, the resolution process usually follows two paths. First, you should raise the issue directly with the casino. Real money casinos in Australia have clear complaint procedures and resolve disputes quickly. If the problem relates to fraud or an unauthorised transaction, your bank steps in. Since PayID is tied to your bank account, the bank can investigate suspicious activity and apply its fraud protection policies. However, it won’t reverse a payment in the same way a card chargeback would. This dual pathway means you should think of PayID disputes less as automatic reversals and more as a case‑by‑case investigation. In practice, this has a few implications. Faster Casino Resolution: Operators know banks won’t simply claw back funds. So, they often prioritise resolving PayID complaints quickly to avoid regulatory trouble. Stronger Fraud Protection: Banks monitor PayID transactions closely. That means suspicious transfers can trigger account holds or investigations. Player Responsibility: Without chargebacks, you must be careful when choosing reputable casinos. Check out our list of legit online casinos with PayID. Did you Know? Making payments using PayID reduces chances of making mistakes. When someone types your PayID on their banking app, your name is revealed. This helps make payments to the right account as you can double-check your details. Advantages and Disadvantages of PayID Payments Pros Secure as bank details are not shared Transactions are processed fast No extra charges for online casino payments Supported by many banks and gambling sites in Australia Simple to use, all you need is a memorable piece of information. Cons Only available within Australia PayID Alternatives There are plenty of payment methods in Australia. If your favorite casino does not support PayID, you can use any of the following options: Payment Method Description Casinos Using It POLi This payment channel works best for people who do not have credit cards. You will not be charged for using it, and you don’t need to register an account. It’s more like PayID. Skrill Almost all modern Australian casinos accept payments through Skrill. The payment mode provides a safe and secure means to make transactions over the internet. Besides, all Skrill casino deposits are instant. Bitcoin As one of the leading payment channels across the world, Bitcoin is very flexible. You can make deposits instantaneously and get your winnings fast. Further, BTC is accepted by many online AU casinos. FAQ Are PayID withdrawals instant or only deposits? Deposits are usually instant, but withdrawals depend on the casino’s processing time. Many PayID casinos now support same-day withdrawals. However, some may take 24–48 hours, depending on internal checks. Can I use multiple PayIDs across different casinos? You can, but each PayID must be linked to a separate bank account or identifier. Some players create a dedicated PayID just for gambling to keep finances cleaner. Can I set deposit limits when using PayID at casinos? Yes, PayID links directly to your bank account. This allows you to set spending limits through your bank’s app. Additionally, some casinos allow you to configure responsible gambling limits that apply specifically to PayID transactions. What happens if I change my phone number or email linked to PayID? If you update your PayID details with your bank, you’ll need to re-register the new PayID with the casino. Your account remains intact, but deposits and withdrawals must be linked to the updated identifier. Do PayID casinos support micro-deposits for testing? Yes, some operators allow small test deposits (as low as AUD 1) via PayID. This allows players to confirm if the link works before committing larger amounts. It’s quite useful, especially for new gamblers. Do PayID casinos show up differently on my bank statement? Yes, transactions made via PayID often display the casino’s registered business name. Sometimes it comes as a generic payment processor label, not “casino.” What happens if a casino loses its PayID license? If a casino’s payment processor is suspended, deposits via PayID stop immediately. That means you’ll have to switch to other options like Osko, POLi, or bank transfer until the casino re-establishes compliance. Is PayID safer against gambling scams? Yes, PayID is pretty safe. That’s because it requires a verified Australian bank account, and scammers can’t easily create fake identities. Meanwhile, crypto wallets can be created anonymously, with no identity verification. This makes them more vulnerable to scams. Our Verdict PayID has been a popular money transfer service in Australia. It is adopted by many casinos due to its reliability and simplicity. Interestingly, over 100 banks support the payment method. Many gamblers are hesitant to provide their banking details to casinos. This payment mode has changed the scene, as Aussie players do not need to disclose their details. Further, players benefit from real-time payments and no extra charges. Creating a PayID is as simple as paying through it. You only need to remember your email or phone number, and you are set. Besides, the payments are accurate as the receiver’s PayID name is disclosed before initiating the transfer. Australian online casinos that accept PayID casinos come with numerous benefits. Players can enjoy tons of bonuses and a massive array of games. With a great selection of online casinos that accept PayID, players will have a great time gambling online. What is so exceptional about this service is how convenient it is. It also has strong backing from Australian financial institutions. Further, players get a seamless mobile experience, making real money gambling possible around the clock. Amelia Taylor Casino Auditor Last Updated: August 28, 2023 Amelia is huge fan of online casinos and Pokies. She was born in Sydney, Australia and spent last few years as an iGaming copywritter. casinoaustraliaonline.net Casino Australia Online.net is one of the biggest websites for online casino comparison in Australia. We do not organise ay kind of gambling or betting activities on our site. [email protected] Mobile Casinos iPhone Casinos Android Casinos Nomini Casino Dazard Casino BetHall Casino Midasluck Casino Ocean Spin Casino KinBet Casino Guides Dama N.V. Casinos Hollycorn N.V. Casinos Gambling Taxes About us About Us CAO on YouTube Terms of use Online Casinos Canada Online casino Nederland Greece-Casinos.com (El) Casinos online España Online Casinos Deutschland Made with by E-legance.net Casino of the Month 250% Up to A$4,000 + 150 free spins Play Now 4.7 /5 Play Now MonsterWin Casino | 2026-01-13T08:48:41 |
https://docs.suprsend.com/docs/react-native-ios-integration | iOS Integration - 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 Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK SuprSend Client SDK Authentication Javascript Android iOS React Native Android Integration iOS Integration Manage Users Sync Events iOS Push Setup Android Push (FCM) Flutter React Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation React Native iOS Integration Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React Native iOS Integration OpenAI Open in ChatGPT This document will cover integration steps for iOS side of your ReactNative application. OpenAI Open in ChatGPT Installation 1 Install Package. npm yarn Copy Ask AI npm install @ suprsend / react - native - sdk @ latest If you are upgrading the SDK version, run pod update inside ios folder. 2 Adding Swift support and Bridge header This step is needed only if your react native project iOS side doesn’t support swift language. To check for swift support in Xcode, open Project Settings --> Build Settings --> Swift Language Version (attached image). If entry is present, you already have swift support in your project. If your project doesn’t support swift then its mandatory to add Swift support in your project by following the steps below. Open “xcodeworkspace” file inside iOS folder. This will open Xcode. Add Swift file to project like shown below. Select Swift File and click on Next button. Now give a suitable name to your file and click Create. After that popup will be shown asking to configure Objective-C bridge header. Click on Create Bridge Header . Thats it! your React native iOS project can now understand code written in Swift language. 3 Inside PodFile change iOS platform version to 13 or greater if it's less than 13. PodFile Copy Ask AI platform :ios , '13.0' // this version has to be 13 or greater 4 Run pod install from inside iOS folder. Copy Ask AI pod install 5 Update the Target SuprSend SDK needs an iOS deployment target of 11 or above, update the target as given in below image if needed. Initialization 1 AppDelegate changes In AppDelegate add the below code inside didFinishLaunchingWithOptions method, just before last returning line. Refer any one of code snippet below based on your projects AppDelegate file language. AppDelegate.m AppDelegate.swift Copy Ask AI #import <SuprSendSdk/SuprSendSdk-Swift.h> //add this ... - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { ... SuprSendSDKConfiguration* configuration = [[SuprSendSDKConfiguration alloc] initWithKey:@workspace_key secret:@workspace_secret]; // add this line [SuprSend.shared configureWithConfiguration:configuration launchOptions:launchOptions]; // add this line return YES; 2 Replace workspace_key and workspace_secret Replace the workspace_key and workspace_secret with your workspace values. You will get both the tokens from Settings -> API Keys in SuprSend dashboard . Logging By default the logs of SuprSend SDK are disabled. You can enable the logs just in debug mode while in development by the below condition. javascript Copy Ask AI suprsend . enableLogging (); // available from v2.0.2 // deprecated from v2.0.2 suprsend . setLogLevel ( level ) suprsend . setLogLevel ( "VERBOSE" ) suprsend . setLogLevel ( "DEBUG" ) suprsend . setLogLevel ( "INFO" ) suprsend . setLogLevel ( "ERROR" ) suprsend . setLogLevel ( "OFF" ) Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Methods to create user and set their mobile push token and other communication channels for sending notifications in ReactNative application. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization Logging | 2026-01-13T08:48:41 |
https://docs.sui.io/guides/developer/getting-started/connect#resource-safety | Hello, World! | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Hello, World! On this page Hello, World! You'll build a "Hello, World!" program to learn the fundamentals of programming on Sui. You create programs on Sui by writing and deploying smart contracts to the network. The most basic unit of storage on Sui is an object . Other blockchains typically structure storage using key-value stores. Sui centers storage around objects with unique ID addresses on-chain. Every Sui smart contract is an object that manipulates other objects. Objects can be immutable or mutable: Immutable objects cannot be transferred, changed, or deleted. No one owns them and anyone can access them publicly. Mutable objects can be transferred, changed, and deleted. A Sui address can own them, or they can be shared for public access. Every object's unique ID and version number references it on-chain. Every transaction on the network takes objects as input, then reads, writes, and mutates the inputs to produce new or altered objects as output. Every object knows the hash of the transaction that produced it. When an object is modified by a transaction, the transaction's output writes the object's mutated contents to the same object ID but with a new version number. Sui has limits on the maximum transaction size (128KB) and number of objects (2,048) used in a transaction. For more information on limits, see Building Against Limits in The Move Book. What is Move? Move is the programming language Sui uses to create smart contracts. It is platform agnostic and enables common libraries, tooling, and developer communities across blockchains with vastly different data and execution models. There are three ways to use Move in the context of Sui: Move packages, Move modules, and Move objects. A Sui Move package is also referred to as a Move smart contract. It is a set of Move bytecode published to the Sui network. It is immutable and cannot be changed or removed, however you can upgrade it. Upgrading creates a new version of the package object on-chain, leaving the original intact. All prior versions of a package still exist on-chain. Once you publish it, other packages can import and use the modules it provides. Anyone can view a package's contents and use a Sui Explorer to see how its logic manipulates other objects. Every Move package on Sui includes one or more Sui Move modules that define the package's interaction with on-chain objects. A module's name is always unique within the package that contains it. A Sui Move module governs a Sui Move object , which is typed data from a Sui Move package. Each Move object value is a struct with fields that can contain primitive types, such as integers and addresses, other objects, and non-object structs. Clone "Hello, World!" Prerequisites Install the latest version of Sui . Configure the Sui client . Create a Sui address . Get SUI Testnet tokens . Download and install an IDE. The following are recommended, as they offer Move extensions: VSCode , corresponding Move extension Emacs , corresponding Move extension Vim , corresponding Move extension Zed , corresponding Move extension Alternatively, you can use the Move web IDE , which does not require a download. It does not support all functions necessary for this guide, however. Download and install Git . To demonstrate creating objects, packages, and how to build your first Sui application, start by cloning the "Hello, World!" example: $ git clone \ https://github.com/MystenLabs/sui-stack-hello-world.git $ cd sui-stack-hello-world/move/hello-world In this project, there are two important files that define the package's logic, information, and its dependencies: move/hello-world/sources/greeting.move : Defines the package's logic. In this example, it defines a basic shared greeting object and public functions to interact with it. move/hello-world/Move.toml : The package's configuration file that defines the package name, dependencies, and addresses. Click to open move/hello-world/Move.toml File not found in manifest: move/hello-world/Move.toml . You probably need to run `pnpm prebuild` and restart the site. View the smart contract code Open the greeting.move file in your IDE of choice. You can see the following Move code: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Code explanation First, this code defines a module called greeting : module hello_world :: greeting { use std :: string ; ... } Then, it defines a public struct called Greeting that contains a unique object ID and text. A struct is a type of resource : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Then, it defines the function new that makes an API call to the Greeting struct and initializes it with the text "Hello world!" , storing it in a new shared object: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Lastly, the package defines a function called update_text that can be called to update the text stored in Greeting : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Resource safety A unique aspect of programming applications on Sui is the resource safety enforced by the Move Bytecode Verifier. Move packages must satisfy the following resource safety parameters: All resources must be either moved into global storage or destroyed by the end of a transaction. Resources cannot be copied. In the "Hello, World!" example, the struct Greeting is a resource type. To satisfy the requirement that all resources must be moved or destroyed by the end of a transaction, Greeting is assigned to new_greeting , which the call to transfer::share_object(new_greeting) then moves into global storage. To mutate Greeting , the function update_text takes the input (&mut Greeting) rather than the resource itself. This function satisfies resource safety as the function does not copy the resource and mutates it via a reference. Learn more about the Move Bytecode Verifier. How does this differ from EVM applications? The Ethereum Virtual Machine adopts a gas-based resource safety strategy. Every opcode on an EVM chain has an associated gas price that makes transactions costly, preventing the network from running a single transaction indefinitely. Build the Move package Before you can publish a Move package to the network, you must first build it. Building your package is necessary because the .move source file is a human-readable piece of code, while the network can only understand bytecode. To build your "Hello, World!" package, first confirm your working directory is ~/sui-stack-hello-world/move/hello-world , then run the following command: $ sui move build The build process fetches and compiles the dependencies defined in the Move.toml file. The Move compiler checks your .move code for type errors, syntax errors, and enforces resource safety , then translates your .move code into bytecode that Sui can execute. info You must build your package before you can publish it, but also before you test it. You cannot run tests ( sui move test ) on your code until it has been built. Publish the Move package Now that your package has been built, you need to publish it. After you publish it, other packages and users can use the package's modules and functions by making calls to the package ID. First, confirm your client is configured to use Testnet as the active environment: $ sui client active-env This should return testnet . If it does not return testnet , follow the client configuration instructions before continuing. Then, check your balance of SUI tokens to confirm you have enough to publish to Testnet: $ sui client balance You should have a balance of SUI tokens: ╭────────────────────────────────────────────╮ │ Balance of coins owned by this address │ ├────────────────────────────────────────────┤ │ ╭────────────────────────────────────────╮ │ │ │ coin balance (raw) balance │ │ │ ├────────────────────────────────────────┤ │ │ │ Sui 56804696124 0.50 SUI │ │ │ ╰────────────────────────────────────────╯ │ ╰────────────────────────────────────────────╯ If you do not have a balance, follow the SUI faucet instructions . Now, publish the package to Testnet with the command: $ sui client publish Click to open Output Transaction Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Data │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Owner: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Budget: 9843200 MIST │ │ Gas Price: 1000 MIST │ │ Gas Payment: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Version: 591332925 │ │ │ Digest: FLC4NXntT7WiHcqCkpDuBUq14DFTfi3EFeUiJcSNHdPu │ │ └── │ │ │ │ Transaction Kind: Programmable │ │ ╭─────────────────────────────────────────────────────────────────────────────────── ───────────────────────╮ │ │ │ Input Objects │ │ │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Pure Arg: Type: address, Value: "0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803" │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │ │ ╭─────────────────────────────────────────────────────────────────────────╮ │ │ │ Commands │ │ │ ├─────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Publish: │ │ │ │ ┌ │ │ │ │ │ Dependencies: │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │ │ │ └ │ │ │ │ │ │ │ │ 1 TransferObjects: │ │ │ │ ┌ │ │ │ │ │ Arguments: │ │ │ │ │ Result 0 │ │ │ │ │ Address: Input 0 │ │ │ │ └ │ │ │ ╰─────────────────────────────────────────────────────────────────────────╯ │ │ │ │ Signatures: │ │ mUxqMIofPq+yIzPxxYM+2mSIPTFneDxhWGGxJ7tM02hnRBRy5/FosnnWKxd4OSAjmaw6FNylwVdqUoUlJSxWCQ== │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ ┌── │ │ │ ID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Owner: Immutable │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Object: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Cost Summary: │ │ Storage Cost: 7843200 MIST │ │ Computation Cost: 1000000 MIST │ │ Storage Rebate: 978120 MIST │ │ Non-refundable Storage Fee: 9880 MIST │ │ │ │ Transaction Dependencies: │ │ 2dkJtqsoQcyCZJvjZnskNVPQeynwVtwCcA9goAru6tTi │ │ 7PStztXyh92keJmrDD1aghHaKVdgCoVkVx4ZmLUfmQeK │ │ Dd9pn1zFcSJjinxQewFd2gQdR4XKsHxFioD5MYnwLZQz │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭─────────────────────── ──────╮ │ No transaction block events │ ╰─────────────────────────────╯ ╭──────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Object Changes │ ├──────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created Objects: │ │ ┌── │ │ │ ObjectID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::package::UpgradeCap │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ObjectID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Balance Changes │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ ┌── │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ CoinType: 0x2::sui::SUI │ │ │ Amount: -7865080 │ │ └── │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ When you publish a Move package to the network, the network uploads and stores the bytecode as a Move package with a unique package ID and version number. The network consumes SUI tokens as gas and processes the transaction on-chain. After successfully executing, the output provides details about the transaction used to publish the package, including the gas cost, transaction digest, dependencies, owner, and sender. For this guide, the most important section is Published Objects , which includes the package's ID, version, and its modules: │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── Both the package ID and module are required to interact with the package from the command line. Take note of both values for future use in the Connecting a Frontend guide. Interact with the Move package Interact with the newly published package by first making a call to the new function that creates a new Greeting object and initialize it with the text "Hello world!" : $ sui client call --package <PACKAGE_ID> --module greeting --function new Replace <PACKAGE_ID> with the package ID the output of the sui client publish command returned. You must include the --package , --module , and --function flags. The output of this call includes a newly created object: ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ Owner: Shared( 591332927 ) │ │ │ Version: 591332927 │ │ │ Digest: 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ └── ... To verify that the object contains the text "Hello world!" , make a call to query the object's information: $ sui client object <OBJECT_ID> Replace <OBJECT_ID> with the value under Created Objects, ID: . You should see the object's details, including a value of text: Hello world! : ╭───────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ objectId │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ version │ 591332927 │ │ digest │ 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ objType │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ owner │ ╭────────┬──────────────────────────────────────────╮ │ │ │ │ Shared │ ╭────────────────────────┬─────────────╮ │ │ │ │ │ │ │ initial_shared_version │ 591332927 │ │ │ │ │ │ │ ╰────────────────────────┴─────────────╯ │ │ │ │ ╰────────┴──────────────────────────────────────────╯ │ │ prevTx │ 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ storageRebate │ 1413600 │ │ content │ ╭───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ dataType │ moveObject │ │ │ │ │ type │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ │ │ │ hasPublicTransfer │ false │ │ │ │ │ fields │ ╭──────┬───────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ id │ ╭────┬──────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ │ │ │ id │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ │ │ │ │ │ │ │ ╰────┴──────────────────────────────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ text │ Hello world! │ │ │ │ │ │ │ ╰──────┴───────────────────────────────────────────────────────────────────────────────╯ │ │ │ │ ╰───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────╯ │ ╰───────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Important transaction considerations You cannot send 2 or more transactions simultaneously, otherwise you encounter an error such as: Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. If you receive this error, you must wait until the current epoch is over before submitting your transaction again. You can see how long is left in the current epoch using Sui Explorer or another network explorer like SuiScan . To prevent the same object from being modified by multiple transactions at once, your address 'locks' the object to prevent conflicting modifications. If you'd like to batch multiple transaction commands together, you can use programmable transaction blocks . Transactions also have limitations regarding total size, number of objects, and number of inputs. Learn more about limitations in Building Against Limits in The Move Book. Next steps Create a Full Stack dApp Connect a frontend interface to your "Hello, World!" smart contract. Access Sui Data Learn more about accessing data on Sui. Join the Community Join the Sui developer community, try out other example projects, or read more documentation. Edit this page What is Move? Clone "Hello, World!" View the smart contract code Code explanation Resource safety Build the Move package Publish the Move package Interact with the Move package Important transaction considerations © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:41 |
https://docs.suprsend.com/reference/cli-installation | Installation - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Getting Started with CLI Installation Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Getting Started with CLI Installation OpenAI Open in ChatGPT Steps to install the SuprSend CLI OpenAI Open in ChatGPT Homebrew (Recommended) Best for developers on macOS or Linux who want the easiest installation and upgrade path with package manager support. Copy Ask AI brew tap suprsend/tap brew install --cask suprsend Binary Releases Best for Windows users, servers or CI/CD environments where you need a pre-compiled binary without relying on package managers. Download from GitHub Releases . Copy Ask AI # Linux/macOS chmod +x suprsend sudo mv suprsend /usr/local/bin/ # Windows: Extract suprsend.exe to your PATH Source Build Best for contributors or advanced users who want the latest unreleased features by building from source. Works on macOS, Linux, and Windows with Go installed. To build SuprSend CLI from source, follow these steps: Ensure you have Go installed on your system (version 1.20 or later). Clone the repository: Copy Ask AI git clone https://github.com/suprsend/cli.git cd cli/cmd/suprsend Build the binary: Copy Ask AI go build -o suprsend The binary will be created in the current directory. You can move it to a location in your PATH for easy access: Copy Ask AI sudo mv suprsend /usr/local/bin/ Verify Installation After installation, you can use CLI by running suprsend command. For example: Copy Ask AI suprsend --help suprsend version When you run suprsend version , you should see the latest version (currently v1.0.0 ). If you see an older version, you may need to update your installation. Community Contribution We welcome community contributions to improve the SuprSend CLI. If you’d like to add features, fix bugs, or improve documentation: Visit the SuprSend CLI GitHub repository Fork the repo and create a feature branch Open a Pull Request with a clear description of your changes and we’ll review and merge it. Was this page helpful? Yes No Suggest edits Raise issue Previous Authentication Set up authentication for the SuprSend CLI using service tokens. Next ⌘ I x github linkedin youtube Powered by On this page Homebrew (Recommended) Binary Releases Source Build Verify Installation Community Contribution | 2026-01-13T08:48:41 |
https://dev.to/vjnvisakh/mastering-interview-body-language-techniques-a-guide-to-non-verbal-communication-58nb | Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication - 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 Visakh Vijayan Posted on Jan 11 • Originally published at dumpd.in Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication # career # interview # tutorial Interview (8 Part Series) 1 Unveiling the Top 50 Full-Stack Interview Questions 2 Unveiling the Top 50 Python Interview Questions: A Deep Dive into Python Proficiency ... 4 more parts... 3 Unlocking the Future: Top 50 DevOps Interview Questions You Must Know 4 Unveiling the Top 50 Cloud Computing Interview Questions 5 Mastering Full-Stack: Top 50 Interview Questions Revealed 6 Mastering Frontend Development: Top 50 Interview Questions Revealed 7 Mastering Technical Interviews: Top 50 Tips for Success 8 Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication The Importance of Body Language in Interviews Body language plays a crucial role in communication, often conveying more than words alone. In an interview setting, your body language can influence the perception of your confidence, credibility, and interest in the role. Key Body Language Techniques to Master 1. Eye Contact Eye contact is a powerful form of non-verbal communication that demonstrates attentiveness and confidence. Maintain good eye contact with your interviewer to show your engagement. interviewer = Interviewer() interviewee = Interviewee() interviewer.make_eye_contact(interviewee) 2. Posture Your posture speaks volumes about your confidence and professionalism. Sit up straight, avoid slouching, and lean slightly forward to show interest. interviewee.sit_up_straight() interviewee.avoid_slouching() interviewee.lean_forward() 3. Hand Gestures Use purposeful hand gestures to emphasize key points and convey enthusiasm. Avoid fidgeting or excessive movements that may distract from your message. interviewee.use_hand_gestures() interviewee.avoid_fidgeting() Practicing and Refining Your Body Language Practice your body language techniques in front of a mirror or with a friend to receive feedback. Focus on creating a positive and professional impression through your non-verbal cues. Conclusion Mastering interview body language techniques can significantly enhance your communication skills and overall interview performance. By paying attention to your non-verbal cues, you can convey confidence, credibility, and enthusiasm effectively. Interview (8 Part Series) 1 Unveiling the Top 50 Full-Stack Interview Questions 2 Unveiling the Top 50 Python Interview Questions: A Deep Dive into Python Proficiency ... 4 more parts... 3 Unlocking the Future: Top 50 DevOps Interview Questions You Must Know 4 Unveiling the Top 50 Cloud Computing Interview Questions 5 Mastering Full-Stack: Top 50 Interview Questions Revealed 6 Mastering Frontend Development: Top 50 Interview Questions Revealed 7 Mastering Technical Interviews: Top 50 Tips for Success 8 Mastering Interview Body Language Techniques: A Guide to Non-Verbal Communication 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 Visakh Vijayan Follow There is nothing else in this world that gives as much happiness as coding Location Kolkata, West Bengal Education MCA Pronouns he/him/his Work Full Stack Developer at JTC Joined Sep 2, 2018 More from Visakh Vijayan Unleashing the Power of Arrow Functions in JavaScript # beginners # javascript # tutorial Unlocking TypeScript's Power: Mastering Type Guards for Safer, Smarter Code # javascript # tutorial # typescript Unleashing the Power of Enums in TypeScript # typescript # programming # tutorial # beginners 💎 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:48:41 |
https://dev.to/zeeshanali0704/polyfil-usereducer-4lf9#comments | Polyfil - useReducer - 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 ZeeshanAli-0704 Posted on Jan 11 Polyfil - useReducer # react # interview # tutorial # javascript Polyfill series (8 Part Series) 1 Polyfill - Promise.all 2 Polyfills for .forEach(), .map(), .filter(), .reduce() in JavaScript ... 4 more parts... 3 Polyfill - Promise 4 Polyfill - fetch 5 Polyfill - call, apply & bind 6 Polyfill - useState (React) 7 Polyfill - useEffect (React) 8 Polyfil - useReducer Below, I'll provide a simple, executable useReducer polyfill with detailed comments, an explanation, expected output, and key interview talking points, mirroring the structure and simplicity of the useState example. Simple Working JavaScript Code for useReducer Polyfill // Simple useReducer polyfill for interview explanation function createUseReducer () { // Array to store state values across multiple "renders" of the component. // This simulates React's internal state storage for a component. let stateStore = []; // Variable to track the current index for hook calls during a single render. // This ensures each useReducer call maps to the same state slot every render. let currentIndex = 0 ; // The useReducer function, mimicking React's hook for managing complex state. function useReducer ( reducer , initialState ) { // Capture the current index for this specific useReducer call. // This index determines where in stateStore this state value lives. const index = currentIndex ; // Increment currentIndex for the next useReducer/useState call in this render. // e.g., First call gets index 0, second gets index 1, etc. currentIndex ++ ; // Initialize the state value at this index if it hasn't been set yet. // This happens during the first render or if state was cleared. if ( stateStore [ index ] === undefined ) { stateStore [ index ] = initialState ; } // Get the current state value from stateStore at this index. // This is what the component will use during this render. const currentState = stateStore [ index ]; // Define the dispatch function to update state using the reducer. // This mimics React's dispatch behavior to update state based on actions. const dispatch = function ( action ) { // Call the reducer with current state and action to get new state. const newState = reducer ( stateStore [ index ], action ); stateStore [ index ] = newState ; console . log ( `State updated to: ${ JSON . stringify ( newState )} at index ${ index } with action: ${ JSON . stringify ( action )} ` ); // In real React, this would trigger a re-render automatically. // Here, we just log the update for demonstration. }; // Return an array with the current state value and the dispatch function. // This matches React's useReducer API: [state, dispatch]. return [ currentState , dispatch ]; } // Function to reset the index to 0 after a render simulation. // This simulates the end of a render cycle, preparing for the next render. // In real React, hook indices reset per render to maintain call order. function resetIndex () { currentIndex = 0 ; console . log ( ' Resetting index for next render ' ); } // Return an object with useReducer and resetIndex functions. // This allows the component to use the hook and reset the index manually. return { useReducer , resetIndex }; } // Create an instance of useReducer by calling createUseReducer(). // This sets up a unique state store for this simulation. const { useReducer , resetIndex } = createUseReducer (); // Reducer function to manage state updates based on actions. // This is a user-defined function passed to useReducer, just like in React. function counterReducer ( state , action ) { switch ( action . type ) { case ' INCREMENT ' : return { ... state , count : state . count + 1 }; case ' DECREMENT ' : return { ... state , count : state . count - 1 }; case ' SET_NAME ' : return { ... state , name : action . payload }; default : return state ; } } // Simulated functional component to demonstrate useReducer usage. // In real React, this would be a component that renders UI. function MyComponent () { // Use useReducer to manage a state object with a counter and name. // Pass the reducer function and initial state. // This will map to index 0 in stateStore. const [ state , dispatch ] = useReducer ( counterReducer , { count : 0 , name : " Zeeshan " }); // Log the current state values during this render. // This shows what the component "sees" at this moment. console . log ( ' Current State - Count: ' , state . count , ' Name: ' , state . name ); // Return the dispatch function to allow updates outside render. // In real React, updates might happen via events like button clicks. return { dispatch }; } // Run the simulation to mimic React rendering the component multiple times. console . log ( ' First Call (Initial Render): ' ); // Call MyComponent for the first time, simulating the initial render. // This initializes state values in stateStore. const { dispatch } = MyComponent (); // Reset the index after the render to prepare for the next call. // This ensures the next call to MyComponent starts at index 0 again. resetIndex (); // Update the state using the dispatch function. // This simulates user interaction or some event updating the state. console . log ( ' \n Updating State: ' ); dispatch ({ type : ' INCREMENT ' }); // Updates state.count to 1. dispatch ({ type : ' SET_NAME ' , payload : ' John ' }); // Updates state.name to "John". // Run the component again to simulate a re-render after state updates. // This mimics React re-rendering the component to reflect new state. console . log ( ' \n Second Call (After Update): ' ); MyComponent (); // Reset the index again after this render to keep hook order consistent. resetIndex (); Enter fullscreen mode Exit fullscreen mode How to Execute In a Browser : Open your browser's developer tools (e.g., Chrome DevTools), go to the "Console" tab, copy-paste the code above, and press Enter. You'll see the logs showing the initial state, updates, and updated state. In Node.js : Save this code in a file (e.g., simpleUseReducer.js ) and run it using node simpleUseReducer.js in your terminal. The output will appear in the console. Expected Output When you run this code, you'll see output similar to this: First Call (Initial Render): Current State - Count: 0 Name: Zeeshan Resetting index for next render Updating State: State updated to: {"count":1,"name":"Zeeshan"} at index 0 with action: {"type":"INCREMENT"} State updated to: {"count":1,"name":"John"} at index 0 with action: {"type":"SET_NAME","payload":"John"} Second Call (After Update): Current State - Count: 1 Name: John Resetting index for next render Enter fullscreen mode Exit fullscreen mode Explanation of Code Purpose : This polyfill demonstrates the basic idea of useReducer —managing complex state in a functional component by using a reducer function to update state based on dispatched actions, across "renders." How It Works : stateStore is a simple array that holds state values. Each useReducer call gets a unique index tracked by currentIndex during a render, ensuring consistency across calls. The state is initialized the first time useReducer is called for that index with the provided initialState . dispatch updates the state by calling the reducer function with the current state and an action, storing the new state in stateStore . Calling MyComponent() multiple times simulates re-renders, showing the updated state. Simplification : Unlike real React, there’s no automatic re-rendering or complex hook order edge cases. It’s a basic demonstration of state management with a reducer using an array. Key Interview Talking Points What is useReducer ? : Explain it’s a React hook for managing state in functional components, especially for complex state logic. It uses a reducer function to update state based on actions, similar to Redux. How This Polyfill Works : Walk through the code: State is stored in an array ( stateStore ) with each useReducer call getting its own slot via currentIndex . dispatch updates the state by invoking the reducer with the current state and an action, storing the result. Calling the component again shows the updated state, mimicking a re-render. Why Use useReducer Over useState ? : Mention that useReducer is preferred for complex state updates (e.g., multiple related fields or logic-heavy transitions) as it centralizes update logic in a reducer, making it more predictable and testable. Why Simple? : Note this is a basic version to show the concept. Real React uses a fiber tree and update queue for state management and rendering, which this manual simulation simplifies. State Persistence : Highlight that state isn’t reset between calls to the component, just like in React, where state persists across renders. Limitations : Point out that this lacks React’s automatic re-rendering, batched updates, or strict hook order rules. It’s purely for conceptual understanding. This useReducer polyfill is intentionally minimal, mirroring the simplicity of the useState example, and focuses on the core idea of state management with a reducer for an interview. It’s easy to explain and execute, showing how state is stored and updated via actions. If you’d like to add more detail, combine it with useState , or explore more complex reducer examples, let me know! Polyfill series (8 Part Series) 1 Polyfill - Promise.all 2 Polyfills for .forEach(), .map(), .filter(), .reduce() in JavaScript ... 4 more parts... 3 Polyfill - Promise 4 Polyfill - fetch 5 Polyfill - call, apply & bind 6 Polyfill - useState (React) 7 Polyfill - useEffect (React) 8 Polyfil - useReducer 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 ZeeshanAli-0704 Follow Results-driven Principal Applications Engineer with 9+ years of experience in scalable web app development using React, Angular, Node.js, and KnockoutJS across BFSI, Media, and Healthcare domains. Location INDIA Pronouns he Work Oracle Joined Aug 13, 2022 More from ZeeshanAli-0704 Polyfill - useEffect (React) # javascript # react # tutorial Polyfill - useState (React) # javascript Polyfill - call, apply & bind # javascript # 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:48:41 |
https://docs.suprsend.com/reference/cli-workflow-list | List Workflows - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Workflow List Workflows Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Workflow List Workflows OpenAI Open in ChatGPT List workflows in a workspace OpenAI Open in ChatGPT Syntax Copy Ask AI suprsend workflow list [flags] Flags Flag Description Default -h, --help Show help for the command – -l, --limit int Number of workflows to list 20 -f, --offset int Starting position for pagination 0 -m, --mode string Workflow mode ( live or draft ) live -o, --output string Output format ( pretty , json , yaml ) pretty Example Copy Ask AI # List live workflows in staging workspace suprsend workflow list # List with custom limit and workspace suprsend workflow list --limit 50 --workspace production # List draft workflows suprsend workflow list --mode draft # piping JSON output to jq suprsend workflow list --output json | jq '.[].slug' Was this page helpful? Yes No Suggest edits Raise issue Previous Pull Workflows Fetch workflows from SuprSend workspace to local directory or server Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:41 |
https://dev.to/szabgab/perl-weekly-598-tiobe-and-perl-2fg | Perl Weekly #598 - TIOBE and Perl - 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 Gabor Szabo Posted on Jan 9, 2023 • Originally published at perlweekly.com Perl Weekly #598 - TIOBE and Perl # perl # news # programming perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? Originally published at Perl Weekly 598 Hi there, Happy New Year everyone !!! Year 2022 saw the biggest release of Perl v5.36 . It was released with big bang. There were lots of positive vibes around it. I had never seen such noise before. If you missed the fun then you can checkout my GitHub repository . I am not a big fan of TIOBE but came across TIOBE Index for January 2023 talking about Perl going up slightly in the index recently. It is refreshing to see the progress. Who knows one day, it would reach the TOP 5 brackets. Looking back the participation in The Weekly Challenge , it looks promising. Nearly 10K contributions in Perl by the members of Team PWC in the last 4 years . What is new happening in Perl? For me, personally, I am looking forward to the modern OO Corinna in core Perl . Curtis wrote an interesting blog post recently where he shared his real life experience with Corinna . Enjoy rest of the newsletter. -- Your editor: Mohammad S. Anwar. Announcements This Week in PSC (092) More update on Perl v5.38. Articles Keeping Your Valuables Under Lock and Key One problem multiple solutions. Highly Recommended. Typed variables Typed variables in Perl? Well do checkout the post. Perl Regex Parsing with the g option Context is imortant, why? You will find the answer in the post. Finding Similar Image Linux Magazine Column 50 Web AoC 2022/23 - Unstable diffusion AoC 2022/24 - These elves require a lot of patience... AoC 2022/25 - Wind down, hot air up! AoC 2022/16 - Paying a debt AoC 2022/16 - OMG what an improvement The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 199 Welcome to a new week with a couple of fun tasks: "Good Pairs" and "Good Triplets". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 198 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Max Gap" and "Prime Count" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Prime the Gaps! Nice discussion about the task "Max Gap", thanks for sharing. Prime the Gap The power of Raku makes the solution simple and easy to follow. Great work, keep it up. Mind The Gap Lots of technical aspects discussed in the blog. You really don't want to miss it. PWC198 - Max Gap Clean straight forward solutions both in Perl and Raku. Thanks for your contribution. PWC198 - Prime Count Pleasantly surprised with the fun approach. Keep up the great work. Master of Golf coding. The end result looks beautiful. Thanks. Perl Weekly Challenge 198: Max Gap and Prime Count Modular solutions makes the code easy to ready. Well done. First Perl Code of the Year! Well, not just Raku but SQL is part of the gang as always. Please do checkout. Perl Weekly Challenge 198 Good use of CPAN module to solve the task elegantly. Keep it up great work. Mind the gap! Thanks for sharing the sort fun. Thanks for your contributions. The Weekly Challenge #198 Well documented solutions. Always fun to follow the blog post. Count Max Kotlin is the choosen one this week from the collection of gems. Keep it up great work. Weekly Challenge 198 Nice demo of code re-use. Why re-inventing the wheel, well done. PWC 198 The consistent contribution is the key factor. Thank you for your support. Rakudo 2023.01 Humming Away Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . Perl Jobs by Perl Careers Bold, beautiful, and… brainy? Senior Perl roles in Malaysia, Dubai and Malta With all the knowledge in your big, beautiful brain, it’s time to join a company that appreciates your breadth of experience. Our client provides online trading services and with offices in Dubai, Malta, and Malaysia, they’ve got the global reach that may provide the challenge you’re looking for. They know that a seasoned Perl pro is just what their team needs as they expand, and that’s where you Perl to Node Cross-training? Yes Please! UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe. UK Remote Perl Role A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Modern Perl and positive team vibes. UK Remote Perl role If you’re a Modern Perl developer in the UK with Go-lang experience (or at least a strong desire to learn) and you’re searching for a team of dynamos, we’ve found the perfect place for you. This award-winning company may be newer, but the combined experience of their people is impressive. No doubt this is one of the many reasons their AI recruitment marketing business has taken off! Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (154 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 150 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution 154 Perl 🐪 Weekly #755 - Does TIOBE help Perl? 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #755 - Does TIOBE help Perl? # perl # news # programming Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming 💎 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:48:41 |
https://docs.suprsend.com/reference/cli-workflow-pull | Pull Workflows - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Workflow Pull Workflows Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Workflow Pull Workflows OpenAI Open in ChatGPT Fetch workflows from SuprSend workspace to local directory or server OpenAI Open in ChatGPT Pull workflows from a SuprSend workspace into your local directory or server. This action does not delete existing workflows; instead, it overwrites workflows with the same slug or creates new ones. By default, pulled workflows are stored in the suprsend/workflow/ directory, but you can change the destination using the -d flag. We recommend specifying a directory when working with multiple production or staging workspaces. Syntax Copy Ask AI suprsend workflow pull [flags] Flags Flag Description Default -h, --help Show help for the command – -g, --slug string Pull individual workflow by passing it’s slug – -d, --dir string Custom directory path for saving pulled workflows suprsend/workflow -m, --mode string Workflow mode to pull ( live or draft ) live Example Copy Ask AI # Pull all live workflows to current directory suprsend workflow pull # Pull workflows into custom directory path suprsend workflow pull --dir dev-environment/workflows # Pull draft workflows from production suprsend workflow pull --mode draft --workspace production # Pull individual workflow by passing it's slug suprsend workflow pull --slug welcome-email Was this page helpful? Yes No Suggest edits Raise issue Previous Push Workflows Push workflows from local directory or server to SuprSend Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:41 |
https://survivejs.com/books/webpack/ | SurviveJS – Webpack 5 Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... SurviveJS – Webpack 5 Webpack ↗ is a module bundler meant for building JavaScript applications and sites. In this book, I will go through main features of webpack while teaching you to compose configuration using webpack-merge ↗ . Incidentally, I developed webpack-merge for the purposes of this book and since then it has become a popular solution for taming the complexity of webpack configuration. The book is meant to web developers ranging from beginners to advanced although you should be familiar with the basic ideas behind JavaScript language to get most out of it. The book content was developed during many years with the help of the community and it complements the official documentation. Even if you know webpack well already, I have taken care to include short summaries capturing the main points of the book so you can fill the gaps in your knowledge and understanding of the tool. Read the webpack book Buy the webpack book ↗ Testimonials Clément Paris Front-end Engineer After weeks failing at configuring webpack, I stumbled upon SurviveJS book while looking for yet another tutorial. Since that day, it has been my go-to resource for every single webpack question I ever had. Andrea Chiumenti CEO Red Software Systems ↗ Brilliant! A must have if you want to to learn webpack but also if need an updated reference guide. I always use it as a reference guide when I develop. Gavin Doughtie Senior Software Engineer Google ↗ Before I worked through the SurviveJS webpack book, my own webpack config, cobbled together from random code on the Internet, was a mystery to me. Afterwards, I have route-splitting and parallel-loading superpowers. Neeraj Singh Founder Big Binary ↗ Webpack is powerful but configuring it can be painful. Same goes with React. There are so many ways of configuring React with asset compilation, minification etc that it is easy to get lost. This book provides practical tips on how to proceed. Aaron Harris Software Engineer This guide was a great starter in taming the Wild West of ESNext-era JavaScript development. Its beauty comes from its commitment to not skipping the fundamentals in favor of a fast demo, but making sure you’re understanding what you’re doing as you bootstrap your next JavaScript-based UI project. Julien Castelain Software Engineer Liferay ↗ This guide is a great way to get started with webpack or improve your existing skills. After a detailed introduction, you’ll start working on a webpack project that provides all you need to push your app to production. Highly recommended. Availability Although you can read the book online for free , you can also purchase it in a copy to support the development of the content. See also consulting for other available options. Leanpub (digital, always up to date with the site) ↗ Amazon (paperback, last major revision) ↗ Kindle (digital, last major revision) ↗ Table of contents Foreword It's a funny story how I started with webpack. Before getting addicted to JavaScript, I also developed in Java. I tried GWT (Google Web Toolkit) in that time. GWT is a Java-to-JavaScript Compiler, which has a great feature: code splitting. I liked this feature and missed it in existing JavaScript t… Preface The book you are reading right now goes years back. It all started with a comment I made on Christian Alfoni's blog in 2014. It was when I discovered webpack and React, and I felt there was a need for a cookbook about the topics. The work began with a GitHub wiki in early 2015. After a while, I re… Introduction Webpack simplifies web development by solving a fundamental problem: bundling. It takes in various assets, such as JavaScript, CSS, and HTML, and transforms them into a format that's convenient to consume through a browser. Doing this well takes a significant amount of pain away from web developmen… What is Webpack Webpack is a module bundler. Webpack can take care of bundling alongside a separate task runner. However, the line between bundler and task runner has become blurred thanks to community-developed webpack plugins. Sometimes these plugins are used to perform tasks that are usually done outside of web… Developing In this part, you get up and running with webpack. You will learn to configure webpack-plugin-serve. Finally, you compose the configuration so that it's possible to expand in the following parts of the book. … Getting Started Before getting started, make sure you are using a recent version of Node. You should use at least the most current LTS (long-term support) version as the configuration of the book has been written with modern Node features in mind. You should have node and npm (or yarn) commands available at your … Development Server When developing a frontend without any special tooling, you often end up having to refresh the browser to see changes. Given this gets annoying fast, there's tooling to remedy the problem. The first tools on the market were LiveReload and Browsersync. The point of either is to allow refreshing the… Composing Configuration Even though not a lot has been done with webpack yet, the amount of configuration is starting to feel substantial. Now you have to be careful about the way you compose it as you have separate production and development targets in the project. The situation can only get worse as you want to add more… Styling In this part, you will learn about styling-related concerns in detail including loading styles, separating CSS, eliminating unused CSS, and autoprefixing. … Loading Styles Webpack doesn't handle styling out of the box, and you will have to use loaders and plugins to allow loading style files. In this chapter, you will set up CSS with the project and see how it works out with automatic browser refreshing. When you make a change to the CSS webpack doesn't have to force… Separating CSS Even though there is a nice build set up now, where did all the CSS go? As per configuration, it has been inlined to JavaScript! Although this can be convenient during development, it doesn't sound ideal. The current solution doesn't allow caching CSS. You can also get a Flash of Unstyled Content … Eliminating Unused CSS Frameworks like Bootstrap or Tailwind tend to come with a lot of CSS. Often you use only a small part of it and if you aren't careful, you will bundle the unused CSS. PurgeCSS is a tool that can achieve this by analyzing files. It walks through your code and figures out which CSS classes are being… Autoprefixing It can be challenging to remember which vendor prefixes you have to use for specific CSS rules to support a large variety of users. Autoprefixing solves this problem. It can be enabled through PostCSS and the autoprefixer plugin. autoprefixer uses Can I Use service to figure out which rules should … Loading Assets In this part, you will learn how to load different types of assets using webpack's loaders. Especially images, fonts, and JavaScript receive particular attention. You also learn how webpack's loader definitions work. … Loader Definitions Webpack provides multiple ways to set up module loaders. Each loader is a function accepting input and returning output. They can have side effects as they can emit to the file system and can intercept execution to implement caching. Anatomy of a loader Webpack supports common JavaScript formats … Loading Images Image loading and processing can be a concern when developing sites and applications. The problem can be solved by pushing the images to a separate service that then takes care of optimizing them and provides an interface for consuming them. For smaller scale usage, webpack is a good option as it … Loading Fonts Loading fonts is similar to loading images. It does come with unique challenges, though. How to know what font formats to support? There can be up to four font formats to worry about if you want to provide first class support to each browser. The problem can be solved by deciding a set of browsers… Loading JavaScript Webpack processes ES2015 module definitions by default and transforms them into code. It does not transform specific syntax, such as const, though. The resulting code can be problematic especially in the older browsers. To get a better idea of the default transform, we can generate a build while s… Building In this part, you enable source maps on the build, discuss how to split it into separate bundles in various ways, and learn to tidy up the result. … Source Maps Source maps in Chrome When your source code has gone through transformations, debugging in the browser becomes a problem. Source maps solve this problem by providing a mapping between the original and the transformed source code. In addition to source compiling to JavaScript, this works for stylin… Code Splitting Web applications tend to grow big as features are developed. The longer it takes for your site to load, the more frustrating it's to the user. This problem is amplified in a mobile environment where the connections can be slow. Even though splitting bundles can help a notch, they are not the only … Bundle Splitting Although code splitting gives control over when code is loaded, it's not the only way webpack lets you shape the output. Bundle splitting is a complementary technique that lets you define splitting behavior on the level of configuration. A common use case is extracting so called vendor bundle that… Tidying Up The current setup doesn't clean the build directory between builds. As a result, it keeps on accumulating files as the project changes. Given this can get annoying, you should clean it up in between. Another nice touch would be to include information about the build itself to the generated bundles… Optimizing In this part, you will learn about code minification, setting environment variables, adding hashing to filenames, webpack runtime, analyzing build statistics, and improving webpack performance. … Minifying Since webpack 4, the production output gets minified using terser by default. Terser is an ES2015+ compatible JavaScript-minifier. Compared to UglifyJS, the earlier standard for many projects, it's a future-oriented option. Although webpack minifies the output by default, it's good to understand h… Tree Shaking Tree shaking is a feature enabled by the ES2015 module definition. The idea is that given it's possible to analyze the module definition statically without running it, webpack can tell which parts of the code are being used and which are not. It's possible to verify this behavior by expanding the a… Environment Variables Sometimes a part of your code should execute only during development. Or you could have experimental features in your build that are not ready for production yet. Controlling environment variables becomes valuable as you can toggle functionality using them. Since JavaScript minifiers can remove de… Adding Hashes to Filenames Even though the generated build works, the file names it uses is problematic. It doesn't allow to leverage client level cache efficiently as there's no way tell whether or not a file has changed. Cache invalidation can be achieved by including a hash to the filenames. T> Starting from version 5, w… Separating a Runtime When webpack writes bundles, it maintains a runtime as well. The runtime includes a manifest of the files to be loaded initially. If the names of the files change, then the manifest changes and the change invalidates the file in which it is contained. For this reason, it can be a good idea to write… Build Analysis Analyzing build statistics is a good step towards understanding webpack better. The available tooling helps to answer the following questions: What's the composition of the project bundles? What kind of dependencies do project modules have? How does the size of the project change over time? Which … Performance Webpack's performance out of the box is often enough for small projects. That said, it begins to hit limits as your project grows in scale, and it's a frequent topic in webpack's issue tracker. There are a couple of ground rules when it comes to optimization: Know what to optimize. Perform fast t… Output This part covers different output techniques webpack provides. You see how to manage a multi-page setup, how to implement server-side rendering, and how to use module federation to develop micro frontends. … Build Targets Even though webpack is used most commonly for bundling web applications, it can do more. You can use it to target Node or desktop environments, such as Electron. Webpack can also bundle as a library while writing an appropriate output wrapper making it possible to consume the library. Webpack's ou… Multiple Pages Even though webpack is often used for bundling single-page applications, it's possible to use it with multiple separate pages as well. The idea is similar to the way you generated many output files in the Targets chapter. That's achievable through MiniHtmlWebpackPlugin and a bit of configuration. … Server-Side Rendering Server-Side Rendering (SSR) is a technique that allows you to serve an initial payload with HTML, JavaScript, CSS, and even application state. You serve a fully rendered HTML page that would make sense even without JavaScript enabled. In addition to providing potential performance benefits, this ca… Module Federation Micro frontends take the idea of microservices to frontend development. Instead of developing the application or a site as a monolith, the point is to split it as smaller portions programmed separately that are then tied together during runtime. With the approach, you can use different technologie… Techniques In this part, you will learn to use webpack techniques such as dynamic loading, using web workers, internationalization, testing, deploying, and package consumption. … Dynamic Loading Even though you can get far with webpack's code splitting features covered in the Code Splitting chapter, there's more to it. Webpack provides more dynamic ways to deal with code through require.context. Dynamic loading with require.context require.context provides a general form of code splittin… Web Workers Web workers allow you to push work outside of main execution thread of JavaScript, making them convenient for lengthy computations and background work. Moving data between the main thread and the worker comes with communication-related overhead. The split provides isolation that forces workers to … Internationalization Internationalization (i18n) is a big topic by itself. The broadest definition has to do with translating your user interface to other languages. Localization (l10n) is a more specific term, and it describes how to adapt your application to a particular locale or market. Different locales can have t… Testing Testing is a vital part of development. Even though techniques, such as linting, can help to spot and solve issues, they have their limitations. Testing can be applied to the code and an application on many different levels. You can unit test a specific piece of code, or you can look at the applic… Deploying Applications A project built with webpack can be deployed to a variety of environments. A public project that doesn't rely on a backend can be pushed to GitHub Pages using the gh-pages package. Also, there are a variety of webpack plugins that can target other environments, such as S3. Deploying with gh-pages … Consuming Packages Sometimes packages have not been packaged the way you expect, and you have to tweak the way webpack interprets them. Webpack provides multiple ways to achieve this. resolve.alias Sometimes packages do not follow the standard rules and their package.json contains a faulty main field. It can be mis… Extending Even though there are a lot of available loaders and plugins for webpack, it's good to be able to extend it. In this part, you go through a couple of short examples to understand how to get started. … Extending with Loaders As you have seen so far, loaders are one of the building blocks of webpack. If you want to load an asset, you most likely need to set up a matching loader definition. Even though there are a lot of available loaders, it's possible you are missing one fitting your purposes. You'll learn to develop … Extending with Plugins Compared to loaders, plugins are a more flexible means to extend webpack. You have access to webpack's compiler and compilation processes. It's possible to run child compilers, and plugins can work in tandem with loaders as MiniCssExtractPlugin shows. Plugins allow you to intercept webpack's execu… Conclusion As this book has demonstrated, webpack is a versatile tool. To make it easier to recap the content and techniques, go through the checklists below. General checklist Source maps** allow you to debug your code in the browser during development. They can also give better quality stack traces during… Appendices As not everything that's worth discussing fits into the main content, you can find related material in brief appendices. These support the primary content and explain specific topics, such as Hot Module Replacement, in greater detail. You will also learn to troubleshoot webpack. … Comparison of Build Tools Back in the day, it was enough to concatenate scripts together. Times have changed, though, and distributing your JavaScript code can be a complicated endeavor. This problem has escalated with the rise of single-page applications (SPAs) as they tend to rely on many big libraries. For this reason, m… Hot Module Replacement Hot Module Replacement (HMR) builds on top of the WDS. It enables an interface that makes it possible to swap modules live. For example, style-loader can update your CSS without forcing a refresh. Implementing HMR for styles is ideal because CSS is stateless by design. HMR is possible with JavaScr… CSS Modules Perhaps the most significant challenge of CSS is that all rules exist within global scope, meaning that two classes with the same name will collide. The limitation is inherent to the CSS specification, but projects have workarounds for the issue. CSS Modules introduces local scope for every module … Searching with React Let's say you want to implement a rough little search for an application without a proper backend. You could do it through lunr and generate a static search index to serve. The problem is that the index can be sizable depending on the amount of the content. The good thing is that you don't need th… Troubleshooting Using webpack can lead to a variety of runtime warnings or errors. Often a particular part of the build fails for a reason or another. A basic process can be used to figure out these problems: Enable stats.errorDetails in webpack configuration to get more information. Study the origin of the error… Glossary Given webpack comes with specific terminology, the principal terms and their explanations have been gathered below. Asset** is a general term for the media and source files of a project that are the raw material used by webpack in building a bundle. Bundle** is the result of bundling. Bundling inv… Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://dev.to/nixx0328#main-content | Nixx0328 - 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 Nixx0328 <s>The boy is clever,he left nothing</s> I'm a 15 years old student|C++ Programmer|One of CZLJ.top's Admins|Minecraft player:Nixx|a boy want to be a White hat hacker! I'm sorry about my hard English=( Location 中国·江苏省·常州市·武进区 Joined Joined on Jun 29, 2024 Personal website https://nixx0328.github.io/ github website Education 中国·江苏省·常州市·武进区·西太湖外国语学校·初中部·八年级（4）班 Pronouns Minecraft cool player! Work ?I'm a student in Grade 8 now. More info about @nixx0328 Badges 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 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Skills/Languages C++.It's my first program language.I learn it for 3 years and get some awards(in China). Now I'm learning more program languages.I know a little about PHP、HTML、SQL.I'm going to build myself's Website! Currently learning C++、PHP、HTML、SQL、Javascript,and Raylib v5.0,a C++ 3D storehouse(raylib.com) Now I plan to build myself WebSite My program tools: ·RedPandaIDE(royqh.net/redpandacpp/) ·VS Code ·phpstudy(phpstudy.com) Currently hacking on A 3D game project.It's like Minecraft.(use Raylib)You can clone it in github.com/Nixx0328/C-Raylib-Project-Minecraft Another is my Website:nixx0328.github.io I'm learning Hacker Techno too (hacker101) Available for About c++ programs、learning SQL and Hacker Technology. If you want,I'm glad to talk about Raylib 3D storehouse and the sandbox game——Minecraft(Yee,I'm crazzy about it) Post 0 posts published Comment 5 comments written Tag 11 tags followed Want to connect with Nixx0328? Create an account to connect with Nixx0328. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in 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:48:41 |
https://survivejs.com/books/ | SurviveJS - Books Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Books I have authored several books related to JavaScript and you can find them on this site. See below for more specific descriptions. SurviveJS – Webpack 5 In this book, I go through main features of webpack ↗ , a module bundler for JavaScript, and show how to compose your own configuration effectively. It doubles as a reference for common webpack techniques and I have included discussion considering alternatives. The book matches the current version of webpack. Read webpack book SurviveJS – Maintenance In this book co-authored with Artem Sapegin ↗ , I explore how to maintain and publish your JavaScript projects. Originally it was split off from the webpack book. The book is largely complete although I want to give it modernization pass to catch up with the latest developments in the space. Read maintenance book SurviveJS – React React book is where it all started and the webpack book was split up from this. The book is not up to date although it may be interesting to follow the book project while building it using some other technology or the latest React APIs. In other words the book could use an update and it is maintained on the site for historical purposes for now. Read React book Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://aws.amazon.com/blogs/developer/category/programing-language/dot-net/ | .NET | AWS Developer Tools Blog Skip to Main Content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Blogs Home Blogs Editions AWS Developer Tools Blog Category: .NET What’s New in the AWS Deploy Tool for .NET by Philippe El Asmar on 14 OCT 2025 in .NET , Announcements , AWS .NET Development , AWS SDK for .NET , AWS Toolkit for Visual Studio , Developer Tools , Visual Studio Permalink Share Version 2.0 of the AWS Deploy Tool for .NET is now available. This new major version introduces several foundational upgrades to improve the deployment experience for .NET applications on AWS. The tool comes with new minimum runtime requirements. We have upgraded it to require .NET 8 because the predecessor, .NET 6, is now out of […] AWS .NET Distributed Cache Provider for Amazon DynamoDB now Generally Available by Garrett Beatty on 03 JUL 2025 in .NET , Advanced (300) , Announcements , AWS .NET Development , AWS SDK for .NET , Developer Tools Permalink Share Today, we are excited to announce the general availability of the AWS .NET Distributed Cache Provider for Amazon DynamoDB. This is a seamless, serverless caching solution that enables .NET developers to efficiently manage their caching needs across distributed systems. Consistent caching is a difficult problem in distributed architectures, where maintaining data integrity and performance across […] Deploy to ARM-Based Compute with AWS Deploy Tool for .NET by Philippe El Asmar on 08 MAY 2025 in .NET , Announcements , AWS .NET Development , AWS SDK for .NET , AWS Toolkit for Visual Studio , Developer Tools , Visual Studio Permalink Share We’re excited to announce that the AWS Deploy Tool for .NET now supports deploying .NET applications to select ARM-based compute platforms on AWS! Whether you’re deploying from Visual Studio or using the .NET CLI, you can now target cost-effective ARM infrastructure like AWS Graviton with the same streamlined experience you’re used to. Why deploy to […] Announcing the end of support for AWS DynamoDB Session State Provider by Philippe El Asmar on 07 MAY 2025 in .NET , AWS SDK for .NET Permalink Share We are announcing the deprecation of the AWS DynamoDB Session State Provider for .NET. Support for this library will continue for the next six months and will officially end on November 14, 2025. After that date, we will no longer publish updates to the library, including security or critical bug fixes. Previously published releases will […] General Availability of AWS SDK for .NET V4.0 by Norm Johanson on 28 APR 2025 in .NET , Announcements , AWS SDK for .NET , Foundational (100) Permalink Share Version 4.0 of the AWS SDK for .NET has been released for general availability (GA). V4 has been in development for a little over a year in our SDK’s public GitHub repository with 13 previews being released. This new version contains performance improvements, consistency with other AWS SDKs, and bug and usability fixes that required […] Building and Debugging .NET Lambda applications with .NET Aspire (Part 2) by Norm Johanson on 04 MAR 2025 in .NET , AWS Lambda Permalink Share In Part 1 of our blog posts for .NET Aspire and AWS Lambda, we showed you how .NET Aspire can be used for running and debugging .NET Lambda functions. In this part, Part 2, we’ll show you how to take advantage of the .NET Aspire programming model for best practices and for connecting dependent resources […] Building and Debugging .NET Lambda applications with .NET Aspire (Part 1) by Norm Johanson on 03 MAR 2025 in .NET , AWS Lambda Permalink Share In a recent post we gave some background on .NET Aspire and introduced our AWS integrations with .NET Aspire that integrate AWS into the .NET dev inner loop for building applications. The integrations included how to provision application resources with AWS CloudFormation or AWS Cloud Development Kit (AWS CDK) and using Amazon DynamoDB local for […] Integrating AWS with .NET Aspire by Norm Johanson on 11 FEB 2025 in .NET Permalink Share .NET Aspire is a new way of building cloud-ready applications. In particular, it provides an orchestration for local environments in which to run, connect, and debug the components of distributed applications. Those components can be .NET projects, databases, containers, or executables. .NET Aspire is designed to have integrations with common components used in distributed applications. […] Preview 4 of AWS SDK for .NET V4 by Norm Johanson on 11 NOV 2024 in .NET , AWS SDK for .NET Permalink Share In August 2024, we announced the first preview of our upcoming version 4 of the AWS SDK for .NET. Since then we have continued making progress and released new previews as we go. At the time of writing this post, the SDK has released preview 4. In this post, we’ll take a look at some […] JSON Structured Logging for .NET Lambda Functions by Norm Johanson on 07 NOV 2024 in .NET , AWS Lambda Permalink Share We are announcing support for JSON structured logging for the .NET managed runtime. This makes the .NET managed runtime compatible with the previously announced logging controls for AWS Lambda, allowing you to toggle logging format and log levels using the Lambda API. Formatting log messages as JSON documents makes it easier to search, filter, and […] ← Older posts @charset "UTF-8";[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4{position:relative;transition:box-shadow .3s ease}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover{box-shadow:var(--rg-shadow-gray-elevation-1, 1px 1px 20px rgba(0, 0, 0, .1))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0.rgft_e79955da,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003.rgft_e79955da,[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover.rgft_e79955da{box-shadow:var(--rg-shadow-gray-elevation-2, 1px 1px 24px rgba(0, 0, 0, .25))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1b2a14d4:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:hover{box-shadow:none}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde{position:relative;transform-style:preserve-3d;overflow:unset!important}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:before{content:"";position:absolute;inset:0;border-radius:inherit;transform:translateZ(-1px);pointer-events:none;transition-property:filter,inset;transition-duration:.3s;transition-timing-function:ease;background-clip:content-box!important;padding:1px}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_3d631df0.rgft_4df65418:hover:before{filter:blur(20px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_5962fadc:hover:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:before{filter:blur(15px)}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_b27cc003:hover:before{filter:none}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_e90ac70d:active:before{filter:blur(8px)!important}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_a4f580d2:before{filter:blur(8px)!important}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #fa6f00 0%, #e433ff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #d14600 0%, #c300e0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #0099ff 0%, #5c7fff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #006ce0 0%, #295eff 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #ff1ae0 0%, #ff386a 50%, #fa6f00 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #d600ba 0%, #eb003b 50%, #d14600 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #00bd6b 0%, #00a4bd 50%, #0099ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #008559 0%, #007e94 50%, #006ce0 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #00bd6b 0%, #0099ff 50%, #8575ff 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #008559 0%, #006ce0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #ad5cff 0%, #0099ff 50%, #00a4bd 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #962eff 0%, #006ce0 50%, #007e94 100%))}[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=light][data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #ff1ae0 0%, #8575ff 50%, #00a4bd 100%))}[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a).rgft_38d8ffac:before,[data-eb-6a8f3296] [data-rg-mode=dark][data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde.rgft_38d8ffac:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #d600ba 0%, #6842ff 50%, #007e94 100%))}[data-eb-6a8f3296] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:linear-gradient(123deg,#d14600,#c300e0,#6842ff)}[data-eb-6a8f3296] [data-rg-theme=fuchsia] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=fuchsia].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-fuchsia, linear-gradient(123deg, #d14600 0%, #c300e0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=indigo] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=indigo].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-indigo, linear-gradient(123deg, #006ce0 0%, #295eff 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=orange] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=orange].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-orange, linear-gradient(123deg, #d600ba 0%, #eb003b 50%, #d14600 100%))}[data-eb-6a8f3296] [data-rg-theme=teal] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=teal].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-teal, linear-gradient(123deg, #008559 0%, #007e94 50%, #006ce0 100%))}[data-eb-6a8f3296] [data-rg-theme=blue] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=blue].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-blue, linear-gradient(123deg, #008559 0%, #006ce0 50%, #6842ff 100%))}[data-eb-6a8f3296] [data-rg-theme=violet] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=violet].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-violet, linear-gradient(123deg, #962eff 0%, #006ce0 50%, #007e94 100%))}[data-eb-6a8f3296] [data-rg-theme=purple] .rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before,[data-eb-6a8f3296] [data-rg-theme=purple].rgft_9e423fbb.rgft_1ed8cbde:not(:disabled,.rgft_3ef5a62a):before{background:var(--rg-shadow-gradient-purple, linear-gradient(123deg, #d600ba 0%, #6842ff 50%, #007e94 100%))}[data-eb-6a8f3296] a.rgft_f7822e54,[data-eb-6a8f3296] button.rgft_f7822e54{--button-size: 44px;--button-pad-h: 24px;--button-pad-borderless-h: 26px;border:2px solid var(--rg-color-background-page-inverted, #0F141A);padding:8px var(--button-pad-h, 24px);border-radius:40px!important;align-items:center;justify-content:center;display:inline-flex;height:var(--button-size, 44px);text-decoration:none!important;text-wrap:nowrap;cursor:pointer;position:relative;transition:all .3s ease}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_094d67e1,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_094d67e1{--button-size: 32px;--button-pad-h: 14px;--button-pad-borderless-h: 16px}[data-eb-6a8f3296] a.rgft_f7822e54>span,[data-eb-6a8f3296] button.rgft_f7822e54>span{color:var(--btn-text-color, inherit)!important}[data-eb-6a8f3296] a.rgft_f7822e54:focus-visible,[data-eb-6a8f3296] button.rgft_f7822e54:focus-visible{outline:2px solid var(--rg-color-focus-ring, #006CE0)!important;outline-offset:4px!important;transition:outline 0s}[data-eb-6a8f3296] a.rgft_f7822e54:focus:not(:focus-visible),[data-eb-6a8f3296] button.rgft_f7822e54:focus:not(:focus-visible){outline:none!important}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_303c672b,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_303c672b{--btn-text-color: var(--rg-color-text-utility-inverted, #FFFFFF);background-color:var(--rg-color-btn-primary-bg, #161D26);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_18409398{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF);border-color:var(--rg-color-background-page-inverted, #0F141A)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_090951dc{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-background-object, #F3F3F7);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_15529d9f{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{--btn-text-color: var(--rg-color-text-utility, #161D26);border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{background-image:linear-gradient(97deg,#ffc0ad,#f8c7ff 37.79%,#d2ccff 75.81%,#c2d1ff)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb950a4e{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a, linear-gradient(120deg, #f8c7ff 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_bb950a4e,[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_bb950a4e{background-image:var(--rg-gradient-a, linear-gradient(120deg, #78008a 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678{--btn-text-color: var(--rg-color-text-utility-inverted, #FFFFFF);background-color:var(--rg-color-btn-visited-bg, #656871);border-color:var(--rg-color-btn-visited-bg, #656871)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678.rgft_18409398,[data-eb-6a8f3296] a.rgft_f7822e54.rgft_bb419678.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_bb419678.rgft_15529d9f{--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-visited-bg, #FFFFFF)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5{--btn-text-color: var(--rg-color-btn-disabled-text, #B4B4BB);background-color:var(--rg-color-btn-disabled-bg, #F3F3F7);border-color:var(--rg-color-btn-disabled-bg, #F3F3F7);cursor:default}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_18409398,[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_15529d9f,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_18409398,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_15529d9f{border:none;padding:10px var(--button-pad-borderless-h, 24px)}[data-eb-6a8f3296] a.rgft_f7822e54.rgft_badebaf5.rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54.rgft_badebaf5.rgft_090951dc{--btn-text-color: var(--rg-color-btn-tertiary-disabled-text, #B4B4BB);background-color:#0000}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_18409398:not(.rgft_bb950a4e),[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_15529d9f:not(.rgft_bb950a4e),[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_18409398:not(.rgft_bb950a4e),[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_15529d9f:not(.rgft_bb950a4e){--btn-text-color: var(--rg-color-text-utility, #161D26);background-color:var(--rg-color-btn-secondary-bg, #FFFFFF)}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{box-shadow:none}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{background-image:linear-gradient(97deg,#ffc0ad80,#f8c7ff80 37.79%,#d2ccff80 75.81%,#c2d1ff80)}[data-eb-6a8f3296] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a-50, linear-gradient(120deg, #f8c7ff 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54:hover:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:hover:not(.rgft_badebaf5),[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:hover:not(.rgft_badebaf5){background-image:var(--rg-gradient-a-50, linear-gradient(120deg, #78008a 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{box-shadow:none}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{background-image:linear-gradient(97deg,#ffc0ad,#f8c7ff 37.79%,#d2ccff 75.81%,#c2d1ff)}[data-eb-6a8f3296] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc{--rg-gradient-angle:97deg;background-image:var(--rg-gradient-a-pressed, linear-gradient(120deg, rgba(248, 199, 255, .5) 20.08%, #d2ccff 75.81%))}[data-eb-6a8f3296] [data-rg-mode=dark] a.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] [data-rg-mode=dark] button.rgft_f7822e54:active:not(.rgft_badebaf5).rgft_090951dc,[data-eb-6a8f3296] a[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:active:not(.rgft_badebaf5),[data-eb-6a8f3296] button[data-rg-mode=dark].rgft_f7822e54.rgft_090951dc:active:not(.rgft_badebaf5){background-image:var(--rg-gradient-a-pressed, linear-gradient(120deg, rgba(120, 0, 138, .5) 24.25%, #b2008f 69.56%))}[data-eb-6a8f3296] .rgft_8711ccd9{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;background:#0000;border:none;margin:0}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_5e58a6df{text-align:center}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_b7ada98b{display:block}[data-eb-6a8f3296] .rgft_8711ccd9.rgft_beb26dc7{font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}[data-eb-6a8f3296] .rgft_8711ccd9 a{display:inline;position:relative;cursor:pointer;text-decoration:none!important;color:var(--rg-color-link-default, #006CE0);background:linear-gradient(to right,currentcolor,currentcolor);background-size:100% .1em;background-position:0 100%;background-repeat:no-repeat}[data-eb-6a8f3296] .rgft_8711ccd9 a:focus-visible{color:var(--rg-color-link-focus, #006CE0)}[data-eb-6a8f3296] .rgft_8711ccd9 a:hover{color:var(--rg-color-link-hover, #003B8F);animation:rgft_d72bdead .3s cubic-bezier(0,0,.2,1)}[data-eb-6a8f3296] .rgft_8711ccd9 a:visited{color:var(--rg-color-link-visited, #6842FF)}@keyframes rgft_d72bdead{0%{background-size:0 .1em}to{background-size:100% .1em}}[data-eb-6a8f3296] .rgft_8711ccd9 b,[data-eb-6a8f3296] b.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 strong,[data-eb-6a8f3296] strong.rgft_8711ccd9{font-weight:700}[data-eb-6a8f3296] i.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 i,[data-eb-6a8f3296] em.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 em{font-style:italic}[data-eb-6a8f3296] u.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 u{text-decoration:underline}[data-eb-6a8f3296] code.rgft_8711ccd9,[data-eb-6a8f3296] .rgft_8711ccd9 code{font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace;border-radius:4px;border:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);color:var(--rg-color-text-secondary, #232B37);padding-top:var(--rg-padding-8);padding-right:var(--rg-padding-8);padding-bottom:var(--rg-padding-8);padding-left:var(--rg-padding-8)}[data-eb-6a8f3296] .rgft_12e1c6fa{display:inline!important;vertical-align:middle}[data-eb-6a8f3296] .rgft_8711ccd9 p img{aspect-ratio:16/9;height:100%;object-fit:cover;width:100%;border-radius:8px;order:1;margin-bottom:var(--rg-margin-4)}[data-eb-6a8f3296] .rgft_8711ccd9 table{table-layout:fixed;border-spacing:0;width:100%}[data-eb-6a8f3296] .rgft_8711ccd9 table td{font-size:14px;border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);padding-top:var(--rg-padding-6);padding-right:var(--rg-padding-6);padding-bottom:var(--rg-padding-6);padding-left:var(--rg-padding-6)}[data-eb-6a8f3296] .rgft_8711ccd9 table td:first-of-type{border-left:1px solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table thead tr:first-of-type>*:first-of-type,[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead)) tr:first-of-type>*:first-of-type{border-top-left-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table thead tr:first-of-type>*:last-of-type,[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead)) tr:first-of-type>*:last-of-type{border-top-right-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table tr:last-of-type td:first-of-type{border-bottom-left-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table tr:last-of-type td:last-of-type{border-bottom-right-radius:16px}[data-eb-6a8f3296] .rgft_8711ccd9 table:not(:has(thead),:has(th)) tr:first-of-type td{border-top:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th{color:var(--rg-color-text-primary-inverted, #FFFFFF);min-width:280px;max-width:400px;padding:0;text-align:left;vertical-align:top;background-color:var(--rg-color-background-object-inverted, #232B37);border-left:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);border-bottom:1px solid var(--rg-color-border-lowcontrast, #CCCCD1);padding-top:var(--rg-padding-6);padding-right:var(--rg-padding-6);padding-bottom:var(--rg-padding-6);padding-left:var(--rg-padding-6);row-gap:var(--rg-margin-5);column-gap:var(--rg-margin-5);max-width:100%;min-width:150px}@media (min-width: 480px) and (max-width: 767px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:100%;min-width:150px}}@media (min-width: 768px) and (max-width: 1023px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:240px;min-width:180px}}@media (min-width: 1024px) and (max-width: 1279px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:350px;min-width:240px}}@media (min-width: 1280px) and (max-width: 1599px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:400px;min-width:280px}}@media (min-width: 1600px){[data-eb-6a8f3296] .rgft_8711ccd9 table th{max-width:400px;min-width:280px}}[data-eb-6a8f3296] .rgft_8711ccd9 table th:first-of-type{border-top-left-radius:16px;border-top:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-left:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th:nth-of-type(n+3){border-left:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_8711ccd9 table th:last-of-type{border-top-right-radius:16px;border-top:0 solid var(--rg-color-border-lowcontrast, #CCCCD1);border-right:0 solid var(--rg-color-border-lowcontrast, #CCCCD1)}[data-eb-6a8f3296] .rgft_a1b66739{display:inline-flex;flex-direction:column;align-items:center;justify-content:center;color:var(--rg-color-text-primary, #161D26);--icon-color: currentcolor}[data-eb-6a8f3296] .rgft_a1b66739.rgft_bc1a8743{height:16px;width:16px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_c0cbb35d{height:20px;width:20px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_bd40fe12{height:32px;width:32px}[data-eb-6a8f3296] .rgft_a1b66739.rgft_27320e58{height:48px;width:48px}[data-eb-6a8f3296] .rgft_a1b66739 svg{fill:none;stroke:none}[data-eb-6a8f3296] .rgft_a1b66739 path[data-fill]:not([fill]){fill:var(--icon-color)}[data-eb-6a8f3296] .rgft_a1b66739 path[data-stroke]{stroke-width:2}[data-eb-6a8f3296] .rgft_a1b66739 path[data-stroke]:not([stroke]){stroke:var(--icon-color)}[data-eb-6a8f3296] .rgft_3ed66ff4{display:inline-flex;flex-direction:column;align-items:center;justify-content:center;color:var(--rg-color-text-primary, #161D26)}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_9124b200{height:10px;width:10px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_bc1a8743{height:16px;width:16px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_c0cbb35d{height:20px;width:20px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_bd40fe12{height:32px;width:32px}[data-eb-6a8f3296] .rgft_3ed66ff4.rgft_27320e58{height:48px;width:48px}[data-eb-6a8f3296] .rgft_98b54368{color:var(--rg-color-text-body, #232B37)}[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_275611e5{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_275611e5{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_275611e5{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_275611e5{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_275611e5{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_275611e5{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_007aef8b{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_007aef8b{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_007aef8b{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_007aef8b{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_98b54368.rgft_ff19c5f9{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_98b54368.rgft_ff19c5f9{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_98b54368.rgft_ff19c5f9{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_98b54368.rgft_ff19c5f9{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_98b54368 ul{list-style-type:disc;margin-top:2rem}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee{display:inline;position:relative;cursor:pointer;text-decoration:none!important;color:var(--rg-color-link-default, #006CE0);background:linear-gradient(to right,currentcolor,currentcolor);background-size:100% .1em;background-position:0 100%;background-repeat:no-repeat}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:focus-visible{color:var(--rg-color-link-focus, #006CE0)}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:hover{color:var(--rg-color-link-hover, #003B8F);animation:rgft_9beb7cc5 .3s cubic-bezier(0,0,.2,1)}[data-eb-6a8f3296] .rgft_98b54368.rgft_2a7f98ee:visited{color:var(--rg-color-link-visited, #6842FF)}@keyframes rgft_9beb7cc5{0%{background-size:0 .1em}to{background-size:100% .1em}}[data-eb-6a8f3296] .rgft_d835af5c{color:var(--rg-color-text-title, #161D26)}[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(4.5rem * var(--font-size-multiplier, 1.6));line-height:1.111;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(3.75rem * var(--font-size-multiplier, 1.6));line-height:1.133;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_3e9243e1{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_3e9243e1{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_3e9243e1{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_3e9243e1{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(3.75rem * var(--font-size-multiplier, 1.6));line-height:1.133;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_54816d41{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_54816d41{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_54816d41{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_54816d41{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(3rem * var(--font-size-multiplier, 1.6));line-height:1.167;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d835af5c.rgft_852a8b78{font-size:calc(2rem * var(--font-size-multiplier, 1.6));line-height:1.25;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d835af5c.rgft_852a8b78{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d835af5c.rgft_852a8b78{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d835af5c.rgft_852a8b78{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_286fbc8d{letter-spacing:1.6px;text-transform:uppercase;color:var(--rg-color-text-eyebrow, #161D26)}[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.714;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_cf5cdf86{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:2;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_286fbc8d.rgft_cf5cdf86{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_286fbc8d.rgft_cf5cdf86{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_286fbc8d.rgft_cf5cdf86{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.714;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:2;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_286fbc8d.rgft_c6f92487{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:2.4;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_286fbc8d.rgft_c6f92487{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_286fbc8d.rgft_c6f92487{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_286fbc8d.rgft_c6f92487{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751{color:var(--rg-color-text-utility, #161D26)}[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_927d7fd1{font-size:calc(1rem * var(--font-size-multiplier, 1.6));line-height:1.5;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_927d7fd1{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_927d7fd1{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_927d7fd1{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_100c8a76{font-size:calc(.875rem * var(--font-size-multiplier, 1.6));line-height:1.429;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_100c8a76{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_100c8a76{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_100c8a76{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_453dc601{font-size:calc(.75rem * var(--font-size-multiplier, 1.6));line-height:1.333;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_453dc601{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_453dc601{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_453dc601{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400;font-family:Amazon Ember Mono,Consolas,Andale Mono WT,Andale Mono,Lucida Console,Lucida Sans Typewriter,DejaVu Sans Mono,Bitstream Vera Sans Mono,Liberation Mono,Nimbus Mono L,Monaco,Courier New,Courier,monospace}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_d27b4751.rgft_949ed5ce{font-size:calc(.625rem * var(--font-size-multiplier, 1.6));line-height:1.2;font-weight:400}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_d27b4751.rgft_949ed5ce{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_d27b4751.rgft_949ed5ce{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_d27b4751.rgft_949ed5ce{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_5d220f64{color:var(--rg-color-text-heading, #161D26)}[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(2.5rem * var(--font-size-multiplier, 1.6));line-height:1.1;font-weight:500;font-family:Amazon Ember Display,Amazon Ember,Helvetica Neue,Helvetica,Arial,sans-serif}@media (min-width: 481px) and (max-width: 768px){[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(2rem * var(--font-size-multiplier, 1.6));line-height:1.25;font-weight:500}}@media (max-width: 480px){[data-eb-6a8f3296] .rgft_5d220f64.rgft_94339b09{font-size:calc(1.75rem * var(--font-size-multiplier, 1.6));line-height:1.286;font-weight:500}}[data-eb-6a8f3296] [data-rg-lang=ar] .rgft_5d220f64.rgft_94339b09{font-family:AmazonEmberArabic,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ja] .rgft_5d220f64.rgft_94339b09{font-family:ShinGo,\30d2\30e9\30ae\30ce\89d2\30b4 Pro W3,Hiragino Kaku Gothic Pro,Osaka,\30e1\30a4\30ea\30aa,Meiryo,\ff2d\ff33 \ff30\30b4\30b7\30c3\30af,MS PGothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=ko] .rgft_5d220f64.rgft_94339b09{font-family:NotoSansKR,Malgun Gothic,sans-serif}[data-eb-6a8f3296] [data-rg-lang=th] .rgft_5d220f64.rgft_94339b09{font-family:NotoSansThai,Helvetica,Arial,sans-serif}[data-eb-6a8f3296] [data-rg-lang=zh] .rgft_5d220f64.rgft_94339b09{font-family:NotoSansTC,Helvetica,Arial,Microsoft Yahei,\5fae\8f6f\96c5\9ed1,STXihei,\534e\6587\7ec6\9ed1,sans-serif}[data-eb-6a8f3296] .rgft_5d220f64.rgft_26b3f3ee{font-size:calc(2rem * v | 2026-01-13T08:48:41 |
https://docs.suprsend.com/reference/cli-profile-list | List Profile - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Profile List Profile Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Profile List Profile OpenAI Open in ChatGPT List all configured SuprSend CLI profiles and their current status. OpenAI Open in ChatGPT List all configured profiles in your local configuration file. You can also check and edit profiles from config file. Default file path is $HOME/.suprsend.yaml . Syntax Copy Ask AI suprsend profile list Was this page helpful? Yes No Suggest edits Raise issue Previous Modify Profile Update an existing profile in the SuprSend CLI configuration Next ⌘ I x github linkedin youtube Powered by On this page Syntax | 2026-01-13T08:48:41 |
https://dev.to/t/newparents | Newparents - 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 # newparents Follow Hide For those new to parenting, from pregnancy to the first year. Create Post 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 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:48:41 |
https://parenting.forem.com/privacy#12-contact-us | Privacy Policy - Parenting 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 Parenting Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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 Parenting — 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. 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 . Parenting © 2016 - 2026. Navigating the chaos and joy of parenting. Log in Create account | 2026-01-13T08:48:41 |
https://docs.python.org/3/license.html#strtod-and-dtoa | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:48:41 |
https://dev.to/szabgab/perl-weekly-594-advent-calendar-31ao | Perl Weekly #594 - Advent Calendar - 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 Gabor Szabo Posted on Dec 12, 2022 • Originally published at perlweekly.com Perl Weekly #594 - Advent Calendar # perl # news # programming perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Originally published at Perl Weekly 594 Hi there, The Advent Calendar celebration begins with the start of December . For all Perl fans, we have Perl Advent Calendar 2022 , thanks to the hard work of Olaf Alders and his team. I am sure you have checked out the amazing daily source of fun. As of today, we have got through 12 days . Do you have any favourite so far? Well I do have mine. To me the best part is the festive flavour in every article. I find it amusing and fun to read the story. I have contributed in the past but never got around to add the spice. I would blame the lack of background knowledge. This year's calendar started with Toby Inkster creation Silent Mite . What a cool way to start the calendar. If you look at closely all the contributions so far, you would notice a fresh air with lots of positive energy. One name stands out very prominently this year is Thibault DUPONCHELLE . His first contribution, Santa is on GitHub was a nice way to begin the journey. Then found a gem from a very dear friend of mine, Julien Fiegehenn talking about good old friend CGI . In fact, I have seen him presenting the subject northpole.cgi at the Perl Conference . I found another piece of work by Thibault DUPONCHELLE about MongoDB . I found the Day 5 contribution Catching dreams is worth checking, if you want to explore MongoDB . If I am not mistaken then few years ago, Dave Cross shared his creation SVG::ChristmasTree in Perl Advent Calendar . I was happy to see it part of this year calendar too, not directly though. Day 8 started with A Perlmas Tree by Maximilian Lika . I found Day 11 contribution very technical dealing with signal ALRM . Not an easy subject to discuss in the Advent Calendar in my humble opinion. Thanks OODLER for the fine contribution, Wake up! Time to open presents! . If you are still looking for more Advent Calendar theme fun then I would highly recommend, The Weekly Challenge Advent Calendar . Like in the past, this year also, it has contributions from Team PWC hand picked by me. I am sure you would find it interesting. I am working on something that I would love to be part of this year Perl Advent Calendar . Hopefully it would be ready soon. Well I am also working on something similar for Raku Advent Calendar . It would be an achievement if I can get both done on time. Please wish me luck. Enjoy rest of the newsletter. -- Your editor: Mohammad S. Anwar. Announcements This Week in PSC (090) More regular updates by PSC team, Good bye PrePAN What a shame we lost PrePAN. It is too late to do anything, unfortunately. Articles Kephra: goto (last) edit A very interesting topic about goto and very engaging article worth checking. RedBlack tree mockup in Corinna Yves Orton wanted to see a complex class implemented in Corinna, so I mocked up a red-black tree. Web AoC 2022/3 - Misplaced supplies and where to find them AoC 2022/4 - Poor planning AoC 2022/5 - Insane crane AoC 2022/6 - Canned diversity AoC 2022/7 - ENOSPC - no space left on device Advent Calendar Silent Mite MooseX::Getopt saves Christmas Santa is on GitHub northpole.cgi Catching dreams St. Nick's Reindeers Need H2O! The Sleigh odometer A Perlmas Tree What did Santa forget? The Christmas Time Machine Wake up! Time to open presents! The Weekly Challenge The Weekly Challenge by Mohammad Anwar will help you step out of your comfort-zone. You can even win prize money of $50 Amazon voucher by participating in the weekly challenge. We pick one winner at the end of the month from among all of the contributors during the month. The monthly prize is kindly sponsored by Peter Sergeant of PerlCareers . The Weekly Challenge - 195 Welcome to a new week with a couple of fun tasks: "Special Integers" and "Most Frequent Even". If you are new to the weekly challenge, why not join us and have fun every week? For more information, please read the FAQ . RECAP - The Weekly Challenge - 194 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Digital Clock" and "Frequency Equalizer" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. The Weekly Challenge Advent Calendar 2022 Digital Frequalizer Lots of Raku magic shared as every week. Plenty to keep you busy. Thanks for sharing. Bag Time! I noticed sharp observations about the task. Good catch. Well done and keep it up great work. Freq Out, Man! Deep task analysis is not to be missed. Highly recommended. PWC194 - Digital Clock Flavio makes the task simple to follow. What a treat, thank you. PWC194 - Frequency Equalizer The frank and open discussion is the highlight. Plenty to keep up busy every week. iffy solutions James introduced new term to me, IIFE. Thanks for your contributions every week. Digital Clock and Frequency Equalizer Great demo of Perl and Raku with such an ease. Thanks for sharing knowledge with us. regular expressions everywhere! Are you regex fan? If yes then this is for you. Thank you. Perl Weekly Challenge 194 Once again we got the demo of PDL this week. Thanks for sharing the knowledge with us. Completing the time and levelling the letters Compact collection of various test cases. This makes the logic easy to follow. Keep it up great work. Digital Equaliser Advise and suggestions in the blog post is worth checking. Thanks for sharing knowledge with us. Digital frequency For both Perl and Python fans, have fun. Well done. PWC 194 Blog post showing the porting of Perl solution to Raku and Julia. Plenty to learn every week. Rakudo 2022.49 ReleaseMas Again Weekly collections NICEPERL's lists Great CPAN modules released last week ; MetaCPAN weekly report ; StackOverflow Perl report . The corner of Gabor A couple of entries sneaked in by Gabor. How to create cpanfile by "perl Makefile.PL"? An interesting possibility to se cpanfile with Makefile.PL Canadian Municipal GitHub Rankings While looking for Open source projects I bumped into an interesting listing of government-related GitHub organizations. Jumphost - Pull Switch Configs with Perl How to install cpanm using HTTP::Tiny and Perl oneliner? I am not sure it is really needed as Strawberry Perl for Windows, the only place where you don't have built in curl already comes with cpanm preinstalled. But nevertheless an interesting possibility. Day 9: CI for Mojo-UserAgent-Cached and Plack-Middleware-Greylist 63 Corporations that share Open Source code Since I posted this, I added a lot more corporations. Thanks to contribution of Dean Hamstead as well. Perl Jobs by Perl Careers Bold, beautiful, and… brainy? Senior Perl roles in Malaysia, Dubai and Malta Our client provides online trading services and with offices in Dubai, Malta, and Malaysia, they’ve got the global reach that may provide the challenge you’re looking for. Their staff count has increased 600 percent in the last four years, and growth is still on the upswing. They know that a seasoned Perl pro is just what their team needs as they expand, and that’s where you come in. Perl to Node Cross-training? Yes Please! UK Remote Perl Role The client is interested in anyone with experience building web apps in Perl, using one of the major Perl frameworks. If you’re a crack-hand with Catalyst, a Mojolicious master, or a distinguished Dancer, they want you. You’ll be deploying apps your work to AWS, so experience would be handy, and the company’s big on testing, so they’d like you to know your way around Test::More. C, C++, and Perl Software Engineers, Let’s Keep the Internet Safe A leading digital safeguarding solutions provider is looking for a software engineer experienced in C, C++, or Perl. You’ll have strong Linux knowledge and a methodical approach to problem solving that you use to investigate, replicate, and address customer issues. Your keen understanding of firewalls, proxies, Iptables, Squid, VPNs/IPSec and HTTP(S) will be key to your success at this company. Perl Developer and Business Owner? Remote Perl role in UK & EU Our clients run a job search engine that has grown from two friends with an idea to a site that receives more than 10 million visits per month. They're looking for a Perl pro with at least three years of experience with high-volume and high-traffic apps and sites, a solid understanding of Object-Oriented Perl (perks if that knowledge includes Moose), SQL/MySQL and DBIx::Class. You joined the Perl Weekly to get weekly e-mails about the Perl programming language and related topics. Want to see more? See the archives of all the issues. Not yet subscribed to the newsletter? Join us free of charge ! (C) Copyright Gabor Szabo The articles are copyright the respective authors. perl-weekly (153 Part Series) 1 Perl 🐪 Weekly #591 - Less than 50% use CI 2 Perl 🐪 Weekly #592 - Perl Blogging? ... 149 more parts... 3 Perl Weekly #593 - Perl on DEV.to 4 Perl Weekly #594 - Advent Calendar 5 Perl Weekly #595 - Happy Hanukkah - Merry Christmas 6 Perl Weekly #596 - New Year Resolution 7 Perl Weekly #597 - Happy New Year! 8 Perl Weekly #598 - TIOBE and Perl 9 Perl Weekly #599 - Open Source Development Course for Perl developers 10 Perl Weekly #600 - 600th edition and still going ... 11 Perl Weekly #601 - The bad apple 12 Perl Weekly #602 - RIP Ben Davies 13 Perl Weekly #603 - Generating prejudice 14 Perl Weekly #604 - P in LAMP? 15 Perl Weekly #605 - Trying to save a disappearing language 16 Perl Weekly #606 - First Love Perl? 17 Perl Weekly #607 - The Perl Planetarium 18 Perl Weekly #608 - Love You Perl!!! 19 Perl Weekly #609 - Open Source and your workplace 20 Perl Weekly #610 - Perl and TPF 21 Perl Weekly #611 - Test coverage on CPAN Digger 22 Perl Weekly #612 - Coming Soon! 23 Perl Weekly #613 - CPAN Dashboard 24 Perl Weekly #614 - Why not Perl? 25 Perl Weekly #615 - PTS - Perl Toolchain Summit 26 Perl Weekly #616 - Camel in India 27 Perl Weekly #617 - The business risks of using CPAN 28 Perl Weekly #618 - Conference Season? 29 Perl Weekly #619 - Maintenance of CPAN modules 30 Perl Weekly #620 - Abandoned modules? 31 Perl Weekly #621 - OSDC - Open Source Development Club 32 Perl Weekly #622 - Perl v5.38 coming soon ... 33 Perl Weekly #623 - perl v5.38.0 was released 34 Perl Weekly #624 - TPRC 2023 35 Perl Weekly #625 - Mohammad Sajid Anwar the new White Camel 36 Perl Weekly #626 - What is Oshun? 37 Perl Weekly #627 - Rust is fun 38 Perl Weekly #628 - Have you tried Perl v5.38? 39 Perl Weekly #630 - Vacation time 40 Perl Weekly #631 - The Koha conference ended 41 Perl Weekly #632 - New school-year 42 Perl Weekly #633 - Remember 9/11? 43 Perl Weekly #634 - Perl v5.39.1 44 Perl Weekly #635 - Is there a Perl developer shortage? 45 Perl Weekly #636 - Happy Birthday Larry 46 Perl Weekly #637 - We are in shock 47 Perl Weekly #638 - Dancing Perl? 48 Perl Weekly #639 - Standards of Conduct 49 Perl Weekly #640 - Perl Workshop 50 Perl Weekly #641 - Advent Calendars 51 Perl Weekly #642 - Perl and PAUSE 52 Perl Weekly #643 - My birthday wishes 53 Perl Weekly #644 - Perl Sponsor? 54 Perl Weekly #645 - Advent Calendars 55 Perl Weekly #646 - Festive Season 56 Perl Weekly #647 - Happy birthday Perl! 🎂 57 Perl Weekly #648 - Merry Christmas 58 Perl Weekly #649 - Happier New Year! 59 Perl Weekly #650 - Perl in 2024 60 Perl Weekly #651 - Watch the release of Perl live! 61 Perl Weekly #653 - Perl & Raku Conference 2024 to Host a Science Track! 62 Perl Weekly #654 - Perl and FOSDEM 63 Perl Weekly #655 - What's new in Perl and on CPAN? What's new in Italy? 64 Perl Weekly #656 - Perl Conference 65 Perl Weekly #657 - Perl Toolchain Summit in 2024 66 Perl Weekly #658 - Perl // Outreachy 67 Perl Weekly #659 - The big chess game 68 Perl Weekly #660 - What's new ... 69 Perl Weekly #661 - Perl Toolchain Summit 2024 70 Perl Weekly #662 - TPRC in Las Vegas 71 Perl Weekly #663 - No idea 72 Perl Weekly #664 - German Perl Workshop 73 Perl Weekly #665 - How to get better at Perl? 74 Perl Weekly #666 - LPW 2024 75 Perl Weekly #667 - Call for papers and sponsors for LPW 2024 76 Perl Weekly #668 - Perl v5.40 77 Perl Weekly #669 - How Time Machine works 78 Perl Weekly #670 - Conference Season ... 79 Perl Weekly #671 - In-person and online events 80 Perl Weekly #672 - It's time ... 81 Perl Weekly #673 - One week till the Perl and Raku conference 82 Perl Weekly #676 - Perl and OpenAI 83 Perl Weekly #677 - Reports from TPRC 2024 84 Perl Weekly #678 - Perl Steering Council 85 Perl Weekly #679 - Perl is like... 86 Perl Weekly #680 - Advent Calendar 87 Perl Weekly #681 - GitHub and Perl 88 Perl Weekly #682 - Perl and CPAN 89 Perl Weekly #683 - An uptick in activity on Reddit? 90 Perl Weekly #685 - LPRW 2024 Schedule Now Available 91 Perl Weekly #686 - Perl Conference 92 Perl Weekly #687 - On secrets 93 Perl Weekly #688 - Perl and Hacktoberfest 94 Perl Weekly #689 - October 7 🎗️ 95 Perl Weekly #690 - London Perl & Raku Workshop 2024 96 Perl Weekly #692 - LPW 2024: Quick Report 97 Perl Weekly #693 - Advertising Perl 98 Perl Weekly #694 - LPW: Past, Present & Future 99 Perl Weekly #695 - Perl: Half of our life 100 Perl Weekly #696 - Perl 5 is Perl 101 Perl Weekly #697 - Advent Calendars 2024 102 Perl Weekly #698 - Perl v5.41.7 103 Perl 🐪 Weekly #699 - Happy birthday Perl 104 Perl 🐪 Weekly #700 - White Camel Award 2024 105 Perl 🐪 Weekly #701 - Happier New Year! 106 Perl 🐪 Weekly #702 - Perl Camel 107 Perl 🐪 Weekly #703 - Teach me some Perl! 108 Perl 🐪 Weekly #704 - Perl Podcast 109 Perl 🐪 Weekly #705 - Something is moving 110 Perl 🐪 Weekly #706 - Perl in 2025 111 Perl 🐪 Weekly #707 - Is it ethical? 112 Perl 🐪 Weekly #708 - Perl is growing... 113 Perl 🐪 Weekly #709 - GPRW and Perl Toolchain Summit 114 Perl 🐪 Weekly #710 - PPC - Perl Proposed Changes 115 Perl 🐪 Weekly #711 - Obfuscating Perl 116 Perl 🐪 Weekly #712 - RIP Zefram 117 Perl 🐪 Weekly #713 - Why do companies migrate away from Perl? 118 Perl 🐪 Weekly #714 - Munging Data? 119 Perl 🐪 Weekly #715 - Why do companies move away from Perl? 120 Perl 🐪 Weekly #716 - CVE in Perl 121 Perl 🐪 Weekly #717 - Happy Easter 122 Perl 🐪 Weekly #719 - How do you deal with the decline? 123 Perl 🐪 Weekly #720 - GPW 2025 124 Perl 🐪 Weekly #721 - Perl Roadmap 125 Perl 🐪 Weekly #723 - Perl Ad Server needs ads 126 Perl 🐪 Weekly #724 - Perl and XS 127 Perl 🐪 Weekly #725 - Perl podcasts? 128 Perl 🐪 Weekly #726 - Perl and ChatGPT 129 Perl 🐪 Weekly #727 - Which versions of Perl do you use? 130 Perl 🐪 Weekly #728 - Perl Conference 131 Perl 🐪 Weekly #729 - Videos from TPRC 132 Perl 🐪 Weekly #730 - RIP MST 133 Perl 🐪 Weekly #731 - Looking for a Perl event organizer 134 Perl 🐪 Weekly #732 - MetaCPAN Success Story 135 Perl 🐪 Weekly #733 - Perl using AI 136 Perl 🐪 Weekly #734 - CPAN Day 137 Perl 🐪 Weekly #735 - Perl-related events 138 Perl 🐪 Weekly #736 - NICEPERL 139 Perl 🐪 Weekly #737 - Perl oneliners 140 Perl 🐪 Weekly #739 - Announcing Dancer2 2.0.0 141 Perl 🐪 Weekly #741 - Money to TPRF 💰 142 Perl 🐪 Weekly #742 - Support TPRF 143 Perl 🐪 Weekly #743 - Writing Perl with LLMs 144 Perl 🐪 Weekly #744 - London Perl Workshop 2025 145 Perl 🐪 Weekly #745 - Perl IDE Survey 146 Perl 🐪 Weekly #746 - YAPC::Fukuoka 2025 🇯🇵 147 Perl 🐪 Weekly #748 - Perl v5.43.5 148 Perl 🐪 Weekly #749 - Design Patterns in Modern Perl 149 Perl 🐪 Weekly #750 - Perl Advent Calendar 2025 150 Perl 🐪 Weekly #751 - Open Source contributions 151 Perl 🐪 Weekly #752 - Marlin - OOP Framework 152 Perl 🐪 Weekly #753 - Happy New Year! 153 Perl 🐪 Weekly #754 - New Year Resolution Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Tib Tib Tib Follow 403 Forbidden Joined Nov 24, 2020 • Dec 12 '22 Dropdown menu Copy link Hide 🙏 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 Gabor Szabo Follow Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood. Location Israel Education HUJI - Hebrew University in Jerusalem, Israel; Fazekas in Budapest, Hungary Work CI, Automation, and DevOps Trainer and Consultant at Self Employed Joined Oct 11, 2017 More from Gabor Szabo Perl 🐪 Weekly #754 - New Year Resolution # perl # news # programming Perl 🐪 Weekly #753 - Happy New Year! # perl # news # programming Perl 🐪 Weekly #752 - Marlin - OOP Framework # perl # news # programming 💎 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:48:41 |
https://survivejs.com/books/ | SurviveJS - Books Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Books I have authored several books related to JavaScript and you can find them on this site. See below for more specific descriptions. SurviveJS – Webpack 5 In this book, I go through main features of webpack ↗ , a module bundler for JavaScript, and show how to compose your own configuration effectively. It doubles as a reference for common webpack techniques and I have included discussion considering alternatives. The book matches the current version of webpack. Read webpack book SurviveJS – Maintenance In this book co-authored with Artem Sapegin ↗ , I explore how to maintain and publish your JavaScript projects. Originally it was split off from the webpack book. The book is largely complete although I want to give it modernization pass to catch up with the latest developments in the space. Read maintenance book SurviveJS – React React book is where it all started and the webpack book was split up from this. The book is not up to date although it may be interesting to follow the book project while building it using some other technology or the latest React APIs. In other words the book could use an update and it is maintained on the site for historical purposes for now. Read React book Books Survivejs – Webpack 5 Survivejs – Maintenance Survivejs – React Conferences Future Frontend ↗ React Finland ↗ Feeling social? Subscribe to the mailing list ↗ Follow @survivejs on X ↗ Follow @survivejs on Bluesky ↗ Follow project on GitHub ↗ Contact me ↗ Subscribe to RSS About SurviveJS is maintained by Juho Vepsäläinen . You can find the site source at GitHub ↗ . | 2026-01-13T08:48:41 |
https://docs.suprsend.com/reference/cli-event-overview | Commands and Flags - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Event Commands and Flags Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Event Commands and Flags OpenAI Open in ChatGPT Reference for managing events in the SuprSend CLI. OpenAI Open in ChatGPT Events are used to trigger workflows in SuprSend. You can use CLI command to manage events and link schema definitions to them - list, push, pull. Syntax Copy Ask AI suprsend event [command] Commands Command Description event list List events in a workspace event push Push events from local directory or server to SuprSend workspace event pull Pull events from SuprSend to local directory or server Inherited Global Flags This command also supports Global Flags , such as: -s, --service-token – Service token for authentication (default: $SUPRSEND_SERVICE_TOKEN ) -v, --verbosity – Log level (debug, info, warn, error, fatal, panic) (default info ) --config – Config file path (default: $HOME/.suprsend.yaml ) -n, --no-color – Disable color output (default: $NO_COLOR ) Was this page helpful? Yes No Suggest edits Raise issue Previous List Events List all events in your workspace. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Commands Inherited Global Flags | 2026-01-13T08:48:41 |
https://docs.suprsend.com/reference/cli-sync | Sync Assets - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Sync Sync Assets Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Sync Sync Assets OpenAI Open in ChatGPT Merge assets from workspace to another workspace OpenAI Open in ChatGPT Clone assets between different workspaces. This command fetches assets from the source workspace, validates them, and pushes them to the destination workspace. Assets failing validation are not pushed to target workspace. Syntax Copy Ask AI suprsend sync [flags] Flags Flag Description Default -a, --assets string Assets to sync ( all , workflow , schema , event , category ) all -f, --from string Source workspace (required) staging -m, --mode string Mode to sync assets ( draft , live ) live -t, --to string Destination workspace (required) production -d, --directory string custom directory path to sync to locally save pulled assets suprsend -h, --help Show help for the command – Example Copy Ask AI # Sync all assets from staging to production suprsend sync # Sync all assets between custom workspaces suprsend sync --from dev-staging --to dev-production # Sync workflows from staging to production suprsend sync --assets workflow # Sync draft schemas from staging to production suprsend sync --assets schema --mode draft Was this page helpful? Yes No Suggest edits Raise issue Previous Commands and Flags Reference for managing workflows in the SuprSend CLI. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:41 |
https://docs.suprsend.com/reference/cli-profile-use | Use Profile - 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 Versioning Versioning and Support Policy CLI Changelog Getting Started with CLI CLI Overview BETA Quickstart Installation Authentication Enable Autocompletion Global Flags Profile Commands and Flags Add Profile Use Profile List Profile Modify Profile Remove Profile Sync Sync Assets Workflow Commands and Flags List Workflows Pull Workflows Push Workflows Enable Workflow Disable Workflow Schema Commands and Flags List Schemas Pull Schemas Push Schemas Commit Schema Generate Types Event Commands and Flags List Events Pull Events Push Events Preference Category Commands and Flags List Categories Pull Categories Push Categories Commit Categories List Category Translations Pull Category Translations Push Category Translations Translation Commands and Flags List Translations Pull Translations Push Translations Commit Translations Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Profile Use Profile Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Profile Use Profile OpenAI Open in ChatGPT Set the active profile to be used in all subsequent commands OpenAI Open in ChatGPT Syntax Copy Ask AI suprsend profile use [flags] Flags Flag Description Default -h, --help Show help for the command – --name string Profile name to set as active (required) – Example Copy Ask AI suprsend profile use --name default Was this page helpful? Yes No Suggest edits Raise issue Previous List Profile List all configured SuprSend CLI profiles and their current status. Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:41 |
https://dev.to/t/mentalgame | Mentalgame - 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 # mentalgame Follow Hide The psychological side of golf, including focus, confidence, and mindset Create Post 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 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:48:42 |
https://docs.sui.io/guides/developer/getting-started/next-steps | Next Steps | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Next Steps On this page Next Steps If you have followed the Getting Started path, you should be ready to continue your journey on Sui. This page details how to continue learning, additional resources, and ways to join the developer community. Click to open Verify "Getting Started" essentials To make sure you have everything you need, paste the following commands into a console in your local environment: $ sui --version $ sui client active-address $ sui client active-env $ sui client gas If all commands are successful, your console displays output similar to the following: sui [version_number]-[commit_hash] 0x6543...7241 testnet ╭── ─────────────┬────────────────────┬──────────────────╮ │ gasCoinId │ mistBalance (MIST) │ suiBalance (SUI) │ ├───────────────┼────────────────────┼──────────────────┤ │ 0x1e86...63b2 │ 5041161576 │ 5.04 │ ╰───────────────┴────────────────────┴──────────────────╯ If you receive an error, revisit the content relevant to the command that caused the error or lacked output. Command Successful if sui --version You installed Sui correctly. sui client active-address You have a Sui address that is currently active. sui client active-env You have set up a connection to Testnet that is currently active. sui client objects You address owns SUI for testing . Continue learning Check out the Counter example dApp to continue your learning and build a full-stack Sui app. Additional documentation The rest of the documentation on this site contains important concepts, guides, and examples for you to continue your Sui journey. There are also resources beyond this documentation that you can reference, as well as a large and growing community whose experience and knowledge you can leverage to get the most out of Sui. SDK documentation Mysten Labs, the company that initiated the creation of Sui, provides SDKs to interact with the network and associated assets. Visit the SDK docs to learn more. The Move Book Move is the language of smart contracts on Sui. The Move Book details the language. Connect with the Sui community Join the Sui Discord Join Suinami Riders on Telegram Checkout the Sui Developer Forum Follow @SuiFoundation on X Schedule office hours Sign up for 1:1 sessions to get developer support or advice from the Sui team. Awesome Sui The Awesome Sui repo is a curated list of developer tools and infrastructure projects within the Sui ecosystem. Upcoming hackathons Check out upcoming hackathon events to build applications alongside other developers. Developer newsletter Sign up for the Sui Developer Newsletter to receive hyperfocused content to help you build on Sui. Developer portal Visit the Sui Developer Portal to find links to courses, videos, and other learning resources. Edit this page Previous Connect a Frontend Next Sui Essentials Continue learning Additional documentation SDK documentation The Move Book Connect with the Sui community Schedule office hours Awesome Sui Upcoming hackathons Developer newsletter Developer portal © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:42 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.