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://golf.forem.com/privacy#8-supplemental-disclosures-for-california-residents | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/link | <link>: The External Resource Link element - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Reference Elements <link> Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) <link>: The External Resource Link element Baseline Widely available * This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015. * Some parts of this feature may have varying levels of support. Learn more See full compatibility Report feedback The <link> HTML element specifies relationships between the current document and an external resource. This element is most commonly used to link to stylesheets , but is also used to establish site icons (both "favicon" style icons and icons for the home screen and apps on mobile devices) among other things. In this article Try it Attributes Examples Technical summary Specifications Browser compatibility See also Try it <link href="/shared-assets/misc/link-element-example.css" rel="stylesheet" /> <p>This text will be red as defined in the external stylesheet.</p> <p style="color: blue"> The <code>style</code> attribute can override it, though. </p> To link an external stylesheet, you'd include a <link> element inside your <head> like this: html <link href="main.css" rel="stylesheet" /> This example provides the path to the stylesheet inside an href attribute and a rel attribute with a value of stylesheet . The rel stands for "relationship", and is one of the key features of the <link> element — the value denotes how the item being linked to is related to the containing document. There are a number of other common types you'll come across. For example, a link to the site's favicon: html <link rel="icon" href="favicon.ico" /> There are a number of other icon rel values, mainly used to indicate special icon types for use on various mobile platforms, e.g.: html <link rel="apple-touch-icon" sizes="114x114" href="apple-icon-114.png" type="image/png" /> The sizes attribute indicates the icon size, while the type contains the MIME type of the resource being linked. These provide useful hints to allow the browser to choose the most appropriate icon available. You can also provide a media type or query inside a media attribute; this resource will then only be loaded if the media condition is true. For example: html <link href="print.css" rel="stylesheet" media="print" /> <link href="mobile.css" rel="stylesheet" media="screen and (width <= 600px)" /> Some interesting new performance and security features have been added to the <link> element too. Take this example: html <link rel="preload" href="myFont.woff2" as="font" type="font/woff2" crossorigin="anonymous" /> A rel value of preload indicates that the browser should preload this resource (see rel="preload" for more details), with the as attribute indicating the specific class of content being fetched. The crossorigin attribute indicates whether the resource should be fetched with a CORS request. Other usage notes: A <link> element can occur either in the <head> or <body> element, depending on whether it has a link type that is body-ok . For example, the stylesheet link type is body-ok, and therefore <link rel="stylesheet"> is permitted in the body. However, this isn't a good practice to follow; it makes more sense to separate your <link> elements from your body content, putting them in the <head> . When using <link> to establish a favicon for a site, and your site uses a Content Security Policy (CSP) to enhance its security, the policy applies to the favicon. If you encounter problems with the favicon not loading, verify that the Content-Security-Policy header's img-src directive is not preventing access to it. The HTML and XHTML specifications define event handlers for the <link> element, but it is unclear how they would be used. Under XHTML 1.0, void elements such as <link> require a trailing slash: <link /> . WebTV supports the use of the value next for rel to preload the next page in a document series. Attributes This element includes the global attributes . as This attribute is required when rel="preload" has been set on the <link> element, optional when rel="modulepreload" has been set, and otherwise should not be used. It specifies the type of content being loaded by the <link> , which is necessary for request matching, application of correct content security policy , and setting of correct Accept request header. Furthermore, rel="preload" uses this as a signal for request prioritization. The table below lists the valid values for this attribute and the elements or resources they apply to. Value Applies To audio <audio> elements document <iframe> and <frame> elements embed <embed> elements fetch fetch, XHR Note: This value also requires <link> to contain the crossorigin attribute, see CORS-enabled fetches . font CSS @font-face Note: This value also requires <link> to contain the crossorigin attribute, see CORS-enabled fetches . image <img> and <picture> elements with srcset or imageset attributes, SVG <image> elements, CSS *-image rules object <object> elements script <script> elements, Worker importScripts style <link rel=stylesheet> elements, CSS @import track <track> elements video <video> elements worker Worker, SharedWorker blocking This attribute explicitly indicates that certain operations should be blocked until specific conditions are met. It must only be used when the rel attribute contains the expect or stylesheet keywords. With rel="expect" , it indicates that operations should be blocked until a specific DOM node has been parsed. With rel="stylesheet" , it indicates that operations should be blocked until an external stylesheet and its critical subresources have been fetched and applied to the document. The operations that are to be blocked must be a space-separated list of blocking tokens listed below. Currently there is only one token: render : The rendering of content on the screen is blocked. Note: Only link elements in the document's <head> can possibly block rendering. By default, a link element with rel="stylesheet" in the <head> blocks rendering when the browser discovers it during parsing. If such a link element is added dynamically via script, you must additionally set blocking = "render" for it to block rendering. crossorigin This enumerated attribute indicates whether CORS must be used when fetching the resource. CORS-enabled images can be reused in the <canvas> element without being tainted . The allowed values are: anonymous A cross-origin request (i.e., with an Origin HTTP header) is performed, but no credential is sent (i.e., no cookie, X.509 certificate, or HTTP Basic authentication). If the server does not give credentials to the origin site (by not setting the Access-Control-Allow-Origin HTTP header) the resource will be tainted and its usage restricted. use-credentials A cross-origin request (i.e., with an Origin HTTP header) is performed along with a credential sent (i.e., a cookie, certificate, and/or HTTP Basic authentication is performed). If the server does not give credentials to the origin site (through Access-Control-Allow-Credentials HTTP header), the resource will be tainted and its usage restricted. If the attribute is not present, the resource is fetched without a CORS request (i.e., without sending the Origin HTTP header), preventing its non-tainted usage. If invalid, it is handled as if the enumerated keyword anonymous was used. See CORS settings attributes for additional information. disabled For rel="stylesheet" only, the disabled Boolean attribute indicates whether the described stylesheet should be loaded and applied to the document. If disabled is specified in the HTML when it is loaded, the stylesheet will not be loaded during page load. Instead, the stylesheet will be loaded on-demand, if and when the disabled attribute is changed to false or removed. Setting the disabled property in the DOM causes the stylesheet to be removed from the document's Document.styleSheets list. fetchpriority Provides a hint of the relative priority to use when fetching a resource of a particular type. Allowed values: high Fetch the resource at a high priority relative to other resources of the same type. low Fetch the resource at a low priority relative to other resources of the same type. auto Don't set a preference for the fetch priority. This is the default. It is used if no value or an invalid value is set. href This attribute specifies the URL of the linked resource. A URL can be absolute or relative. hreflang This attribute indicates the language of the linked resource. It is purely advisory. Values should be valid BCP 47 language tags . Use this attribute only if the href attribute is present. imagesizes For rel="preload" and as="image" only, the imagesizes attribute has similar syntax and semantics as the sizes attribute that indicates to preload the appropriate resource used by an img element with corresponding values for its srcset and sizes attributes. imagesrcset For rel="preload" and as="image" only, the imagesrcset attribute has similar syntax and semantics as the srcset attribute that indicates to preload the appropriate resource used by an img element with corresponding values for its srcset and sizes attributes. integrity Contains inline metadata — a base64-encoded cryptographic hash of the resource (file) you're telling the browser to fetch. The browser can use this to verify that the fetched resource has been delivered without unexpected manipulation. The attribute must only be specified when the rel attribute is specified to stylesheet , preload , or modulepreload . See Subresource Integrity . media This attribute specifies the media that the linked resource applies to. Its value must be a media type / media query . This attribute is mainly useful when linking to external stylesheets — it allows the user agent to pick the best adapted one for the device it runs on. referrerpolicy A string indicating which referrer to use when fetching the resource: no-referrer means that the Referer header will not be sent. no-referrer-when-downgrade means that no Referer header will be sent when navigating to an origin without TLS (HTTPS). This is a user agent's default behavior, if no policy is otherwise specified. origin means that the referrer will be the origin of the page, which is roughly the scheme, the host, and the port. origin-when-cross-origin means that navigating to other origins will be limited to the scheme, the host, and the port, while navigating on the same origin will include the referrer's path. unsafe-url means that the referrer will include the origin and the path (but not the fragment, password, or username). This case is unsafe because it can leak origins and paths from TLS-protected resources to insecure origins. rel This attribute names a relationship of the linked document to the current document. The attribute must be a space-separated list of link type values . sizes This attribute defines the sizes of the icons for visual media contained in the resource. It must be present only if the rel contains a value of icon or a non-standard type such as Apple's apple-touch-icon . It may have the following values: any , meaning that the icon can be scaled to any size as it is in a vector format, like image/svg+xml . a white-space separated list of sizes, each in the format <width in pixels>x<height in pixels> or <width in pixels>X<height in pixels> . Each of these sizes must be contained in the resource. Note: Most icon formats are only able to store one single icon; therefore, most of the time, the sizes attribute contains only one entry. Microsoft's ICO format and Apple's ICNS format can store multiple icon sizes in a single file. ICO has better browser support, so you should use this format if cross-browser support is a concern. title The title attribute has special semantics on the <link> element. When used on a <link rel="stylesheet"> it defines a default or an alternate stylesheet . type This attribute is used to define the type of the content linked to. The value of the attribute should be a MIME type such as text/html , text/css , and so on. The common use of this attribute is to define the type of stylesheet being referenced (such as text/css ), but given that CSS is the only stylesheet language used on the web, not only is it possible to omit the type attribute, but is actually now recommended practice. It is also used on rel="preload" link types, to make sure the browser only downloads file types that it supports. Non-standard attributes target Deprecated Defines the frame or window name that has the defined linking relationship or that will show the rendering of any linked resource. Obsolete attributes charset Deprecated This attribute defines the character encoding of the linked resource. The value is a space- and/or comma-delimited list of character sets as defined in RFC 2045 . The default value is iso-8859-1 . Note: To produce the same effect as this obsolete attribute, use the Content-Type HTTP header on the linked resource. rev Deprecated The value of this attribute shows the relationship of the current document to the linked document, as defined by the href attribute. The attribute thus defines the reverse relationship compared to the value of the rel attribute. Link type values for the attribute are similar to the possible values for rel . Note: Instead of rev , you should use the rel attribute with the opposite link type value . For example, to establish the reverse link for made , specify author . Also, this attribute doesn't stand for "revision" and must not be used with a version number, even though many sites misuse it in this way. Examples Including a stylesheet To include a stylesheet in a page, use the following syntax: html <link href="style.css" rel="stylesheet" /> Providing alternative stylesheets You can also specify alternative style sheets . The user can choose which style sheet to use by choosing it from the View > Page Style menu. This provides a way for users to see multiple versions of a page. html <link href="default.css" rel="stylesheet" title="Default Style" /> <link href="fancy.css" rel="alternate stylesheet" title="Fancy" /> <link href="basic.css" rel="alternate stylesheet" title="Basic" /> Providing icons for different usage contexts You can include links to several icons on the same page, and the browser will choose which one works best for its particular context using the rel and sizes values as hints. html <!-- iPad Pro with high-resolution Retina display: --> <link rel="apple-touch-icon" sizes="167x167" href="/apple-touch-icon-167x167.png" /> <!-- 3x resolution iPhone: --> <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon-180x180.png" /> <!-- non-Retina iPad, iPad mini, etc.: --> <link rel="apple-touch-icon" sizes="152x152" href="/apple-touch-icon-152x152.png" /> <!-- 2x resolution iPhone and other devices: --> <link rel="apple-touch-icon" href="/apple-touch-icon-120x120.png" /> <!-- basic favicon --> <link rel="icon" href="/favicon.ico" /> For information about what sizes to choose for Apple icons, see Apple's documentation on configuring web applications and the referenced Apple human interface guidelines . Usually, it is sufficient to provide a large image, such as 192x192, and let the browser scale it down as needed, but you may want to provide images with different levels of detail for different sizes, as the Apple design guideline recommends. Providing smaller icons for lower resolutions also saves bandwidth. It may not be necessary to provide <link> elements at all. For example, browsers automatically request /favicon.ico from the root of a site, and Apple also automatically requests /apple-touch-icon-[size].png , /apple-touch-icon.png , etc. However, providing explicit links protects you against changes to these conventions. Conditionally loading resources with media queries You can provide a media type or query inside a media attribute; this resource will then only be loaded if the media condition is true. For example: html <link href="print.css" rel="stylesheet" media="print" /> <link href="mobile.css" rel="stylesheet" media="all" /> <link href="desktop.css" rel="stylesheet" media="screen and (width >= 600px)" /> <link href="highres.css" rel="stylesheet" media="screen and (resolution >= 300dpi)" /> Stylesheet load events You can determine when a style sheet has been loaded by watching for a load event to fire on it; similarly, you can detect if an error has occurred while processing a style sheet by watching for an error event: html <link rel="stylesheet" href="mystylesheet.css" id="my-stylesheet" /> js const stylesheet = document.getElementById("my-stylesheet"); stylesheet.onload = () => { // Do something interesting; the sheet has been loaded }; stylesheet.onerror = () => { console.log("An error occurred loading the stylesheet!"); }; Note: The load event fires once the stylesheet and all of its imported content has been loaded and parsed, and immediately before the styles start being applied to the content. Preload examples You can find a number of <link rel="preload"> examples in Preloading content with rel="preload" . Blocking rendering till a resource is fetched You can include render token inside a blocking attribute; the rendering of the page will be blocked till the resource and its critical subresources are fetched and applied to the document. For example: html <link blocking="render" rel="stylesheet" href="example.css" crossorigin /> Technical summary Content categories Metadata content. If itemprop is present: Flow content and phrasing content . Permitted content None; it is a void element . Tag omission Must have a start tag and must not have an end tag. Permitted parents Any element that accepts metadata elements. If itemprop is present: any element that accepts phrasing content . Implicit ARIA role link with href attribute Permitted ARIA roles No role permitted DOM interface HTMLLinkElement Specifications Specification HTML # the-link-element Browser compatibility Enable JavaScript to view this browser compatibility table. See also Link HTTP header Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 30, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:42 |
https://reactjs.org/community/support.html#stack-overflow | React Community – React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog GET INVOLVED Community React Conferences React Meetups React Videos Meet the Team Docs Contributors Translations Acknowledgements Versioning Policy Is this page useful? Community React Community React has a community of millions of developers. On this page we’ve listed some React-related communities that you can be a part of; see the other pages in this section for additional online and in-person learning materials. Code of Conduct Before participating in React’s communities, please read our Code of Conduct. We have adopted the Contributor Covenant and we expect that all community members adhere to the guidelines within. Stack Overflow Stack Overflow is a popular forum to ask code-level questions or if you’re stuck with a specific error. Read through the existing questions tagged with reactjs or ask your own ! Popular Discussion Forums There are many online forums which are a great place for discussion about best practices and application architecture as well as the future of React. If you have an answerable code-level question, Stack Overflow is usually a better fit. Each community consists of many thousands of React users. DEV’s React community Hashnode’s React community Reactiflux online chat Reddit’s React community News For the latest news about React, follow @reactjs on Twitter , @react.dev on Bluesky and the official React blog on this website. Next React Conferences Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms On this page Overview Code of Conduct Stack Overflow Popular Discussion Forums News | 2026-01-13T08:48:42 |
https://golf.forem.com/youtube_golf/golfcom-warming-up-with-jon-rahm-and-tyrrell-hatton-1m4l | Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton - Golf 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 Golf Forem 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 YouTube Golf Posted on Jul 10, 2025 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame Jon Rahm and Tyrrell Hatton team up on GOLF.com’s Warming Up series, showing why they’re golf soulmates both on and off the course. They share plenty of laughs—Hatton calls Rahm a “big teddy bear” despite his fierce on-course look, while Rahm insists Hatton is “one of the funniest people you’ll ever meet.” Beyond the jokes, they dive into their game-day mindsets: Rahm says he’s “irrationally positive,” whereas Hatton warns that too much positivity can drain you. Their chemistry and contrasting approaches make this rare two-player interview a must-watch for golf fans. 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 YouTube Golf Follow Joined Jun 22, 2025 More from YouTube Golf No Laying Up Podcast: Everyone Only: The Gimme Golf Club Origin Story | NLU Pod, Ep 1033 # golf # golfpodcasts # golfyoutube # localgolf Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service # pgatour # historyofgolf # golfyoutube # golfmedia Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals # coursereviews # golfdestinations # localgolf # golfyoutube 💎 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://golf.forem.com/t/rydercup | Rydercup - Golf 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 Golf Forem Close # rydercup Follow Hide The biennial clash between USA and Europe Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Hindsight at Bethpage: The Principles Keegan Looked Past Ben Halpern Ben Halpern Ben Halpern Follow Oct 3 '25 Hindsight at Bethpage: The Principles Keegan Looked Past # pgatour # rydercup # coursearchitecture # coursestrategy 11 reactions Comments Add Comment 3 min read Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#a-provide-our-services | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://golf.forem.com/new/mentalgame | New Post - Golf 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 Golf Forem Close Join the Golf Forem Golf Forem is a community of 3,676,891 amazing golfers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Golf Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://docs.suprsend.com/docs/node-trigger-workflow-from-api | Trigger Workflow from API - 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 Python SDK Node.js SDK Integrate Node SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Java SDK Go SDK SuprSend Client SDK 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 Node.js SDK Trigger Workflow from API Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Node.js SDK Trigger Workflow from API OpenAI Open in ChatGPT Learn how to trigger workflows using direct workflow API, with code snippets and examples. OpenAI Open in ChatGPT It is a unified API to trigger workflow and doesn’t require user creation before hand to trigger notification. Recommended for platforms transitioning their existing notifications to SuprSend. If you are using our frontend SDKs to configure notifications and passing events and user properties from third-party data platforms like Segment, then event-based trigger would be a better choice. 📘 Available in SDK version >= 1.10.0 Payload Schema Once your request is accepted, you can check the status of your request in the SuprSend Logs . Sample Payload Response Copy Ask AI const { Suprsend , WorkflowTriggerRequest } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "_workspace_key_" , "_workspace_secret_" ); // Prepare workflow payload const body = { "workflow" : "_workflow_slug_" , "actor" : { "distinct_id" : "0fxxx8f74-xxxx-41c5-8752-xxxcb6911fb08" , "name" : "actor_1" , "$skip_create" : true }, "recipients" : [ // notify user { "distinct_id" : "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09" , "$email" : [ " [email protected] " ], "name" : "recipient_1" , "$preferred_language" : "en" , "$timezone" : "America/New_York" , "$skip_create" : true }, // notify object { "object_type" : "teams" , "id" : "finance" , "$skip_create" : true } ], "data" : { "first_name" : "User" , "invoice_amount" : "$5000" , "invoice_id" : "Invoice-1234" } }; // Create workflow instance const w1 = new WorkflowTriggerRequest ( body , { tenant_id: "tenant_id1" , idempotency_key: "_unique_identifier_of_the_request_" }); // Trigger workflow const response = supr_client . workflows . trigger ( w1 ); response . then ( res => console . log ( "response" , res )); To prevent automatic creation of an actor, or recipient (user/object) in SuprSend (the case where they already exist in your system), you can use the "$skip_create": true flag. This can be applied inside the actor, individual user recipient objects, or object recipient objects. Property Type Description workflow string Slug of the designed workflow on the SuprSend dashboard. You’ll get the slug from workflow settings. recipients array of string / array of objects List of users who need to be notified. You can add up to 100 recipients in a workflow trigger. You can either pass recipients as an array of distinct_ID (if the user is pre-synced in the SuprSend database) or define recipient information inline . actor (Optional) string / object Includes distinct_id and properties of the user who performed the action. You can use it for cross-user notifications where you need to include actor properties in the notification template. Actor properties can be added as $actor.<prop> . data object Variable data required to render dynamic template content or workflow properties such as dynamic delay or channel override in the send node. tenant_id (Optional) string Trigger workflow for a specific tenant/brand. idempotency_key (Optional) string Unique identifier of the request. We’ll be returning idempotency_key in our outbound webhook response . You can use it to map notification statuses and replies in your system. recipients[].$preferred_language string To set the recipient’s preferred language. This is to support localization in notification content. You can pass the language in ISO 639-1 2-letter format. Refer to all language codes here . recipients[].$timezone string To set the recipient’s timezone. Used to send notifications in the user’s local timezone. You can pass the timezone in IANA (TZ identifier) format. Sending notification to Multiple Users Recipients in workflow call is an array of distinct_ids or recipient objects. You can pass up to 100 recipients in a single workflow trigger. SuprSend will internally convert it into multiple workflow triggers, one for each recipient in the array. json Copy Ask AI "recipients" : [ "distinct_id1" , "distinct_id2" ] ---- OR ------ "recipients" : [ { "distinct_id" : "id1" , "$email" :[ " [email protected] " ], "name" : "recipient_1" }, { "distinct_id" : "id1" , "$email" :[ " [email protected] " ], "name" : "recipient_2" } ] Use lists to broadcast to a large list of users: We recommend you to use lists and broadcast to send notifications to a user list larger than 1000 users. This approach allows bulk processing, resulting in significantly faster delivery compared to individual workflow calls. Sending individual workflows to a large set of users may introduce delays in your notification queue. Identifying Recipients Inline One of the benefits of using direct workflow trigger is that you can identify recipients inline. You can include recipient channel information, their channel preferences, and their user properties along with the workflow trigger. Upon triggering the workflow, the recipient will be automatically created in the SuprSend database in the background. This facilitates dynamic synchronization of your user data within SuprSend and eliminates the need for any migration efforts on your end to start sending notifications from SuprSend. You can also use recipient properties in your template as $recipient.<property> . This is how the complete recipient object with look like json Copy Ask AI "recipients" : [{ "distinct_id" : "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09" , "$email" :[ " [email protected] " ], // email communication channel "$sms" :[ "+15555555555" ], // sms communication channel "$channels" :[ "email" , "inbox" ], "$preferred_language" : "en" , "$timezone" : "America/New_York" , "custom_prop1" : "value_1" , // custom property "custom_prop2" : "value_2" , // custom property }] Property Type Description distinct_id string Unique identifier of the user to be notified. communication channels ( $email , $sms , etc.) array of string / objects The communication channel info provided will be updated in the user profile in the background. For this workflow, only the specified channel values for this recipient will be used for sending notifications instead of all channel values present in the user profile. $channels array of string By default, notifications will be sent to all channels defined in the workflow delivery nodes. However, if a user has a specific channel preference for a notification (e.g. they only want to receive payment reminders via email), you can include that preference in the workflow payload. This ensures notifications are sent only to the channels specified here. Supported channels: email, sms, whatsapp, androidpush, iospush, slack, webpush, ms_teams .You can always use our in-built preference APIs to maintain user notification preferences. Preferences defined within SuprSend will automatically apply with workflow triggers. $preferred_language string Sets the recipient’s preferred language to support localization in notification content. You can pass the language in ISO 639-1 2-letter format. Refer to all language codes here . $timezone string Sets the recipient’s timezone to send notifications in the user’s local timezone. You can pass the timezone in IANA (TZ identifier) format. * object You can pass other user properties to render dynamic template content. These properties will also be set in the user profile and can be used in the template as $recipient.<property> . Add user communication channel json Copy Ask AI "$email" :[ " [email protected] " ], "$whatsapp" :[ "+15555555555" ], "$sms" :[ "+15555555555" ], "$androidpush" : [{ "token" : "__android_push_token__" , "provider" : "fcm" , "device_id" : "" }], "$iospush" :[{ "token" : "__ios_push_token__" , "provider" : "apns" , "device_id" : "" }], // slack using email "$slack" : [{ "email" : " [email protected] " , "access_token" : "xoxb-XXXXXXXX" }] // slack using member_id "$slack" : [{ "user_id" : "U/WXXXXXXXX" , "access_token" : "xoxb-XXXXXX" }] // slack channel "$slack" : [{ "channel" : "CXXXXXXXX" , "access_token" : "xoxb-XXXXXX" }] // slack incoming webhook "$slack" : [{ "incoming_webhook" : { "url" : "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" } }] // MS teams user or channel using conversation_id "$ms_teams" : [{ "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "conversation_id" : "19:c1524d7c-a06f-456f-8abe-xxxx" }] // MS teams user using user_id "$ms_teams" : [{ "tenant_id" : "c1981ab2-9aaf-xxxx-xxxx" , "service_url" : "https://smba.trafficmanager.net/amer" , "user_id" : "29:1nsLcmJ2RKtYH6Cxxxx-xxxx" }] // MS teams incoming webhook "$ms_teams" : [{ "incoming_webhook" : { "url" : "https://wnk1z.webhook.office.com/webhookb2/XXXXXXXXX" } }] Sending cross-user notifications In scenarios where you need to notify a group of users based on another user’s action, such as sending a notification to the document owner when someone comments on it, you can specify the actor in your workflow call. This allows you to use actor’s name or other properties in your notification template. Actor properties can be included in the template as $actor.<property> . text Copy Ask AI //handlebar template Hi { {$recipient.name }}, { {$actor.name }} added { {length comments }} new comments on the { {doc_name }}. // rendered content with Sample Data Hi recipient_ 1 , actor_ 1 added 2 new comments on the annual IT report. Sample Workflow Body Copy Ask AI { "workflow" : "new_comment" , "actor" : { "distinct_id" : "0fxxx8f74-xxxx-41c5-8752-xxxcb6911fb08" , "name" : "actor_1" }, "recipients" : [ { "distinct_id" : "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09" , "$email" : [ " [email protected] " ], "name" : "recipient_1" } ], "data" :{ "doc_name" : "annual IT report" , "date" : "2024-01-01" , "comments" : [ "change the date" , "rest looks good" ] } } Sending notification to anonymous user You can send notifications to anonymous users by passing "is_transient": true in your recipient object. This approach is recommended for scenarios where you need to send notifications to unregistered users without creating them in the SuprSend platform. The same way, you can pass "is_transient": true in your actor object to use actor properties in template without creating user profile. Request Copy Ask AI const workflow_payload = { "workflow" : "_workflow_slug_" , "actor" : { "is_transient" : true , // for anonymous actor "name" : "actor_1" }, "recipients" : [ { "is_transient" : true , // for anonymous recipient "$email" : [ " [email protected] " ], "name" : "recipient_1" } ], "data" : { "first_name" : "User" , "invoice_amount" : "$5000" , "invoice_id" : "Invoice-1234" } } Multi-tenant notifications For cases where you want to send notifications to your enterprise customers end users, pass the tenant_id in your workflow instance. You can use this to dynamically manage tenant level notification customizations . This includes the ability to customize template design or content and route notifications via tenant vendors. Request Copy Ask AI const workflow = new WorkflowTriggerRequest ( workflow_body , { tenant_id: "tenant_id1" }) Idempotent requests SuprSend supports idempotency to ensure that requests can be retried safely without duplicate processing. If Suprsend receives and processes a request with an idempotency_key, it will skip processing requests with same idempotency_key for next 24 hours. Idempotency key should be uniquely generated for each request (max 255 characters allowed). Spaces in start and end of the key will be trimmed. Here are some common approaches for generating idempotency keys: Generate a random UUID for each request. Construct the idempotency key by combining relevant information about the request . This can include parameters, identifiers, or specific contextual details that are meaningful within your application. e.g., you could concatenate the user ID, action, and timestamp to form an idempotency key like user147-new-comment-1687437670 Request-specific Identifier : If your request already contains a unique identifier, such as an order ID or a job ID, you can use that identifier directly as the idempotency key. javascript Copy Ask AI const workflow = new WorkflowTriggerRequest ( workflow_body , { idempotency_key: "_unique_request_identifier" }) Bulk API for triggering multiple workflows Bulk API allows you to send multiple workflow requests in a single call. Use .append() and workflows.bulk_trigger_instance() to add however-many-records to call in bulk. Request Response Copy Ask AI const { Suprsend , WorkflowTriggerRequest } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "_workspace_key_" , "_workspace_secret_" ); // workflow1 instance const wf1 = new WorkflowTriggerRequest ( wf_body1 , { tenant_id: "tenant_id1" , idempotency_key: "_unique_identifier_of_the_request_" }) // workflow2 instance const wf2 = new WorkflowTriggerRequest ( body2 ) // create bulk instance const bulk_ins = supr_client . workflows . bulk_trigger_instance () // add workflows instances to bulk instance bulk_ins . append ( wf1 , wf2 ) // trigger workflows const response = bulk_ins . trigger (); response . then ( res => console . log ( "response" , res )); Add attachment (in email) To add one or more attachments to a notification (viz. Email), call wf_instance.add_attachment() for each file with local path or remote attachment url. Ensure that file path is valid, and public(for remote url) otherwise it will raise error. Request Copy Ask AI const wf_instance = new WorkflowTriggerRequest ( wf_body ); wf_instance . add_attachment ( "/home/user/billing.pdf" ); wf_instance . add_attachment ( "https://www.adobe.com/sample_file.pdf" ); A single workflow instance size (including attachment) must not exceed 800KB (800 x 1024 bytes). Dynamic workflow trigger You can trigger workflow from node SDK by using supr_client.trigger_workflow method. Import Workflow class before calling this method. Once your request is accepted, you can check the status of your request in the SuprSend Logs section. Request Response Copy Ask AI const { Workflow } = require ( "@suprsend/node-sdk" ) // Prepare Workflow body const workflow_body = { "name" : "workflow_name" , "template" : "template_slug" , "notification_category" : "notification_category" , //notification category transactional/promotional/system "delay" : "time_delay" , // time delay after which the first notification will be sent "trigger_at" : "date string in ISO 8601" , // to trigger scheduled notifications "users" : [ { "distinct_id" : "distinct_id" , // unique identifier of the user // if $channels is present, communication will be triggered on mentioned channels only. // "$channels": ["email"], // User communication channel can be added as [optional]: // "$email":[" [email protected] "], // "$whatsapp":["+15555555555"], // "$sms":["+15555555555"], // "$androidpush": [{"token": "__android_push_token__", "provider": "fcm", "device_id": ""}], // "$iospush":[{"token": "__ios_push_token__", "provider": "apns", "device_id": ""}], // "$slack": { //"email": " [email protected] ", //"access_token": "xoxb-XXXXXXXX" //} --- slack using email // "$slack": { // "user_id": "U/WXXXXXXXX", // "access_token": "xoxb-XXXXXX" //} --- slack using member_id //"$slack": { //"channel": "CXXXXXXXX", //"access_token": "xoxb-XXXXXX" //} --- slack channel //"$slack": { //"incoming_webhook": { //"url": "https://hooks.slack.com/services/TXXXX/BXXXX/XXXXXXX" //} //} --- slack incoming webhook // "$ms_teams": { //"tenant_id": "c1981ab2-9aaf-xxxx-xxxx", //"service_url": "https://smba.trafficmanager.net/amer", //"conversation_id": "19:c1524d7c-a06f-456f-8abe-xxxx" //} --- MS teams user or channel using conversation_id // "$ms_teams": { //"tenant_id": "c1981ab2-9aaf-xxxx-xxxx", //"service_url": "https://smba.trafficmanager.net/amer", //"user_id": "29:1nsLcmJ2RKtYH6Cxxxx-xxxx" //} --- MS teams user using user_id // "$ms_teams": { // "incoming_webhook": { // "url": "https://wnk1z.webhook.office.com/webhookb2/XXXXXXXXX" // } //} --- MS teams incoming webhook } ], // delivery instruction [optional]. how should notifications be sent, and whats the success metric "delivery" : { "smart" : < boolean_value > , "success": "success_metric", "time_to_live": "TTL duration", // will be applicable for smart = TRUE "mandatory_channels": [] // list of mandatory channels e.g ["email"], will be applicable for smart = TRUE }, // data can be any json "data": { "key" : "value" , "nested_key" : { "nested_key1" : "some_value_1" , "nested_key2" : { "nested_key3" : "some_value_3" , }, } } } const wf = new Workflow(workflow_body, { tenant_id = "default" , idempotency_key = "__uniq_request_id__" } ) // Trigger workflow const response = supr_client.trigger_workflow(wf); // returns promise response.then((res) => console.log("response", res)); For configuring a workflow from backend, you can pass following properties in your method Parameter Description Format Obligation name It is the unique name of the workflow. You can see workflow-related analytics on the workflow page (how many notifications were sent, delivered, clicked, or interacted). The workflow name should be easily identifiable for your reference at a later stage. text Mandatory template It is the unique slug name of the template created on the SuprSend platform. You can get this slug name by clicking on the clipboard icon next to the Template name on the SuprSend templates page. It is the same for all channels. slug name Mandatory notification_category You can understand more about them in the Notification Category documentation. system / transactional / promotional Mandatory delay Workflow will be halted for the time mentioned in delay and become active once the delay period is over. XXdXXhXXmXXs or if it’s a number (n), then delay is in seconds (n). Optional trigger_at Trigger workflow on a specific date-time. Date string in ISO 8601 format e.g. "2021-08-27T20:14:51.643Z" Optional users Array object of target users. At least 1 user is mandatory. distinct_id for each user is mandatory. Channel information is non-mandatory (If you have already sent channel information via backend or Frontend SDK (on app or website)).Notification will be sent only to the channels defined in workflow if channel information is added. json"users": [ { "distinct_id": "value", "$channels": [], "channel_information_dict" #(optional) }] Mandatory delivery Delivery instructions for the workflow. You can set Smart Delivery preference by setting "smart":true .By default, delivery instruction will be: json"delivery": { "smart": false, "success": "seen"} jsondelivery: { "smart": True/False, "success": "delivered/seen/interaction/<some-user-defined-success-event>", "time_to_live": "<TTL duration>", "mandatory_channels": [] # list of mandatory channels e.g "notification",} Optional data JSON object. To replace the variables in the template. Templates use handlebars.js language. json"data": { "key": { "key": "value", "key": "value" }} Optional brand_id Brand_id of the tenant to trigger notifications on behalf of your tenants. string Optional idempotency_key Unique key in the request call for idempotent requests . string Optional For setting $sms and $whatsapp , +<countrycode> is mandatory to send along with phone number. Eg: +1 for US To find the template slug name on SuprSend platform, click on the clipboard icon on Templates page. Templates > Template Details Page Bulk API for triggering multiple workflows Bulk API allows you to send multiple workflow requests in a single call. There isn’t any limit on number-of-records that can be added to bulk_workflows instance. Use .append() on bulk_workflows instance to add however-many-records to call in bulk. Request Response Copy Ask AI const { Workflow } = require ( "@suprsend/node-sdk" ) const bulk_ins = supr_client . bulk_workflows . new_instance () // one or more workflow instances const workflow1 = new Workflow ({ ... }) // body must be a proper workflow request json/dict const workflow2 = new Workflow ({ ... }) // body must be a proper workflow request json/dict // --- use .append on bulk instance to add one or more records bulk_ins . append ( workflow1 ) bulk_ins . append ( workflow2 ) // OR bulk_ins . append ( workflow1 , workflow2 ) // ------- const response = bulk_ins . trigger () response . then (( res ) => console . log ( "response" , res )); Was this page helpful? Yes No Suggest edits Raise issue Previous Tenants Learn how to create, update, fetch, & list tenants using NodeJS SDK. Next ⌘ I x github linkedin youtube Powered by On this page Payload Schema Sending notification to Multiple Users Identifying Recipients Inline Add user communication channel Sending cross-user notifications Sending notification to anonymous user Multi-tenant notifications Idempotent requests Bulk API for triggering multiple workflows Add attachment (in email) Dynamic workflow trigger Bulk API for triggering multiple workflows self.__next_f.push([1,"33:[\"$\",\"$L34\",null,{\"children\":[[\"$\",\"$L35\",null,{\"id\":\"_mintlify-page-mode-script\",\"strategy\":\"beforeInteractive\",\"dangerouslySetInnerHTML\":{\"__html\":\"document.documentElement.setAttribute('data-page-mode', 'none');\"}}],[\"$\",\"$L36\",null,{\"theme\":\"maple\"}],[\"$\",\"$L37\",null,{\"docsConfig\":\"$1b:props:children:props:children:props:docsConfig\",\"pageMetadata\":\"$1b:props:children:props:value:pageMetadata\"}],[[\"$\",\"style\",\"0\",{\"data-custom-css-index\":0,\"data-custom-css-path\":\"style.css\",\"dangerouslySetInnerHTML\":{\"__html\":\"#navbar {\\n background: \\\"#ff1900\\\";\\n padding: 1rem;\\n}\"}}]],[\"$\",\"$L38\",null,{\"customJsDisabled\":false,\"jsFiles\":[]}],[\"$\",\"$L39\",null,{\"slug\":\"docs/node-trigger-workflow-from-api\",\"pageMetadata\":\"$1b:props:children:props:value:pageMetadata\",\"theme\":\"maple\",\"children\":[\"$\",\"$L3a\",null,{\"mdxSource\":{\"compiledSource\":\"$3b\",\"frontmatter\":{},\"scope\":{\"codeStyling\":\"system\",\"config\":{},\"pageMetadata\":{\"title\":\"Trigger Workflow from API\",\"description\":\"Learn how to trigger workflows using direct workflow API, with code snippets and examples.\",\"href\":\"/docs/node- | 2026-01-13T08:48:42 |
https://docs.python.org/3/library/stdtypes.html#str.format | Built-in Types — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents Built-in Types Truth Value Testing Boolean Operations — and , or , not Comparisons Numeric Types — int , float , complex Bitwise Operations on Integer Types Additional Methods on Integer Types Additional Methods on Float Additional Methods on Complex Hashing of numeric types Boolean Type - bool Iterator Types Generator Types Sequence Types — list , tuple , range Common Sequence Operations Immutable Sequence Types Mutable Sequence Types Lists Tuples Ranges Text and Binary Sequence Type Methods Summary Text Sequence Type — str String Methods Formatted String Literals (f-strings) Debug specifier Conversion specifier Format specifier Template String Literals (t-strings) printf -style String Formatting Binary Sequence Types — bytes , bytearray , memoryview Bytes Objects Bytearray Objects Bytes and Bytearray Operations printf -style Bytes Formatting Memory Views Set Types — set , frozenset Mapping Types — dict Dictionary view objects Context Manager Types Type Annotation Types — Generic Alias , Union Generic Alias Type Standard Generic Classes Special Attributes of GenericAlias objects Union Type Other Built-in Types Modules Classes and Class Instances Functions Methods Code Objects Type Objects The Null Object The Ellipsis Object The NotImplemented Object Internal Objects Special Attributes Integer string conversion length limitation Affected APIs Configuring the limit Recommended configuration Previous topic Built-in Constants Next topic Built-in Exceptions This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Built-in Types | Theme Auto Light Dark | Built-in Types ¶ The following sections describe the standard types that are built into the interpreter. The principal built-in types are numerics, sequences, mappings, classes, instances and exceptions. Some collection classes are mutable. The methods that add, subtract, or rearrange their members in place, and don’t return a specific item, never return the collection instance itself but None . Some operations are supported by several object types; in particular, practically all objects can be compared for equality, tested for truth value, and converted to a string (with the repr() function or the slightly different str() function). The latter function is implicitly used when an object is written by the print() function. Truth Value Testing ¶ Any object can be tested for truth value, for use in an if or while condition or as operand of the Boolean operations below. By default, an object is considered true unless its class defines either a __bool__() method that returns False or a __len__() method that returns zero, when called with the object. [ 1 ] If one of the methods raises an exception when called, the exception is propagated and the object does not have a truth value (for example, NotImplemented ). Here are most of the built-in objects considered false: constants defined to be false: None and False zero of any numeric type: 0 , 0.0 , 0j , Decimal(0) , Fraction(0, 1) empty sequences and collections: '' , () , [] , {} , set() , range(0) Operations and built-in functions that have a Boolean result always return 0 or False for false and 1 or True for true, unless otherwise stated. (Important exception: the Boolean operations or and and always return one of their operands.) Boolean Operations — and , or , not ¶ These are the Boolean operations, ordered by ascending priority: Operation Result Notes x or y if x is true, then x , else y (1) x and y if x is false, then x , else y (2) not x if x is false, then True , else False (3) Notes: This is a short-circuit operator, so it only evaluates the second argument if the first one is false. This is a short-circuit operator, so it only evaluates the second argument if the first one is true. not has a lower priority than non-Boolean operators, so not a == b is interpreted as not (a == b) , and a == not b is a syntax error. Comparisons ¶ There are eight comparison operations in Python. They all have the same priority (which is higher than that of the Boolean operations). Comparisons can be chained arbitrarily; for example, x < y <= z is equivalent to x < y and y <= z , except that y is evaluated only once (but in both cases z is not evaluated at all when x < y is found to be false). This table summarizes the comparison operations: Operation Meaning < strictly less than <= less than or equal > strictly greater than >= greater than or equal == equal != not equal is object identity is not negated object identity Unless stated otherwise, objects of different types never compare equal. The == operator is always defined but for some object types (for example, class objects) is equivalent to is . The < , <= , > and >= operators are only defined where they make sense; for example, they raise a TypeError exception when one of the arguments is a complex number. Non-identical instances of a class normally compare as non-equal unless the class defines the __eq__() method. Instances of a class cannot be ordered with respect to other instances of the same class, or other types of object, unless the class defines enough of the methods __lt__() , __le__() , __gt__() , and __ge__() (in general, __lt__() and __eq__() are sufficient, if you want the conventional meanings of the comparison operators). The behavior of the is and is not operators cannot be customized; also they can be applied to any two objects and never raise an exception. Two more operations with the same syntactic priority, in and not in , are supported by types that are iterable or implement the __contains__() method. Numeric Types — int , float , complex ¶ There are three distinct numeric types: integers , floating-point numbers , and complex numbers . In addition, Booleans are a subtype of integers. Integers have unlimited precision. Floating-point numbers are usually implemented using double in C; information about the precision and internal representation of floating-point numbers for the machine on which your program is running is available in sys.float_info . Complex numbers have a real and imaginary part, which are each a floating-point number. To extract these parts from a complex number z , use z.real and z.imag . (The standard library includes the additional numeric types fractions.Fraction , for rationals, and decimal.Decimal , for floating-point numbers with user-definable precision.) Numbers are created by numeric literals or as the result of built-in functions and operators. Unadorned integer literals (including hex, octal and binary numbers) yield integers. Numeric literals containing a decimal point or an exponent sign yield floating-point numbers. Appending 'j' or 'J' to a numeric literal yields an imaginary number (a complex number with a zero real part) which you can add to an integer or float to get a complex number with real and imaginary parts. The constructors int() , float() , and complex() can be used to produce numbers of a specific type. Python fully supports mixed arithmetic: when a binary arithmetic operator has operands of different numeric types, the operand with the “narrower” type is widened to that of the other, where integer is narrower than floating point. Arithmetic with complex and real operands is defined by the usual mathematical formula, for example: x + complex ( u , v ) = complex ( x + u , v ) x * complex ( u , v ) = complex ( x * u , x * v ) A comparison between numbers of different types behaves as though the exact values of those numbers were being compared. [ 2 ] All numeric types (except complex) support the following operations (for priorities of the operations, see Operator precedence ): Operation Result Notes Full documentation x + y sum of x and y x - y difference of x and y x * y product of x and y x / y quotient of x and y x // y floored quotient of x and y (1)(2) x % y remainder of x / y (2) -x x negated +x x unchanged abs(x) absolute value or magnitude of x abs() int(x) x converted to integer (3)(6) int() float(x) x converted to floating point (4)(6) float() complex(re, im) a complex number with real part re , imaginary part im . im defaults to zero. (6) complex() c.conjugate() conjugate of the complex number c divmod(x, y) the pair (x // y, x % y) (2) divmod() pow(x, y) x to the power y (5) pow() x ** y x to the power y (5) Notes: Also referred to as integer division. For operands of type int , the result has type int . For operands of type float , the result has type float . In general, the result is a whole integer, though the result’s type is not necessarily int . The result is always rounded towards minus infinity: 1//2 is 0 , (-1)//2 is -1 , 1//(-2) is -1 , and (-1)//(-2) is 0 . Not for complex numbers. Instead convert to floats using abs() if appropriate. Conversion from float to int truncates, discarding the fractional part. See functions math.floor() and math.ceil() for alternative conversions. float also accepts the strings “nan” and “inf” with an optional prefix “+” or “-” for Not a Number (NaN) and positive or negative infinity. Python defines pow(0, 0) and 0 ** 0 to be 1 , as is common for programming languages. The numeric literals accepted include the digits 0 to 9 or any Unicode equivalent (code points with the Nd property). See the Unicode Standard for a complete list of code points with the Nd property. All numbers.Real types ( int and float ) also include the following operations: Operation Result math.trunc(x) x truncated to Integral round(x[, n]) x rounded to n digits, rounding half to even. If n is omitted, it defaults to 0. math.floor(x) the greatest Integral <= x math.ceil(x) the least Integral >= x For additional numeric operations see the math and cmath modules. Bitwise Operations on Integer Types ¶ Bitwise operations only make sense for integers. The result of bitwise operations is calculated as though carried out in two’s complement with an infinite number of sign bits. The priorities of the binary bitwise operations are all lower than the numeric operations and higher than the comparisons; the unary operation ~ has the same priority as the other unary numeric operations ( + and - ). This table lists the bitwise operations sorted in ascending priority: Operation Result Notes x | y bitwise or of x and y (4) x ^ y bitwise exclusive or of x and y (4) x & y bitwise and of x and y (4) x << n x shifted left by n bits (1)(2) x >> n x shifted right by n bits (1)(3) ~x the bits of x inverted Notes: Negative shift counts are illegal and cause a ValueError to be raised. A left shift by n bits is equivalent to multiplication by pow(2, n) . A right shift by n bits is equivalent to floor division by pow(2, n) . Performing these calculations with at least one extra sign extension bit in a finite two’s complement representation (a working bit-width of 1 + max(x.bit_length(), y.bit_length()) or more) is sufficient to get the same result as if there were an infinite number of sign bits. Additional Methods on Integer Types ¶ The int type implements the numbers.Integral abstract base class . In addition, it provides a few more methods: int. bit_length ( ) ¶ Return the number of bits necessary to represent an integer in binary, excluding the sign and leading zeros: >>> n = - 37 >>> bin ( n ) '-0b100101' >>> n . bit_length () 6 More precisely, if x is nonzero, then x.bit_length() is the unique positive integer k such that 2**(k-1) <= abs(x) < 2**k . Equivalently, when abs(x) is small enough to have a correctly rounded logarithm, then k = 1 + int(log(abs(x), 2)) . If x is zero, then x.bit_length() returns 0 . Equivalent to: def bit_length ( self ): s = bin ( self ) # binary representation: bin(-37) --> '-0b100101' s = s . lstrip ( '-0b' ) # remove leading zeros and minus sign return len ( s ) # len('100101') --> 6 Added in version 3.1. int. bit_count ( ) ¶ Return the number of ones in the binary representation of the absolute value of the integer. This is also known as the population count. Example: >>> n = 19 >>> bin ( n ) '0b10011' >>> n . bit_count () 3 >>> ( - n ) . bit_count () 3 Equivalent to: def bit_count ( self ): return bin ( self ) . count ( "1" ) Added in version 3.10. int. to_bytes ( length = 1 , byteorder = 'big' , * , signed = False ) ¶ Return an array of bytes representing an integer. >>> ( 1024 ) . to_bytes ( 2 , byteorder = 'big' ) b'\x04\x00' >>> ( 1024 ) . to_bytes ( 10 , byteorder = 'big' ) b'\x00\x00\x00\x00\x00\x00\x00\x00\x04\x00' >>> ( - 1024 ) . to_bytes ( 10 , byteorder = 'big' , signed = True ) b'\xff\xff\xff\xff\xff\xff\xff\xff\xfc\x00' >>> x = 1000 >>> x . to_bytes (( x . bit_length () + 7 ) // 8 , byteorder = 'little' ) b'\xe8\x03' The integer is represented using length bytes, and defaults to 1. An OverflowError is raised if the integer is not representable with the given number of bytes. The byteorder argument determines the byte order used to represent the integer, and defaults to "big" . If byteorder is "big" , the most significant byte is at the beginning of the byte array. If byteorder is "little" , the most significant byte is at the end of the byte array. The signed argument determines whether two’s complement is used to represent the integer. If signed is False and a negative integer is given, an OverflowError is raised. The default value for signed is False . The default values can be used to conveniently turn an integer into a single byte object: >>> ( 65 ) . to_bytes () b'A' However, when using the default arguments, don’t try to convert a value greater than 255 or you’ll get an OverflowError . Equivalent to: def to_bytes ( n , length = 1 , byteorder = 'big' , signed = False ): if byteorder == 'little' : order = range ( length ) elif byteorder == 'big' : order = reversed ( range ( length )) else : raise ValueError ( "byteorder must be either 'little' or 'big'" ) return bytes (( n >> i * 8 ) & 0xff for i in order ) Added in version 3.2. Changed in version 3.11: Added default argument values for length and byteorder . classmethod int. from_bytes ( bytes , byteorder = 'big' , * , signed = False ) ¶ Return the integer represented by the given array of bytes. >>> int . from_bytes ( b ' \x00\x10 ' , byteorder = 'big' ) 16 >>> int . from_bytes ( b ' \x00\x10 ' , byteorder = 'little' ) 4096 >>> int . from_bytes ( b ' \xfc\x00 ' , byteorder = 'big' , signed = True ) -1024 >>> int . from_bytes ( b ' \xfc\x00 ' , byteorder = 'big' , signed = False ) 64512 >>> int . from_bytes ([ 255 , 0 , 0 ], byteorder = 'big' ) 16711680 The argument bytes must either be a bytes-like object or an iterable producing bytes. The byteorder argument determines the byte order used to represent the integer, and defaults to "big" . If byteorder is "big" , the most significant byte is at the beginning of the byte array. If byteorder is "little" , the most significant byte is at the end of the byte array. To request the native byte order of the host system, use sys.byteorder as the byte order value. The signed argument indicates whether two’s complement is used to represent the integer. Equivalent to: def from_bytes ( bytes , byteorder = 'big' , signed = False ): if byteorder == 'little' : little_ordered = list ( bytes ) elif byteorder == 'big' : little_ordered = list ( reversed ( bytes )) else : raise ValueError ( "byteorder must be either 'little' or 'big'" ) n = sum ( b << i * 8 for i , b in enumerate ( little_ordered )) if signed and little_ordered and ( little_ordered [ - 1 ] & 0x80 ): n -= 1 << 8 * len ( little_ordered ) return n Added in version 3.2. Changed in version 3.11: Added default argument value for byteorder . int. as_integer_ratio ( ) ¶ Return a pair of integers whose ratio is equal to the original integer and has a positive denominator. The integer ratio of integers (whole numbers) is always the integer as the numerator and 1 as the denominator. Added in version 3.8. int. is_integer ( ) ¶ Returns True . Exists for duck type compatibility with float.is_integer() . Added in version 3.12. Additional Methods on Float ¶ The float type implements the numbers.Real abstract base class . float also has the following additional methods. classmethod float. from_number ( x ) ¶ Class method to return a floating-point number constructed from a number x . 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.from_number(x) delegates to x.__float__() . If __float__() is not defined then it falls back to __index__() . Added in version 3.14. float. as_integer_ratio ( ) ¶ Return a pair of integers whose ratio is exactly equal to the original float. The ratio is in lowest terms and has a positive denominator. Raises OverflowError on infinities and a ValueError on NaNs. float. is_integer ( ) ¶ Return True if the float instance is finite with integral value, and False otherwise: >>> ( - 2.0 ) . is_integer () True >>> ( 3.2 ) . is_integer () False Two methods support conversion to and from hexadecimal strings. Since Python’s floats are stored internally as binary numbers, converting a float to or from a decimal string usually involves a small rounding error. In contrast, hexadecimal strings allow exact representation and specification of floating-point numbers. This can be useful when debugging, and in numerical work. float. hex ( ) ¶ Return a representation of a floating-point number as a hexadecimal string. For finite floating-point numbers, this representation will always include a leading 0x and a trailing p and exponent. classmethod float. fromhex ( s ) ¶ Class method to return the float represented by a hexadecimal string s . The string s may have leading and trailing whitespace. Note that float.hex() is an instance method, while float.fromhex() is a class method. A hexadecimal string takes the form: [ sign ] [ '0x' ] integer [ '.' fraction ] [ 'p' exponent ] where the optional sign may by either + or - , integer and fraction are strings of hexadecimal digits, and exponent is a decimal integer with an optional leading sign. Case is not significant, and there must be at least one hexadecimal digit in either the integer or the fraction. This syntax is similar to the syntax specified in section 6.4.4.2 of the C99 standard, and also to the syntax used in Java 1.5 onwards. In particular, the output of float.hex() is usable as a hexadecimal floating-point literal in C or Java code, and hexadecimal strings produced by C’s %a format character or Java’s Double.toHexString are accepted by float.fromhex() . Note that the exponent is written in decimal rather than hexadecimal, and that it gives the power of 2 by which to multiply the coefficient. For example, the hexadecimal string 0x3.a7p10 represents the floating-point number (3 + 10./16 + 7./16**2) * 2.0**10 , or 3740.0 : >>> float . fromhex ( '0x3.a7p10' ) 3740.0 Applying the reverse conversion to 3740.0 gives a different hexadecimal string representing the same number: >>> float . hex ( 3740.0 ) '0x1.d380000000000p+11' Additional Methods on Complex ¶ The complex type implements the numbers.Complex abstract base class . complex also has the following additional methods. classmethod complex. from_number ( x ) ¶ Class method to convert a number to a complex number. For a general Python object x , complex.from_number(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__() . Added in version 3.14. Hashing of numeric types ¶ For numbers x and y , possibly of different types, it’s a requirement that hash(x) == hash(y) whenever x == y (see the __hash__() method documentation for more details). For ease of implementation and efficiency across a variety of numeric types (including int , float , decimal.Decimal and fractions.Fraction ) Python’s hash for numeric types is based on a single mathematical function that’s defined for any rational number, and hence applies to all instances of int and fractions.Fraction , and all finite instances of float and decimal.Decimal . Essentially, this function is given by reduction modulo P for a fixed prime P . The value of P is made available to Python as the modulus attribute of sys.hash_info . CPython implementation detail: Currently, the prime used is P = 2**31 - 1 on machines with 32-bit C longs and P = 2**61 - 1 on machines with 64-bit C longs. Here are the rules in detail: If x = m / n is a nonnegative rational number and n is not divisible by P , define hash(x) as m * invmod(n, P) % P , where invmod(n, P) gives the inverse of n modulo P . If x = m / n is a nonnegative rational number and n is divisible by P (but m is not) then n has no inverse modulo P and the rule above doesn’t apply; in this case define hash(x) to be the constant value sys.hash_info.inf . If x = m / n is a negative rational number define hash(x) as -hash(-x) . If the resulting hash is -1 , replace it with -2 . The particular values sys.hash_info.inf and -sys.hash_info.inf are used as hash values for positive infinity or negative infinity (respectively). For a complex number z , the hash values of the real and imaginary parts are combined by computing hash(z.real) + sys.hash_info.imag * hash(z.imag) , reduced modulo 2**sys.hash_info.width so that it lies in range(-2**(sys.hash_info.width - 1), 2**(sys.hash_info.width - 1)) . Again, if the result is -1 , it’s replaced with -2 . To clarify the above rules, here’s some example Python code, equivalent to the built-in hash, for computing the hash of a rational number, float , or complex : import sys , math def hash_fraction ( m , n ): """Compute the hash of a rational number m / n. Assumes m and n are integers, with n positive. Equivalent to hash(fractions.Fraction(m, n)). """ P = sys . hash_info . modulus # Remove common factors of P. (Unnecessary if m and n already coprime.) while m % P == n % P == 0 : m , n = m // P , n // P if n % P == 0 : hash_value = sys . hash_info . inf else : # Fermat's Little Theorem: pow(n, P-1, P) is 1, so # pow(n, P-2, P) gives the inverse of n modulo P. hash_value = ( abs ( m ) % P ) * pow ( n , P - 2 , P ) % P if m < 0 : hash_value = - hash_value if hash_value == - 1 : hash_value = - 2 return hash_value def hash_float ( x ): """Compute the hash of a float x.""" if math . isnan ( x ): return object . __hash__ ( x ) elif math . isinf ( x ): return sys . hash_info . inf if x > 0 else - sys . hash_info . inf else : return hash_fraction ( * x . as_integer_ratio ()) def hash_complex ( z ): """Compute the hash of a complex number z.""" hash_value = hash_float ( z . real ) + sys . hash_info . imag * hash_float ( z . imag ) # do a signed reduction modulo 2**sys.hash_info.width M = 2 ** ( sys . hash_info . width - 1 ) hash_value = ( hash_value & ( M - 1 )) - ( hash_value & M ) if hash_value == - 1 : hash_value = - 2 return hash_value Boolean Type - bool ¶ Booleans represent truth values. The bool type has exactly two constant instances: True and False . The built-in function bool() converts any value to a boolean, if the value can be interpreted as a truth value (see section Truth Value Testing above). For logical operations, use the boolean operators and , or and not . When applying the bitwise operators & , | , ^ to two booleans, they return a bool equivalent to the logical operations “and”, “or”, “xor”. However, the logical operators and , or and != should be preferred over & , | and ^ . Deprecated since version 3.12: The use of the bitwise inversion operator ~ is deprecated and will raise an error in Python 3.16. bool is a subclass of int (see Numeric Types — int, float, complex ). In many numeric contexts, False and True behave like the integers 0 and 1, respectively. However, relying on this is discouraged; explicitly convert using int() instead. Iterator Types ¶ Python supports a concept of iteration over containers. This is implemented using two distinct methods; these are used to allow user-defined classes to support iteration. Sequences, described below in more detail, always support the iteration methods. One method needs to be defined for container objects to provide iterable support: container. __iter__ ( ) ¶ Return an iterator object. The object is required to support the iterator protocol described below. If a container supports different types of iteration, additional methods can be provided to specifically request iterators for those iteration types. (An example of an object supporting multiple forms of iteration would be a tree structure which supports both breadth-first and depth-first traversal.) This method corresponds to the tp_iter slot of the type structure for Python objects in the Python/C API. The iterator objects themselves are required to support the following two methods, which together form the iterator protocol : iterator. __iter__ ( ) ¶ Return the iterator object itself. This is required to allow both containers and iterators to be used with the for and in statements. This method corresponds to the tp_iter slot of the type structure for Python objects in the Python/C API. iterator. __next__ ( ) ¶ Return the next item from the iterator . If there are no further items, raise the StopIteration exception. This method corresponds to the tp_iternext slot of the type structure for Python objects in the Python/C API. Python defines several iterator objects to support iteration over general and specific sequence types, dictionaries, and other more specialized forms. The specific types are not important beyond their implementation of the iterator protocol. Once an iterator’s __next__() method raises StopIteration , it must continue to do so on subsequent calls. Implementations that do not obey this property are deemed broken. Generator Types ¶ Python’s generator s provide a convenient way to implement the iterator protocol. If a container object’s __iter__() method is implemented as a generator, it will automatically return an iterator object (technically, a generator object) supplying the __iter__() and __next__() methods. More information about generators can be found in the documentation for the yield expression . Sequence Types — list , tuple , range ¶ There are three basic sequence types: lists, tuples, and range objects. Additional sequence types tailored for processing of binary data and text strings are described in dedicated sections. Common Sequence Operations ¶ The operations in the following table are supported by most sequence types, both mutable and immutable. The collections.abc.Sequence ABC is provided to make it easier to correctly implement these operations on custom sequence types. This table lists the sequence operations sorted in ascending priority. In the table, s and t are sequences of the same type, n , i , j and k are integers and x is an arbitrary object that meets any type and value restrictions imposed by s . The in and not in operations have the same priorities as the comparison operations. The + (concatenation) and * (repetition) operations have the same priority as the corresponding numeric operations. [ 3 ] Operation Result Notes x in s True if an item of s is equal to x , else False (1) x not in s False if an item of s is equal to x , else True (1) s + t the concatenation of s and t (6)(7) s * n or n * s equivalent to adding s to itself n times (2)(7) s[i] i th item of s , origin 0 (3)(8) s[i:j] slice of s from i to j (3)(4) s[i:j:k] slice of s from i to j with step k (3)(5) len(s) length of s min(s) smallest item of s max(s) largest item of s Sequences of the same type also support comparisons. In particular, tuples and lists are compared lexicographically by comparing corresponding elements. This means that to compare equal, every element must compare equal and the two sequences must be of the same type and have the same length. (For full details see Comparisons in the language reference.) Forward and reversed iterators over mutable sequences access values using an index. That index will continue to march forward (or backward) even if the underlying sequence is mutated. The iterator terminates only when an IndexError or a StopIteration is encountered (or when the index drops below zero). Notes: While the in and not in operations are used only for simple containment testing in the general case, some specialised sequences (such as str , bytes and bytearray ) also use them for subsequence testing: >>> "gg" in "eggs" True Values of n less than 0 are treated as 0 (which yields an empty sequence of the same type as s ). Note that items in the sequence s are not copied; they are referenced multiple times. This often haunts new Python programmers; consider: >>> lists = [[]] * 3 >>> lists [[], [], []] >>> lists [ 0 ] . append ( 3 ) >>> lists [[3], [3], [3]] What has happened is that [[]] is a one-element list containing an empty list, so all three elements of [[]] * 3 are references to this single empty list. Modifying any of the elements of lists modifies this single list. You can create a list of different lists this way: >>> lists = [[] for i in range ( 3 )] >>> lists [ 0 ] . append ( 3 ) >>> lists [ 1 ] . append ( 5 ) >>> lists [ 2 ] . append ( 7 ) >>> lists [[3], [5], [7]] Further explanation is available in the FAQ entry How do I create a multidimensional list? . If i or j is negative, the index is relative to the end of sequence s : len(s) + i or len(s) + j is substituted. But note that -0 is still 0 . The slice of s from i to j is defined as the sequence of items with index k such that i <= k < j . If i is omitted or None , use 0 . If j is omitted or None , use len(s) . If i or j is less than -len(s) , use 0 . If i or j is greater than len(s) , use len(s) . If i is greater than or equal to j , the slice is empty. The slice of s from i to j with step k is defined as the sequence of items with index x = i + n*k such that 0 <= n < (j-i)/k . In other words, the indices are i , i+k , i+2*k , i+3*k and so on, stopping when j is reached (but never including j ). When k is positive, i and j are reduced to len(s) if they are greater. When k is negative, i and j are reduced to len(s) - 1 if they are greater. If i or j are omitted or None , they become “end” values (which end depends on the sign of k ). Note, k cannot be zero. If k is None , it is treated like 1 . Concatenating immutable sequences always results in a new object. This means that building up a sequence by repeated concatenation will have a quadratic runtime cost in the total sequence length. To get a linear runtime cost, you must switch to one of the alternatives below: if concatenating str objects, you can build a list and use str.join() at the end or else write to an io.StringIO instance and retrieve its value when complete if concatenating bytes objects, you can similarly use bytes.join() or io.BytesIO , or you can do in-place concatenation with a bytearray object. bytearray objects are mutable and have an efficient overallocation mechanism if concatenating tuple objects, extend a list instead for other types, investigate the relevant class documentation Some sequence types (such as range ) only support item sequences that follow specific patterns, and hence don’t support sequence concatenation or repetition. An IndexError is raised if i is outside the sequence range. Sequence Methods Sequence types also support the following methods: sequence. count ( value , / ) ¶ Return the total number of occurrences of value in sequence . sequence. index ( value[, start[, stop] ) ¶ Return the index of the first occurrence of value in sequence . Raises ValueError if value is not found in sequence . The start or stop arguments allow for efficient searching of subsections of the sequence, beginning at start and ending at stop . This is roughly equivalent to start + sequence[start:stop].index(value) , only without copying any data. Caution Not all sequence types support passing the start and stop arguments. Immutable Sequence Types ¶ The only operation that immutable sequence types generally implement that is not also implemented by mutable sequence types is support for the hash() built-in. This support allows immutable sequences, such as tuple instances, to be used as dict keys and stored in set and frozenset instances. Attempting to hash an immutable sequence that contains unhashable values will result in TypeError . Mutable Sequence Types ¶ The operations in the following table are defined on mutable sequence types. The collections.abc.MutableSequence ABC is provided to make it easier to correctly implement these operations on custom sequence types. In the table s is an instance of a mutable sequence type, t is any iterable object and x is an arbitrary object that meets any type and value restrictions imposed by s (for example, bytearray only accepts integers that meet the value restriction 0 <= x <= 255 ). Operation Result Notes s[i] = x item i of s is replaced by x del s[i] removes item i of s s[i:j] = t slice of s from i to j is replaced by the contents of the iterable t del s[i:j] removes the elements of s[i:j] from the list (same as s[i:j] = [] ) s[i:j:k] = t the elements of s[i:j:k] are replaced by those of t (1) del s[i:j:k] removes the elements of s[i:j:k] from the list s += t extends s with the contents of t (for the most part the same as s[len(s):len(s)] = t ) s *= n updates s with its contents repeated n times (2) Notes: If k is not equal to 1 , t must have the same length as the slice it is replacing. The value n is an integer, or an object implementing __index__() . Zero and negative values of n clear the sequence. Items in the sequence are not copied; they are referenced multiple times, as explained for s * n under Common Sequence Operations . Mutable Sequence Methods Mutable sequence types also support the following methods: sequence. append ( value , / ) ¶ Append value to the end of the sequence This is equivalent to writing seq[len(seq):len(seq)] = [value] . sequence. clear ( ) ¶ Added in version 3.3. Remove all items from sequence . This is equivalent to writing del sequence[:] . sequence. copy ( ) ¶ Added in version 3.3. Create a shallow copy of sequence . This is equivalent to writing sequence[:] . Hint The copy() method is not part of the MutableSequence ABC , but most concrete mutable sequence types provide it. sequence. extend ( iterable , / ) ¶ Extend sequence with the contents of iterable . For the most part, this is the same as writing seq[len(seq):len(seq)] = iterable . sequence. insert ( index , value , / ) ¶ Insert value into sequence at the given index . This is equivalent to writing sequence[index:index] = [value] . sequence. pop ( index = -1 , / ) ¶ Retrieve the item at index and also removes it from sequence . By default, the last item in sequence is removed and returned. sequence. remove ( value , / ) ¶ Remove the first item from sequence where sequence[i] == value . Raises ValueError if value is not found in sequence . sequence. reverse ( ) ¶ Reverse the items of sequence in place. This method maintains economy of space when reversing a large sequence. To remind users that it operates by side-effect, it returns None . Lists ¶ Lists are mutable sequences, typically used to store collections of homogeneous items (where the precise degree of similarity will vary by application). class list ( iterable = () , / ) ¶ Lists may be constructed in several ways: Using a pair of square brackets to denote the empty list: [] Using square brackets, separating items with commas: [a] , [a, b, c] Using a list comprehension: [x for x in iterable] Using the type constructor: list() or list(iterable) The constructor builds a list whose items are the same and in the same order as iterable ’s items. iterable may be either a sequence, a container that supports iteration, or an iterator object. If iterable is already a list, a copy is made and returned, similar to iterable[:] . For example, list('abc') returns ['a', 'b', 'c'] and list( (1, 2, 3) ) returns [1, 2, 3] . If no argument is given, the constructor creates a new empty list, [] . Many other operations also produce lists, including the sorted() built-in. Lists implement all of the common and mutable sequence operations. Lists also provide the following additional method: sort ( * , key = None , reverse = False ) ¶ This method sorts the list in place, using only < comparisons between items. Exceptions are not suppressed - if any comparison operations fail, the entire sort operation will fail (and the list will likely be left in a partially modified state). sort() accepts two arguments that can only be passed by keyword ( keyword-only arguments ): key specifies a function of one argument that is used to extract a comparison key from each list element (for example, key=str.lower ). The key corresponding to each item in the list is calculated once and then used for the entire sorting process. The default value of None means that list items are sorted directly without calculating a separate key value. The functools.cmp_to_key() utility is available to convert a 2.x style cmp function to a key function. reverse is a boolean value. If set to True , then the list elements are sorted as if each comparison were reversed. This method modifies the sequence in place for economy of space when sorting a large sequence. To remind users that it operates by side effect, it does not return the sorted sequence (use sorted() to explicitly request a new sorted list instance). The sort() method is guaranteed to be stable. A sort is stable if it guarantees not to change the relative order of elements that compare equal — this is helpful for sorting in multiple passes (for example, sort by department, then by salary grade). For sorting examples and a brief sorting tutorial, see Sorting Techniques . CPython implementation detail: While a list is being sorted, the effect of attempting to mutate, or even inspect, the list is undefined. The C implementation of Python makes the list appear empty for the duration, and raises ValueError if it can detect that the list has been mutated during a sort. Thread safety Reading a single element from a list is atomic : lst [ i ] # list.__getitem__ The following methods traverse the list and use atomic reads of each item to perform their function. That means that they may return results affected by concurrent modifications: item in lst lst . index ( item ) lst . count ( item ) All of the above methods/operations are also lock-free. They do not block concurrent modifications. Other operations that hold a lock will not block these from observing intermediate states. All other operations from here on block using the per-object lock. Writing a single item via lst[i] = x is safe to call from multiple threads and will not corrupt the list. The following operations return new objects and appear atomic to other threads: lst1 + lst2 # concatenates two lists into a new list x * lst # repeats lst x times into a new list lst . copy () # returns a shallow copy of the list Methods that only operate on a single elements with no shifting required are atomic : lst . append ( x ) # append to the end of the list, no shifting required lst . pop () # pop element from the end of the list, no shifting required The clear() method is also atomic . Other threads cannot observe elements being removed. The sort() method is not atomic . Other threads cannot observe intermediate states during sorting, but the list appears empty for the duration of the sort. The following operations may allow lock-free operations to observe intermediate states since they modify multiple elements in place: lst . insert ( idx , item ) # shifts elements lst . pop ( idx ) # idx not at the end of the list, shifts elements lst *= x # copies elements in place The remove() method may allow concurrent modifications since element comparison may execute arbitrary Python code (via __eq__() ). extend() is safe to call from multiple threads. However, its guarantees depend on the iterable passed to it. If it is a list , a tuple , a set , a frozenset , a dict or a dictionary view object (but not their subclasses), the extend operation is safe from concurrent modifications to the iterable. Otherwise, an iterator is created which can be concurrently modified by another thread. The same applies to inplace concatenation of a list with other iterables when using lst += iterable . Similarly, assigning to a list slice with lst[i:j] = iterable is safe to call from multiple threads, but iterable is only locked when it is also a list (but not its subclasses). Operations that involve multiple accesses, as well as iteration, are never atomic. For example: # NOT atomic: read-modify-write lst [ i ] = lst [ i ] + 1 # NOT atomic: check-then-act if lst : item = lst . pop () # NOT thread-safe: iteration while modifying for item in lst : process ( item ) # another thread may modify lst Consider external synchronization when sharing list instances across threads. See Python support for free threading for more information. Tuples ¶ Tuples are immutable sequences, typically used to store collections of heterogeneous data (such as the 2-tuples produced by the enumerate() built-in). Tuples are also used for cases where an immutable sequence of homogeneous data is needed (such as allowing storage in a set or dict instance). class tuple ( iterable = () , / ) ¶ Tuples may be constructed in a number of ways: Using a pair of parentheses to denote the empty tuple: () Using a trailing comma for a singleton tuple: a, or (a,) Separating items with commas: a, b, c or (a, b, c) Using the tuple() built-in: tuple() or tuple(iterable) The constructor builds a tuple whose items are the same and in the same order as iterable ’s items. iterable may be either a sequence, a container that supports iteration, or an iterator object. If iterable is already a tuple, it is returned unchanged. For example, tuple('abc') returns ('a', 'b', 'c') and tuple( [1, 2, 3] ) returns (1, 2, 3) . If no argument is given, the constructor creates a new empty tuple, () . Note that it is actually the comma which makes a tuple, not the parentheses. The parentheses are optional, except in the empty tuple case, or when they are needed to avoid syntactic ambiguity. For example, f(a, b, c) is a function call with three arguments, while f((a, b, c)) is a function call with a 3-tuple as the sole argument. Tuples implement all of the common sequence operations. For heterogeneous collections of data where access by name is clearer than access by index, collections.namedtuple() may be a more appropriate choice than a simple tuple object. Ranges ¶ The range type represents an immutable sequence of numbers and is commonly used for looping a specific number of times in for loops. class range ( stop , / ) ¶ class range ( start , stop , step = 1 , / ) The arguments to the range constructor must be integers (either built-in int or any object that implements the __index__() special method). If the step argument is omitted, it defaults to 1 . If the start argument is omitted, it defaults to 0 . If step is zero, ValueError is raised. For a positive step , the contents of a range r are determined by the formula r[i] = start + step*i where i >= 0 and r[i] < stop . For a negative step , the contents of the range are still determined by the formula r[i] = start + step*i , but the constraints are i >= 0 and r[i] > stop . A range object will be empty if r[0] does not meet the value constraint. Ranges do support negative indices, but these are interpreted as indexing from the end of the sequence determined by the positive indices. Ranges containing absolute values larger than sys.maxsize are permitted but some features (such as len() ) may raise OverflowError . Range examples: >>> list ( range ( 10 )) [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] >>> list ( range ( 1 , 11 )) [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] >>> list ( range ( 0 , 30 , 5 )) [0, 5, 10, 15, 20, 25] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( 0 , - 10 , - 1 )) [0, -1, -2, -3, -4, -5, -6, -7, -8, -9] >>> list ( range ( 0 )) [] >>> list ( range ( 1 , 0 )) [] Ranges implement all of the common sequence operations except concatenation and repetition (due to the fact that range objects can only represent sequences that follow a strict pattern and repetition and concatenation will usually violate that pattern). start ¶ The value of the start parameter (or 0 if the parameter was not supplied) stop ¶ The value of the stop parameter step ¶ The value of the step parameter (or 1 if the parameter was not supplied) The advantage of the range type over a regular list or tuple is that a range object will always take the same (small) amount of memory, no matter the size of the range it represents (as it only stores the start , stop and step values, calculating individual items and subranges as needed). Range objects implement the collections.abc.Sequence ABC, and provide features such as containment tests, element index lookup, slicing and support for negative indices (see Sequence Types — list, tuple, range ): >>> r = range ( 0 , 20 , 2 ) >>> r range(0, 20, 2) >>> 11 in r False >>> 10 in r True >>> r . index ( 10 ) 5 >>> r [ 5 ] 10 >>> r [: 5 ] range(0, 10, 2) >>> r [ - 1 ] 18 Testing range objects for equality with == and != compares them as sequences. That is, two range objects are considered equal if they represent the same sequence of values. (Note that two range objects that compare equal might have different start , stop and step attributes, for example range(0) == range(2, 1, 3) or range(0, 3, 2) == range(0, 4, 2) .) Changed in version 3.2: Implement the Sequence ABC. Support slicing and negative indices. Test int objects for membership in constant time instead of iterating through all items. Changed in version 3.3: Define ‘==’ and ‘!=’ to compare range objects based on the sequence of values they define (instead of comparing based on object identity). Added the start , stop and step attributes. See also The linspace recipe shows how to implement a lazy version of range suitable for floating-point applications. Text and Binary Sequence Type Methods Summary ¶ The following table summarizes the text and binary sequence types methods by category. Category str methods bytes and bytearray methods Formatting str.format() str.format_map() f-strings printf-style String Formatting printf-style Bytes Formatting Searching and Replacing str.find() str.rfind() bytes.find() bytes.rfind() str.index() str.rindex() bytes.index() bytes.rindex() str.startswith() bytes.startswith() str.endswith() bytes.endswith() str.count() bytes.count() str.replace() bytes.replace() Splitting and Joining str.split() str.rsplit() bytes.split() bytes.rsplit() str.splitlines() bytes.splitlines() str.partition() bytes.partition() str.rpartition() bytes.rpartition() str.join() bytes.join() String Classification str.isalpha() bytes.isalpha() str.isdecimal() str.isdigit() bytes.isdigit() str.isnumeric() str.isalnum() bytes.isalnum() str.isidentifier() str.islower() bytes.islower() str.isupper() bytes.isupper() str.istitle() bytes.istitle() str.isspace() bytes.isspace() str.isprintable() Case Manipulation str.lower() bytes.lower() str.upper() bytes.upper() str.casefold() str.capitalize() bytes.capitalize() str.title() bytes.title() str.swapcase() bytes.swapcase() Padding and Stripping str.ljust() str.rjust() bytes.ljust() bytes.rjust() str.center() bytes.center() str.expandtabs() bytes.expandtabs() str.strip() bytes.strip() str.lstrip() str.rstrip() bytes.lstrip() bytes.rstrip() Translation and Encoding str.translate() bytes.translate() str.maketrans() bytes.maketrans() str.encode() bytes.decode() Text Sequence Type — str ¶ Textual data in Python is handled with str objects, or strings . Strings are immutable sequences of Unicode code points. String literals are written in a variety of ways: Single quotes: 'allows embedded "double" quotes' Double quotes: "allows embedded 'single' quotes" Triple quoted: '''Three single quotes''' , """Three double quotes""" Triple quoted strings may span multiple lines - all associated whitespace will be included in the string literal. String literals that are part of a single expression and have only whitespace between them will be implicitly converted to a single string literal. That is, ("spam " "eggs") == "spam eggs" . See String and Bytes literals for more about the various forms of string literal | 2026-01-13T08:48:42 |
https://docs.suprsend.com/reference/cli-translation-push | Push Translations - 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 Translation Push Translations Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Translation Push Translations OpenAI Open in ChatGPT Push translations from local directory to SuprSend OpenAI Open in ChatGPT Push workflows from local to suprsend. Pushed translations are saved in draft version. Make sure to pass --commit=true flag to commit the translations while pushing, or use the translation commit command separately. Syntax Copy Ask AI suprsend translation push [flags] Flags Flag Description Default -h, --help Show help for the command – -c, --commit string Commit the translation (—commit=true) false -m, --commit-message string Commit message for the translation – -d, --dir string Directory for translations pull to ./suprsend/translation Example Copy Ask AI # Push translations from default directory suprsend translation push # Push translations from custom directory suprsend translation push --dir dev-environment/translations # Push translations and commit them suprsend translation push --commit=true --commit-message "Updated French translations" # Push translations to production workspace suprsend translation push --workspace production Was this page helpful? Yes No Suggest edits Raise issue Previous Commit Translations Commit translations to make them live in the workspace Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:42 |
https://python.org.br/traducao/ | Python Brasil-Como colaborar com a tradução Python Brasil Impressione-se Empresas Projetos Brasileiros Inicie-se Introdução Qual Python? Download do python Instalação Linux Instalação Mac Instalação Windows Ferramentas Aprenda mais Web Mobile Games Científico Wiki Participe Lista de Discussões Comunidades Locais Pyladies Eventos Contribua Grupos de Discussão On-line Tradução APyB Código de Conduta Como colaborar com a tradução Uma excelente forma de contribuir com a comunidade é através da tradução da documentação da linguagem, de bibliotecas e de ferramentas. Com isso você contribui com o crescimento da comunidade aumentando o alcance da linguagem dentro de pessoas nativas do Português Brasileiro. Caso haja interesse em contribuir, a comunidade possui um grupo no Telegram destinado a essa tarefa que pode ser acessado através do seguinte link: https://t.me/pybr_i18n As traduções estão sendo feitas através da plataforma transifex . Para ajudar com a tradução basta criar uma conta e seguir para um dos projetos em andamento abaixo: Tradução da documentação da linguagem Python Para começar a traduzir faça sua requisição através de: https://www.transifex.com/python-doc/public/ Tradução da documentação do framework Django Para começar a traduzir faça sua requisição através de: https://www.transifex.com/django/public/ Você pode também participar da lista de e-mails para discussão sobre tradução do Django: https://groups.google.com/d/forum/django-i18n E ler mais sobre a localização do projeto em: https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#documentation Referências de tradução O Luciano Ramalho e mais uma galera, criaram algumas dicas para quando eles estavam traduzindo o tutorial oficial do Python 2.7 que podem ser usados como referência ao realizar as traduções: http://turing.com.br/pydoc/2.7/tutorial/NOTAS.html#notas-para-os-tradutores-da-versao-pt-br Tradução offline Embora o processo de tradução possa ser feito diretamente pelo navegador web, também é possível gerar a documentação traduzida no computador. Isso pode facilitar o processo de revisão já que pelo browser fica mais difícil visualizar links quebrados e navegar pela documentação. Para gerar a documentação em português siga os passos a seguir (usaremos o Django como exemplo): 1 - Conforme a documentação do Transifex , será preciso criar um arquivo chamado .transifexrc na raiz do seu diretório pessoal (ex.: /home/user/.transifexrc ) contendo seu login e senha no Transifex: [https://www.transifex.com] username = user token = password = passw0rd hostname = https://www.transifex.com 2 - Será preciso baixar os repositórios e instalar algumas bibliotecas, para isso é recomendado criar uma pasta de trabalho: mkdir ~/traducoes/django-br && cd ~/traducoes/django-br 3 - Faça o clone do repositório no GitHub: git clone https://github.com/django/django.git 4 - Faça também o clone do repositório contendo as traduções do Django (como as traduções consomem muito espaço, elas foram movidas para um repositório separado): git clone https://github.com/django/django-docs-translations.git 5 - Para gerar a documentação em português, nós vamos trabalhar dentro do diretório django-docs-translations : cd django-docs-translations/ 6 - Existem várias traduções disponíveis, uma para cada versão do Django, nesse exemplo nós vamos gerar a documentação para a versão 1.10.x: git checkout stable/1.10.x 7 - Para a instalação das bibliotecas, é recomendado também criar e ativar um virtualenv: python -m venv .django-br source .django-br/bin/activate 6 - Para gerar a documentação, o Django utiliza uma biblioteca chamada Sphinx, você pode instalá-la rodando o comando abaixo: pip install sphinx 7 - Para baixar as últimas traduções do site Transifex, nós vamos precisar instalar também a biblioteca Transifex-Client : pip install transifex-client 8 - Com o Transifex-Client instalado e com o arquivo .transifexrc configurado na raiz do seu diretório pessoal, será possível executar o comando abaixo para baixar as traduções do Transifex: tx pull -f -l pt_BR 9 - Com o download das traduções concluído, agora é preciso executar o comando 'make translations' para compilá-las: make translations 10 - Também é necessário criar um link simbólico para que o Sphinx gere a documentação utilizando os arquivos baixados e compilados por você (ao invés dos arquivos padrão no repositório do Django): ln -s ~/traducoes/django-br/django-docs-translations/translations/ ~/traducoes/django-br/django/docs/locale 11 - Agora saia do repositório django-docs-translations e vá para o repositório django, onde vamos encontrar um diretório chamado docs . É dentro desse diretório que vamos poder gerar a documentação: cd ../django/docs/ 12 - Dentro do diretório docs do repositório do Django, após executar os passos acima, rode o comando abaixo para que o Sphinx gere a documentação em português: make html LANGUAGE=pt_BR 13 - Como medida de segurança, eu sugiro excluir o arquivo ~/.transifexrc do seu home ou apagar a senha contida dentro dele já que o Transifex não oferece autenticação via tokens (ainda): rm ~/.transifexrc 14 - Ao final do processo, um novo diretório _build é criado e dentro desse diretório é possível encontrar também o diretório html contendo os arquivos gerados pelo Sphinx. Para visualizar a documentação entre em _build/html/ : cd _build/html/ A página principal da documentação é a index.html , clique duas vezes nesse arquivo para que ele seja aberto no seu browser. Clique nos links para navegar pela documentação, embora sejam links html, todo o conteúdo está contido dentro da pasta _build e portanto disponível offline. O Sphinx permite ainda gerar a documentação em outros formatos como .pdf . Dicas de tradução Nesta seção apresentamos agumas dicas de tradução. Atenção com palavras de grafia parecida Model: Modelo -- Classe que representa uma tabela. Module: Módulo -- Módulo Python, e dentro do Django ainda pode ser o nome de uma Django "app". Cuidado com neologismo A maioria dos termos de computação vem do inglês. E muitas vezes usamos os termos em inglês sem nos dar conta, ou pior, usamos uma tradução cujo o sentido da palavra em português é outro. Adotando a linguagem neutra de gênero Tente usar a linguagem neutra de gênero, pois é uma forma inclusiva de comunicação. Usar 'x' ou '@' no final de termos masculinos ou femininos não é inclusivo e não é reconhecido por leitores de tela. Tente usar uma linguagem que se refira à pessoas, não somente ao masculino ou feminino. Por exemplo: Se você está interessado em contribuir entre em contato conosco Use ao invés disso: Caso haja interesse em contribuir entre em contato conosco Para saber mais sobre a linguagem neutra de gênero você poder ler este artigo da ThoughtWorks Brasil: Adotando a linguagem neutra de gênero Cuidado com os artigos Em inglês as palavras não possuem gênero, portando tenha atenção quanto a concordância dos artigos ao realizar a tradução: Or use a common ancestor to hold the :class:`~django.db.models.AutoField` alguém poderia traduzir como usando o artigo "o" referindo-se ao "autoField": Ou use um acestral comum para manter o :class:`~django.db.models.AutoField` Mas não seria correto. Talvez para uma leitura menos atenta fique até estranho, o que é bom pois chamará atenção se usarmos um artigo feminino neste caso. Ou use um acestral comum para manter a :class:`~django.db.models.AutoField` quer dizer, "ou use um acestral comum para a manter a classe ~django.db.models.AutoField" Depois do texto renderizado, a diretiva :class: não é mostrada, e usar o artigo correto ajuda a lembrar que referenciamos uma classe ou método por exemplo. Não tente explicar mais que na autoria original Cuidado ao achar que um texto em inglês não está bem explicado, ou falta detalhes. Você pode ter razão, e a solução é sugerir melhorias no texto original. Se ao invés disso, tentar escrever um texto melhor na tradução, além do problema raiz persistir, pode acontecer de estar sendo repetitivo. O erro no texto original pode existir, mas antes de afirmá-lo, procure ler o contexto todo e entender se aquele detalhe ou explicação deveria estar ali, ou já foi comentado em outra seção, ou se é realmente papel do texto explicar em detalhes tal condição. Glossário de tradução Este glossário tem como objetivo criar uma consistência de tradução entre os projetos: Sobre Este site busca reunir todo o conteúdo produzido e traduzido pela comunidade brasileira bem como informações relevantes em relação a mesma. Social GitHub Twitter Instagram Facebook Lista de Discussões Telegram Planet Python | 2026-01-13T08:48:42 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#main-content | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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.devcycle.com/platform/feature-flags/status-and-lifecycle#theme-svg-external-link | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:42 |
https://survivejs.com/blog/ | SurviveJS - Blog Skip to content Home Search ☰ Home Books Blog Research Workshops Presentations Open source Consulting Search About me Loading... Blog posts The blog consists mainly of developer interviews. If you have a specific topic in mind, I recommend checking out the topic index . Impressions on Web Summit 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. … Published: 21.11.2024 state-ref - Easy to integrate state management library - Interview with Kim Jinwoo State management is one of those recurring themes in frontend development. State becomes an issue when you try to build something even a little comple… Published: 18.10.2024 KaibanJS - Open-source framework for building multi-agent AI systems - Interview with Dariel Vila 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 inte… Published: 11.10.2024 How to get started with web development in 2024? In the past few years, technologies such as ChatGPT have changed the way we work. It has never been as easy to develop web applications as today, but … Published: 23.9.2024 Singulatron - AI On-Premise - Interview with Janos Dobronszki You could say Artificial Intelligence (AI) is eating the world. The problem is that often, you have to use an external service to leverage its benefit… Published: 22.8.2024 JavaScript patterns - Pyramid of doom In this post, I will introduce you to the concept of the pyramid of doom. Although the pattern is not typical anymore, it is good to know how you migh… Published: 31.5.2024 SurviveJS - What did I learn by rewriting this site If you have used this site earlier, you might have noticed it looks different now. That is because I did a massive rewrite of it. I had the following … Published: 21.5.2024 RelativeCI - In-depth bundle stats analysis and monitoring - Interview with Viorel Cojocaru In terms of development productivity, Continuous Integration (CI) has become a common technique across development teams across the world. In this ar… Published: 7.7.2023 Future Frontend - A new conference to reimagine the future of the frontend - Interview with Juho Vepsäläinen For a conference organizer, one of the hardest things to do is to keep your conference relevant. That is exactly the problem we faced with React Finla… Published: 30.1.2023 Console Cat - Privacy-friendly CLI telemetry in less than five minutes - Interview with Matt Evenson As an open source developer of Node.js command line tools, you often have the question of which versions are being used and how. To solve the problem… Published: 28.7.2022 Nhost - Backend-as-a-Service with GraphQL for modern app development - Interview with Johan Eliasson Developing a full-blown web application, including a backend, can be quite an undertaking for a single developer or a small team. Several solutions ha… Published: 27.1.2022 How to tame the devDependencies of your project? It's not uncommon for a normal JavaScript application to have thousands of dependencies. Once you start having multiple projects, the problem of havin… Published: 13.1.2022 Medusa - Own your ecommerce stack - Interview with Sebastian Rindom Building an online shop can be complex, and there are many factors to consider, not to mention compliance with all the different laws. To learn more … Published: 14.12.2021 iHateReading - Where knowledge is shared - Interview with Shrey Vijayvargiya Developing content is hard work, and it takes consistent effort to become a successful content producer. To learn more about one approach, I am inter… Published: 16.6.2021 Forage Analytics - Analytics for React Native - Interview with Steven Malone Analytics is a big topic. What you don't know, you cannot optimize. To learn more about it, I am interviewing Steven Malone about Forage Analytics, a… Published: 31.5.2021 Blitz.js - The Full-stack React Framework - Interview with Brandon Bayer Although React is a UI library, that doesn't mean you couldn't write full-stack applications around it. Frameworks, such as Next.js, have appeared to … Published: 12.4.2021 Rubico - [a]synchronous functional programming - Interview with Richard Tong One of the tricky parts of JavaScript is dealing with asynchronous behavior. The language itself has introduced improved syntax (async/await) and util… Published: 10.3.2021 PropagateAt - Talk to your greatest fans via text - Interview with Kumar Abhirup Developing your products is both exciting and challenging. There's both the business side and the development side to worry about and to manage. Both … Published: 12.2.2021 GruCloud - Infrastructure as Code in JavaScript - Interview with Frederic Heem For me, it's always amazing how complex infrastructure it's possible to configure these days. If you master a platform like AWS or GCP, you can do qui… Published: 3.2.2021 Renderlesskit React - Collection of composable headless hooks - Interview with Anurag Hazra When developing user interfaces with React, you often create a set of basic primitives. Another option is to consume them from a third-party library a… Published: 29.1.2021 PixelCraft - a Pixel Art Editor - Interview with Abhishek Chaudhary It's cool to write small web applications for the sake of learning. You can set the boundaries yourself and experiment with new technologies. Abhishe… Published: 19.1.2021 Nullstack - Full-stack JavaScript Components - Interview with Christian Mortaro If you look into what happened during the past few years in the world of JavaScript, you can see that component thinking made it to the mainstream. Ev… Published: 15.1.2021 Preloading Web Assets Preloading data is useful yet perhaps underused web development technique. When it comes to performance, the best work is the one you don't have to do… Published: 8.12.2020 CV Compiler - The Fastest Way to Improve Your CV - Interview with Andrew Stetsenko When you apply for a new position or a business case, often people want to see your CV (Curriculum Vitae). Although it sounds simple to create one, it… Published: 1.12.2020 "SurviveJS - Webpack 5" - Amazon Version is Available Doing a paper release of a book comes with additional thrill as once you go paper, there's no going back. Any mistakes you might have in the book are … Published: 27.11.2020 Plasmic - The fast and fun visual builder for React - Interview with Yang Zhang Developing user interfaces with React tends to require effort and often it's done at the level of code. What if we could create user interfaces in the… Published: 16.11.2020 Multi-platform applications with JavaScript - Interview with Valentyn Poliskyi Developing multi-platform applications is difficult. Thankfully the advent of JavaScript has made it a possibility for an increasing amount of develop… Published: 9.11.2020 Rockpack - Skip config, code React - Interview with Sergey Aleksandrov As you might know, configuring webpack isn't the most fun thing in the world and that's exactly the reason why I wrote a thick book about it. For man… Published: 2.11.2020 "SurviveJS - Webpack 5" - Further webpack 5 updates Webpack 5 has been available for a couple of weeks by now. The previous release of the book covered majority of the required changes but I realized th… Published: 30.10.2020 End-to-end testing - Interview with Erik Fogg Testing is topic that comes up often in software development as it's an important part of verifying what we did works. That said, it's a complex topic… Published: 29.10.2020 Algolia with Netlify - Easy search for static sites - Interview with Samuel Bodin Setting up and maintaining a search on a static site is often a chore. You could handle indexing yourself using a solution like Lunr but even with tha… Published: 19.10.2020 Ukrainian developer market - Interview with Eliza Kravchenko I've encountered many Ukrainian developers during my career and even visited the country a couple of times speaking at conferences. During each trip, … Published: 12.10.2020 Eleventy - A simpler static site generator - Interview with Jeremias Menichelli Static site generation is a topic that is becoming increasingly popular due to the rise of JAMStack. Instead of maintaining a server, the idea is to g… Published: 5.10.2020 How to learn effectively as a developer I recently received an interesting question from a reader that changed his career path and headed to technology. He mentioned he was getting overwhelm… Published: 24.9.2020 Pipcook - Bridging JavaScript with Python for machine learning - Interview with Wenhe Li There's a lot of excitement about machine learning and its applications. The question is, what can you do with and where to apply the technique and ho… Published: 14.9.2020 NoCode programming - Doing more with less code - Interview with Alex Moldovan What if you could create programs without coding? If you've ever used something like Microsoft Excel or Google Sheets, you've already done this at one… Published: 7.9.2020 ExtendsClass - Online Tools for Developers - Interview with Cyril Bois One of the great things about being a developer is that you can literally create your own tools to make it easier to do your work. Cyril Bois has bee… Published: 3.9.2020 "SurviveJS - Webpack" book updated to webpack 5 Webpack 5 is getting near and it felt like a good time to update the book. Although it's still in beta, it seems quite stable already and it's worth e… Published: 28.8.2020 Midway - A Node.js framework for Serverless - Interview with Harry Chen Serverless computing is one of those approaches that has taken the world by storm. The idea is to make computing a flexible resource you consume on-de… Published: 24.8.2020 Enroute - Envoy Route Controller - Interview with Chintan Thakker When developing APIs, you often get questions like how to combine and control data coming from different sources. That's where proxy-based approaches … Published: 12.8.2020 Detox - Testing React Native - Interview with Mykola Solopii Testing mobile applications is a tough topic as you have to worry about different devices, and the interaction model is challenging. Detox is a solut… Published: 6.8.2020 Synthetics - Monitor availability and performance of your website and APIs - Interview with Siva Kaliappan Anything you don't measure or test, you cannot improve. The wisdom applies particularly to web as we develop our websites and applications. Without an… Published: 18.6.2020 JavaScript Security - Interview with David Balaban Given JavaScript dominates the world of web development, it has become a good target for malicious actors. Furthermore, the flexibility has led to a p… Published: 28.4.2020 MonoLisa - Font follows function - Interview with Marcus Sterz As a developer, font is something you end up using every day at your work. One year ago I teamed up with Andrey Okonetchikov and Marcus Sterz, to crea… Published: 10.3.2020 Debugging JavaScript - Interview with Mehdi Osman Debugging JavaScript is one of those topics where people tend to be divided into two camps - those that console.log and those that use a debugger. In… Published: 4.3.2020 React Cosmos - A development environment for ambitious developers - Interview with Ovidiu Cherecheş Developing user interfaces can be complex as you have to think about different ways it's going to be used and you have to design patterns and componen… Published: 13.2.2020 Webix - Declarative UI Framework for Rapid Development - Interview with Maksim Kozhukh If there's something that has changed during the past few years, it's the way we develop user interfaces using JavaScript. Earlier we've learned about… Published: 7.2.2020 VPNpro - How do VPNs work - Interview with Olivia Scott If there's one web technology I never looked that much into, it's VPNs (Virtual Private Networks). In these times when privacy is more valued than eve… Published: 28.1.2020 Squareboat - Growing an IT Business - Interview with Gaurav Gupta What is it like to grow an IT business? At least in my experience, it's not the easiest thing to do, and there are many things you have to get right t… Published: 16.12.2019 Tomo - Like CRA but more flexible - Interview with Jason Wohlgemuth Although tools like create-react-app (CRA) are great, they can at times be inflexible. They might provide great defaults but at the same time you lose… Published: 4.9.2019 Secure Coding - Interview with Liran Tal There's more than one way to code, and you'll find multiple programming styles. One aspect that's perhaps neglected sometimes is secure coding. To le… Published: 31.7.2019 Experiences on CSSCamp and JSCamp 2019 I was invited to CSSCamp 2019 (17.07) and JSCamp 2019 (18-19.07) by David Pich, the main organizer, to help out. I performed speaker interviews and a … Published: 27.7.2019 Sketch.sh - Interactive ReasonML sketchbook - Interview with Nguyen Dang Khoa Often learning a new programming language like ReasonML can be an arduous process as you have to set up the environment and tooling before you can beg… Published: 16.7.2019 Experiences on WorkerConf 2019 I was invited to WorkerConf 2019 (27-28.06) as a speaker. I also participated a workshop and went hiking after the conference. It was a small-scale co… Published: 2.7.2019 Minima - To-do lists done right - Interview with Alex Fedoseev If there's one thing that transformed my life, it's the adoption of the Getting Things Done (GTD) methodology. The key part for me was to begin what's… Published: 17.6.2019 Reakit - Build accessible rich web apps with React - Interview with Diego Haz When building web applications and sites using React, you have to think carefully about the user interface. You might either go with an established us… Published: 10.6.2019 Benefit - utility CSS library - Interview with Chad Donohue One of the developments that has began to change the way we style our applications and sites is the introduction of utility classes. Tailwind is an ex… Published: 3.6.2019 Webpack UI - Configure webpack with a UI - Interview with Even Stensberg Webpack is infamous for being a bundler that's not entirely easy to configure. That's one of the main reasons why I wrote the webpack book available o… Published: 31.5.2019 ReasonML - Type safety with ease - Interview with Gabriel Rubens I've had the chance to observe the evolution of the ReasonML ecosystem up close. For me, it seems to solve many pain points of the current JavaScript/… Published: 27.5.2019 Express Gateway - A microservices API Gateway built on top of Express.js - Interview with Vincenzo Chianese If you are dealing with microservices, you get questions like how to manage and orchestrate them. Vincenzo Chianese has come up with a solution desig… Published: 22.4.2019 Experiences on typeof 2019 I was invited to typeof 2019 (27-29.03) as a speaker and a workshop instructor. It was a small-scale conference (about 200 people) held in Porto, Port… Published: 6.4.2019 Functional Programming - Interview with Arfat Salman If there's one programming style I like a lot, it's functional programming. Although it's not the best fit for all problems, often having means to dec… Published: 5.4.2019 Dredd - Language-agnostic HTTP API Testing Tool - Interview with Honza Javorek If there's one thing developers have to deal with most of the days, it's APIs. For web developers, this often means dealing with HTTP and external ser… Published: 22.3.2019 Managing css-in-js Components with Namespaces I've settled on using Emotion for styling my React applications. The API is close to styled-components and especially Emotion 10 is filled with functi… Published: 19.3.2019 atomic-layout - Layout composition as a React component - Interview with Artem Zakharchenko Often layouting a web page is an afterthought. Put a div here and there, sprinkle some CSS, and call it done. Perhaps you are more advanced and use CS… Published: 15.3.2019 Pesto - A career accelerator for India’s top software engineering talent - Interview with Andrew Linfoot One of the unique aspects of the internet is that it makes us all equal in a strange way. What it means is that collaboration is possible on a new lev… Published: 8.3.2019 Codecrumbs - Document a Codebase by Breadcrumbs - Interview with Bohdan Liashenko Developers spend most of their time reading and understanding code. That said, not much has changed in the past decades in the way we do it. Perhaps t… Published: 1.3.2019 packtracker.io - Webpack bundle analysis, for every commit - Interview with Jonathan D. Johnson When using webpack to bundle your project, it's important to keep an eye on the output. There are multiple tools for this purpose. Now there's also a … Published: 22.2.2019 Overmind - Frictionless State Management - Interview with Christian Alfoni Although state management solutions like Redux have become the standard, at least with React, there's still room for innovation in the space. Sometim… Published: 15.2.2019 webpack-config-plugins - Best practices for webpack loader configurations - Interview with Jan Nicklas Managing webpack configuration can get tough especially if you try to track best practices and optimizations. To address this problem, Jan Nicklas ha… Published: 18.1.2019 SurviveJS - Summary of 2018 2018 was mostly a consulting year for me. I also did travel within Europe and discovered countries such as Croatia and Armenia. It was my first year a… Published: 3.1.2019 webpack-plugin-serve - A Development Server in a webpack Plugin - Interview with Andrew Powell Usually, when you use webpack, you also have to set up its development server as well. Traditionally doing this hasn't been trivial and has required a… Published: 13.12.2018 React Union - React for CMSs and Portals - Interview with Tomáš Konrády React has uses beyond application development. One of the perhaps surprising use cases is to integrate it within a Content Management System (CMS) suc… Published: 2.12.2018 Unicon - Wrangle SVGs from your favorite design tool - Interview with Travis Arnold So far design and development have been considered separate disciplines. Recently tooling has begun to appear to bridge this gap. To understand more … Published: 26.11.2018 Experiences on HalfStack London 2018 I was invited to HalfStack London 2018 as a guest as we are considering bringing the conference series to Vienna. Therefore it was vital for me to get… Published: 18.11.2018 React India 2019 - The international React.js conference in Goa, India - Interview with Manjula Dube It is exciting to organize a conference, especially when it's the first of its kind in a region. To learn more about one such event, I'm interviewing … Published: 11.11.2018 Experiences on WebCamp Zagreb 2018 I was invited to WebCamp Zagreb as a speaker and a workshop trainer. I gave one of my webpack workshops at the event and discussed static websites and… Published: 10.10.2018 Experiences on WebExpo 2018 I was invited to WebExpo 2018 as a visitor since I spoke at the conference last year. Prague is one of my favorite cities in Europe, and the conferenc… Published: 24.9.2018 Refract - Manage Component Side Effects the Reactive Way - Interview with Thomas Roch. It's difficult to write an application without side effects. Consider handling requests, dealing with third parties, managing storage for example. The… Published: 16.9.2018 DSS - Deterministic Style Sheets - Interview with Giuseppe Gurgone CSS is perhaps one of the most controversial parts of web development. For some, it's the favorite, for some the least pleasant part. As a result, man… Published: 5.9.2018 SurviveJS - Fall Events Summer is over and I've made travel plans for the Fall. More details below. WebExpo - 21-23.09.2018 WebExpo 2018 I went to WebExpo last year for th… Published: 4.9.2018 Uppy - Painless Uploads for JavaScript - Interview with Artur Paikin Let's say you are building a CMS or a blog with an admin interface. It won't take long until you want to upload files to your service. There are stand… Published: 17.7.2018 GraphQL Finland - Learn GraphQL Up North - Interview with Mikhail Novikov Following the success of React Finland, we decided to organize another event this year. GraphQL Finland has a different scope, and it's going to be th… Published: 5.7.2018 Progressive Web Apps - The Why and How - Interview with Maciej Caputa Even though the web started from content, it has transformed into an application platform. Approaches like Progressive Web Apps are a clear sign of th… Published: 25.6.2018 Proppy - Functional props composition for components - Interview with Fahad Ibnay Heylaal You might be familiar with packages like Recompose that make it easier to compose components. Recompose is React-specific solution. What if there was … Published: 22.6.2018 SurviveJS - Summer Events Summer is a great time to travel and see new places. So far I've scheduled three events for the Summer although more may appear depending on the publi… Published: 30.5.2018 Fastpack - Pack JavaScript code fast and easy - Interview with Oleksiy Golovko Tools like browserify and webpack popularized the idea of bundling. The idea is to transform your web application into a format that can be distribute… Published: 29.5.2018 lint-staged - Run Linters on git Staged Files - Interview with Andrey Okonetchnikov Although linting a project is a good technique to adopt, it comes with a cost as you have to wait for the linter to complete its work. Andrey Okonetc… Published: 8.4.2018 "SurviveJS - Webpack" book updated to webpack 4 Quite a bit has happened in the world of webpack. Most notably, the webpack reached version 4 recently. The purpose of this release of the book is to … Published: 19.3.2018 Webpack in Munich, May 2018 In addition to writing and consulting, I do occasional training. Most often it's around my webpack book and it supports different levels of sessions w… Published: 17.3.2018 Experiences on Concat 2018 I participated Concat 2018 at Salzburg this year. I held a four-hour webpack workshop with Tobias Koppers, the author of the tool, and visited the eve… Published: 5.3.2018 Verdaccio - A lightweight npm proxy registry - Interview with Juan Picado If you develop JavaScript applications, you most likely use npm, the most famous package manager available for JavaScript. At the time of writing, it … Published: 26.2.2018 Parket - A state management library inspired by mobx-state-tree - Interview with Leah Ullmann State management is one of those topics that divides opinions. So far we've seen a couple of options so far. In this post, we'll cover Parket, a solu… Published: 16.2.2018 substyle - Build Styling Agnostic Components for React - Interview with Jan-Felix Schwarz One of the tricky things about writing React components meant for public consumption is making them compatible with various styling approaches used by… Published: 8.2.2018 Experiences on AgentConf 2018 I was invited to AgentConf 2018 on its second iteration about a month ago as one of the organizers saw a presentation of mine about npm packaging. I g… Published: 6.2.2018 Experiences on ScriptConf 2018 One of the benefits of living in Vienna is that it's easy to reach central Europe and its conferences. Given Linz is close to Vienna (about 90 minutes… Published: 1.2.2018 Illuminate - Syntax highlighter for Node - Interview with Vivek Bansal One of the core features of this site is custom syntax highlighting. I had to figure out ways to deal with custom syntax provided by Leanpub. Initiall… Published: 30.1.2018 Logux - Replace AJAX-REST - Interview with Andrey Sitnik When you build a web application, you often have to communicate with a backend. It's not uncommon to do this using AJAX against a RESTful API. Logux … Published: 26.1.2018 Fastify - Fast and low overhead web framework for Node.js - Interview with Tomas Della Vedova Servers, servers, servers. I've written a lot of Node.js servers since I began using it. Initially, I went through the API it provides but after a whi… Published: 17.1.2018 BEM - Methodology to enable reuse in front-end development - Interview with Sergey Berezhnoy Developing large scale applications requires a certain amount of discipline. Sometimes it is enforced by the environment; sometimes you have to apply … Published: 12.1.2018 SurviveJS - Summary of 2017 It was quite a year for me. You could say a life-changing one even. I visited at least ten countries in Europe, and most of them were new acquaintance… Published: 31.12.2017 controllerim - MobX Inspired State Management for React - Interview with Nir Yosef When you are writing applications, eventually you have to decide how to manage state. You can get far with React setState and lift the state in the co… Published: 27.12.2017 React Finland - Your Chance to Learn React Up North - Interview with Juho Vepsäläinen There are a lot of React conferences these days. React has become one of the most popular web technologies during the past few years so this is unders… Published: 23.12.2017 redux-saga-test-plan - Test Redux Saga with an easy plan - Interview with Jeremy Fairbank Redux Saga is famous for being easy to test but what if it could be even more comfortable. redux-saga-test-plan by Jeremy Fairbank was designed precis… Published: 20.12.2017 Redux Form - The best way to manage your form state in Redux - Interview with Erik Rasmussen Forms are a frequent topic in web development as we saw in the earlier interview about a-plus-forms. This time around, I'm interviewing Erik Rasmussen… Published: 11.12.2017 Redux Zero - Single Store, No Reducers - Interview with Matheus Lima Although using Redux is straight-forward once you understand the approach and its nuances, after a while it gets repetitive. It's easy to end up with … Published: 4.12.2017 Flow Runtime - A runtime type system for JavaScript with full Flow compatibility - Interview with Charles Pick As discussed in the maintenance book, typing your code can be valuable in many ways. In part, it's about communication. Having the type information av… Published: 26.11.2017 a-plus-forms - A+ forms. Would use again - Interview with Nikolay Nemshilov If you think about it, a lot of web development has something to do with forms. Every time you capture information, you most likely require a form. It… Published: 20.11.2017 “SurviveJS — Webpack” v2.1 and “SurviveJS — Maintenance” v0.9 What do you do when you realize a book has become too big? You split it of course. The webpack book began to feel this way after the previous release … Published: 17.11.2017 Cabbie - WebDriver for the masses - Interview with Forbes Lindesay Testing is a lasting topic in software development. There are lots of tools, especially for JavaScript. In this interview, you'll learn about Cabbie, … Published: 13.11.2017 react-lite - Implementation of React optimized for small size - Interview with Jade Even though React API is small, the implementation is quite sizable due to all the work it does behind the façade. For this reason, people have develo… Published: 6.11.2017 React Day Berlin - Fully Packed Day of Your Favorite React Content - Interview with Robert Haritonov There are a lot of React events out there these days and it seems a new one appears every week somewhere around the world. To continue on the theme, … Published: 17.10.2017 unexpected-react - Test Full Virtual DOM - Interview with Dave Brotherstone Testing React components is a constant topic. You can test through solutions like Jest or Enzyme. Or you could try something else like unexpected-reac… Published: 29.9.2017 Experiences on WebExpo 2017 I was invited to WebExpo 2017 to discuss how I bootstrapped my business. Prague is one of the favorite cities of mine, so it was hard to say no. I'm h… Published: 24.9.2017 Kea - High level abstraction between React and Redux - Interview with Marius Andra Redux took the React world by a storm when it was introduced. The simple idea provided a guideline for the community and "solved" state management for… Published: 18.9.2017 Experiences on React Next 2017 I had the privilege to participate in React Next 2017 as an invited speaker. Participation gave me a good chance to learn more about Israel and also a… Published: 15.9.2017 FrintJS - Build reactive applications with React and RxJS - Interview with Fahad Ibnay Heylaal React gives a lot of freedom by default. You can choose which libraries to use to complement it. Freedom comes with responsibility, though. Now you ar… Published: 6.9.2017 Neutrino - Create modern JavaScript applications with minimal configuration - Interview with Eli Perelman Setting up a project can require a significant amount of effort if you want to control every single detail. This might be one reason why there are so … Published: 28.8.2017 Idyll - Narratives for the web - Interview with Matthew Conlen Since the early days of the web, people have wanted to visualize data to share with others. Even though the platform provides something basic for thes… Published: 21.8.2017 Motorcycle.js - A statically-typed, functional and reactive framework for modern browsers - Interview with Tylor Steinberger Functional reactive programming allows us to think carefully about state and side effects. The question is, how to do that in JavaScript? Motorcycle.… Published: 18.8.2017 Next.js - Framework for server-rendered React apps - Interview with Arunoda Susiripala Building universal web applications combining server side rendering with front-end is popular these days. The approach is not without its problems, th… Published: 15.8.2017 Rekit - Toolkit for building scalable React applications - Interview with Nate Wang Perhaps the greatest thing about React is how flexible it is. It contains some opinions but not too many. You still have plenty of freedom. Sometimes … Published: 9.8.2017 Redux-First Router - Just dispatch actions - Interview with James Gillmore Routing is one of those classic topics that comes up again and again. HTML5 History API itself is quite simple, but there are different opinions on ho… Published: 7.8.2017 documentation.js - The documentation system for modern JavaScript - Interview with Tom MacWright When you are using a library seriously, you will spend a lot of time with its documentation. It's one of those things that sets good libraries apart f… Published: 31.7.2017 Rill - Universal web application framework - Interview with Dylan Piercey There's a lot of talk about universal web applications but developing them tends to be harder than it might sound. You will have to worry about the di… Published: 28.7.2017 d-l-l - Easy, automatic, optimized DLL config handler for webpack - Interview with James Wiens Perhaps one of my favorite webpack performance related tricks is setting up DLLs so that you avoid work. The problem is that maintaining the setup req… Published: 24.7.2017 Material-UI - React Components that Implement Google's Material Design - Interview with Olivier Tassinari Design is difficult as you have to come up with a set of rules to describe it – a system. You don't always have to devise one yourself, and Material D… Published: 21.7.2017 Fall Tour - Vienna Clinics, ReactNext, WebExpo, ReactiveConf Even though I have traveled a lot this year already, it looks like more travel is in store. The travels so far have been valuable regarding experience… Published: 19.7.2017 dont-break - Check if you break dependents - Interview with Gleb Bahmutov Releasing new versions of npm modules is an npm publish away. But how do you make sure you don't accidentally break a dependent project? Even if you a… Published: 17.7.2017 Rollup - Next-generation ES6 module bundler - Interview with Rich Harris Given JavaScript application source cannot be consumed easily through the browser "as is" just yet, the process of bundling is needed. The point is to… Published: 10.7.2017 JSS - Author CSS Using JavaScript as a Host Language - Interview with Oleg Isonen If there's one thing that divides web developers, it's styling. A part of this has to do with the different requirements of websites and web applicati… Published: 7.7.2017 renovate - Keep npm dependencies up-to-date - Interview with Rhys Arkins There's one pain most JavaScript developers share - dependency management. More specifically, how to keep them up to date. Sometimes even one month is… Published: 3.7.2017 Most.js - Monadic streams for reactive programming - Interview with Brian Cavalier If there's one trend that has been nice to notice, it's the rise of reactive programming. You can see this in technologies like RxJS and cycle.js. To… Published: 26.6.2017 React Alicante - The international React.js conference in Spain - Interview with Victoria Quirante There are plenty of events out there. What is it like to organize one? I know it's hard work based on what I've seen. To get more perspective, I'm in… Published: 23.6.2017 Hard-cover Edition of the Webpack Book and Training Print on Demand services like KDP are ideal for self-publishers like me as they take a lot of pain out of the process. You don't have to worry about p… Published: 22.6.2017 Working with Junior Developers - Interview with Aimee Knight Even though software development is often seen from a technical perspective, there's a softer side to it. It is hard to avoid not having to work with … Published: 20.6.2017 vx - The Power of D3 with the Benefits of React - Interview with Harrison Shoff Data visualization is a big topic itself. When it comes to the web, D3 is perhaps the most well-known solution. Even though you can wrap it with React… Published: 12.6.2017 unmarshaller - Toolbox for configuration - Interview with Sven Sauleau Serialization, or the process of transforming data from a shape to another, is a common problem you encounter eventually when programming. Perhaps you… Published: 5.6.2017 Popper.js - Easy Tooltips and Popovers - Interview with Federico Zivolo There are times when a vanilla ` or ` doesn't cut it. What if you want to do something more complex? Popper.js by Federico Zivolo achieves exactly th… Published: 29.5.2017 SurviveJS Euro Summer Tour 2017 It's time for another tour. This time around I'll be focusing on training. I have material specifically for webpack and React and this will be a good … Published: 28.5.2017 ES Modules - Interview with Bradley Farias Even though ES6 (ES2015) brought modules to the language, it missed one important thing - a loading method. Proper support is currently being implemen… Published: 22.5.2017 Blue Arrow Awards - Finnish Code Ambassador of 2017 In the beginning, there was a swamp, a hoe, and Jussi. Originally a large part of Finland was swamp and life were hard, but as Jussi worked on the swa… Published: 21.5.2017 async-reactor - Render Async Stateless Functional Components in React - Interview with Sven Sauleau One common way to deal with asynchronous concerns (fetching for example) in React is to push the problem to a state manager or handling it through lif… Published: 15.5.2017 WebpackBin - Webpack Code Sandbox - Interview with Christian Alfoni Online tools are great for prototyping ideas and even workshops. You avoid the pain of setup while giving up some degree of control. Often this is a g… Published: 9.5.2017 SurviveJS Euro Tour 2017 Recap In this post, I will go through the biggest realizations gained in my Euro tour. I know it's a cliché thing to say, but trips like this grow you as a … Published: 3.5.2017 Fluture - Fantasy Land compliant alternative to Promises - Interview with Aldwin Vlasblom Dealing with the asynchronous code has always been a challenge in JavaScript. Callbacks are the classic way, and since then we've gained higher level … Published: 2.5.2017 CodeSandbox - Online React Playground - Interview with Ives van Hoorne Getting started with React can be daunting especially if you want to understand the entire setup. Solutions like create-react-app have hidden a lot of… Published: 24.4.2017 Scrimba - Interactive Screencasts Created in an Instant - Interview with Per Harald Borgen YouTube and the web are filled with screencasts. They provide a great way to learn difficult concepts as you can see in practice how something specifi… Published: 17.4.2017 SurviveJS - Webpack - v2.0 - Results and Errata Enough time has passed since the major release of the webpack book so it's a good time to evaluate how well it went. As no release is perfect, I've be… Published: 12.4.2017 Sanctuary - Refuge from unsafe JavaScript - Interview with David Chambers If there's something that's easy, it's making mistakes while coding JavaScript. Overlook one detail and you have a runtime error! One way to deal with… Published: 10.4.2017 Rambda - Faster and Smaller Alternative to Ramda - Interview with Dejan Toteff Even though you can get far with JavaScript's native functionality, eventually you'll find yourself writing little utilities to make it easier. For th… Published: 3.4.2017 SurviveJS - Webpack - v2.0 Here we go then. This is the big release I've been working towards for the past few months. Compared to the previous release this one is more polished… Published: 29.3.2017 Hyperapp - Tiny Library for Frontend Applications - Interview with Jorge Bucaran Micro-sized JavaScript libraries are a niche of their own. Often the idea is to use modern JavaScript APIs and expose them in an easier way. The earli… Published: 13.3.2017 SurviveJS Euro Tour 2017 You know how rockstars tour to support their albums? Who is to say a book author could not do the same? Through a couple of coincidences, it looks li… Published: 10.3.2017 Code Quality - Interview with João Caxaria What makes code good? How do you tell bad code from good one? Issues like this come to mind when you think about the concept of code quality. To get a… Published: 6.3.2017 SurviveJS - Webpack - v1.9 If the previous release was a big step, this is another one. By the looks of it, the final paper version will be around 450 pages. Don't worry, though… Published: 1.3.2017 SurviveJS - Webpack - v1.8 Compared to the previous release this one has gained more weight. The PDF version of the book is close to 400 pages due to new content and enhancement… Published: 18.2.2017 SurviveJS - Webpack - v1.7.0 Compared to the previous release we've proceeded a step or two closer towards paper. This time around in addition to the usual tweaks there are a coup… Published: 4.2.2017 Unexpected - The Extensible BDD Assertion Toolkit - Interview with Sune Simonsen When it comes to testing, often you assert certain truths. At the very least you might have simple asserts sprinkled in your code. Or you might push … Published: 30.1.2016 ajv - The Fastest JSON Schema Validator - Interview with Evgeny Poberezkin Describing what things are is an essential skill for a programmer. We might do that implicitly, but we often have to think about structure regardless.… Published: 23.1.2017 SurviveJS - Webpack - v1.6.0 You might have noticed that webpack 2 reached a final release. That means it's a good time to update this book as well. Even though it's mostly a main… Published: 19.1.2017 isomorphic-webpack - Universal module consumption using webpack - Interview with Gajus Kuizinas A lot of people see isomorphic rendering as a holy grail given it gives advantages a SPAs lost compared to earlier solutions. The fact that you can pr… Published: 10.1.2017 SurviveJS - Webpack - v1.5.0 New year, new chance to write. The previous release put the writing gear back on and it's time to continue. This time around there are quite a big cha… Published: 3.1.2017 Styletron - Universal, high-performance JavaScript styles - Interview with Ryan Tsao Styling is one of those topics that's under flux. My React styling chapter alone covers quite a few approaches and Michele Bertoli's list has a lot mo… Published: 26.12.2016 SurviveJS - Webpack - v1.4.2 Alright, here we go again. It has been a while since the previous release and it's time for a big Winter update! Quite a bit has happened since. I sp… Published: 19.12.2016 Inferno - Blazing fast, React-like UI library - Interview with Dominic Gannaway One of the cool things about React is that it managed to pull a lot of people into the component world. Even though there was initial resistance, the … Published: 12.12.2016 Svelte - The magical disappearing UI framework - Interview with Rich Harris If jQuery gave us proper control over the DOM, and React brought components to the limelight, what's next? Svelte by Rich Harris might be an answer to… Published: 7.12.2016 webpack-merge - Taming Webpack Configuration - Interview with Juho Vepsäläinen It's almost funny how far a simple idea can fly sometimes. When writing my first book, I ran into the problem of configuring webpack. I prefer to keep… Published: 29.11.2016 StarRatio - Compare JavaScript Projects - Interview with Dmitry Zaets Comparing different JavaScript projects is surprisingly tough. This is a problem encountered by many developers daily. Most often it's the easiest to … Published: 14.11.2016 RE:DOM - Tiny but Super Fast DOM Library - Interview with Juha Lindstedt Sometimes small is beautiful. Juha Lindstedt's FRZR, a 4kB view library, was a nice example of that as we saw earlier. This time we'll discuss evoluti… Published: 31.10.2016 Glamor - Inline CSS for React et al - Interview with Sunil Pai If you ask multiple React developers their styling approaches, you will also get multiple different answers. One trend is clear, though, the movement … Published: 17.10.2016 Teaching JavaScript - Interview with Bianca Gandolfo I have chosen one approach when it comes to teaching JavaScript and related topics. Books are just a way amongst many others. Today I'm interviewing a… Published: 3.10.2016 react-game-kit - Make games with React - Interview with Ken Wheeler What's more fun than making applications with React? Making games of course! I remember coding Pong in Python (harder than it sounds) and writing a te… Published: 26.9.2016 Reactotron - A CLI and OS X App for Inspecting - Interview with Steve Kellock If there's one thing that has set React community apart, it's the focus on developer experience (DX). Historically developer tools haven't been the gr… Published: 19.9.2016 Reactabular - Spectacular tables for React - Interview with Juho Vepsäläinen Writing a little HTML table isn't particularly hard. It all gets more complex when you need logic like filtering, pagination, or fixed headers. A simp… Published: 12.9.2016 Assetgraph - Optimization Framework for Web Pages and Applications - Interview with Peter Müller If you have written a web application or site, you have had to deal with various assets like images, fonts, HTML, JavaScript code, whatnot. It's not a… Published: 5.9.2016 PureScript - Strongly Typed Programming Language Compiling to JavaScript - Interview with Phil Freeman It's interesting how JavaScript development proceeds in cycles. While a lot of people might be happy with the standard language, there are always some… Published: 22.8.2016 CodeceptJS - Modern Era Acceptance Testing for Node.js - Interview with Michael Bodnarchuk Testing is a complicated topic. Just peppering your code with unit tests isn't often enough. You'll need something more, especially if you are develop… Published: 15.8.2016 Mostly Adequate Guide to Functional Programming - Interview with Brian Lonsdorf You might have heard about Mostly Adequate Guide to Functional Programming (in JavaScript) by Brian Lonsdorf. It's one of the better known free books … Published: 1.8.2016 tcomb - Type checking and DDD for JavaScript - Interview with Giulio Canti Given JavaScript is loosely typed, it can be amazingly productive language for prototyping. The problems begin once your project grows in complexity. … Published: 25.7.2016 redux-saga - Saga Middleware for Redux to Handle Side Effects - Interview with Yassine Elouafi When developing front-ends, handling asynchronous behavior is always bit of a challenge. Yassine Elouafi's redux-saga provides one solution to this pr… Published: 18.7.2016 Snabbdom - a Virtual DOM Focusing on Simplicity - Interview with Simon Friis Vindum If you have been using React, you have used one implementation of virtual DOM perhaps without thinking too much about it. It's one of those concepts t… Published: 11.7.2016 SurviveJS - Webpack - v1.3.1 Compared to the previous release this is a conservative release. There are certain bug fixes and content improvements, but no new chapters. The focus … Published: 14.6.2016 npms.io - A better and open source search for node modules - Interview with André Cruz As I lamented earlier this year, it's increasingly difficult to find npm packages. One way to describe this is npmopeia. The feeling that the package … Published: 13.6.2016 Mikey - React/Redux CLI/Framework - Interview with Michael Farrell It is tedious and boring to do the same thing over and over. That's where generator tools come in as they take some grunt work out of coding. Mikey by… Published: 6.6.2016 SurviveJS - React - v2.5.3 It has been a while since the previous release and a lot has happened. In addition to ramping up my consulting and training business, I managed to pub… Published: 1.6.2016 Builder - A npm-based task runner - Interview with Ryan Roemer Builder by Formidable Labs is one of those projects tackling the boilerplate issue. It is a project that repurposes npm scripts into something more po… Published: 16.5.2016 SurviveJS - Webpack - v1.2.0 As I've been working towards splitting the first book, I realized I must do one more release of this webpack one before I can complete it. That's what… Published: 11.5.2016 nwb - CLI for React Applications and Components - Interview with Jonny Buchanan Boilerplate code is perhaps one of the leading causes of JavaScript fatigue. You often have to go through certain motions to set up a project or maint… Published: 9.5.2016 Kotatsu - Less Boilerplate for Modern JavaScript - Interview with Guillaume Plique npm alone has more than three thousand JavaScript boilerplates. Often it's easier to maintain your own than to use one designed by someone else. Every… Published: 2.5.2016 Hashnode - Community for Software Developers - Interview with Sandeep Panda One of the challenges of being a web developer is keeping up with the world. The field moves ahead constantly and it's easy to fail to see the forest … Published: 25.4.2016 SurviveJS - Webpack - v1.1.0 Compared to the first release a couple of weeks ago, this version has matured quite a bit. I've been reviewing the content with my editor (thanks Jesú… Published: 24.4.2016 FRZR - a Tiny View Library - Interview with Juha Lindstedt Often when you pick up a JavaScript library it's going to be a little chunky - tens, or even hundreds of kilobytes. Though this can be entirely accept… Published: 18.4.2016 SurviveJS - Webpack and React - v2.1.0 It has been a while since the previous release and quite a bit has happened. As you might have noticed, there's actually a new book about webpack out … Published: 17.4.2016 Relax - New generation CMS on top of React and Node.js - Interview with Bruno Mota Even though I've spent a lot of time with web development, I never really delved into the world of Content Management Systems (CMS). I'm of course awa… Published: 11.4.2016 SurviveJS - Webpack - v1.0.0 I'm currently in process of splitting up the big book (SurviveJS - Webpack and React). The split allows me to dig deeper in both topics. This book, Su… Published: 2.4.2016 React.rocks - React Components and Demos - Interview with Jeff Winkler Given there's a lot going on in the React ecosystem, it can be difficult to keep up. Jeff Winkler maintains a service known as React.rocks to alleviat… Published: 14.3.2016 Reindex - Instant GraphQL Backend for Your React Apps - Interview with Ville Immonen More often than not, you are going to need a back-end for your application. Particularly RESTful APIs are popular. They are not the only choice, thoug… Published: 7.3.2016 SurviveJS - Learn Webpack and React - Interview with Juho Vepsäläinen There is always some level of tension between getting things done and learning new technologies. A lot of the recent JavaScript fatigue stems from tha… Published: 29.2.2016 react-styleguidist - Style guide generator for React - Interview with Artem Sapegin People have been developing style guides for their sites and applications for quite a while. They define basic building blocks and aesthetics. This is… Published: 22.2.2016 SurviveJS - Webpack and React - v2.0.0 When I started this project roughly a year ago I had no idea how rewarding and demanding one it would be. Writing books is way harder than it sounds. … Published: 15.2.2016 SurviveJS - Webpack and React - v2.0.0-rc4 The previous release candidate prompted a nice amount of feedback. I've taken that into account in this release. I have a date for the final in sight … Published: 7.2.2016 Towards a Common Component Definition There has been talk of JavaScript fatigue. It's true the field is progressing fast. And as you move fast, it can be tiring for sure. Fortunately, as w… Published: 2.2.2016 SurviveJS - Webpack and React - v2.0.0-rc3 If the previous release candidate had few changes, this one is the opposite. I consider this good news as it's better to catch bigger issues now rathe… Published: 22.1.2016 SurviveJS - Webpack and React - v2.0.0-rc2 Not a lot has happened since the previous release cand | 2026-01-13T08:48:42 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#status-categories | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:42 |
https://perlweekly.com/archive/755.html | Perl Weekly Issue #755 - 2026-01-12 - Does TIOBE help Perl? Perl Weekly Issue #755 - 2026-01-12 - Does TIOBE help Perl? latest | archive | edited by Gabor Szabo This edition was made possible by the supporters of our cause . Don't miss the next issue! Enter your e-mail: --> --> Hi there! Dave Cross has an article showing position of Perl on the TIOBE index. As I don't see any up-tick in new subscribers to the Perl Weekly nor do I see any increase in the MetaCPAN activity I keep track of, I doubt that the changes in the position reflects actual changes in the market. However I wonder, could the TIOBE index have an impact on the interest in Perl? How and when could we see that? Speaking of the MetaCPAN report , I'd love if someone sent a PR to the Perl Weekly that would generates same graphs using these numbers. Here is the issue for it. And another comment related to those stats. I just noticed that the No CI column went up from 30-40% to 80-90% in recent weeks. I wonder why? Is it because some changes in the way I am collecting the data or are those real changes? Is it real change? I also just noticed some negative numbers in the No VCS (%) column. That's not good. I guess I have to investigate this. Maybe during one of the Perl code reading and open source contribution events. Enjoy your week! Gabor Szabo Announcements New York Perlmongers (NY.PM) by James E Keenan New York Perlmongers ( NY.PM ) has a new mailing-list organized as a Google Group. Sign up here . (Note: we are not doing unrequested transfers from our previous mailing list.) NY.PM social event: Thursday, January 15, 6:00 pm EST at Barcade, 148 West 24 St, Manhattan: send-off for a long-time member returning to the U.K. ANNOUNCE: Perl.Wiki V 1.37 by Ron Savage ( RSAVAGE ) Get it, as usual, from his Wiki Haven . Articles Marlin Racing by Toby Inkster ( TOBYINK ) Which of the 7 OOP frameworks of Perl is the fastest? The Perl Claude Agent by Robert Acock It's a library that brings the agentic capabilities of Claude Code into your Perl applications. Manwar sending a Pull-Request to JQ::Lite by Mohammad Sajid Anwar ( MANWAR ) This video was recorded during the most recent Perl code reading and open source contribution event. For links check out the OSDC Perl page and join us at our next event! Perl in the TIOBE Index by Dave Cross ( DAVECROSS ) See also the discussion . DBIx::Class::Async - UPDATE by Mohammad Sajid Anwar ( MANWAR ) Discussion nfo - a user-friendly info reader Why do you need Perl for this? - asks the first commenter. convert string to regex Allowing your users to put regexes in a configuration file. Is it a good idea? How to do it? MetaCPAN perlmodules.net is (was) down for 1-2 weeks by Alexander Karelas ( KARJALA ) Is the MetaCPAN API changing? The ElasticSearch upgrade on MetaCPAN impaceted a number of other web site, but it seems things are working again. Perl This week in PSC (210) | 2026-01-05 The Weekly Challenge The Weekly Challenge by Mohammad Sajid Anwar will help you step out of your comfort-zone. You can even win prize money of $50 by participating in the weekly challenge. We pick one champion at the end of the month from among all of the contributors during the month, thanks to the sponsor Lance Wicks. The Weekly Challenge - 356 by Mohammad Sajid Anwar ( MANWAR ) Welcome to a new week with a couple of fun tasks "Kolakoski Sequence" and "Who Wins". 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 - 355 by Mohammad Sajid Anwar ( MANWAR ) Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Thousand Separator" and "Mountain Array" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Mountain Separator by Arne Sommer The post demonstrates an idiomatic and compact use of Raku for typical programming challenges. It balances expressive language features with clarity, though readers unfamiliar with hyperoperators and the pipeline style might need supplemental explanation. Perl Weekly Challenge: Week 355 by Jaldhar H. Vyas Technically solid, readable, and well-structured. The solutions are both correct and practical, illustrating good problem decomposition and Perl/Raku coding style. Separated Mountains by Jorg Sommrey Efficient and idiomatic Perl for the thousand separator using a classic unpack pattern.️ A formally defined mountain array solution with vectorised and language-diverse implementations. number formatting and sorting by Luca Ferrari This is a well‑engineered, comprehensive, and professionally presented technical write‑up that goes beyond minimal solutions to showcase how to solve the Weekly Challenge across ecosystems. It favors clarity and breadth over micro‑optimizations, making it valuable for learners and polyglot developers alike. Perl Weekly Challenge 355 by W Luis Mochan The solutions for Weekly Challenge #355 are technically strong, correct, and efficient. Task 2 (Mountain Array) leverages PDL for vectorized comparisons, producing a concise, single-pass check for mountain arrays while correctly handling edge cases such as plateaus and short arrays. Thousand Mountains by Matthias Muth This is technically excellent, showing a high level of Perl proficiency, algorithmic awareness, and performance consciousness. Both tasks are solved correctly, with multiple alternative implementations explored and benchmarked, demonstrating a thoughtful and professional approach rather than a "just pass the tests" mentality. Oh to live on Array Mountain… by Packy Anderson ( PACKY ) This post is a strong, well-executed multi-language technical write-up that emphasizes algorithmic reasoning, clarity of transformation, and comparative programming paradigms over minimalism or raw performance. Thousands of mountains by Peter Campbell Smith This submission demonstrates strong problem understanding, solid algorithmic choices, and pragmatic Perl coding. The solutions are intentionally explicit, readable, and correct, favoring clarity and single-pass logic over clever one-liners. Both tasks are handled with approaches that scale reasonably and align well with Perl’s strengths. The Weekly Challenge #355 by Robbie Hatley This submission is technically strong, correct, and deliberately written for clarity and maintainability rather than brevity. It reflects an experienced Perl programmer who values explicit logic, readable structure, and thorough documentation. Mountains by the Thousand by Roger Bell West ( FIREDRAKE ) This is a thoughtful, well-structured solution to both Weekly Challenge tasks, with a clear emphasis on explicit logic and state-based reasoning rather than relying on library tricks. Roger demonstrates good cross-language fluency and a solid grasp of algorithm design. Commify every mountain by Simon Green ( SGREEN ) This post delivers clean, pragmatic, and idiomatic solutions to both tasks in The Weekly Challenge #355. It emphasizes using the right tool for the job, clarity, and efficiency over algorithmic novelty. Weekly collections NICEPERL's lists by Miguel Prz ( NICEPERL ) Great CPAN modules released last week . Events Perl Maven online: Live Open Source contribution January 24, 2025 Boston.pm - online February 10, 2025 German Perl/Raku Workshop 2026 in Berlin March 16-18, 2025 You know, you could get the Perl Weekly right in your mailbox. Every Week. Free of charge! Enter your e-mail: --> --> Just ONE e-mail each Monday. Easy to unsubscribe . No spam. Your e-mail address is safe. (C) Copyright Gabor Szabo . The articles are copyright the respective authors. This newsletter is about the Perl programming language. Sections: Announcements Articles Discussion MetaCPAN Perl The Weekly Challenge Weekly collections Events | 2026-01-13T08:48:42 |
https://docs.devcycle.com/platform/feature-flags/status-and-lifecycle#completed | Status and Lifecycle | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Features Variables and Variations Targeting Status and Lifecycle Stale Feature Notifications Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Platform Feature Flags Status and Lifecycle On this page Feature Status and Lifecycle Management In DevCycle, Features have Statuses that indicate their current position in the feature lifecycle. Statuses provide a clear, at-a-glance understanding of where a Feature is in its development, release, and cleanup process. Each Status belongs to a Status Category , which defines how the Feature behaves, what actions are allowed, and how it is displayed across the dashboard. Statuses Every Feature in DevCycle always has one Status , which determines its lifecycle stage. By default, DevCycle provides a set of predefined Statuses aligned to core lifecycle categories. The default Statuses are: Development Live Completed Archived In addition to the default Statuses, teams can define custom Statuses within their Project settings. This allows teams to better align Feature lifecycle tracking with their internal development and release processes while preserving DevCycle's lifecycle guarantees. Each custom Status inherits the behavior of their Category. Status changes are not automatic and are always managed explicitly by the user. Status Categories Statuses are grouped into Categories , which define shared lifecycle behavior. Development This Category represents Features that are actively being built, tested, or prepared for release. By default, new Features are created with the Development Status. While a Feature is in Development, all Targeting rules and Variations remain editable. This stage is typically used while work is ongoing and before a Feature is considered ready for a broader release. Below are some examples of different Statuses that would make sense in the Development Category: In Development Pending Design QA Internal Testing Live The Live Category represents Features that are actively running in production or being exposed to users. While a Feature is Live, all Targeting rules and Variations remain editable. Below are some examples of different Statuses that would make sense in the Live Category: Beta Ramping In Production Live Experiment Completed The Completed Category represents Features that have reached the end of active development and rollout. A Feature may be considered Completed once it has been tested, approved, and is fully released, or when no further targeting changes are expected. When a Feature is moved into a Status within the Completed Category, it enters a semi-read-only state : A single final (release) Variation must be selected All Environments will serve this Variation to all users Targeting rules are replaced with an "All users" rule New targeting rules and Variations cannot be added Variable values may still be edited Environments can still be toggled on or off When using the CLI to generate TypeScript types, Variables belonging to a Feature in the Completed Category will be marked as deprecated . Below are some examples of different Statuses that would make sense in the Completed Category: Ready for Cleanup All Users Enabled Stable Release Cleanup Checklist Upon entering a Completed Status, a cleanup checklist is shown for each Variable associated with the Feature. This checklist helps teams determine when it is safe to remove Variables from their codebase or archive them. If a Variable is still referenced in code or evaluated in production, removing it may result in default values being served. If Code References are enabled, additional context will be provided to assist with cleanup. Archived The Archived Category represents the terminal lifecycle state for Features. This Category and Status cannot be edited or changed. A Feature should be archived once it has been fully cleaned up and its Variables have been removed from the codebase. When a Feature is Archived: It becomes fully read-only It is hidden from standard dashboard views Audit Logs remain accessible for historical reference Metrics & Reach data will not be visible on the dashboard for Archived features Archiving Features helps keep both your dashboard and codebase clean while preserving valuable lifecycle history. Note: Feature deletion still exists, but should only be used for mistakes. Deleting a Feature permanently removes it and its Audit Log. Archived Features retain historical data that may be used for future reporting and analysis. Changing Status Moving a Feature to Completed When a Feature is moved into the Completed Category: A final Variation must be selected All Environments serve that Variation to all users Existing Environment statuses are preserved Targeting rules are replaced with a single "All users" rule Additional Variations and targeting rules are locked Reverting to Development or Live Features in the Completed Category can be reverted back to an earlier Status. When reverting: Previous Variations become available again Changes made to Variable values while Completed are retained Prior targeting rules are not restored and must be reconfigured Viewing Features by Status (Kanban View) On the Feature list page, users can switch between a List view and a Kanban-style view that displays Features grouped by their current Status, allowing teams to quickly visualize progress across the Feature lifecycle. In this view: Each column represents a Feature Status Each column header includes a total count of Features in each Status Features appear as cards within the column matching their current Status, and can be sorted differently by selected criteria Columns are ordered based on the Status order defined in Project Settings Status colors are reflected in the column headers for quick visual scanning This view is intended for high-level lifecycle tracking and workflow management. Selecting a Feature card opens the Feature detail view for configuration, targeting, and Variable management. Managing Statuses Statuses are managed at the Project level and apply to all Features within that Project. Each Project starts with a default set of Statuses aligned to DevCycle's lifecycle categories. Teams may customize these Statuses to better reflect their internal workflows. Project Settings Statuses can be viewed and managed from the Project Settings page under the Feature Statuses section. From this page, users can: View all Statuses grouped by Category Create new custom Statuses within supported Categories Edit existing Status names (Note: each Status must have a unique key) Reorder Statuses within a Category Assign colors to Statuses for quick visual identification Add a description to provide context behind what a Status represents Select the default Status applied when a new Feature is created Changes made in Project Settings take effect immediately and apply across the Project. Status Categories and Rules Statuses must belong to one of DevCycle's predefined Categories. The following rules apply: New Categories cannot be created Each Category must contain at least one Status The last remaining Status in a Category cannot be deleted Status labels and ordering within a Category can be modified Permissions for Status Changes Permission Rules When permissions are enabled: Statuses in the Development and Live Categories can be applied by any user with access to the Project Statuses in the Completed and Archived Categories can only be applied by users with the Publisher permission Only Publishers can create, and modify Feature Statuses in the Project Settings Edit this page Last updated on Jan 9, 2026 Previous EdgeDB (Stored Custom Properties) Next Stale Feature Notifications Statuses Status Categories Development Live Completed Archived Changing Status Moving a Feature to Completed Reverting to Development or Live Viewing Features by Status (Kanban View) Managing Statuses Project Settings Permissions for Status Changes DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:42 |
https://golf.forem.com/t/golfyoutube | Golfyoutube - Golf 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 Golf Forem Close # golfyoutube Follow Hide Sharing and discussing the best golf YouTube channels Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu No Laying Up Podcast: Everyone Only: The Gimme Golf Club Origin Story | NLU Pod, Ep 1033 YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 No Laying Up Podcast: Everyone Only: The Gimme Golf Club Origin Story | NLU Pod, Ep 1033 # golf # golfpodcasts # golfyoutube # localgolf Comments Add Comment 1 min read Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service # pgatour # historyofgolf # golfyoutube # golfmedia Comments Add Comment 1 min read Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals # coursereviews # golfdestinations # localgolf # golfyoutube Comments Add Comment 1 min read Golf.com: Is new LPGA Commissioner Craig Kessler ready for the job? YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Is new LPGA Commissioner Craig Kessler ready for the job? # lpga # womensgolf # golfpodcasts # golfyoutube Comments Add Comment 1 min read Grant Horvat: My First Round on Tour. YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Grant Horvat: My First Round on Tour. # golfyoutube # kornferrytour # equipment # apparel Comments Add Comment 1 min read Grant Horvat: Can We Beat Bryson & Garrett in a Golf Match? YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Grant Horvat: Can We Beat Bryson & Garrett in a Golf Match? # golf # golfyoutube # roundrecap # equipment Comments Add Comment 1 min read Bryan Bros Golf: We Flew To Germany For Golf Match! YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Bryan Bros Golf: We Flew To Germany For Golf Match! # golfyoutube # dpworldtour # equipment # launchmonitors Comments Add Comment 1 min read Bryan Bros Golf: The $100,000 Golf Match! YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Bryan Bros Golf: The $100,000 Golf Match! # golfyoutube # roundrecap # equipment # launchmonitors Comments Add Comment 1 min read Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # roundrecap # golfyoutube # lessons # swingtips Comments Add Comment 1 min read Peter Finch Golf: I take on the best 50 PGA Pros for £100,000 (My Best Round Of The Year!) YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Peter Finch Golf: I take on the best 50 PGA Pros for £100,000 (My Best Round Of The Year!) # golf # pgachampionship # roundrecap # golfyoutube Comments Add Comment 1 min read Peter Finch Golf: I take on the best 50 PGA Pros for £100,000 (My Best Round Of The Year!) YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Peter Finch Golf: I take on the best 50 PGA Pros for £100,000 (My Best Round Of The Year!) # pgachampionship # roundrecap # golfyoutube # equipment Comments Add Comment 1 min read Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # golfyoutube # roundrecap # dpworldtour # livgolf Comments Add Comment 1 min read Grant Horvat: Can We Beat Bryson & Garrett in a Golf Match? YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Grant Horvat: Can We Beat Bryson & Garrett in a Golf Match? # golf # golfyoutube # roundrecap # equipment Comments Add Comment 1 min read Grant Horvat: My First Round on Tour. YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Grant Horvat: My First Round on Tour. # golfyoutube # roundrecap # milestones # equipment Comments Add Comment 1 min read Golf With Aimee: Stop Losing Power & Direction – Fix Your Lead Foot! YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf With Aimee: Stop Losing Power & Direction – Fix Your Lead Foot! # swingcritique # swingtips # drills # golfyoutube Comments Add Comment 1 min read Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Warming Up with Jon Rahm and Tyrrell Hatton # golfyoutube # livgolf # rydercup # mentalgame Comments Add Comment 1 min read Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Secrets of Long Island Private Golf: A 1-Member Club, Hamptons Hideaways and Caddie Confessionals # coursereviews # localgolf # golfdestinations # golfyoutube Comments Add Comment 1 min read Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service YouTube Golf YouTube Golf YouTube Golf Follow Jul 10 '25 Golf.com: Bringing the Anthem to the PGA Tour: One Family's Story of Service # golf # pgatour # golfyoutube # historyofgolf Comments Add Comment 1 min read Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Rick Shiels Golf: Can Bad golfer CHEATING Beat Tour Pro? # golfyoutube # roundrecap # formats # livgolf Comments Add Comment 1 min read Peter Finch Golf: I take on the best 50 PGA Pros for £100,000 (My Best Round Of The Year!) YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Peter Finch Golf: I take on the best 50 PGA Pros for £100,000 (My Best Round Of The Year!) # pgachampionship # roundrecap # golfyoutube # equipment Comments Add Comment 1 min read Grant Horvat: My First Round on Tour. YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Grant Horvat: My First Round on Tour. # golf # golfyoutube # milestones # roundrecap Comments Add Comment 1 min read Bryan Bros Golf: We Flew To Germany For Golf Match! YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Bryan Bros Golf: We Flew To Germany For Golf Match! # roundrecap # dpworldtour # golfyoutube # launchmonitors Comments Add Comment 1 min read Peter Finch Golf: Can I MAKE THE CUT at the PGA Championship? YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Peter Finch Golf: Can I MAKE THE CUT at the PGA Championship? # pgachampionship # gearreviews # techgadgets # golfyoutube Comments Add Comment 1 min read Grant Horvat: Can We Beat Bryson & Garrett in a Golf Match? YouTube Golf YouTube Golf YouTube Golf Follow Jul 9 '25 Grant Horvat: Can We Beat Bryson & Garrett in a Golf Match? # golf # golfyoutube # roundrecap # equipment Comments Add Comment 1 min read Golf With Aimee: Stop Losing Power & Direction – Fix Your Lead Foot! YouTube Golf YouTube Golf YouTube Golf Follow Jul 7 '25 Golf With Aimee: Stop Losing Power & Direction – Fix Your Lead Foot! # swingtips # drills # swingcritique # golfyoutube 2 reactions Comments Add Comment 1 min read loading... trending guides/resources Anybody watching the Internet Invitational? 💎 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://www.heroku.com/policy/privacy | Salesforce Privacy Information | Salesforce Skip to content Products Back Products Agentforce Back Agentforce Humans with Agents drive customer success together. Explore Agentforce How Agentforce works Why Agentforce? Agentforce Builder Agentforce Voice Agentforce Dev Tools AgentExchange Customer Stories Use Cases Agentforce Pricing ROI Calculator Sales Back Sales Boost pipeline, win rate, and revenue with Sales Cloud. See all sales solutions Sales Force Automation Sales AI Sales Agents Sales Performance Management Partner Cloud Revenue Lifecycle Management CPQ Sales Pricing Service Back Service Cut service costs with humans & AI agents on one platform. See all service solutions Customer Service Management Field Service IT Service Self-Service Digital Engagement Service Analytics Customer Service AI Contact Center Voice & Phone Support HR Service Service Pricing Marketing Back Marketing Personalize every moment of engagement across the customer lifecycle with AI agents, actionable data, and workflows. See all marketing solutions Marketing AI Email Marketing, Mobile, & Advertising B2B Marketing Automation Personalization Marketing Analytics Customer Data Platform Loyalty Management Small Business Marketing Marketing Pricing Commerce Back Commerce Increase revenue and deliver consistent customer experiences across online, in-store, and mobile channels with Commerce Cloud. See all commerce solutions B2C Commerce B2B Commerce Order Management Commerce AI Payments Commerce Innovations Commerce Pricing Analytics Back Analytics Empower every user, in every industry to transform trusted data into actionable insights, wherever they work. Explore analytics solutions Tableau Next Tableau Semantics Tableau CRM Analytics Data Culture Analytics Pricing Slack Back Slack Bring your people, agents data, apps and Salesforce solutions to where work happens in Slack. Learn about Slack and Salesforce AI-Powered Productivity Slack Platform Salesforce in Slack Agentforce in Slack Salesforce channels Pricing CRM Net Zero Back Net Zero Sustainability, simplified with Agentforce. See all Net Zero solutions Agentforce for Net Zero Cloud Net Zero Cloud Net Zero Marketplace Net Zero Pricing Small Business Back Small Business Find more customers, win their business, and keep them happy with tools that help you work smarter, not harder. Explore small business solutions Free Suite Starter Suite Pro Suite Marketing Sales Service Commerce Productivity with Slack Small Business Pricing Data Back Data Bring together, understand, and act on all your data, from any source. Explore Data 360 How Data 360 Works How Connectivity Works Data Security & Privacy Connectors Directory Analytics Platform Back Agentforce 360 Platform Build and customize your Agentforce and Customer 360 with the Agentforce 360 Platform. See all platform capabilities Agentforce Artificial Intelligence Agentforce & AI App Development Data Security & Privacy Informatica Analytics MuleSoft Flow Automation Heroku Customer Success Back Customer Success Reach your goals with our customer success experts. See all services Success Plans Professional Services Plans & Services Pricing Partner Apps & Experts Back Partner Apps & Experts Get the most out of Salesforce with partners, apps, solutions, and consultants. About our partners AppExchange Partner Apps Consultants Become a Partner Pricing Product Support See all products Discover the #1 AI CRM Humans with Agents drive customer success together. Explore the Salesforce portfolio Discover the #1 AI CRM Humans with Agents drive customer success together. Explore the Salesforce portfolio Industries Back Industries Automotive Back Automotive Drive a lifetime of loyalty. Explore automotive solutions OEM Dealer/Retailers Captive Software-Defined Vehicle (SDV) Automotive Cloud Automotive Pricing Communications Back Communications Deliver the connected future, faster. Explore communications solutions Unify the Telecom Customer Journey Accelerate Communication Sales Simplify Wholesale Transactions Light Up Fiber Experiences Fulfill the Perfect Order Optimize Telecom Customer Service Communications Cloud Communications Cloud Pricing Construction & Real Estate Back Engineering, Construction & Real Estate Achieve operational excellence. Explore engineering, construction, and real estate solutions Real Estate Engineering & Construction Residential & Commercial Services Consumer Goods Back Consumer Goods Deliver profitable growth. Explore consumer goods solutions Fast-Moving Consumer Goods Home Durables Distributors Apparel, Footwear, and Accessories Beauty Consumer Goods Cloud Consumer Goods Cloud Pricing Education Back Education Deliver connected education journeys for life on the #1 AI CRM. Explore education solutions Recruitment & Admissions Academic Operations Student Success Advancement & Alumni Relations Communications, Marketing, and Engagement Lifelong Learning K-12 Education Cloud Education Cloud Pricing Energy & Utilities Back Energy & Utilities Lead the energy transition. Explore energy & utilities solutions Power & Utilities Oil & Gas Energy & Utilities Cloud Energy & Utilities Cloud Pricing Financial Services Back Financial Services Empower your customers’ financial success with trusted AI. Explore financial services solutions Scale Service Streamline Onboarding Personalize Engagement Modernize Insurance Sales Next Gen Service for Banking Next Gen Advisor for Wealth Financial Services Cloud Financial Services Pricing Healthcare & Life Sciences Back Healthcare & Life Sciences Grow healthy relationships on the #1 AI CRM. Explore health and life sciences solutions Provider Payer Public Sector Health Pharma MedTech Health Cloud Life Sciences Cloud Health Cloud Pricing Life Sciences Cloud Pricing Manufacturing Back Manufacturing Connect the value chain. Explore manufacturing solutions Modernize Commercial Operations Transform the Service Experience Simplify Partner Engagement Manufacturing Cloud Manufacturing Cloud Pricing Media Back Media Cultivate loyal audiences faster. Explore media solutions Accelerate Advertising Sales Automate Media and Entertainment Processes Grow Subscriber Relationships Maximize Audience Engagement Streamline Production and Operations Media Cloud Media Cloud Pricing Nonprofit Back Nonprofit Build relationships that drive change. Explore nonprofit solutions Fundraising Marketing and Engagement Program and Outcome Management IT Operations for Nonprofit Grantmaking Volunteer Management Nonprofit Cloud Nonprofit Cloud Pricing Professional Services Back Professional Services Increase client trust. Explore professional services solutions Accounting, Tax, and Audit Consulting Staffing and Recruiting Legal Public Sector Back Public Sector Modernize government service. Explore public sector solutions Federal/National State and Local Defense and National Security Government Cloud Public Sector Solutions Government Cloud Pricing Public Sector Apps Pricing Retail Back Retail Smarter retail starts with Salesforce. Explore retail solutions Fashion Restaurants Grocery, Drug, and Convenience Stores Mass Merchants and Department Stores Retail Cloud POS Technology Back Technology Drive cost-efficient growth with intelligent automated processes. Explore technology solutions Unlock Partner Growth Drive Recruiting Revenue Travel, Transportation & Hospitality Back Travel, Transportation & Hospitality Deliver connected experiences. Explore travel, transportation, and hospitality experiences Travel Transportation and Logistics Hospitality See all industries Explore Salesforce for industries. Get industry-specific innovations that modernize your business, save time, and lower costs. See all industries Explore Salesforce for industries. Get industry-specific innovations that modernize your business, save time, and lower costs. See all industries Customers Back Customers Customer Stories Back Customer Stories Explore success stories from customers of all sizes, in every industry. See all stories Customer Highlights from Earnings Tableau Stories MuleSoft Stories Slack Stories Heroku Stories Salesforce on Salesforce Stories Back Salesforce on Salesforce Stories Explore success stories of how Salesforce uses our own technology to run every part of our business. See all stories Trailblazer Stories Back Trailblazer Stories Meet the innovators driving business impact and building successful careers with Salesforce. See all stories Trailblazer Series Trailblazer 360 Blog Be a Trailblazer Explore success stories. See how our customers transform their businesses with CRM + AI + Data + Trust. See all stories Explore success stories. See how our customers transform their businesses with CRM + AI + Data + Trust. See all stories Events Back Events Dreamforce Back Dreamforce Relive the innovation and inspiration of Dreamforce 2025 with on-demand keynotes, sessions, and highlights available anytime on Salesforce+. Learn more Save the Date for Dreamforce 2026 Mark your calendar for next year’s Dreamforce. Join us in San Francisco for more learning, inspiration, and innovation. Dreamforce 2025 Main Keynote Watch the headline keynote from Dreamforce 2025, featuring groundbreaking announcements and inspiring customer stories. Best of Dreamforce 2025 Catch the top sessions, moments, and takeaways, all in one place. TDX Back TDX Relive the best of TDX 2025 with on-demand technical sessions, product deep dives, and community-led discussions. Learn more Save the Date for TDX 2026 Join the must-attend conference for Salesforce developers, admins, and architects — save your spot now. TDX 2025 Main Keynote Watch the keynote showcasing the latest innovations in AI agents, data, integration, automation, and more. Best of TDX 2025 Catch the most impactful sessions, announcements, and community highlights from TDX 2025. Connections Back Connections Revisit the most impactful moments from Connections 2025 and learn how marketers can lead the way with next-gen innovations. Learn more Save the Date for Connections 2026 Be part of the marketing and commerce event of the year. Mark your calendar and join us for more insights, innovation, and inspiration. Connections 2025 Main Keynote Watch the keynote that sets the stage for an agentic future where customer engagement will never be the same. Best of Connections 2025 Explore the standout sessions, product demos, and takeaways. Tableau Conference Back Tableau Conference Revisit the excitement of Tableau Conference 2025 with on-demand keynotes, trainings, and data stories from around the world. Learn more Save the Date for Tableau Conference 2026 Mark your calendar for the data event of the year — connect with the Tableau community and sharpen your analytics skills. Tableau Conference 2025 Main Keynote Watch the keynote that unveiled the future of data and analytics, featuring product innovations and inspiring customer stories. Best of Tableau Conference 2025 See the top sessions, data visualizations, and takeaways from this year’s gathering of data enthusiasts. Agentforce World Tours Back Agentforce World Tours Join us in cities around the world to experience the latest Salesforce innovations in apps, data, and agents. Connect with leaders and experts from your industry at an Agentforce World Tour near you. Learn more Find an Agentforce World Tour in a city near you Browse current Agentforce World Tour events, or sign up today to be the first to know when one is coming to a city near you Agentforce World Tour New York Explore 140+ expert-led sessions, demos, and hands-on trainings featuring Dreamforce’s boldest launches. All in one day, all for free. Agentforce World Tour Chicago Experience the Dreamforce innovations that power Agentic Enterprises with expert-led sessions, demos, and hands-on trainings. All in one day, all for free. Salesforce+ Back Salesforce+ Fuel your professional growth and transform your company with our free live streaming and on-demand events. Visit Salesforce+ Watch Dreamforce On-Demand Stream the world’s largest, most trusted technology event. Agentforce and AI Join us to learn how AI agents are driving customer success. Data, Analytics, and Integration Explore data and AI demos, trainings, and release announcements. My List Save inspiring content to watch later. More Salesforce Events Back More Salesforce Events Dive into highlights from past events and explore on-demand content for every role and industry. See all events Webinars Join live webinars or listen to on-demand webinars at any time. Community Led Learn from peers, build your Salesforce network, and give back to the community. Customer Success Events Build product knowledge and get implementation and adoption guidance from Salesforce experts. Developer Events Learn and get hands-on the with the latest product innovations. Local User Groups Join groups to meet, collaborate, and learn new skills with Trailblazers. Salesforce Events Join us in person or on Salesforce+ to experience expert-led learning and groundbreaking innovation. See all events Salesforce Events Join us in person or on Salesforce+ to experience expert-led learning and groundbreaking innovation. See all events Learning Back Learning Learning on Trailhead Back Learning on Trailhead Skill up for the future from anywhere with Trailhead, our free, online learning platform. Explore Trailhead Trails Explore guided learning paths to quickly learn in-demand skills. Expert-led Learning Accelerate learning with access to Salesforce experts. Salesforce Certification Earn resume-worthy Salesforce credentials. Career Paths Find your career in the Salesforce ecosystem. Try Salesforce for Free Back Try Salesforce for Free Explore free and trial offers for Salesforce data, analytics, and CRM products — for any size business, in any industry. Get started Free Suite The free CRM suite with sales, service, marketing, and Slack for a maximum of 2 users. Starter Suite The marketing, sales, service, and commerce tools you need to succeed — all in a single CRM suite. Developer Edition Build enterprise-quality apps fast and get hands-on with Agentforce and Data Cloud. New to Salesforce Back New to Salesforce Salesforce is the #1 AI CRM, with AI agents, data, and CRM apps on a single, unified platform. Learn more about Salesforce What is CRM? Learn all about what CRM is, what it does, and how it can improve customer relationships. What is Customer 360? Salesforce’s category-leading apps for sales, service, marketing, commerce, IT, and more. What are AI agents? Learn more about AI agents and how they can help your business. What is Agentforce? It’s always-on digital labor augmenting every employee, department, and business process to improve customer experiences. Blogs Back Blogs Discover tips and insights from experts to supercharge your digital journey. Explore all blogs The 360 Blog Get the latest on AI, data, digital labor, and more. AI Research Blog Keep up with Salesforce’s AI research team and stay on the cutting edge of technology. Developer Blog Get the latest tooling innovation news, insights, and inspiration. Salesblazer Grow your career with the latest in sales content, training, and events — all part of the world’s leading sales community. Resources Back Resources Find free articles, guides, best practices, research, and more. Explore all resources Analyst Reports Read the latest studies and reports from the world’s best-known business analysts. Partners Explore industry-leading Salesforce partner apps and experts. Developer Documentation Get developer guides, tutorials, sample code, and API references. Newsletter Sign up to receive the latest Salesforce tips and insights, tailored just for you. Become a Trailblazer. Unlock free hands-on learning, our global community, original series, and support. Join for free Become a Trailblazer. Unlock free hands-on learning, our global community, original series, and support. Join for free Support Back Support Help & Documentation Back Help & Documentation Need help? Ask Agentforce. Find documentation, access learning resources, log cases, and more – all the support you need, wherever you need it. Ask Agentforce on Salesforce Help Known Issues Find up-to-date information and status about our technology bugs and workarounds. Developer Documentation Find tutorials, sample code, developer guides, and API references. Architecture Center Explore diagrams, decision guides, and resources to build trusted, easy, and adaptable solutions. Communities Back Communities Meet people, learn skills, find apps and experts, and share feedback by joining Salesforce communities. Explore communities Trailblazer Community Connect with peers to learn skills and grow. Slack Community Connect with Slack end users, admins, and developers. MuleSoft Community Connect with MuleSoft developers, architects and business users. Tableau Community Connect with Tableau analysts, admins, developers and business users. Partner Community Collaborate, learn, and manage your partner business. IdeaExchange Help us build the Salesforce roadmap by sharing your feedback. Services & Plans Back Services & Plans Reach your goals with our customer success experts. See all services Success Plans Get the right level of support and guidance to grow your business. Professional Services Implement, innovate, and transform your enterprise with help from Salesforce experts. Account Management Back Account Management Manage your Salesforce subscriptions and contracts. Explore Your Account features. Your Account App Make payments, buy products, and manage renewals (Salesforce login required). Billing Portal Access invoices and make payments (Trailblazer ID login required). Digital Wallet Track and manage consumption with near-real time usage data. Questions? We can help. Get answers fast with Agentforce. Explore product documentation, access learning resources, log cases, and more. Get started Questions? We can help. Get answers fast with Agentforce. Explore product documentation, access learning resources, log cases, and more. Get started Company Back Company About Salesforce Back About Salesforce Learn about our history, products, and values. See our story What Is Salesforce? Leadership Global Offices Salesforce Swag Store Salesforce Ventures Investor Relations Our Values Back Our Values We are guided by our values and strive to do well in business while doing good in our communities. See what drives us Trust Customer success Innovation Equality Sustainability Our Impact Back Our Impact Business is the greatest platform for change. We use the full power of Salesforce to make the world a better place for all of our stakeholders. Learn about our Impact initiatives Equality Accessibility Sustainability Philanthropy Ethical and Humane Use Public Policy Careers Back Careers Start a new journey with us – a career here at Salesforce. See all careers University Recruiting News Back Newsroom Stay informed with the latest news and announcements, fresh off the press. Visit the newsroom Analyst Reports Quarter in Review Legal Back Legal Find answers to your questions about Salesforce agreement terms, policies, intellectual property, corporate governance and compliance for customers, employees, partners and suppliers. See legal For Customers For Partners and Alliances For Suppliers Terms of Service TMCU Guidelines DMCA Privacy Info Compliance Product Accessibility Status Governance More Salesforce Brands Back More Salesforce Brands Explore the Salesforce brands delivering success now. See our brands Tableau Slack MuleSoft Heroku Hear our story. We believe in building relationships – not just between companies and customers, but among our global communities. Learn about us Hear our story. We believe in building relationships – not just between companies and customers, but among our global communities. Learn about us Contact Us Back Contact Us By phone 1-800-664-9073 Online Contact Us Change Region Back Change Region Americas América Latina (Español) Brasil (Português) Canada (English) Canada (Français) United States (English) Europe, Middle East, and Africa España (Español) Deutschland (Deutsch) France (Français) Italia (Italiano) Nederland (Nederlands) Sverige (Svenska) United Kingdom (English) All other countries (English) Asia Pacific Australia & New Zealand (English) India (English) 日本 (日本語) 中国 (简体中文) 台灣 (繁體中文) 한국 (한국어) ประเทศไทย (ไทย) All other countries (English) 1-800-664-9073 Contact Us 1-800-664-9073 Change Region Americas América Latina (Español) Brasil (Português) Canada (English) Canada (Français) United States (English) Europe, Middle East, and Africa España (Español) Deutschland (Deutsch) France (Français) Italia (Italiano) Nederland (Nederlands) Sverige (Svenska) United Kingdom (English) All other countries (English) Asia Pacific Australia & New Zealand (English) India (English) 日本 (日本語) 中国 (简体中文) 台灣 (繁體中文) 한국 (한국어) ประเทศไทย (ไทย) All other countries (English) Change Region Change Region Americas América Latina (Español) Brasil (Português) Canada (English) Canada (Français) United States (English) Europe, Middle East, and Africa España (Español) Deutschland (Deutsch) France (Français) Italia (Italiano) Nederland (Nederlands) Sverige (Svenska) United Kingdom (English) All other countries (English) Asia Pacific Australia & New Zealand (English) India (English) 日本 (日本語) 中国 (简体中文) 台灣 (繁體中文) 한국 (한국어) ประเทศไทย (ไทย) All other countries (English) Start for free Start for free Privacy Information Trust is our #1 value. Salesforce’s top priority is the security and privacy of the data that we are entrusted to protect. See Privacy Statement Learn about our commitment to privacy How we protect our Customer’s data as a Processor Our cloud services are designed to help customers comply with privacy laws around the world. Discover more about our commitment to protecting customer data as a processor. Global Privacy Resources for Salesforce Products Data Processing Addendum Data Processing Addendum FAQ Data Transfer Mechanisms FAQ Salesforce's Notice of Data Privacy Framework Certification Trust and Compliance Documentation Salesforce's Notice of APEC CBPR and PRP Certifications Salesforce's EU Processor Binding Corporate Rules Salesforce's UK Processor Binding Corporate Rules Salesforce Group Affiliates for UK Binding Corporate Rules for Processors How we protect data as a Controller We continuously monitor the global privacy landscape and adapt our privacy program accordingly. Discover more about our commitment to compliance with global privacy laws as a controller Salesforce Candidate Privacy Statement Salesforce Apps, Add-ins and Extensions Privacy Statement Privacy Statement (Bahasa Indonesia) Contact Information To exercise your rights relating to your personal data, or if you have questions regarding our privacy practices, please fill out this form , or email us at privacy@salesforce.com. For more information about contacting us, see the “Contacting Us” section below. Salesforce’s Data Transfer Mechanisms FAQ Learn how Salesforce is responding to the new SCCs in Salesforce's FAQ about transfers of personal data. Learn more Privacy Statement When you use and interact with our websites or services, communicate with us, visit our offices or attend our events, among other activities further described within the full Privacy Statement, we may collect, use, share and process information relating to you ("Personal Data"). These Privacy Statement Highlights summarize our Personal Data processing practices and your related rights. Privacy Statement Overview Important Information Salesforce’s full Privacy Statement contains more information about Salesforce’s privacy practices. Responsible Salesforce Entity Salesforce, Inc. and/or its affiliated entities (“Salesforce, “we”, “us”, or the “Company”) act as the controllers of your Personal Data and are responsible for its processing, unless expressly specified otherwise in our full Privacy Statement. For the avoidance of doubt, our Privacy Statement does not apply to the extent we process Personal Data in the role of a processor on behalf of our customers. A list of Salesforce’s affiliates can be found in the List of Subsidiaries section of Salesforce’s most recent Form 10-K, available under the SEC Filings tab by selecting the “Annual Filings” filter on the page located here . Purposes for which we process Personal Data We collect and process Personal Data for a variety of purposes, including but not limited to the following: to provide our websites (including our social media pages); to display personalized advertisements and content; to manage event registrations, attendance, and participation in webinars, contests or promotions; to ensure the safety and security of our offices, premises, employees and events; to send marketing communications; to handle support or service-related requests; to prospect sales leads; to develop and optimize the performance of our services; to manage and document our customer and user accounts; to administer surveys and conduct research; and to comply with our legal obligations and defend Salesforce. For the entire list of purposes for which we Process your Personal Data, please see the full Privacy Statement. We only collect and process your Personal Data to the extent it is necessary for fulfilling these purposes and where we can rely on a legal basis for such processing as set out in our full Privacy Statement. Where legally required, we will ask you for your prior consent to processing. Please review the "What Personal Data do we collect?" and "Purposes for which we process your Personal Data and the legal bases on which we rely" sections in our full Privacy Statement for further details. Also, please review the "How long do we keep your Personal Data?" section to learn how long we store your Personal Data. Who do we share Personal Data with We may share Personal Data with various parties, including: service providers; Salesforce affiliates; event sponsors; partners; customers with whom you are affiliated and/or the applicable partner responsible for access to your services; contest and promotion sponsors; third-party networks and websites; Salesforce-affiliated App Exchange partners; professional advisors; third parties involved in a corporate transaction; third party accounts (in relation to Tableau); and public authorities. Please review the "Who do we share Personal Data with" section in our full Privacy Statement for the full list and more detailed information about each category listed above. International transfer of Personal Data Your Personal Data may be transferred to, and stored by us, in the United States and by our affiliates and third parties (as disclosed in the full Privacy Statement) as listed in the Privacy Statement. Therefore, your Personal Data may be processed and stored outside your country or jurisdiction, including in places that may not provide the same level of protection. As described in the "International transfers of Personal Data" section of our full Privacy Statement, we have implemented safeguards to ensure an adequate level of protection where your Personal Data is transferred, including, where required, standard contractual clauses or an alternative mechanism for the transfer of Personal Data as approved by the European Commission. Salesforce also commits to comply with the EU-U.S. Data Privacy Framework, the Swiss-U.S. Data Privacy Framework, and the UK Extension to the EU-U.S. Data Privacy Framework (collectively, the “DPF”) and certifies its adherence to the DPF Principles as set forth by the U.S. Department of Commerce. For more information, please see the full Privacy Statement. Your rights relating to Personal Data You have certain rights relating to your Personal Data, subject to local data protection laws. Depending on the applicable laws, these rights may include the right to: Access your Personal Data held by us; Know more about how we process your Personal Data; Rectify inaccurate Personal Data and, taking into account the purpose of processing the Personal Data, ensure it is complete; Erase or delete your Personal Data; Restrict our processing of your Personal Data; Transfer your Personal Data to another controller (data portability), to the extent possible; Object to any processing of your Personal Data; Opt out of certain disclosures of your Personal Data to third parties; Know what categories of Personal Data are shared for delivering advertisements on non Salesforce websites, applications, and services and the categories of recipients of such Personal Data; Opt out of the sharing of your Personal Data for delivering advertisements on non-Salesforce websites, applications, and services; If you’re under the age of 16, or such other applicable age of consent for privacy purposes in relevant individual jurisdictions, opt in to certain disclosures of your Personal Data to third parties; Not be subject to a decision based solely on automated processing, including profiling, which produces legal effects (“automated decision-making”); Withdraw your consent at any time (to the extent we rely on consent as our legal basis for processing); Complain about the use of your Personal Data; Not be discriminated against for exercising your rights as described above; and Appeal our refusal to act upon your request to exercise a right relating to your Personal Data by following the steps provided in response to your inquiry. For more details on your rights and choices and how to exercise them, please review the "Your rights relating to your Personal Data" section in our full Privacy Statement. Contacting us To exercise your rights relating to your Personal Data, or if you have questions regarding our privacy practices, please fill out this form, email us at privacy@salesforce.com, call us at tel:1-800-931-7365 or write to us at: Salesforce Data Protection Officer (Salesforce Privacy Team) (and in India, a Grievance Officer) 415 Mission St., 3rd Floor San Francisco, CA 94105, USA When you contact us, please indicate in which country and/or state you reside. If you have an unresolved concern in respect of our processing of your Personal Data that you believe we have not addressed satisfactorily, you can contact our U.S.-based third party dispute resolution provider (free of charge) at https://feedback-form.truste.com/watchdog/request. If you believe that we have not been able to assist with your complaint or concern, and you are located in the EEA or the UK, you have the right to lodge a complaint with the competent supervisory authority. If you work or reside in a country that is a member of the European Union or that is in the EEA, you may find the contact details for your appropriate data protection authority on the following website. Full Salesforce Privacy Statement Effective as of August 26, 2025. At Salesforce, trust is our #1 value. This Privacy Statement describes how Salesforce collects, uses, shares or otherwise processes information relating to individuals (“Personal Data”) and the rights associated with that processing. 1. Responsible Salesforce entity Salesforce, Inc. and/or its affiliated entities (“Salesforce, “we”, “us”, or the “Company”) are responsible for the processing of your Personal Data as described in this Privacy Statement, unless specified otherwise, and act as the controller of such Personal Data. A list of Salesforce’s affiliates can be found in the List of Subsidiaries section of Salesforce’s most recent Form 10-K, available under the SEC Filings tab by selecting the “Annual Filings” filter on the page located here . This Privacy Statement does not apply to the extent we process Personal Data as a processor or service provider on behalf of our customers, including where we offer to our customers various services through which our customers (or their affiliates): (i) create their own websites and applications running on our platforms; (ii) sell or offer their own products and services; (iii) send electronic communications to others; or (iv) otherwise collect, use, share or process Personal Data via our services. For detailed privacy information related to a Salesforce customer or a customer affiliate who uses Salesforce services as the controller, please contact our customer directly. We are not responsible for the privacy or data security practices of our customers, which may differ from those explained in this Privacy Statement. For more information, please also see Section 10.3 below. 2. When this Privacy Statement applies This Privacy Statement applies to the processing of Personal Data collected by us when you: • Visit or interact with our websites that display or link to this Privacy Statement; • Visit or interact with our branded social media pages; • Visit our offices or other premises; • Receive communications from us or otherwise communicate with us, including but not limited to emails, phone calls, texts or faxes; • Use our services where we act as a controller of your Personal Data; • Register for, attend or take part in our events, webinars, programs, trainings, certifications or contests; • Act as or work for a service provider or supplier to Salesforce, to the extent Salesforce acts as a controller with respect to your Personal Data; • Are employed by a customer using our services where your Personal Data has been shared with us in our capacity as a controller (for example, during the sales or contracting process); • Participate in a Salesforce community, such as that focused on open source development; or • Participate in surveys, research or other similar data collection facilitated by us. We also host several online marketplaces such as: • AppExchange, which is an online marketplace for on-demand web applications that run on the Salesforce platform and that may be provided by us or by third parties (see https://appexchange.salesforce.com/ ), and • Tableau’s Extension Gallery ( https://extensiongallery.tableau.com ) which offers connectors and solutions that provide additional functionality for Tableau, such as dashboard extensions. When applications, connectors, extensions or other solutions are provided by us and they link to this Privacy Statement, this Privacy Statement applies. When these offerings are provided by third parties, the privacy statement of the relevant third party applies and this Privacy Statement does not. Our websites and services may contain links to other websites, applications, platforms and services maintained by third parties. Salesforce does not control these and the information practices of those third parties, including the social media platforms that host our branded social media pages, are governed by their own privacy statements. It is recommended that you read the applicable privacy statements carefully to understand their privacy practices. In some circumstances, we also collect, or our partners provide us with, publicly available information which may contain Personal Data that you have published or that has been made available online. The way in which our partners collect this is detailed in their own privacy statements, available on their websites. Salesforce may use artificial intelligence to process your Personal Data, including to develop and deploy AI systems. Where artificial intelligence is leveraged, it will only be used where legally permissible, in compliance with this Privacy Statement, and in a manner which is consistent with our commitments and values. More information on Salesforce’s responsible AI practices can be found here. For the avoidance of doubt, this applies where Salesforce processes your Personal Data as a controller. It does not apply to Personal Data you voluntarily submit to our services as an authorised user of a Salesforce customer for which Salesforce always acts as a processor. 3. What Personal data do we collect? 3.1 Personal Data we collect directly from you The Personal Data we collect directly from you depends on how you choose to interact with us and what you choose to share. This may include identifiers such as contact information, professional or employment-related information, financial account information, commercial information, visual information such as your image, and internet activity information, among others. Below are examples of the types of data we may collect in the following situations: Personal Data Collection Scenarios Situations Categories of Personal Data If you express an interest in obtaining additional information about our services; request customer support (including accessing the Help & Training Portal); use our “Contact Us” or similar features; register to use our websites or to receive communications; sign up for an event, webinar or contest; participate in a program, training, certification or survey; use our services; download certain content; or are employed by a customer using our services where your information has been shared with us Contact information, such as your name, job title, company name, address, phone number, email address, username and password, other information you have voluntarily chosen to share or communicate to Salesforce If you make purchases via our websites or register for an event or webinar Contact information, financial and billing information, such as billing name and address, credit card number or bank account information If you attend an event Attendee badge information which may include name, title, company name, address, country, phone number and email address, image and video, such as from CCTV footage If you give your explicit consent and only for specified events, your biometric information, such as an image of your facial features for identification purposes To the extent that national or local laws require it, this may also include health status, including your temperature, COVID-19-related symptoms, exposure to COVID-19 positive individuals, vaccination status, testing results, and recent travel history If you register with us for purposes such as, joining a community that we host or participating in a program, training or certification Username, photo, video (such as during an online certification exam) or other biographical information, such as your occupation, location, social media profiles or usernames, company name, areas of expertise and interests If you interact with our websites or emails Information about your device and your usage of our websites or emails (such as Internet Protocol (IP) addresses or other identifiers), which may qualify as Personal Data (please see Section 4 below) using cookies, web beacons, or similar technologies If you use and interact with our services Information about your device and your usage of our services through log files and other technologies, some of which may qualify as Personal Data (including Usage Data) (please see Section 4 below) If you communicate with us via a phone call Information such as your name, voice, telephone number and any other Personal Data voluntarily shared If you visit our offices or other premises Name, email address, phone number, company name, time and date of arrival, image or video, such as from CCTV footage To the extent that national or local laws require it, this may also include health status, including your temperature, COVID-19-related symptoms, exposure to COVID-19 positive individuals, vaccination status, testing results, and recent travel history If you voluntarily submit certain information to us, such as filling out a survey, responding to a questionnaire or participating in other forms of research Information you have provided as part of that request, which may include Personal Data and special categories of Personal Data, to the extent you voluntarily choose to provide it If you are a supplier or service provider to Salesforce (or work for a supplier or service provider) Contact information, payment and billing information If you provide us, our service providers or our affiliates with any Personal Data relating to other individuals, you: • represent that you have the authority to do so, • where required, have obtained their necessary consent(s) to share their Personal Data with us for processing, and • acknowledge and accept that it may be used in accordance with this Privacy Statement. If you believe that your Personal Data has been provided to us improperly, or want to exercise your rights relating to your Personal Data, please contact us by using the information in Section 13 below. 3.2 Personal Data we collect from other sources We also collect information about you from other sources including partners from whom we collect or purchase Personal Data, or who provide us with publicly available information which may contain Personal Data. We may combine this information with Personal Data provided by you. Provision of our services: • The Personal Data we collect to provide our services may include information you have made publicly available online (such as when using social media sites) or that is published by third parties and contains information about you (such as news articles). For a select number of services, we collect this Personal Data from partners who may receive this data when you visit or use their services or through the third parties they work with. • In addition, the Personal Data we collect to provide our services may include location information from third parties, which helps us offer features like identity management and multi-factor authentication for security purposes. Advertising: The Personal Data we collect from other sources for the purposes of tailored advertising includes personal identifiers professional or employment-related information, education information, commercial information, internet activity information, and inferences about preferences and behaviors. We collect this from third party providers of business contact information, including mailing addresses, job titles, email addresses, phone numbers, user behavior data, IP addresses, social media profiles, LinkedIn URLs and custom profiles for purposes of tailored advertising, delivering relevant email content, event promotion and profiling, marketing campaign eligibility, and verifying contact information. This helps us update, expand, and analyze our records, identify new customers, and create more tailored and relevant advertising to provide services that may be of interest to you. Additional sources: In addition, we also collect Personal Data from the following sources: • Another individual at your organization who may provide us with your personal information, which may include Personal Data and special categories of Personal Data, to the extent you consent to providing it and sharing it; • Platforms such as GitHub to manage code check-ins and pull requests. If you participate in an open source or community development project, we may associate your code repository username with your community account so we can inform you of program changes that are important to your participation or relate to additional security requirements; and • Only where necessary for security purposes, we may collect information that is publicly available online (such as accessible through search engines or public social media sites), as well as images, physical descriptions and other pertinent information necessary to address a credible security threat to our employees, events or premises. 4. What Device and Usage Data do we process? We use common information-gathering tools, such as tools for collecting data, cookies, web beacons, pixels, and similar technologies to collect information that may contain Personal Data as you navigate our websites, our services, or interact with emails we have sent to you. 4.1 Device and Usage Data As is true of most websites, we collect certain device information when individual users visit our websites. This information may include identifiers, commercial information, and internet activity information such as IP address (or proxy server information), device and application information, identification numbers and features, location, browser type, plug-ins, integrations, Internet service provider, mobile carrier, the pages and files viewed, searches, referring website, app or ad, operating system, system configuration information, advertising and language preferences, date and time stamps associated with your usage, and frequency of visits to the websites. This information is used for the purposes set out in Section 5 of this Privacy Statement below. In addition, we collect certain information as part of your use of our services (“Usage Data”). This information may include: (i) identifiers, such as user ID, organization ID, username, email address and user type; (ii) commercial information; and (iii) internet activity information such as IP address (or proxy server), mobile device number, device and application identification numbers, location, language, browser type, Internet service provider or mobile carrier, user interactions such as the pages and files viewed, website and webpage interactions including searches and other actions you take, operating system type and version, system configuration information, date and time stamps associated with your usage and details of which of our services and versions you are using. This information is used for the purposes set out in detail in Section 5 of this Privacy Statement below. We may also use aggregated Usage Data for legitimate internal business purposes, such as to identify additional customer opportunities, and to ensure that we are meeting the demands of our customers and their users. For more information regarding Tableau specifically, please see here and here . 4.2 Our use of cookies, web beacons and other tracking technologies on our website and in email communications to you. We use technologies such as web beacons, pixels, tags, and JavaScript, alone or in conjunction with cookies, to collect information about the use of our websites and how people interact with our emails. When you visit our websites, we, or an authorized third party, may place a cookie on your device that collects information, including Personal Data, about your online activities over time and across different sites. Cookies allow us to track use, infer browsing preferences, and improve and customize your browsing experience. We use both session-based and persistent cookies on our websites. Session-based cookies exist only during a single session and disappear from your device when you close your browser or turn off the device. Persistent cookies remain on your device after you close your browser or turn your device off. To change your cookie settings and preferences for one of our websites, navigate to the “Cookie Preferences” link available in any salesforce.com website footer to choose your settings. You can also control the use of cookies on your device, but choosing to disable cookies on your device may limit your ability to use some features on our websites and services. We also use web beacons and pixels on our websites and in emails. For example, we may place a pixel in a marketing email that notifies us when you click on a link in the email. We use these technologies to operate and improve our websites and marketing emails – please see more details in the “Advertising Cookies” row in the table below. For instructions on how to unsubscribe from our marketing emails, please see Section 10.4 below. The following describes how we use different categories of cookies and similar technologies, and details your options for managing the data collection settings of these technologies: Options for Managing Data Collection Settings Type of Cookies Description Managing Settings Required cookies Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, aggregate site analytics cookies, authentication cookies, and security cookies. If you have chosen to identify yourself to us, we may place on your browser a cookie that allows us to uniquely identify you when you are logged into the websites and to process your online transactions and requests. Because required cookies are essential to operate the websites, there is no option to opt out of these cookies. Functional cookies Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual. Functional cookies may also be used to improve how our websites function and to help us provide you with more relevant communications, including marketing communications. These cookies collect information about how our websites are used, including which pages are viewed most often. We may use our own technology or third-party technology to track and analyze usage information to provide enhanced interactions and more relevant communications, and to track the performance of our advertisements. Salesforce may also use HTML5 local storage or Flash cookies for the above-mentioned purposes. These technologies differ from browser cookies in the amount and type of data they store, and how they store it. We need your prior consent to use functional cookies. To change your cookie settings and preferences, | 2026-01-13T08:48:40 |
https://parenting.forem.com/about#main-content | About 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 About Parenting Welcome to Parenting! Parenting is the most rewarding, challenging, and unpredictable journey of a lifetime. Whether you're celebrating a first smile, navigating the tumultuous teens, or learning to let go with adult children, we're here for you. Parenting is a warm and supportive community built by parents, for parents. We're here to share the unfiltered realities—the sleepless nights and the belly laughs, the tough questions and the proudest moments. You are not alone on this adventure. Our Mission Our purpose is simple: to create a judgment-free space where parents can connect, share experiences, and find solidarity. We embrace the idea that there is no one-size-fits-all manual for raising children. Instead, we learn from each other, offering diverse perspectives and unwavering support through every stage of parenthood, from the first cries of infancy to the complexities of having grown-up kids. What to Discuss We encourage open and honest conversations about all aspects of family life. Jump into discussions or start your own on topics like: Milestone Moments: Share the joy of first steps, graduations, and everything in between. Tough Questions: From sleep training and toddler tantrums to screen time debates and difficult conversations. Product & Resource Swaps: Ask for recommendations on everything from the best strollers to books on navigating teenage anxiety. Personal Stories: Share the funny, messy, and beautiful moments that make up your unique parenting story. Seeking Advice: Get real-world perspectives on challenges you're facing. Relationship Dynamics: Discuss co-parenting, managing family expectations, and finding time for your partner. How to Get Involved Becoming part of our community is easy! Here’s how you can contribute: Ask a question: No question is too big or too small. The collective wisdom here is one of our greatest assets. Share your experience: Your story could be exactly what another parent needs to hear today. Offer support: Sometimes, the best response is a simple, "I've been there too." Lend an ear and a virtual shoulder to lean on. Leave some love: Engage with posts that resonate with you. Your participation helps great conversations rise to the top. Our Community Values To keep this a safe, welcoming, and helpful space for everyone, we ask all members to follow a few simple guidelines: Be Kind and Respectful. We all have different backgrounds and parenting styles. Engage in constructive, not critical, conversations. It's okay to disagree with an idea, but it's never okay to attack a person. Support, Don't Judge. This is a shame-free zone. Offer empathy and encouragement. We are here to lift each other up. Protect Privacy. Be mindful of sharing personally identifiable information about yourself and your children. What you share is public. Never share private information about other members. This Is Not a Substitute for Professional Advice. While sharing personal experiences is valuable, please remember that this community cannot provide professional medical, legal, or mental health advice. Always consult a qualified expert for serious concerns. No Spam or Self-Promotion. This community is for connection, not for advertising. Please refrain from unsolicited marketing or excessive self-promotion. We're so glad you're here ❤️ 💎 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:42 |
https://squoosh.app | Squoosh Drop OR Paste Or try one of these: 2.8MB 2.9MB 1.6MB 13KB Small Smaller images mean faster load times. Squoosh can reduce file size and maintain high quality. Simple Open your image, inspect the differences, then save instantly. Feeling adventurous? Adjust the settings for even smaller files. Secure Worried about privacy? Images never leave your device since Squoosh does all the work locally. Privacy Source on Github Initialization error: This site requires JavaScript, which is disabled in your browser. reload | 2026-01-13T08:48:42 |
https://perlweekly.com/archive/755.html | Perl Weekly Issue #755 - 2026-01-12 - Does TIOBE help Perl? Perl Weekly Issue #755 - 2026-01-12 - Does TIOBE help Perl? latest | archive | edited by Gabor Szabo This edition was made possible by the supporters of our cause . Don't miss the next issue! Enter your e-mail: --> --> Hi there! Dave Cross has an article showing position of Perl on the TIOBE index. As I don't see any up-tick in new subscribers to the Perl Weekly nor do I see any increase in the MetaCPAN activity I keep track of, I doubt that the changes in the position reflects actual changes in the market. However I wonder, could the TIOBE index have an impact on the interest in Perl? How and when could we see that? Speaking of the MetaCPAN report , I'd love if someone sent a PR to the Perl Weekly that would generates same graphs using these numbers. Here is the issue for it. And another comment related to those stats. I just noticed that the No CI column went up from 30-40% to 80-90% in recent weeks. I wonder why? Is it because some changes in the way I am collecting the data or are those real changes? Is it real change? I also just noticed some negative numbers in the No VCS (%) column. That's not good. I guess I have to investigate this. Maybe during one of the Perl code reading and open source contribution events. Enjoy your week! Gabor Szabo Announcements New York Perlmongers (NY.PM) by James E Keenan New York Perlmongers ( NY.PM ) has a new mailing-list organized as a Google Group. Sign up here . (Note: we are not doing unrequested transfers from our previous mailing list.) NY.PM social event: Thursday, January 15, 6:00 pm EST at Barcade, 148 West 24 St, Manhattan: send-off for a long-time member returning to the U.K. ANNOUNCE: Perl.Wiki V 1.37 by Ron Savage ( RSAVAGE ) Get it, as usual, from his Wiki Haven . Articles Marlin Racing by Toby Inkster ( TOBYINK ) Which of the 7 OOP frameworks of Perl is the fastest? The Perl Claude Agent by Robert Acock It's a library that brings the agentic capabilities of Claude Code into your Perl applications. Manwar sending a Pull-Request to JQ::Lite by Mohammad Sajid Anwar ( MANWAR ) This video was recorded during the most recent Perl code reading and open source contribution event. For links check out the OSDC Perl page and join us at our next event! Perl in the TIOBE Index by Dave Cross ( DAVECROSS ) See also the discussion . DBIx::Class::Async - UPDATE by Mohammad Sajid Anwar ( MANWAR ) Discussion nfo - a user-friendly info reader Why do you need Perl for this? - asks the first commenter. convert string to regex Allowing your users to put regexes in a configuration file. Is it a good idea? How to do it? MetaCPAN perlmodules.net is (was) down for 1-2 weeks by Alexander Karelas ( KARJALA ) Is the MetaCPAN API changing? The ElasticSearch upgrade on MetaCPAN impaceted a number of other web site, but it seems things are working again. Perl This week in PSC (210) | 2026-01-05 The Weekly Challenge The Weekly Challenge by Mohammad Sajid Anwar will help you step out of your comfort-zone. You can even win prize money of $50 by participating in the weekly challenge. We pick one champion at the end of the month from among all of the contributors during the month, thanks to the sponsor Lance Wicks. The Weekly Challenge - 356 by Mohammad Sajid Anwar ( MANWAR ) Welcome to a new week with a couple of fun tasks "Kolakoski Sequence" and "Who Wins". 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 - 355 by Mohammad Sajid Anwar ( MANWAR ) Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Thousand Separator" and "Mountain Array" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Mountain Separator by Arne Sommer The post demonstrates an idiomatic and compact use of Raku for typical programming challenges. It balances expressive language features with clarity, though readers unfamiliar with hyperoperators and the pipeline style might need supplemental explanation. Perl Weekly Challenge: Week 355 by Jaldhar H. Vyas Technically solid, readable, and well-structured. The solutions are both correct and practical, illustrating good problem decomposition and Perl/Raku coding style. Separated Mountains by Jorg Sommrey Efficient and idiomatic Perl for the thousand separator using a classic unpack pattern.️ A formally defined mountain array solution with vectorised and language-diverse implementations. number formatting and sorting by Luca Ferrari This is a well‑engineered, comprehensive, and professionally presented technical write‑up that goes beyond minimal solutions to showcase how to solve the Weekly Challenge across ecosystems. It favors clarity and breadth over micro‑optimizations, making it valuable for learners and polyglot developers alike. Perl Weekly Challenge 355 by W Luis Mochan The solutions for Weekly Challenge #355 are technically strong, correct, and efficient. Task 2 (Mountain Array) leverages PDL for vectorized comparisons, producing a concise, single-pass check for mountain arrays while correctly handling edge cases such as plateaus and short arrays. Thousand Mountains by Matthias Muth This is technically excellent, showing a high level of Perl proficiency, algorithmic awareness, and performance consciousness. Both tasks are solved correctly, with multiple alternative implementations explored and benchmarked, demonstrating a thoughtful and professional approach rather than a "just pass the tests" mentality. Oh to live on Array Mountain… by Packy Anderson ( PACKY ) This post is a strong, well-executed multi-language technical write-up that emphasizes algorithmic reasoning, clarity of transformation, and comparative programming paradigms over minimalism or raw performance. Thousands of mountains by Peter Campbell Smith This submission demonstrates strong problem understanding, solid algorithmic choices, and pragmatic Perl coding. The solutions are intentionally explicit, readable, and correct, favoring clarity and single-pass logic over clever one-liners. Both tasks are handled with approaches that scale reasonably and align well with Perl’s strengths. The Weekly Challenge #355 by Robbie Hatley This submission is technically strong, correct, and deliberately written for clarity and maintainability rather than brevity. It reflects an experienced Perl programmer who values explicit logic, readable structure, and thorough documentation. Mountains by the Thousand by Roger Bell West ( FIREDRAKE ) This is a thoughtful, well-structured solution to both Weekly Challenge tasks, with a clear emphasis on explicit logic and state-based reasoning rather than relying on library tricks. Roger demonstrates good cross-language fluency and a solid grasp of algorithm design. Commify every mountain by Simon Green ( SGREEN ) This post delivers clean, pragmatic, and idiomatic solutions to both tasks in The Weekly Challenge #355. It emphasizes using the right tool for the job, clarity, and efficiency over algorithmic novelty. Weekly collections NICEPERL's lists by Miguel Prz ( NICEPERL ) Great CPAN modules released last week . Events Perl Maven online: Live Open Source contribution January 24, 2025 Boston.pm - online February 10, 2025 German Perl/Raku Workshop 2026 in Berlin March 16-18, 2025 You know, you could get the Perl Weekly right in your mailbox. Every Week. Free of charge! Enter your e-mail: --> --> Just ONE e-mail each Monday. Easy to unsubscribe . No spam. Your e-mail address is safe. (C) Copyright Gabor Szabo . The articles are copyright the respective authors. This newsletter is about the Perl programming language. Sections: Announcements Articles Discussion MetaCPAN Perl The Weekly Challenge Weekly collections Events | 2026-01-13T08:48:42 |
https://devguide.python.org/ | Python Developer’s Guide Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content Python Developer's Guide Python Developer's Guide Getting started Setup and building Fixing “easy” issues (and beyond) Git bootcamp and cheat sheet Lifecycle of a pull request Where to get help Generative AI Development workflow Following Python’s development Changing Python Development cycle Adding to the stdlib Standard library extension modules Changing Python’s C API Changing CPython’s grammar Porting to a new platform Software Bill-of-Materials (SBOM) Python Security Response Team (PSRT) Issues and triaging Issue tracker Triaging an issue GitHub labels GitHub issues for BPO users Triage Team Documentation Getting started Helping with documentation Style guide reStructuredText markup Translations Translating Coordinating Helping with the Developer’s Guide Testing and buildbots Running and writing tests Silence warnings from the test suite Increase test coverage Working with buildbots New buildbot workers Development tools Argument Clinic Tutorial How-to guides GDB support Dynamic analysis with Clang Tools for tracking compiler warnings Core team Responsibilities Accepting pull requests Experts index Team log Motivations and affiliations How to join the core team Memorialization CPython’s internals Status of Python versions Python Contributor’s Guide (draft) [Plan for the Contributor’s Guide] Introduction The CPython project Code of Conduct Roles Governance Generative AI GitHub Directory structure Communication channels Outreach Issues and triaging Issue tracker Triaging an issue GitHub labels Reviewing Triage Team Documentation contributions Getting started Helping with documentation Style guide reStructuredText markup Pull request lifecycle Translating Helping with the Developer’s Guide Code contributions Setup and building Git tips Pull request lifecycle Development workflow Following Python’s development Development cycle Adding to the stdlib Standard library extension modules Changing Python’s C API Changing Python Changing CPython’s grammar Porting to a new platform Software Bill-of-Materials (SBOM) Python Security Response Team (PSRT) Testing and buildbots Running and writing tests Silence warnings from the test suite Increase test coverage Working with buildbots New buildbot workers Development tools Argument Clinic Tutorial How-to guides GDB support Dynamic analysis with Clang Tools for tracking compiler warnings Core team Responsibilities Accepting pull requests Experts index Team log Motivations and affiliations How to join the core team Accessibility, design, and user success Security and infrastructure contributions Workflows Install Git Get the source code Install Dependencies Compile and build Regenerating auto-created files Install Git Using GitHub Codespaces Back to top View this page Edit this page Python Developer’s Guide ¶ This guide is a comprehensive resource for contributing to Python – for both new and experienced contributors. It is maintained by the same community that maintains Python. We welcome your contributions to Python! Quick reference ¶ Here are the basic steps needed to get set up and contribute a pull request. This is meant as a checklist, once you know the basics. For complete instructions please see the setup guide . Install and set up Git and other dependencies (see the Git Setup page for detailed information). Fork the CPython repository to your GitHub account and get the source code using: git clone https://github.com/<your_username>/cpython cd cpython Build Python: Unix ./configure --with-pydebug && make -j $( nproc ) macOS ./configure --with-pydebug && make -j8 Windows PCbuild\build.bat -e -d See also more detailed instructions , how to install and build dependencies , and the platform-specific pages for Unix , macOS , and Windows . Run the tests : Unix ./python -m test -j3 macOS ./python.exe -m test -j8 Note: Most macOS systems use ./python.exe in order to avoid filename conflicts with the Python directory. Windows .\python.bat -m test -j3 Create a new branch where your work for the issue will go, for example: git checkout -b fix-issue-12345 main If an issue does not already exist, please create it . Trivial issues (for example, typo fixes) do not require any issue to be created. Once you fixed the issue, run the tests, and the patchcheck: Unix make patchcheck macOS make patchcheck Windows .\python.bat Tools\patchcheck\patchcheck.py If everything is ok, commit. Push the branch on your fork on GitHub and create a pull request . Include the issue number using gh-NNNN in the pull request description. For example: gh-12345: Fix some bug in spam module Add a News entry into the Misc/NEWS.d directory as individual file. The news entry can be created by using blurb-it , or the blurb tool and its blurb add command. Please read more about blurb in its repository . Note First time contributors will need to sign the Contributor Licensing Agreement (CLA) as described in the Licensing section of this guide. Quick links ¶ Here are some links that you probably will reference frequently while contributing to Python: Issue tracker Buildbot status Where to get help PEPs (Python Enhancement Proposals) Git bootcamp and cheat sheet Contributing ¶ We encourage everyone to contribute to Python and that’s why we have put up this developer’s guide. If you still have questions after reviewing the material in this guide, then the Core Python Mentorship group is available to help guide new contributors through the process. A number of individuals from the Python community have contributed to a series of excellent guides at Open Source Guides . Core developers and contributors alike will find the following guides useful: How to Contribute to Open Source Building Welcoming Communities Guide for contributing to Python: Contributors Documentarians Triagers Core team Setup and building Helping with documentation Issue tracker Responsibilities Where to get help Getting started Triaging an issue Team log Lifecycle of a pull request Style guide Helping triage issues Accepting pull requests Running and writing tests reStructuredText primer Experts index Development cycle Fixing “easy” issues (and beyond) Translating GitHub labels Motivations and affiliations Following Python’s development Helping with the Developer’s Guide GitHub issues for BPO users Experts index Git bootcamp and cheat sheet Triage Team Development cycle We recommend that the documents in this guide be read as needed. You can stop where you feel comfortable and begin contributing immediately without reading and understanding these documents all at once. If you do choose to skip around within the documentation, be aware that it is written assuming preceding documentation has been read so you may find it necessary to backtrack to fill in missing concepts and terminology. Proposing changes to Python itself ¶ Improving Python’s code, documentation and tests are ongoing tasks that are never going to be “finished”, as Python operates as part of an ever-evolving system of technology. An even more challenging ongoing task than these necessary maintenance activities is finding ways to make Python, in the form of the standard library and the language definition, an even better tool in a developer’s toolkit. While these kinds of change are much rarer than those described above, they do happen and that process is also described as part of this guide: Adding to the stdlib Changing Python Other interpreter implementations ¶ This guide is specifically for contributing to the Python reference interpreter, also known as CPython (while most of the standard library is written in Python, the interpreter core is written in C and integrates most easily with the C and C++ ecosystems). There are other Python implementations, each with a different focus. Like CPython, they always have more things they would like to do than they have developers to work on them. Some major examples that may be of interest are: PyPy : A Python interpreter focused on high speed (JIT-compiled) operation on major platforms. GraalPy : A Python interpreter which has first-class support for embedding in Java, built on GraalVM. Jython : A Python interpreter focused on good integration with the Java Virtual Machine (JVM) environment. IronPython : A Python interpreter focused on good integration with the Common Language Runtime (CLR) provided by .NET and Mono. Stackless : A Python interpreter focused on providing lightweight microthreads while remaining largely compatible with CPython specific extension modules. MicroPython : A tiny Python interpreter with small subset of the Python standard library that is optimised to run on microcontrollers and in constrained environments. CircuitPython : A fork of MicroPython designed to simplify experimenting and learning to code on low-cost microcontroller boards. Key resources ¶ Coding style guides PEP 7 (Style Guide for C Code) PEP 8 (Style Guide for Python Code) Issue tracker Experts index Buildbot status Source code Browse online Snapshot of the *main* branch PEPs (Python Enhancement Proposals) Where to get help Team log Additional resources ¶ Anyone can clone the sources for this guide. See Helping with the Developer’s Guide . Help with … CPython’s internals Changing CPython’s grammar Tool support GDB support Dynamic analysis with Clang Various tools with configuration files as found in the Misc directory Information about editors and their configurations can be found in the wiki python.org maintenance Search this guide Code of conduct ¶ Please note that all interactions on Python Software Foundation -supported infrastructure is covered by the PSF Code of Conduct , which includes all infrastructure used in the development of Python itself (for example, mailing lists, issue trackers, GitHub, etc.). In general this means everyone is expected to be open, considerate, and respectful of others no matter what their position is within the project. Status of Python branches ¶ Moved to Status of Python versions Full table of contents ¶ Getting started Setup and building Install Git Get the source code Compile and build Install dependencies Regenerate configure Regenerate the ABI dump Troubleshoot the build Editors and tools Directory structure Using a container Fixing “easy” issues (and beyond) Git bootcamp and cheat sheet Forking CPython GitHub repository Cloning a forked CPython repository Configure the remotes Listing the remote repositories Setting up your name and email address Enabling autocrlf on Windows Creating and switching branches Deleting branches Renaming branch Staging and committing files Reverting changes Stashing changes Comparing changes Pushing changes Creating a pull request Linking to issues and pull requests Updating your CPython fork Applying a patch to Git Checking out others’ pull requests Accepting and merging a pull request Cancelling an automatic merge Backporting merged changes Editing a pull request prior to merging GitHub CLI Git worktree Lifecycle of a pull request Introduction Quick guide Step-by-step guide Making good PRs Copyrights patchcheck Making good commits Licensing Submitting Converting an existing patch from b.p.o to GitHub Reviewing Keeping continuous integration green Update branch button Committing/rejecting Crediting Where to get help Discourse Ask #python-dev Core mentorship File a bug Generative AI Acceptable uses Unacceptable uses Considerations for success Development workflow Following Python’s development Standards of behaviour in these communication channels Mailing lists Discourse (discuss.python.org web forum) Discord (private chat server) IRC Blogs Setting expectations for open source participation Additional repositories Changing Python Considerations Suggesting new features and language changes PEP process Development cycle Branches Stages Repository administration Governance Adding to the stdlib Adding to a pre-existing module Adding a new module Adding a new environment variable Standard library extension modules Classifying extension modules Adding an extension module to CPython Changing Python’s C API The internal API Public C API Unstable C API Limited API Changing CPython’s grammar Porting to a new platform Software Bill-of-Materials (SBOM) Updating a dependency Adding a new dependency Removing a dependency Python Security Response Team (PSRT) Vulnerability report triage Coordinating a vulnerability report Handling code signing certificate reports Template responses Issues and triaging Issue tracker Using the issue tracker Disagreement with a resolution on the issue tracker Triaging an issue Checklist for triaging Helping triage issues GitHub labels Type labels Component labels OS labels Topic labels Version labels Other labels Labels specific to PRs GitHub issues for BPO users How to format my comments nicely? How to attach files to an issue? How to link to file paths in the repository when writing comments? How to do advanced searches? Where is the “nosy list”? How to add issue dependencies? What on earth is a “mannequin”? Where did the “resolution” field go? Where did the “low”, “high”, and “critical” priorities go? How to find a random issue? Where are regression labels? Triage Team Becoming a member of the Python triage team Documentation Getting started Introduction Building the documentation Helping with documentation Python documentation Helping with documentation issues Translating Proofreading Style guide Footnotes Capitalization Specific words Use simple language Charged terminology to avoid Diátaxis Links Affirmative tone Author attribution Pronunciation of dunder names Economy of expression Security considerations (and other concerns) Code examples Code equivalents Audience Function signatures reStructuredText markup Quick reference reStructuredText primer Typographic conventions Additional markup constructs Translations Translating Coordinating Helping with the Developer’s Guide Developer’s Guide workflow Testing and buildbots Running and writing tests Running Writing Benchmarks Silence warnings from the test suite Increase test coverage Common gotchas Measuring coverage Filing the issue Measuring coverage of C code with gcov and lcov Working with buildbots In case of trouble Buildbot failures on pull requests Triggering on pull requests Checking results of automatic builds Stability Flags-dependent failures Ordering-dependent failures Transient failures New buildbot workers Preparing for buildbot worker setup Setting up the buildbot worker Buildbot worker operation Required ports Required resources Security considerations Development tools Argument Clinic Background Reference GDB support Page moved CPython tips Dynamic analysis with Clang What is Clang? What are sanitizers? Clang/LLVM setup Python build setup Analyzing the output Tools for tracking compiler warnings What to do if a warning check fails GitHub CI Updating the warning ignore file Core team Responsibilities Communication channels and bug notifications Sign a contributor agreement Pull request merging Expectations Accepting pull requests Assessing a pull request Updating NEWS and What’s New in Python Working with Git Experts index Stdlib Tools Platforms Miscellaneous Documentation translations Team log Procedure for granting or dropping access Motivations and affiliations Published entries Goals of this page Limitations on scope How to join the core team What it takes Gaining commit privileges Poll template Memorialization Rationale The process CPython’s internals Status of Python versions Supported versions Unsupported versions Full chart Status key Python Contributor’s Guide (draft) Using this guide Contents [Plan for the Contributor’s Guide] Introduction The CPython project Issues and triaging Documentation contributions Code contributions Core team Accessibility, design, and user success Security and infrastructure contributions Workflows Next Getting started Copyright © 2011 Python Software Foundation Made with Sphinx and @pradyunsg 's Furo On this page Python Developer’s Guide Quick reference Quick links Contributing Proposing changes to Python itself Other interpreter implementations Key resources Additional resources Code of conduct Status of Python branches Full table of contents | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#3-how-we-use-your-information | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://youtu.be/2m8-iS3XiaE | State Management with RxJS - AiA 363 - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x89ec257d8a0d4192"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtqOUZobEtWNUdsayjkjZjLBjIKCgJLUhIEGgAgEA%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRLl5ZrEd0XNQ0XsbSH4OpSLACLziW7mYQrkHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","collectionThumbnailViewModel","thumbnailHoverOverlayViewModel","badgeViewModel","avatarStackViewModel","dialogViewModel","dialogHeaderViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","endScreenPlaylistRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtqOUZobEtWNUdsayjkjZjLBjIKCgJLUhIEGgAgEA%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjq97T1kIiSAxV1mlYBHSzlO90yDHJlbGF0ZWQtYXV0b0ihk97uktHPt9oBmgEFCAMQ-B3KAQRXP6a9","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=IIyMPA69yJA\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"IIyMPA69yJA","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjq97T1kIiSAxV1mlYBHSzlO90yDHJlbGF0ZWQtYXV0b0ihk97uktHPt9oBmgEFCAMQ-B3KAQRXP6a9","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=IIyMPA69yJA\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"IIyMPA69yJA","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjq97T1kIiSAxV1mlYBHSzlO90yDHJlbGF0ZWQtYXV0b0ihk97uktHPt9oBmgEFCAMQ-B3KAQRXP6a9","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=IIyMPA69yJA\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"IIyMPA69yJA","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"State Management with RxJS - AiA 363"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 63회"},"shortViewCount":{"simpleText":"조회수 63회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCzJtOC1pUzNYaWFFGmBFZ3N5YlRndGFWTXpXR2xoUlVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHpKdE9DMXBVek5ZYVdGRkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}}],"trackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"1","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJUCEKVBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},{"innertubeCommand":{"clickTrackingParams":"CJUCEKVBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJYCEPqGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJYCEPqGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"2m8-iS3XiaE"},"likeParams":"Cg0KCzJtOC1pUzNYaWFFIAAyDAjljZjLBhDmg9rlAQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CJYCEPqGBCITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}}}}}}}]}},"accessibilityText":"다른 사용자 1명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJUCEKVBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"2","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJQCEKVBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},{"innertubeCommand":{"clickTrackingParams":"CJQCEKVBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"2m8-iS3XiaE"},"removeLikeParams":"Cg0KCzJtOC1pUzNYaWFFGAAqDAjljZjLBhDp_NrlAQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 1명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJQCEKVBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isTogglingDisabled":true}},"likeStatusEntityKey":"EgsybTgtaVMzWGlhRSA-KAE%3D","likeStatusEntity":{"key":"EgsybTgtaVMzWGlhRSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJICEKiPCSITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}},{"innertubeCommand":{"clickTrackingParams":"CJICEKiPCSITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJMCEPmGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJMCEPmGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"2m8-iS3XiaE"},"dislikeParams":"Cg0KCzJtOC1pUzNYaWFFEAAiDAjljZjLBhDdyNzlAQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CJMCEPmGBCITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJICEKiPCSITCOr3tPWQiJIDFXWaVgEdLOU73Q==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJECEKiPCSITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}},{"innertubeCommand":{"clickTrackingParams":"CJECEKiPCSITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"2m8-iS3XiaE"},"removeLikeParams":"Cg0KCzJtOC1pUzNYaWFFGAAqDAjljZjLBhDZ6dzlAQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJECEKiPCSITCOr3tPWQiJIDFXWaVgEdLOU73Q==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isTogglingDisabled":true}},"dislikeEntityKey":"EgsybTgtaVMzWGlhRSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgsybTgtaVMzWGlhRSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CI8CEOWWARgDIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},{"innertubeCommand":{"clickTrackingParams":"CI8CEOWWARgDIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgsybTgtaVMzWGlhRaABAQ%3D%3D","commands":[{"clickTrackingParams":"CI8CEOWWARgDIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJACEI5iIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CI8CEOWWARgDIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CI0CEOuQCSITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CI4CEPuGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D2m8-iS3XiaE\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CI4CEPuGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=2m8-iS3XiaE","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"2m8-iS3XiaE","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=da6f3e892dd789a1\u0026ip=1.208.108.242\u0026initcwndbps=3705000\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CI4CEPuGBCITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}}}}}},"trackingParams":"CI0CEOuQCSITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CIsCEOuQCSITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}},{"innertubeCommand":{"clickTrackingParams":"CIsCEOuQCSITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CIwCEPuGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D2m8-iS3XiaE\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CIwCEPuGBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=2m8-iS3XiaE","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"2m8-iS3XiaE","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=da6f3e892dd789a1\u0026ip=1.208.108.242\u0026initcwndbps=3705000\u0026mt=1768293891\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CIwCEPuGBCITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CIsCEOuQCSITCOr3tPWQiJIDFXWaVgEdLOU73Q==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","superTitleLink":{"runs":[{"text":"Adventures in Angular Podcast Episodes","navigationEndpoint":{"clickTrackingParams":"CIoCELW0CRgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLJesql-aSfX6PKiA6XAjzbUCWiYCUkU2q","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLJesql-aSfX6PKiA6XAjzbUCWiYCUkU2q"}}}]},"dateText":{"simpleText":"2022. 12. 27."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"3년 전"}},"simpleText":"3년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Top End Devs","navigationEndpoint":{"clickTrackingParams":"CIkCEOE5IhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CIkCEOE5IhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 4.5천명"}},"simpleText":"구독자 4.5천명"},"trackingParams":"CIkCEOE5IhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCABJEQ57MIn6X3TIHIebJUw","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CPsBEJsrIhMI6ve09ZCIkgMVdZpWAR0s5TvdKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Top End Devs을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Top End Devs을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CIgCEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CIcCEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CIACEJf5ASITCOr3tPWQiJIDFXWaVgEdLOU73Q==","command":{"clickTrackingParams":"CIACEJf5ASITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CIACEJf5ASITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CIYCEOy1BBgDIhMI6ve09ZCIkgMVdZpWAR0s5TvdMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRXP6a9","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcSAggBGAAgBFITCgIIAxILMm04LWlTM1hpYUUYAA%3D%3D"}},"trackingParams":"CIYCEOy1BBgDIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CIUCEO21BBgEIhMI6ve09ZCIkgMVdZpWAR0s5TvdMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRXP6a9","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcSAggDGAAgBFITCgIIAxILMm04LWlTM1hpYUUYAA%3D%3D"}},"trackingParams":"CIUCEO21BBgEIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CIECENuLChgFIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIECENuLChgFIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CIICEMY4IhMI6ve09ZCIkgMVdZpWAR0s5Tvd","dialogMessages":[{"runs":[{"text":"Top End Devs"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CIQCEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdMgV3YXRjaMoBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"CgIIAxILMm04LWlTM1hpYUUYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CIQCEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CIMCEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CIECENuLChgFIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CPsBEJsrIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CP8BEP2GBCITCOr3tPWQiJIDFXWaVgEdLOU73TIJc3Vic2NyaWJlygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D2m8-iS3XiaE%26continue_action%3DQUFFLUhqa3BxSmZyd3Fzd3BfMW9adjdPMWNzQzZEc24xUXxBQ3Jtc0ttZTl4a0xUT3ZLTjFIQktmYnozSFA4a0RHYmx2S3ZldWpjNnRWeEFLeG96U2hreUhVNlR5VkxEY0c0dkp3SEY4VHlZN1JDZWR3Q3ZRNGw2QkNfRVhhNUlSajdPMGFvYXJPaVM2WU9mejhOOFlrMEd0cWRtYUlXVFVfSHlHOFdZM0FISWJqejZodVp6SGw5dFJxaGNWSnRFWER2QkdJbHZDQUxTUzJXRVQ2Qm9OamxzTWU5SUR3UTNYZVMzZW1sWUt1VW5WNmM\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CP8BEP2GBCITCOr3tPWQiJIDFXWaVgEdLOU73coBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=2m8-iS3XiaE","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"2m8-iS3XiaE","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=da6f3e892dd789a1\u0026ip=1.208.108.242\u0026initcwndbps=3705000\u0026mt=1768293891\u0026oweuc="}}}}},"continueAction":"QUFFLUhqa3BxSmZyd3Fzd3BfMW9adjdPMWNzQzZEc24xUXxBQ3Jtc0ttZTl4a0xUT3ZLTjFIQktmYnozSFA4a0RHYmx2S3ZldWpjNnRWeEFLeG96U2hreUhVNlR5VkxEY0c0dkp3SEY4VHlZN1JDZWR3Q3ZRNGw2QkNfRVhhNUlSajdPMGFvYXJPaVM2WU9mejhOOFlrMEd0cWRtYUlXVFVfSHlHOFdZM0FISWJqejZodVp6SGw5dFJxaGNWSnRFWER2QkdJbHZDQUxTUzJXRVQ2Qm9OamxzTWU5SUR3UTNYZVMzZW1sWUt1VW5WNmM","idamTag":"66429"}},"trackingParams":"CP8BEP2GBCITCOr3tPWQiJIDFXWaVgEdLOU73Q=="}}}}}},"subscribedEntityKey":"EhhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CPsBEJsrIhMI6ve09ZCIkgMVdZpWAR0s5TvdKPgdMgV3YXRjaMoBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"EgIIAxgAIgsybTgtaVMzWGlhRQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CPsBEJsrIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPsBEJsrIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CPwBEMY4IhMI6ve09ZCIkgMVdZpWAR0s5Tvd","dialogMessages":[{"runs":[{"text":"Top End Devs"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CP4BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdKPgdMgV3YXRjaMoBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"CgIIAxILMm04LWlTM1hpYUUYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CP4BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CP0BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Amal Ayyash is a UX Designer and Front-end Developer. and her current main focus is Angular. She joins Chuck and Lucas to discuss her article, “RxJS-based state management in Angular”. She starts the show off by explaining the reason why she chose to use RxJS to create state management instead of using NgRX. She also gives advice to other developers, encouraging them to use their own frameworks or codes rather than third-party solutions.\n\nhttps://topenddevs.com/podcasts/adven...","commandRuns":[{"startIndex":443,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CPoBEM2rARgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdSKGT3u6S0c-32gHKAQRXP6a9","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbk1XOWhmckMzVTR2UDZWU0F4OUZBUURDSXhqZ3xBQ3Jtc0ttQW4yS2lsTWdPSTZOaGRzbnRzczNoQ0E5YllTbzA3Z2hNWlhLRWhfLXR5OXNmN0s4VTIxcVRjXzBLQ0VHYnFNalIzM1B0T0U5MmV0NklGZ0h3YXFTak5FZmtuYko1XzE4U2ZhdW91NkdUOGZLbkJ5Zw\u0026q=https%3A%2F%2Ftopenddevs.com%2Fpodcasts%2Fadventures-in-angular%2Fepisodes%2Fstate-management-with-rxjs-aia-363\u0026v=2m8-iS3XiaE","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbk1XOWhmckMzVTR2UDZWU0F4OUZBUURDSXhqZ3xBQ3Jtc0ttQW4yS2lsTWdPSTZOaGRzbnRzczNoQ0E5YllTbzA3Z2hNWlhLRWhfLXR5OXNmN0s4VTIxcVRjXzBLQ0VHYnFNalIzM1B0T0U5MmV0NklGZ0h3YXFTak5FZmtuYko1XzE4U2ZhdW91NkdUOGZLbkJ5Zw\u0026q=https%3A%2F%2Ftopenddevs.com%2Fpodcasts%2Fadventures-in-angular%2Fepisodes%2Fstate-management-with-rxjs-aia-363\u0026v=2m8-iS3XiaE","target":"TARGET_NEW_WINDOW","nofollow":true}}}}],"styleRuns":[{"startIndex":0,"length":443,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":443,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":443,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":443,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CPkBELsvGAMiEwjq97T1kIiSAxV1mlYBHSzlO93KAQRXP6a9","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SCzJtOC1pUzNYaWFFGAYyJSIRIgsybTgtaVMzWGlhRTAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CPkBELsvGAMiEwjq97T1kIiSAxV1mlYBHSzlO90=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CPgBELovIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/MvoFYuEn6SU/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAj5XbgK08pmBosYp9NaPExufEm6g","width":168,"height":94},{"url":"https://i.ytimg.com/vi/MvoFYuEn6SU/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAA0yDJubDcWd08tqQGduBvjsOaXw","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"37:52","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"MvoFYuEn6SU","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"37분 52초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CPcBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"MvoFYuEn6SU","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPcBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CPYBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"MvoFYuEn6SU"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPYBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CO8BENTEDBgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CPUBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPUBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"MvoFYuEn6SU","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPUBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["MvoFYuEn6SU"],"params":"CAQ%3D"}},"videoIds":["MvoFYuEn6SU"],"videoCommand":{"clickTrackingParams":"CPUBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=MvoFYuEn6SU\u0026pp=0gcJCZgAKgI3ePta","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"MvoFYuEn6SU","playerParams":"0gcJCZgAKgI3ePta","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh26z.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=32fa0562e127e925\u0026ip=1.208.108.242\u0026initcwndbps=4413750\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPUBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPQBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CO8BENTEDBgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"AiA 241: Azure Functions with Colby Tresness LIVE at Microsoft BUILD"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"Top End Devs 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CO8BENTEDBgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"Top End Devs"}}]},{"metadataParts":[{"text":{"content":"조회수 627회"}},{"text":{"content":"6년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CPABEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPMBEP6YBBgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPMBEP6YBBgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPMBEP6YBBgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"MvoFYuEn6SU","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPMBEP6YBBgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["MvoFYuEn6SU"],"params":"CAQ%3D"}},"videoIds":["MvoFYuEn6SU"],"videoCommand":{"clickTrackingParams":"CPMBEP6YBBgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=MvoFYuEn6SU","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"MvoFYuEn6SU","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh26z.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=32fa0562e127e925\u0026ip=1.208.108.242\u0026initcwndbps=4413750\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPIBEJSsCRgBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPIBEJSsCRgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPIBEJSsCRgBIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtNdm9GWXVFbjZTVQ%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPABEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtNdm9GWXVFbjZTVQ%3D%3D","commands":[{"clickTrackingParams":"CPABEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPEBEI5iIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPABEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"MvoFYuEn6SU","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CO8BENTEDBgAIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","visibility":{"types":"12"}}},"accessibilityContext":{"label":"AiA 241: Azure Functions with Colby Tresness LIVE at Microsoft BUILD 37분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CO8BENTEDBgAIhMI6ve09ZCIkgMVdZpWAR0s5TvdMgdyZWxhdGVkSKGT3u6S0c-32gGaAQUIARD4HcoBBFc_pr0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=MvoFYuEn6SU","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"MvoFYuEn6SU","nofollow":true,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh26z.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=32fa0562e127e925\u0026ip=1.208.108.242\u0026initcwndbps=4413750\u0026mt=1768293891\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/JnwjU06yoEE/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAXsS9Qj9VlVnSEeMxaXl1NdXutYA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/JnwjU06yoEE/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDsacHP-YW0RHeEZtJEK4ugIi7hHA","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"9:43","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"JnwjU06yoEE","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"9분 43초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CO4BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"JnwjU06yoEE","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CO4BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CO0BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"JnwjU06yoEE"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CO0BEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"COYBENTEDBgBIhMI6ve09ZCIkgMVdZpWAR0s5Tvd"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"COwBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COwBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"JnwjU06yoEE","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COwBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["JnwjU06yoEE"],"params":"CAQ%3D"}},"videoIds":["JnwjU06yoEE"],"videoCommand":{"clickTrackingParams":"COwBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5TvdygEEVz-mvQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=JnwjU06yoEE\u0026pp=ugUEEgJlbg%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"JnwjU06yoEE","playerParams":"ugUEEgJlbg%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=267c23534eb2a041\u0026ip=1.208.108.242\u0026initcwndbps=3736250\u0026mt=1768293891\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"COwBEPBbIhMI6ve09ZCIkgMVdZpWAR0s5Tvd","type":"BUTTON_ | 2026-01-13T08:48:42 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#audience | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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.python.org/3/license.html#zstandard-bindings | 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:42 |
https://highlight.io/ambassador-program | Highlight Ambassador Program Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up The Highlight Ambassador Program Join our community of enthusiasts and experts committed to spreading the word about our open-source observability platform. Apply Now What You'll Do Educate others about Highlight and OpenTelemetry Create content and participate in events Build relationships within the developer community Collaborate with the Highlight team on initiatives Ambassador Perks Exclusive access to early releases and beta features Official swag and recognition as a community leader Opportunities to feature your content Connect with like-minded developers Conference tickets for promoting Highlight Who Can Apply We're looking for developers, DevOps engineers, content creators, and anyone passionate about observability and the open-source community. Whether you're experienced or just starting, if you believe in Highlight's mission, we want to hear from you! Apply Now Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#1-what-does-this-privacy-policy-apply-to | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#2-personal-information-we-collect | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://docs.python.org/download.html | Download — Python 3.14.2 documentation Theme Auto Light Dark Navigation index modules | Python » 3.14.2 Documentation » Download | Theme Auto Light Dark | Download Python 3.14 documentation Last updated on: Jan 13, 2026 (06:19 UTC). Download an archive containing all the documentation for this version of Python: Format Packed as .zip Packed as .tar.bz2 HTML Download Download Plain text Download Download Texinfo Download Download EPUB Download We no longer provide pre-built PDFs of the documentation. To build a PDF archive, follow the instructions in the Developer's Guide and run make dist-pdf in the Doc/ directory of a copy of the CPython repository. See the directory listing for file sizes. Problems Open an issue if you have comments or suggestions for the Python documentation. « Navigation index modules | Python » 3.14.2 Documentation » Download | 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:42 |
https://docs.suprsend.com/docs/integrate-go-sdk#initialization | Integrate Go SDK - 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 Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK 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 Go SDK Integrate Go SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Integrate Go SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Go SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation Install suprsend-go sdk bash Copy Ask AI go get github.com/suprsend/suprsend-go Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). Request Copy Ask AI package main import ( " log " suprsend " github.com/suprsend/suprsend-go " ) // Initialize SDK func main () { opts := [] suprsend . ClientOption { // suprsend.WithDebug(true), } suprClient , err := suprsend . NewClient ( "__workspace_key__" , "__workspace_secret__" , opts ... ) if err != nil { log . Println ( err ) } } Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Go SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:48:42 |
https://golf.forem.com/privacy#11-other-provisions | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:42 |
https://docs.python.org/3/license.html#zero-clause-bsd-license-for-code-in-the-python-documentation | 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:42 |
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:42 |
https://www.youtube.com/watch?v=7cPWmID5XAk&list=PLNG_1j3cPCaZZ7etkzWA7JfdmKWT0pMsa&index=10 | The ROI of Designing with React - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x93774a1ec3d1167b"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtDM3VLbFc5YUN1USjnjZjLBjIKCgJLUhIEGgAgSw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRr3UFYcCIHjE2raxgjxeo2O0ALgiXrsoOr5HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","messageRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","continuationItemRenderer","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","adsEngagementPanelContentRenderer","engagementPanelTitleHeaderRenderer","chipBarViewModel","chipViewModel","sectionListRenderer","macroMarkersListRenderer","macroMarkersListItemRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtDM3VLbFc5YUN1USjnjZjLBjIKCgJLUhIEGgAgSw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwiA7v72kIiSAxUnRTgFHfPKHHEyDHJlbGF0ZWQtYXV0b0iJuOWHiNP14e0BmgEFCAMQ-B3KAQQ1uX8m","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FZ0cG47msEk\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FZ0cG47msEk","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiA7v72kIiSAxUnRTgFHfPKHHEyDHJlbGF0ZWQtYXV0b0iJuOWHiNP14e0BmgEFCAMQ-B3KAQQ1uX8m","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FZ0cG47msEk\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FZ0cG47msEk","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiA7v72kIiSAxUnRTgFHfPKHHEyDHJlbGF0ZWQtYXV0b0iJuOWHiNP14e0BmgEFCAMQ-B3KAQQ1uX8m","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FZ0cG47msEk\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FZ0cG47msEk","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"The ROI of Designing with React"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 5,946회"},"shortViewCount":{"simpleText":"조회수 5.9천회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CJ8CEMyrARgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCzdjUFdtSUQ1WEFrGmBFZ3MzWTFCWGJVbEVOVmhCYTBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHpkalVGZHRTVVExV0VGckwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CJ8CEMyrARgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}}],"trackingParams":"CJ8CEMyrARgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"85","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKoCEKVBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},{"innertubeCommand":{"clickTrackingParams":"CKoCEKVBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKsCEPqGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKsCEPqGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"7cPWmID5XAk"},"likeParams":"Cg0KCzdjUFdtSUQ1WEFrIAAyDAjojZjLBhD_x6zBAQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CKsCEPqGBCITCIDu_vaQiJIDFSdFOAUd88occQ=="}}}}}}}]}},"accessibilityText":"다른 사용자 85명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKoCEKVBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"86","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKkCEKVBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},{"innertubeCommand":{"clickTrackingParams":"CKkCEKVBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"7cPWmID5XAk"},"removeLikeParams":"Cg0KCzdjUFdtSUQ1WEFrGAAqDAjojZjLBhDfua3BAQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 85명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKkCEKVBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CJ8CEMyrARgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isTogglingDisabled":true}},"likeStatusEntityKey":"Egs3Y1BXbUlENVhBayA-KAE%3D","likeStatusEntity":{"key":"Egs3Y1BXbUlENVhBayA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKcCEKiPCSITCIDu_vaQiJIDFSdFOAUd88occQ=="}},{"innertubeCommand":{"clickTrackingParams":"CKcCEKiPCSITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKgCEPmGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKgCEPmGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"7cPWmID5XAk"},"dislikeParams":"Cg0KCzdjUFdtSUQ1WEFrEAAiDAjojZjLBhCFga_BAQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CKgCEPmGBCITCIDu_vaQiJIDFSdFOAUd88occQ=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKcCEKiPCSITCIDu_vaQiJIDFSdFOAUd88occQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKYCEKiPCSITCIDu_vaQiJIDFSdFOAUd88occQ=="}},{"innertubeCommand":{"clickTrackingParams":"CKYCEKiPCSITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"7cPWmID5XAk"},"removeLikeParams":"Cg0KCzdjUFdtSUQ1WEFrGAAqDAjojZjLBhCfoq_BAQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKYCEKiPCSITCIDu_vaQiJIDFSdFOAUd88occQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CJ8CEMyrARgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isTogglingDisabled":true}},"dislikeEntityKey":"Egs3Y1BXbUlENVhBayA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egs3Y1BXbUlENVhBayD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKQCEOWWARgCIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},{"innertubeCommand":{"clickTrackingParams":"CKQCEOWWARgCIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgs3Y1BXbUlENVhBa6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CKQCEOWWARgCIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CKUCEI5iIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKQCEOWWARgCIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CKICEOuQCSITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKMCEPuGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D7cPWmID5XAk%2526pp%253D0gcJCfcAYGclG_1k\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKMCEPuGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=7cPWmID5XAk\u0026pp=0gcJCfcAYGclG_1k","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"7cPWmID5XAk","playerParams":"0gcJCfcAYGclG_1k","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=edc3d69880f95c09\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CKMCEPuGBCITCIDu_vaQiJIDFSdFOAUd88occQ=="}}}}}},"trackingParams":"CKICEOuQCSITCIDu_vaQiJIDFSdFOAUd88occQ=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CKACEOuQCSITCIDu_vaQiJIDFSdFOAUd88occQ=="}},{"innertubeCommand":{"clickTrackingParams":"CKACEOuQCSITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKECEPuGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D7cPWmID5XAk%2526pp%253D0gcJCfcAYGclG_1k\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKECEPuGBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=7cPWmID5XAk\u0026pp=0gcJCfcAYGclG_1k","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"7cPWmID5XAk","playerParams":"0gcJCfcAYGclG_1k","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=edc3d69880f95c09\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CKECEPuGBCITCIDu_vaQiJIDFSdFOAUd88occQ=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CKACEOuQCSITCIDu_vaQiJIDFSdFOAUd88occQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CJ8CEMyrARgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","dateText":{"simpleText":"2021. 12. 9."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"4년 전"}},"simpleText":"4년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"React Conf","navigationEndpoint":{"clickTrackingParams":"CJ4CEOE5IhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CJ4CEOE5IhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 3.43만명"}},"simpleText":"구독자 3.43만명"},"trackingParams":"CJ4CEOE5IhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UC1hOCRBN2mnXgN5reSoO3pQ","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CJACEJsrIhMIgO7-9pCIkgMVJ0U4BR3zyhxxKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CJ0CEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CJwCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CJUCEJf5ASITCIDu_vaQiJIDFSdFOAUd88occQ==","command":{"clickTrackingParams":"CJUCEJf5ASITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CJUCEJf5ASITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CJsCEOy1BBgDIhMIgO7-9pCIkgMVJ0U4BR3zyhxxMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQQ1uX8m","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggBGAAgBFITCgIIAxILN2NQV21JRDVYQWsYAA%3D%3D"}},"trackingParams":"CJsCEOy1BBgDIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CJoCEO21BBgEIhMIgO7-9pCIkgMVJ0U4BR3zyhxxMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQQ1uX8m","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggDGAAgBFITCgIIAxILN2NQV21JRDVYQWsYAA%3D%3D"}},"trackingParams":"CJoCEO21BBgEIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CJYCENuLChgFIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJYCENuLChgFIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CJcCEMY4IhMIgO7-9pCIkgMVJ0U4BR3zyhxx","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CJkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxMgV3YXRjaMoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILN2NQV21JRDVYQWsYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CJkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CJgCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CJYCENuLChgFIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CJACEJsrIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJQCEP2GBCITCIDu_vaQiJIDFSdFOAUd88occTIJc3Vic2NyaWJlygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D7cPWmID5XAk%2526pp%253D0gcJCfcAYGclG_1k%26continue_action%3DQUFFLUhqblNKUGtyMXBzS0t1d2FqU1BjV3hVaURWSlJFUXxBQ3Jtc0tsTlhxUVd6OWxKbXAxbkg0X3drenpnbTRFMDBLSWxVZkloTl83MU1qYXZtYkwyRHgxR0pTUDYzZGszclZZczk1cW42bF9VMnEtZkdOSG51Mk1LUUxkSlZZazFVTzlGWmkxWGpZYm55YlVyRzVjcHlFcjBLc09UUTBvamVWelFvZ2h2dGNNUmZfWVhWd2twSmpqS3JoeG82LUVGZFRicGdhVS1KUk10dnpucGNkSWI0X3owSWhFdlFVNnFzMmpsN2dYYXlIMHU\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJQCEP2GBCITCIDu_vaQiJIDFSdFOAUd88occcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=7cPWmID5XAk\u0026pp=0gcJCfcAYGclG_1k","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"7cPWmID5XAk","playerParams":"0gcJCfcAYGclG_1k","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=edc3d69880f95c09\u0026ip=1.208.108.242\u0026initcwndbps=3691250\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqblNKUGtyMXBzS0t1d2FqU1BjV3hVaURWSlJFUXxBQ3Jtc0tsTlhxUVd6OWxKbXAxbkg0X3drenpnbTRFMDBLSWxVZkloTl83MU1qYXZtYkwyRHgxR0pTUDYzZGszclZZczk1cW42bF9VMnEtZkdOSG51Mk1LUUxkSlZZazFVTzlGWmkxWGpZYm55YlVyRzVjcHlFcjBLc09UUTBvamVWelFvZ2h2dGNNUmZfWVhWd2twSmpqS3JoeG82LUVGZFRicGdhVS1KUk10dnpucGNkSWI0X3owSWhFdlFVNnFzMmpsN2dYYXlIMHU","idamTag":"66429"}},"trackingParams":"CJQCEP2GBCITCIDu_vaQiJIDFSdFOAUd88occQ=="}}}}}},"subscribedEntityKey":"EhhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CJACEJsrIhMIgO7-9pCIkgMVJ0U4BR3zyhxxKPgdMgV3YXRjaMoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"EgIIAxgAIgs3Y1BXbUlENVhBaw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CJACEJsrIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJACEJsrIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CJECEMY4IhMIgO7-9pCIkgMVJ0U4BR3zyhxx","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CJMCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxKPgdMgV3YXRjaMoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILN2NQV21JRDVYQWsYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CJMCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CJICEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CI8CEM2rARgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CI8CEM2rARgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CI8CEM2rARgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CI8CEM2rARgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CI8CEM2rARgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CI8CEM2rARgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Linton Ye","styleRuns":[{"startIndex":0,"length":9,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":9,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"messageRenderer":{"text":{"runs":[{"text":"댓글이 사용 중지되었습니다. "},{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CI4CEJY7GAAiEwiA7v72kIiSAxUnRTgFHfPKHHHKAQQ1uX8m","commandMetadata":{"webCommandMetadata":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko"}}}]},"trackingParams":"CI4CEJY7GAAiEwiA7v72kIiSAxUnRTgFHfPKHHE="}}],"trackingParams":"CI0CELsvGAMiEwiA7v72kIiSAxUnRTgFHfPKHHE=","sectionIdentifier":"comment-item-section"}}],"trackingParams":"CIwCELovIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/pj5N-Khihgc/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBe418zAEgrK8nz2lVa5hfLGw12-Q","width":168,"height":94},{"url":"https://i.ytimg.com/vi/pj5N-Khihgc/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAox6aKNoDup6er69UGEUVApcrr6g","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"18:36","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"pj5N-Khihgc","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"18분 36초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CIsCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"pj5N-Khihgc","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIsCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CIoCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"pj5N-Khihgc"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIoCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CIMCENTEDBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CIkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"pj5N-Khihgc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CIkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pj5N-Khihgc"],"params":"CAQ%3D"}},"videoIds":["pj5N-Khihgc"],"videoCommand":{"clickTrackingParams":"CIkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIkCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIgCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CIMCENTEDBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"스트리밍 서버 렌더링(서스펜스 기능 포함)"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CIMCENTEDBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회수 5.2만회"}},{"text":{"content":"4년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CIQCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CIcCEP6YBBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CIcCEP6YBBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIcCEP6YBBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"pj5N-Khihgc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CIcCEP6YBBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pj5N-Khihgc"],"params":"CAQ%3D"}},"videoIds":["pj5N-Khihgc"],"videoCommand":{"clickTrackingParams":"CIcCEP6YBBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VUw%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VUw%3D%3D","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CIYCEJSsCRgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CIYCEJSsCRgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CIYCEJSsCRgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtwajVOLUtoaWhnYw%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CIQCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtwajVOLUtoaWhnYw%3D%3D","commands":[{"clickTrackingParams":"CIQCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CIUCEI5iIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CIQCEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"pj5N-Khihgc","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CIMCENTEDBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","visibility":{"types":"12"}}},"accessibilityContext":{"label":"스트리밍 서버 렌더링(서스펜스 기능 포함) 18분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CIMCENTEDBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhxxMgdyZWxhdGVkSIm45YeI0_Xh7QGaAQUIARD4HcoBBDW5fyY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pj5N-Khihgc\u0026pp=ugUHEgVlbi1VU9IHCQlNCgGHKiGM7w%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pj5N-Khihgc","playerParams":"ugUHEgVlbi1VU9IHCQlNCgGHKiGM7w%3D%3D","nofollow":true,"ustreamerConfig":"KgkKBxIFZW4tVVM=","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a63e4df8a8628607\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/FZ0cG47msEk/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDH5r7Pql2X_EahvH-14ODdUVWJ5Q","width":168,"height":94},{"url":"https://i.ytimg.com/vi/FZ0cG47msEk/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLCTtuJn7VO4tBUlWnafyCq1IkkwwQ","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"33:49","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"FZ0cG47msEk","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"33분 49초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CIICEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"FZ0cG47msEk","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIICEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CIECEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"FZ0cG47msEk"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIECEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CPoBENTEDBgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CIACEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIACEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"FZ0cG47msEk","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CIACEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["FZ0cG47msEk"],"params":"CAQ%3D"}},"videoIds":["FZ0cG47msEk"],"videoCommand":{"clickTrackingParams":"CIACEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FZ0cG47msEk","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FZ0cG47msEk","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-jwwy.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=159d1c1b8ee6b049\u0026ip=1.208.108.242\u0026initcwndbps=4130000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIACEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CP8BEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxx","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CPoBENTEDBgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxx"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"React 18 Keynote"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPoBENTEDBgBIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회수 13만회"}},{"text":{"content":"4년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEPBbIhMIgO7-9pCIkgMVJ0U4BR3zyhxxygEENbl_Jg==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CP4BEP6YBBgAIhMIgO7-9pCIkgMVJ0U4BR3zyhx | 2026-01-13T08:48:42 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#in-my-brain | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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.python.org/genindex.html | Index — Python 3.14.2 documentation Theme Auto Light Dark Navigation index modules | Python » 3.14.2 Documentation » Index | Theme Auto Light Dark | Index Index pages by letter: Symbols | _ | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z Full index on one page (can be huge) « Navigation index modules | Python » 3.14.2 Documentation » Index | 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:43 |
https://docs.suprsend.com/docs/node-send-event-data | Send and Track Events - 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 Python SDK Node.js SDK Integrate Node SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Java SDK Go SDK SuprSend Client SDK 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 Node.js SDK Send and Track Events Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Node.js SDK Send and Track Events OpenAI Open in ChatGPT Learn how to send events to trigger workflows, with code snippets and examples. OpenAI Open in ChatGPT Send Event You can send event to Suprsend platform by using the supr_client.track_event method. When you call supr_client.track_event , the SDK internally makes an HTTP call to SuprSend Platform to register this request, and you’ll immediately receive a response indicating the acceptance status. The actual processing/execution of event happens asynchronously. Request Sample Response Copy Ask AI const { Suprsend , Event } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "_workspace_key_" , "_workspace_secret_" ); // dictionary containing variable/info about event, If none use {} const properties = { "key1" : "value1" , "key2" : "value2" } const event = new Event ( distinct_id , event_name , properties , { tenant_id : "_tenant_id" , idempotency_key = "__uniq_request_id__" }) // trigger request const response = supr_client . track_event ( event ) response . then (( res ) => console . log ( "response" , res )); Parameter Description distinct_id distinct_id of subscriber performing the event. event_name string identifier for the event like product_purchased . This should exactly match the one from created workflow. properties dictionary representing event information. This can be used to pass variables to template. Property keys shouldn’t start with ss_ or $ . tenant_id (Optional) Tenant ID of the tenant. idempotency_key (Optional) unique key in the request call for idempotent requests . Event naming guidelines: Event Name or Property Name should not start with or , as we have reserved these symbols for our internal events and property names. Idempotent requests SuprSend supports idempotency to ensure that requests can be retried safely without duplicate processing. If Suprsend receives and processes a request with an idempotency_key , it will skip processing requests with same idempotency_key for next 24 hours. You can use this key to track webhooks related to workflow notifications. To make an idempotent request, pass idempotency_key in the event instance. idempotency_key should be unique that you generate for each request. You may use any string up to 255 characters in length as an idempotency key. Ensure that you don’t add any space in start and end of the key as it will be trimmed. Here are some common approaches for assigning idempotency keys: Generate a random UUID for each request. Construct the idempotency key by combining relevant information about the request . This can include parameters, identifiers, or specific contextual details that are meaningful within your application. e.g., you could concatenate the user ID, action, and timestamp to form an idempotency key like user147-new-comment-1687437670 Request-specific Identifier : If your request already contains a unique identifier, such as an order ID or a job ID, you can use that identifier directly as the idempotency key. Trigger multiple events in bulk Use .append() on bulk_events instance to add however-many-records to call in bulk. Request Response Copy Ask AI const { Suprsend , Event } = require ( "@suprsend/node-sdk" ); const supr_client = new Suprsend ( "_workspace_key_" , "_workspace_secret_" ); // create bulk instance const bulk_ins = supr_client . bulk_events . new_instance (); // create event1 instance const event1 = new Event ( "distinct_id1" , "event_name1" , { "k1" : "v1" }) // create event2 instance const event2 = new Event ( "distinct_id2" , "event_name2" , { "k2" : "v2" }) // add event instance to bulk instance bulk_ins . append ( event1 ); bulk_ins . append ( event2 ); // OR bulk_ins . append ( event1 , event2 ); // trigger request const response = bulk_ins . trigger (); response . then (( res ) => console . log ( "response" , res )); Add file attachment (for email) To add one or more attachments to a notification (viz. Email), call add_attachment() on event instance for each attachment file. Ensure that attachment url is valid and public, otherwise error will be raised. Since event API size can’t be > 100 KB, local file paths can’t be passed in event attachment. javascript Copy Ask AI const event = new Event ( distinct_id , event_name , properties ); event . add_attachment ( "/home/user/billing.pdf" ); event . add_attachment ( "https://www.adobe.com/sample_file.pdf" ); A single event instance size (including attachment) must not exceed 100KB (100 x 1024 bytes). Was this page helpful? Yes No Suggest edits Raise issue Previous Trigger Workflow from API Learn how to trigger workflows using direct workflow API, with code snippets and examples. Next ⌘ I x github linkedin youtube Powered by On this page Send Event Idempotent requests Trigger multiple events in bulk Add file attachment (for email) | 2026-01-13T08:48:43 |
https://aws.amazon.com/blogs/developer/tag/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 Tag: .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 * var(-- | 2026-01-13T08:48:43 |
https://es.react.dev/ | React Únete a la React Conf del 7 al 8 de Octubre. Más información. React v 19.1 Búsqueda ⌘ Ctrl K Aprende Referencia Comunidad Blog React La biblioteca para interfaces de usuario web y nativas Aprende React Referencia de la API Crea interfaces de usuario a partir de componentes React te permite construir interfaces de usuario a partir de piezas individuales llamadas componentes. Crea tus propios componentes de React como Thumbnail , LikeButton , y Video . Luego combínalos para formar pantallas, páginas y aplicaciones. Video.js function Video ( { video } ) { return ( < div > < Thumbnail video = { video } /> < a href = { video . url } > < h3 > { video . title } </ h3 > < p > { video . description } </ p > </ a > < LikeButton video = { video } /> </ div > ) ; } My video Video description Sin importar si trabajas por tu cuenta o con otros miles de desarrolladores, utilizar React se siente igual. Está diseñado para permitirte combinar a la perfección componentes escritos por personas, equipos y organizaciones de forma independiente. Escribe componentes con código y marcado Los componentes de React son funciones de JavaScript. ¿Quieres mostrar algún contenido condicionalmente? Utiliza una sentencia if . ¿Mostrar una lista? Prueba la función map() de un array. Aprender React es aprender a programar. VideoList.js function VideoList ( { videos , emptyHeading } ) { const count = videos . length ; let heading = emptyHeading ; if ( count > 0 ) { const noun = count > 1 ? 'Videos' : 'Video' ; heading = count + ' ' + noun ; } return ( < section > < h2 > { heading } </ h2 > { videos . map ( video => < Video key = { video . id } video = { video } /> ) } </ section > ) ; } 3 Videos First video Video description Second video Video description Third video Video description Esta sintaxis de marcado se llama JSX. Es una extensión de la sintaxis de JavaScript popularizada por React. Al poner marcado JSX cerca de la lógica de renderizado relacionada hace que los componentes de React sean fáciles de crear, mantener y eliminar. Añade interactividad dondequiera que la necesites Los componentes de React reciben datos y devuelven lo que debe aparecer en la pantalla. Puedes pasarles nuevos datos en respuesta a una interacción, como cuando el usuario escribe en un campo de texto. React actualizará entonces la pantalla para que se corresponda con los nuevos datos. SearchableVideoList.js import { useState } from 'react' ; function SearchableVideoList ( { videos } ) { const [ searchText , setSearchText ] = useState ( '' ) ; const foundVideos = filterVideos ( videos , searchText ) ; return ( < > < SearchInput value = { searchText } onChange = { newText => setSearchText ( newText ) } /> < VideoList videos = { foundVideos } emptyHeading = { `No matches for “ ${ searchText } ”` } /> </ > ) ; } example.com / videos.html React Videos A brief history of React Buscar 5 Videos React: The Documentary The origin story of React Rethinking Best Practices Pete Hunt (2013) Introducing React Native Tom Occhino (2015) Introducing React Hooks Sophie Alpert and Dan Abramov (2018) Introducing Server Components Dan Abramov and Lauren Tan (2020) No tienes que construir toda tu página con React. Añade React a tu página HTML existente y renderiza componentes interactivos de React en cualquier lugar de ella. Añade React a tu página Cubre todo el stack con un framework React es una biblioteca. Te permite agrupar componentes, pero no prescribe cómo hacer el enrutamiento y la obtención de datos. Para construir una aplicación completa en React, recomendamos un framework full-stack de React como Next.js o Remix . confs/[slug].js import { db } from './database.js' ; import { Suspense } from 'react' ; async function ConferencePage ( { slug } ) { const conf = await db . Confs . find ( { slug } ) ; return ( < ConferenceLayout conf = { conf } > < Suspense fallback = { < TalksLoading /> } > < Talks confId = { conf . id } /> </ Suspense > </ ConferenceLayout > ) ; } async function Talks ( { confId } ) { const talks = await db . Talks . findAll ( { confId } ) ; const videos = talks . map ( talk => talk . video ) ; return < SearchableVideoList videos = { videos } /> ; } example.com / confs/react-conf-2021 React Conf 2021 React Conf 2019 Buscar 19 Videos React Conf React 18 Keynote The React Team React Conf React 18 for App Developers Shruti Kapoor React Conf Streaming Server Rendering with Suspense Shaundai Person React Conf The First React Working Group Aakansha Doshi React Conf React Developer Tooling Brian Vaughn React Conf React without memo Xuan Huang (黄玄) React Conf React Docs Keynote Rachel Nabors React Conf Things I Learnt from the New React Docs Debbie O'Brien React Conf Learning in the Browser Sarah Rainsberger React Conf The ROI of Designing with React Linton Ye React Conf Interactive Playgrounds with React Delba de Oliveira React Conf Re-introducing Relay Robert Balicki React Conf React Native Desktop Eric Rozell and Steven Moyes React Conf On-device Machine Learning for React Native Roman Rädle React Conf React 18 for External Store Libraries Daishi Kato React Conf Building Accessible Components with React 18 Diego Haz React Conf Accessible Japanese Form Components with React Tafu Nakazaki React Conf UI Tools for Artists Lyle Troxell React Conf Hydrogen + React 18 Helen Lin React también es una arquitectura. Los frameworks que la implementan te permiten obtener datos en componentes asíncronos que se ejecutan en el servidor o incluso durante la compilación. Lee datos de un archivo o una base de datos y pásalos hacia abajo a tus componentes interactivos. Comienza a usar un framework Utiliza lo mejor de cada plataforma A las personas les encantan las aplicaciones web y nativas por razones diferentes. React te permite construir tanto aplicaciones web como nativas utilizando las mismas habilidades. Se apoya en las fortalezas únicas de cada plataforma para permitir que tus interfaces se sientan naturales en cada una de ellas. example.com Mantente fiel a la web Las personas esperan que las páginas de las aplicaciones web carguen rápidamente. En el servidor, React te permite servir HTML bajo demanda mientras aún estás cargando datos, rellenando progresivamente el contendido faltante antes de que cargue ningún código de JavaScript. En el cliente, React puede usar APIs web estándares para mantener tu interfaz de usuario responsiva incluso en medio del renderizado. 2:19 AM Logra una UI realmente nativa Las personas esperan que las aplicaciones nativas se vean y se sientan como su plataforma. React Native y Expo te permiten construir aplicaciones en React para Android, iOS y más. Lucen y se sienten como nativas porque sus UIs son realmente nativas. No es una vista web: tus componentes de React renderizan vistas reales de Android e iOS provistas por la plataforma. Con React, puedes ser un desarrollador web y de aplicaciones nativas. Tu equipo puede producir para muchas plataformas sin sacrificar la experiencia de usuario. Tu organización puede tender puentes para romper el aislamiento entre plataformas y formar equipos que estén a cargo de funcionalidades completas de extremo a extremo. Construye para plataformas nativas Actualiza cuando el futuro esté listo React atiende los cambios con cuidado. Cada commit de React se prueba en escenarios críticos para el negocio con más de mil millones de usuarios. Más de 100 000 componentes de React en Meta ayudan a validar cada estrategia de migración. El equipo de React siempre está investigando como mejorar React. Algunas investigaciones toman años en arrojar resultados. React tiene el listón alto para llevar una idea de investigación a producción. Solo enfoques probados se vuelven parte de React. Lee más noticias de React Últimas noticias de React View Transitions and Activity April 23, 2025 React Compiler RC April 21, 2025 Sunsetting Create React App February 14, 2025 React 19 December 05, 2024 Lee más noticias de React Únete a una comunidad de millones No estás solo. Dos millones de desarrolladores de todo el mundo visitan la documentación de React cada mes. React es algo que las personas y los equipos pueden estar de acuerdo. Es por esto que React es más que una biblioteca, una arquitectura, o incluso un ecosistema. React es una comunidad. Es un lugar dónde puedes pedir ayuda, encontrar oportunidades y conocer nuevos amigos. Conocerás tanto desarrolladores como diseñadores, principiantes y expertos, investigadores y artistas, maestros y estudiantes. Nuestros antecedentes pueden ser muy diferentes, pero React nos permite a todos crear juntos interfaces de usuario. Bienvenido a la comunidad de React Introducción Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Aprender React Inicio rápido Instalación Describir la UI Agregar interactividad Gestión del estado Puertas de escape Referencia de la API React APIs React DOM APIs Comunidad Código de conducta Conoce al equipo Contribuidores de la documentación Agradecimientos Más Blog React Native Privacidad Términos | 2026-01-13T08:48:43 |
https://openapi.tools/categories/sdk-generators | SDK Generators | 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 . SDK Generators Generate code to give to consumers, to help them avoid interacting at a HTTP level. SDK Generators 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:43 |
https://docs.python.org/3/glossary.html#term-immutable | Glossary — Python 3.14.2 documentation Theme Auto Light Dark Previous topic Deprecations Next topic About this documentation This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » Glossary | Theme Auto Light Dark | Glossary ¶ >>> ¶ The default Python prompt of the interactive shell. Often seen for code examples which can be executed interactively in the interpreter. ... ¶ Can refer to: The default Python prompt of the interactive shell when entering the code for an indented code block, when within a pair of matching left and right delimiters (parentheses, square brackets, curly braces or triple quotes), or after specifying a decorator. The three dots form of the Ellipsis object. abstract base class ¶ Abstract base classes complement duck-typing by providing a way to define interfaces when other techniques like hasattr() would be clumsy or subtly wrong (for example with magic methods ). ABCs introduce virtual subclasses, which are classes that don’t inherit from a class but are still recognized by isinstance() and issubclass() ; see the abc module documentation. Python comes with many built-in ABCs for data structures (in the collections.abc module), numbers (in the numbers module), streams (in the io module), import finders and loaders (in the importlib.abc module). You can create your own ABCs with the abc module. annotate function ¶ A function that can be called to retrieve the annotations of an object. This function is accessible as the __annotate__ attribute of functions, classes, and modules. Annotate functions are a subset of evaluate functions . annotation ¶ A label associated with a variable, a class attribute or a function parameter or return value, used by convention as a type hint . Annotations of local variables cannot be accessed at runtime, but annotations of global variables, class attributes, and functions can be retrieved by calling annotationlib.get_annotations() on modules, classes, and functions, respectively. See variable annotation , function annotation , PEP 484 , PEP 526 , and PEP 649 , which describe this functionality. Also see Annotations Best Practices for best practices on working with annotations. argument ¶ A value passed to a function (or method ) when calling the function. There are two kinds of argument: keyword argument : an argument preceded by an identifier (e.g. name= ) in a function call or passed as a value in a dictionary preceded by ** . For example, 3 and 5 are both keyword arguments in the following calls to complex() : complex ( real = 3 , imag = 5 ) complex ( ** { 'real' : 3 , 'imag' : 5 }) positional argument : an argument that is not a keyword argument. Positional arguments can appear at the beginning of an argument list and/or be passed as elements of an iterable preceded by * . For example, 3 and 5 are both positional arguments in the following calls: complex ( 3 , 5 ) complex ( * ( 3 , 5 )) Arguments are assigned to the named local variables in a function body. See the Calls section for the rules governing this assignment. Syntactically, any expression can be used to represent an argument; the evaluated value is assigned to the local variable. See also the parameter glossary entry, the FAQ question on the difference between arguments and parameters , and PEP 362 . asynchronous context manager ¶ An object which controls the environment seen in an async with statement by defining __aenter__() and __aexit__() methods. Introduced by PEP 492 . asynchronous generator ¶ A function which returns an asynchronous generator iterator . It looks like a coroutine function defined with async def except that it contains yield expressions for producing a series of values usable in an async for loop. Usually refers to an asynchronous generator function, but may refer to an asynchronous generator iterator in some contexts. In cases where the intended meaning isn’t clear, using the full terms avoids ambiguity. An asynchronous generator function may contain await expressions as well as async for , and async with statements. asynchronous generator iterator ¶ An object created by an asynchronous generator function. This is an asynchronous iterator which when called using the __anext__() method returns an awaitable object which will execute the body of the asynchronous generator function until the next yield expression. Each yield temporarily suspends processing, remembering the execution state (including local variables and pending try-statements). When the asynchronous generator iterator effectively resumes with another awaitable returned by __anext__() , it picks up where it left off. See PEP 492 and PEP 525 . asynchronous iterable ¶ An object, that can be used in an async for statement. Must return an asynchronous iterator from its __aiter__() method. Introduced by PEP 492 . asynchronous iterator ¶ An object that implements the __aiter__() and __anext__() methods. __anext__() must return an awaitable object. async for resolves the awaitables returned by an asynchronous iterator’s __anext__() method until it raises a StopAsyncIteration exception. Introduced by PEP 492 . atomic operation ¶ An operation that appears to execute as a single, indivisible step: no other thread can observe it half-done, and its effects become visible all at once. Python does not guarantee that high-level statements are atomic (for example, x += 1 performs multiple bytecode operations and is not atomic). Atomicity is only guaranteed where explicitly documented. See also race condition and data race . attached thread state ¶ A thread state that is active for the current OS thread. When a thread state is attached, the OS thread has access to the full Python C API and can safely invoke the bytecode interpreter. Unless a function explicitly notes otherwise, attempting to call the C API without an attached thread state will result in a fatal error or undefined behavior. A thread state can be attached and detached explicitly by the user through the C API, or implicitly by the runtime, including during blocking C calls and by the bytecode interpreter in between calls. On most builds of Python, having an attached thread state implies that the caller holds the GIL for the current interpreter, so only one OS thread can have an attached thread state at a given moment. In free-threaded builds of Python, threads can concurrently hold an attached thread state, allowing for true parallelism of the bytecode interpreter. attribute ¶ A value associated with an object which is usually referenced by name using dotted expressions. For example, if an object o has an attribute a it would be referenced as o.a . It is possible to give an object an attribute whose name is not an identifier as defined by Names (identifiers and keywords) , for example using setattr() , if the object allows it. Such an attribute will not be accessible using a dotted expression, and would instead need to be retrieved with getattr() . awaitable ¶ An object that can be used in an await expression. Can be a coroutine or an object with an __await__() method. See also PEP 492 . BDFL ¶ Benevolent Dictator For Life, a.k.a. Guido van Rossum , Python’s creator. binary file ¶ A file object able to read and write bytes-like objects . Examples of binary files are files opened in binary mode ( 'rb' , 'wb' or 'rb+' ), sys.stdin.buffer , sys.stdout.buffer , and instances of io.BytesIO and gzip.GzipFile . See also text file for a file object able to read and write str objects. borrowed reference ¶ In Python’s C API, a borrowed reference is a reference to an object, where the code using the object does not own the reference. It becomes a dangling pointer if the object is destroyed. For example, a garbage collection can remove the last strong reference to the object and so destroy it. Calling Py_INCREF() on the borrowed reference is recommended to convert it to a strong reference in-place, except when the object cannot be destroyed before the last usage of the borrowed reference. The Py_NewRef() function can be used to create a new strong reference . bytes-like object ¶ An object that supports the Buffer Protocol and can export a C- contiguous buffer. This includes all bytes , bytearray , and array.array objects, as well as many common memoryview objects. Bytes-like objects can be used for various operations that work with binary data; these include compression, saving to a binary file, and sending over a socket. Some operations need the binary data to be mutable. The documentation often refers to these as “read-write bytes-like objects”. Example mutable buffer objects include bytearray and a memoryview of a bytearray . Other operations require the binary data to be stored in immutable objects (“read-only bytes-like objects”); examples of these include bytes and a memoryview of a bytes object. bytecode ¶ Python source code is compiled into bytecode, the internal representation of a Python program in the CPython interpreter. The bytecode is also cached in .pyc files so that executing the same file is faster the second time (recompilation from source to bytecode can be avoided). This “intermediate language” is said to run on a virtual machine that executes the machine code corresponding to each bytecode. Do note that bytecodes are not expected to work between different Python virtual machines, nor to be stable between Python releases. A list of bytecode instructions can be found in the documentation for the dis module . callable ¶ A callable is an object that can be called, possibly with a set of arguments (see argument ), with the following syntax: callable ( argument1 , argument2 , argumentN ) A function , and by extension a method , is a callable. An instance of a class that implements the __call__() method is also a callable. callback ¶ A subroutine function which is passed as an argument to be executed at some point in the future. class ¶ A template for creating user-defined objects. Class definitions normally contain method definitions which operate on instances of the class. class variable ¶ A variable defined in a class and intended to be modified only at class level (i.e., not in an instance of the class). closure variable ¶ A free variable referenced from a nested scope that is defined in an outer scope rather than being resolved at runtime from the globals or builtin namespaces. May be explicitly defined with the nonlocal keyword to allow write access, or implicitly defined if the variable is only being read. For example, in the inner function in the following code, both x and print are free variables , but only x is a closure variable : def outer (): x = 0 def inner (): nonlocal x x += 1 print ( x ) return inner Due to the codeobject.co_freevars attribute (which, despite its name, only includes the names of closure variables rather than listing all referenced free variables), the more general free variable term is sometimes used even when the intended meaning is to refer specifically to closure variables. complex number ¶ An extension of the familiar real number system in which all numbers are expressed as a sum of a real part and an imaginary part. Imaginary numbers are real multiples of the imaginary unit (the square root of -1 ), often written i in mathematics or j in engineering. Python has built-in support for complex numbers, which are written with this latter notation; the imaginary part is written with a j suffix, e.g., 3+1j . To get access to complex equivalents of the math module, use cmath . Use of complex numbers is a fairly advanced mathematical feature. If you’re not aware of a need for them, it’s almost certain you can safely ignore them. concurrency ¶ The ability of a computer program to perform multiple tasks at the same time. Python provides libraries for writing programs that make use of different forms of concurrency. asyncio is a library for dealing with asynchronous tasks and coroutines. threading provides access to operating system threads and multiprocessing to operating system processes. Multi-core processors can execute threads and processes on different CPU cores at the same time (see parallelism ). concurrent modification ¶ When multiple threads modify shared data at the same time. Concurrent modification without proper synchronization can cause race conditions , and might also trigger a data race , data corruption, or both. context ¶ This term has different meanings depending on where and how it is used. Some common meanings: The temporary state or environment established by a context manager via a with statement. The collection of keyvalue bindings associated with a particular contextvars.Context object and accessed via ContextVar objects. Also see context variable . A contextvars.Context object. Also see current context . context management protocol ¶ The __enter__() and __exit__() methods called by the with statement. See PEP 343 . context manager ¶ An object which implements the context management protocol and controls the environment seen in a with statement. See PEP 343 . context variable ¶ A variable whose value depends on which context is the current context . Values are accessed via contextvars.ContextVar objects. Context variables are primarily used to isolate state between concurrent asynchronous tasks. contiguous ¶ A buffer is considered contiguous exactly if it is either C-contiguous or Fortran contiguous . Zero-dimensional buffers are C and Fortran contiguous. In one-dimensional arrays, the items must be laid out in memory next to each other, in order of increasing indexes starting from zero. In multidimensional C-contiguous arrays, the last index varies the fastest when visiting items in order of memory address. However, in Fortran contiguous arrays, the first index varies the fastest. coroutine ¶ Coroutines are a more generalized form of subroutines. Subroutines are entered at one point and exited at another point. Coroutines can be entered, exited, and resumed at many different points. They can be implemented with the async def statement. See also PEP 492 . coroutine function ¶ A function which returns a coroutine object. A coroutine function may be defined with the async def statement, and may contain await , async for , and async with keywords. These were introduced by PEP 492 . CPython ¶ The canonical implementation of the Python programming language, as distributed on python.org . The term “CPython” is used when necessary to distinguish this implementation from others such as Jython or IronPython. current context ¶ The context ( contextvars.Context object) that is currently used by ContextVar objects to access (get or set) the values of context variables . Each thread has its own current context. Frameworks for executing asynchronous tasks (see asyncio ) associate each task with a context which becomes the current context whenever the task starts or resumes execution. cyclic isolate ¶ A subgroup of one or more objects that reference each other in a reference cycle, but are not referenced by objects outside the group. The goal of the cyclic garbage collector is to identify these groups and break the reference cycles so that the memory can be reclaimed. data race ¶ A situation where multiple threads access the same memory location concurrently, at least one of the accesses is a write, and the threads do not use any synchronization to control their access. Data races lead to non-deterministic behavior and can cause data corruption. Proper use of locks and other synchronization primitives prevents data races. Note that data races can only happen in native code, but that native code might be exposed in a Python API. See also race condition and thread-safe . deadlock ¶ A situation in which two or more tasks (threads, processes, or coroutines) wait indefinitely for each other to release resources or complete actions, preventing any from making progress. For example, if thread A holds lock 1 and waits for lock 2, while thread B holds lock 2 and waits for lock 1, both threads will wait indefinitely. In Python this often arises from acquiring multiple locks in conflicting orders or from circular join/await dependencies. Deadlocks can be avoided by always acquiring multiple locks in a consistent order. See also lock and reentrant . decorator ¶ A function returning another function, usually applied as a function transformation using the @wrapper syntax. Common examples for decorators are classmethod() and staticmethod() . The decorator syntax is merely syntactic sugar, the following two function definitions are semantically equivalent: def f ( arg ): ... f = staticmethod ( f ) @staticmethod def f ( arg ): ... The same concept exists for classes, but is less commonly used there. See the documentation for function definitions and class definitions for more about decorators. descriptor ¶ Any object which defines the methods __get__() , __set__() , or __delete__() . When a class attribute is a descriptor, its special binding behavior is triggered upon attribute lookup. Normally, using a.b to get, set or delete an attribute looks up the object named b in the class dictionary for a , but if b is a descriptor, the respective descriptor method gets called. Understanding descriptors is a key to a deep understanding of Python because they are the basis for many features including functions, methods, properties, class methods, static methods, and reference to super classes. For more information about descriptors’ methods, see Implementing Descriptors or the Descriptor How To Guide . dictionary ¶ An associative array, where arbitrary keys are mapped to values. The keys can be any object with __hash__() and __eq__() methods. Called a hash in Perl. dictionary comprehension ¶ A compact way to process all or part of the elements in an iterable and return a dictionary with the results. results = {n: n ** 2 for n in range(10)} generates a dictionary containing key n mapped to value n ** 2 . See Displays for lists, sets and dictionaries . dictionary view ¶ The objects returned from dict.keys() , dict.values() , and dict.items() are called dictionary views. They provide a dynamic view on the dictionary’s entries, which means that when the dictionary changes, the view reflects these changes. To force the dictionary view to become a full list use list(dictview) . See Dictionary view objects . docstring ¶ A string literal which appears as the first expression in a class, function or module. While ignored when the suite is executed, it is recognized by the compiler and put into the __doc__ attribute of the enclosing class, function or module. Since it is available via introspection, it is the canonical place for documentation of the object. duck-typing ¶ A programming style which does not look at an object’s type to determine if it has the right interface; instead, the method or attribute is simply called or used (“If it looks like a duck and quacks like a duck, it must be a duck.”) By emphasizing interfaces rather than specific types, well-designed code improves its flexibility by allowing polymorphic substitution. Duck-typing avoids tests using type() or isinstance() . (Note, however, that duck-typing can be complemented with abstract base classes .) Instead, it typically employs hasattr() tests or EAFP programming. dunder ¶ An informal short-hand for “double underscore”, used when talking about a special method . For example, __init__ is often pronounced “dunder init”. EAFP ¶ Easier to ask for forgiveness than permission. This common Python coding style assumes the existence of valid keys or attributes and catches exceptions if the assumption proves false. This clean and fast style is characterized by the presence of many try and except statements. The technique contrasts with the LBYL style common to many other languages such as C. evaluate function ¶ A function that can be called to evaluate a lazily evaluated attribute of an object, such as the value of type aliases created with the type statement. expression ¶ A piece of syntax which can be evaluated to some value. In other words, an expression is an accumulation of expression elements like literals, names, attribute access, operators or function calls which all return a value. In contrast to many other languages, not all language constructs are expressions. There are also statement s which cannot be used as expressions, such as while . Assignments are also statements, not expressions. extension module ¶ A module written in C or C++, using Python’s C API to interact with the core and with user code. f-string ¶ f-strings ¶ String literals prefixed with f or F are commonly called “f-strings” which is short for formatted string literals . See also PEP 498 . file object ¶ An object exposing a file-oriented API (with methods such as read() or write() ) to an underlying resource. Depending on the way it was created, a file object can mediate access to a real on-disk file or to another type of storage or communication device (for example standard input/output, in-memory buffers, sockets, pipes, etc.). File objects are also called file-like objects or streams . There are actually three categories of file objects: raw binary files , buffered binary files and text files . Their interfaces are defined in the io module. The canonical way to create a file object is by using the open() function. file-like object ¶ A synonym for file object . filesystem encoding and error handler ¶ Encoding and error handler used by Python to decode bytes from the operating system and encode Unicode to the operating system. The filesystem encoding must guarantee to successfully decode all bytes below 128. If the file system encoding fails to provide this guarantee, API functions can raise UnicodeError . The sys.getfilesystemencoding() and sys.getfilesystemencodeerrors() functions can be used to get the filesystem encoding and error handler. The filesystem encoding and error handler are configured at Python startup by the PyConfig_Read() function: see filesystem_encoding and filesystem_errors members of PyConfig . See also the locale encoding . finder ¶ An object that tries to find the loader for a module that is being imported. There are two types of finder: meta path finders for use with sys.meta_path , and path entry finders for use with sys.path_hooks . See Finders and loaders and importlib for much more detail. floor division ¶ Mathematical division that rounds down to nearest integer. The floor division operator is // . For example, the expression 11 // 4 evaluates to 2 in contrast to the 2.75 returned by float true division. Note that (-11) // 4 is -3 because that is -2.75 rounded downward . See PEP 238 . free threading ¶ A threading model where multiple threads can run Python bytecode simultaneously within the same interpreter. This is in contrast to the global interpreter lock which allows only one thread to execute Python bytecode at a time. See PEP 703 . free variable ¶ Formally, as defined in the language execution model , a free variable is any variable used in a namespace which is not a local variable in that namespace. See closure variable for an example. Pragmatically, due to the name of the codeobject.co_freevars attribute, the term is also sometimes used as a synonym for closure variable . function ¶ A series of statements which returns some value to a caller. It can also be passed zero or more arguments which may be used in the execution of the body. See also parameter , method , and the Function definitions section. function annotation ¶ An annotation of a function parameter or return value. Function annotations are usually used for type hints : for example, this function is expected to take two int arguments and is also expected to have an int return value: def sum_two_numbers ( a : int , b : int ) -> int : return a + b Function annotation syntax is explained in section Function definitions . See variable annotation and PEP 484 , which describe this functionality. Also see Annotations Best Practices for best practices on working with annotations. __future__ ¶ A future statement , from __future__ import <feature> , directs the compiler to compile the current module using syntax or semantics that will become standard in a future release of Python. The __future__ module documents the possible values of feature . By importing this module and evaluating its variables, you can see when a new feature was first added to the language and when it will (or did) become the default: >>> import __future__ >>> __future__ . division _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192) garbage collection ¶ The process of freeing memory when it is not used anymore. Python performs garbage collection via reference counting and a cyclic garbage collector that is able to detect and break reference cycles. The garbage collector can be controlled using the gc module. generator ¶ A function which returns a generator iterator . It looks like a normal function except that it contains yield expressions for producing a series of values usable in a for-loop or that can be retrieved one at a time with the next() function. Usually refers to a generator function, but may refer to a generator iterator in some contexts. In cases where the intended meaning isn’t clear, using the full terms avoids ambiguity. generator iterator ¶ An object created by a generator function. Each yield temporarily suspends processing, remembering the execution state (including local variables and pending try-statements). When the generator iterator resumes, it picks up where it left off (in contrast to functions which start fresh on every invocation). generator expression ¶ An expression that returns an iterator . It looks like a normal expression followed by a for clause defining a loop variable, range, and an optional if clause. The combined expression generates values for an enclosing function: >>> sum ( i * i for i in range ( 10 )) # sum of squares 0, 1, 4, ... 81 285 generic function ¶ A function composed of multiple functions implementing the same operation for different types. Which implementation should be used during a call is determined by the dispatch algorithm. See also the single dispatch glossary entry, the functools.singledispatch() decorator, and PEP 443 . generic type ¶ A type that can be parameterized; typically a container class such as list or dict . Used for type hints and annotations . For more details, see generic alias types , PEP 483 , PEP 484 , PEP 585 , and the typing module. GIL ¶ See global interpreter lock . global interpreter lock ¶ The mechanism used by the CPython interpreter to assure that only one thread executes Python bytecode at a time. This simplifies the CPython implementation by making the object model (including critical built-in types such as dict ) implicitly safe against concurrent access. Locking the entire interpreter makes it easier for the interpreter to be multi-threaded, at the expense of much of the parallelism afforded by multi-processor machines. However, some extension modules, either standard or third-party, are designed so as to release the GIL when doing computationally intensive tasks such as compression or hashing. Also, the GIL is always released when doing I/O. As of Python 3.13, the GIL can be disabled using the --disable-gil build configuration. After building Python with this option, code must be run with -X gil=0 or after setting the PYTHON_GIL=0 environment variable. This feature enables improved performance for multi-threaded applications and makes it easier to use multi-core CPUs efficiently. For more details, see PEP 703 . In prior versions of Python’s C API, a function might declare that it requires the GIL to be held in order to use it. This refers to having an attached thread state . global state ¶ Data that is accessible throughout a program, such as module-level variables, class variables, or C static variables in extension modules . In multi-threaded programs, global state shared between threads typically requires synchronization to avoid race conditions and data races . hash-based pyc ¶ A bytecode cache file that uses the hash rather than the last-modified time of the corresponding source file to determine its validity. See Cached bytecode invalidation . hashable ¶ An object is hashable if it has a hash value which never changes during its lifetime (it needs a __hash__() method), and can be compared to other objects (it needs an __eq__() method). Hashable objects which compare equal must have the same hash value. Hashability makes an object usable as a dictionary key and a set member, because these data structures use the hash value internally. Most of Python’s immutable built-in objects are hashable; mutable containers (such as lists or dictionaries) are not; immutable containers (such as tuples and frozensets) are only hashable if their elements are hashable. Objects which are instances of user-defined classes are hashable by default. They all compare unequal (except with themselves), and their hash value is derived from their id() . IDLE ¶ An Integrated Development and Learning Environment for Python. IDLE — Python editor and shell is a basic editor and interpreter environment which ships with the standard distribution of Python. immortal ¶ Immortal objects are a CPython implementation detail introduced in PEP 683 . If an object is immortal, its reference count is never modified, and therefore it is never deallocated while the interpreter is running. For example, True and None are immortal in CPython. Immortal objects can be identified via sys._is_immortal() , or via PyUnstable_IsImmortal() in the C API. immutable ¶ An object with a fixed value. Immutable objects include numbers, strings and tuples. Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an important role in places where a constant hash value is needed, for example as a key in a dictionary. Immutable objects are inherently thread-safe because their state cannot be modified after creation, eliminating concerns about improperly synchronized concurrent modification . import path ¶ A list of locations (or path entries ) that are searched by the path based finder for modules to import. During import, this list of locations usually comes from sys.path , but for subpackages it may also come from the parent package’s __path__ attribute. importing ¶ The process by which Python code in one module is made available to Python code in another module. importer ¶ An object that both finds and loads a module; both a finder and loader object. interactive ¶ Python has an interactive interpreter which means you can enter statements and expressions at the interpreter prompt, immediately execute them and see their results. Just launch python with no arguments (possibly by selecting it from your computer’s main menu). It is a very powerful way to test out new ideas or inspect modules and packages (remember help(x) ). For more on interactive mode, see Interactive Mode . interpreted ¶ Python is an interpreted language, as opposed to a compiled one, though the distinction can be blurry because of the presence of the bytecode compiler. This means that source files can be run directly without explicitly creating an executable which is then run. Interpreted languages typically have a shorter development/debug cycle than compiled ones, though their programs generally also run more slowly. See also interactive . interpreter shutdown ¶ When asked to shut down, the Python interpreter enters a special phase where it gradually releases all allocated resources, such as modules and various critical internal structures. It also makes several calls to the garbage collector . This can trigger the execution of code in user-defined destructors or weakref callbacks. Code executed during the shutdown phase can encounter various exceptions as the resources it relies on may not function anymore (common examples are library modules or the warnings machinery). The main reason for interpreter shutdown is that the __main__ module or the script being run has finished executing. iterable ¶ An object capable of returning its members one at a time. Examples of iterables include all sequence types (such as list , str , and tuple ) and some non-sequence types like dict , file objects , and objects of any classes you define with an __iter__() method or with a __getitem__() method that implements sequence semantics. Iterables can be used in a for loop and in many other places where a sequence is needed ( zip() , map() , …). When an iterable object is passed as an argument to the built-in function iter() , it returns an iterator for the object. This iterator is good for one pass over the set of values. When using iterables, it is usually not necessary to call iter() or deal with iterator objects yourself. The for statement does that automatically for you, creating a temporary unnamed variable to hold the iterator for the duration of the loop. See also iterator , sequence , and generator . iterator ¶ An object representing a stream of data. Repeated calls to the iterator’s __next__() method (or passing it to the built-in function next() ) return successive items in the stream. When no more data are available a StopIteration exception is raised instead. At this point, the iterator object is exhausted and any further calls to its __next__() method just raise StopIteration again. Iterators are required to have an __iter__() method that returns the iterator object itself so every iterator is also iterable and may be used in most places where other iterables are accepted. One notable exception is code which attempts multiple iteration passes. A container object (such as a list ) produces a fresh new iterator each time you pass it to the iter() function or use it in a for loop. Attempting this with an iterator will just return the same exhausted iterator object used in the previous iteration pass, making it appear like an empty container. More information can be found in Iterator Types . CPython implementation detail: CPython does not consistently apply the requirement that an iterator define __iter__() . And also please note that free-threaded CPython does not guarantee thread-safe behavior of iterator operations. key function ¶ A key function or collation function is a callable that returns a value used for sorting or ordering. For example, locale.strxfrm() is used to produce a sort key that is aware of locale specific sort conventions. A number of tools in Python accept key functions to control how elements are ordered or grouped. They include min() , max() , sorted() , list.sort() , heapq.merge() , heapq.nsmallest() , heapq.nlargest() , and itertools.groupby() . There are several ways to create a key function. For example. the str.casefold() method can serve as a key function for case insensitive sorts. Alternatively, a key function can be built from a lambda expression such as lambda r: (r[0], r[2]) . Also, operator.attrgetter() , operator.itemgetter() , and operator.methodcaller() are three key function constructors. See the Sorting HOW TO for examples of how to create and use key functions. keyword argument ¶ See argument . lambda ¶ An anonymous inline function consisting of a single expression which is evaluated when the function is called. The syntax to create a lambda function is lambda [parameters]: expression LBYL ¶ Look before you leap. This coding style explicitly tests for pre-conditions before making calls or lookups. This style contrasts with the EAFP approach and is characterized by the presence of many if statements. In a multi-threaded environment, the LBYL approach can risk introducing a race condition between “the looking” and “the leaping”. For example, the code, if key in mapping: return mapping[key] can fail if another thread removes key from mapping after the test, but before the lookup. This issue can be solved with locks or by using the EAFP approach. See also thread-safe . lexical analyzer ¶ Formal name for the tokenizer ; see token . list ¶ A built-in Python sequence . Despite its name it is more akin to an array in other languages than to a linked list since access to elements is O (1). list comprehension ¶ A compact way to process all or part of the elements in a sequence and return a list with the results. result = ['{:#04x}'.format(x) for x in range(256) if x % 2 == 0] generates a list of strings containing even hex numbers (0x..) in the range from 0 to 255. The if clause is optional. If omitted, all elements in range(256) are processed. lock ¶ A synchronization primitive that allows only one thread at a time to access a shared resource. A thread must acquire a lock before accessing the protected resource and release it afterward. If a thread attempts to acquire a lock that is already held by another thread, it will block until the lock becomes available. Python’s threading module provides Lock (a basic lock) and RLock (a reentrant lock). Locks are used to prevent race conditions and ensure thread-safe access to shared data. Alternative design patterns to locks exist such as queues, producer/consumer patterns, and thread-local state. See also deadlock , and reentrant . loader ¶ An object that loads a module. It must define the exec_module() and create_module() methods to implement the Loader interface. A loader is typically returned by a finder . See also: Finders and loaders importlib.abc.Loader PEP 302 locale encoding ¶ On Unix, it is the encoding of the LC_CTYPE locale. It can be set with locale.setlocale(locale.LC_CTYPE, new_locale) . On Windows, it is the ANSI code page (ex: "cp1252" ). On Android and VxWorks, Python uses "utf-8" as the locale encoding. locale.getencoding() can be used to get the locale encoding. See also the filesystem encoding and error handler . magic method ¶ An informal synonym for special method . mapping ¶ A container object that supports arbitrary key lookups and implements the methods specified in the collections.abc.Mapping or collections.abc.MutableMapping abstract base classes . Examples include dict , collections.defaultdict , collections.OrderedDict and collections.Counter . meta path finder ¶ A finder returned by a search of sys.meta_path . Meta path finders are related to, but different from path entry finders . See importlib.abc.MetaPathFinder for the methods that meta path finders implement. metaclass ¶ The class of a class. Class definitions create a class name, a class dictionary, and a list of base classes. The metaclass is responsible for taking those three arguments and creating the class. Most object oriented programming languages provide a default implementation. What makes Python special is that it is possible to create custom metaclasses. Most users never need this tool, but when the need arises, metaclasses can provide powerful, elegant solutions. They have been used for logging attribute access, adding thread-safety, tracking object creation, implementing singletons, and many other tasks. More information can be found in Metaclasses . method ¶ A function which is defined inside a class body. If called as an attribute of an instance of that class, the method will get the instance object as its first argument (which is usually called self ). See function and nested scope . method resolution order ¶ Method Resolution Order is the order in which base classes are searched for a member during lookup. See The Python 2.3 Method Resolution Order for details of the algorithm used by the Python interpreter since the 2.3 release. module ¶ An object that serves as an organizational unit of Python code. Modules have a namespace containing arbitrary Python objects. Modules are loaded into Python by the process of importing . See also package . module spec ¶ A namespace containing the import-related information used to load a module. An instance of importlib.machinery.ModuleSpec . See also Module specs . MRO ¶ See method resolution order . mutable ¶ An object with state that is allowed to change during the course of the program. In multi-threaded programs, mutable objects that are shared between threads require careful synchronization to avoid race conditions . See also immutable , thread-safe , and concurrent modification . named tuple ¶ The term “named tuple” applies to any type or class that inherits from tuple and whose indexable elements are also accessible using named attributes. The type or class may have other features as well. Several built-in types are named tuples, including the values returned by time.localtime() and os.stat() . Another example is sys.float_info : >>> sys . float_info [ 1 ] # indexed access 1024 >>> sys . float_info . max_exp # named field access 1024 >>> isinstance ( sys . float_info , tuple ) # kind of tuple True Some named tuples are built-in types (such as the above examples). Alternatively, a named tuple can be created from a regular class definition that inherits from tuple and that defines named fields. Such a class can be written by hand, or it can be created by inheriting typing.NamedTuple , or with the factory function collections.namedtuple() . The latter techniques also add some extra methods that may not be found in hand-written or built-in named tuples. namespace ¶ The place where a variable is stored. Namespaces are implemented as dictionaries. There are the local, global and built-in namespaces as well as nested namespaces in objects (in methods). Namespaces support modularity by preventing naming conflicts. For instance, the functions builtins.open and os.open() are distinguished by their namespaces. Namespaces also aid readability and maintainability by making it clear which module implements a function. For instance, writing random.seed() or itertools.islice() makes it clear that those functions are implemented by the random and itertools modules, respectively. namespace package ¶ A package which serves only as a container for subpackages. Namespace packages may have no physical representation, and specifically are not like a regular package because they have no __init__.py file. Namespace packages allow several individually installable packages to have a common parent package. Otherwise, it is recommended to use a regular package . For more information, see PEP 420 and Namespace packages . See also module . native code ¶ Code that is compiled to machine instructions and runs directly on the processor, as opposed to code that is interpreted or runs in a virtual machine. In the context of Python, native code typically refers to C, C++, Rust or Fortran code in extension modules that can be called from Python. See also extension module . nested scope ¶ The ability to refer to a variable in an enclosing definition. For instance, a function defined inside another function can refer to variables in the outer function. Note that nested scopes by default work only for reference and not for assignment. Local variables both read and write in the innermost scope. Likewise, global variables read and write to the global namespace. The nonlocal allows writing to outer scopes. new-style class ¶ Old name for the flavor of classes now used for all class objects. In earlier Python versions, only new-style classes could use Python’s newer, versatile features like __slots__ , descriptors, properties, __getattribute__() , class methods, and static methods. non-deterministic ¶ Behavior where the outcome of a program can vary between executions with the same inputs. In multi-threaded programs, non-deterministic behavior often results from race conditions where the relative timing or interleaving of threads affects the result. Proper synchronization using locks and other synchronization primitives helps ensure deterministic behavior. object ¶ Any data with state (attributes or value) and defined behavior (methods). Also the ultimate base class of any new-style class . optimized scope ¶ A scope where target local variable names are reliably known to the compiler when the code is compiled, allowing optimization of read and write access to these names. The local namespaces for functions, generators, coroutines, comprehensions, and generator expressions are optimized in this fashion. Note: most interpreter optimizations are applied to all scopes, only those relying on a known set of local and nonlocal variable names are restricted to optimized scopes. optional module ¶ An extension module that is part of the standard library , but may be absent in some builds of CPython , usually due to missing third-party libraries or because the module is not available for a given platform. See Requirements for optional modules for a list of optional modules that require third-party libraries. package ¶ A Python module which can contain submodules or recursively, subpackages. Technically, a package is a Python module with a __path__ attribute. See also regular package and namespace package . parallelism ¶ Executing multiple operations at the same time (e.g. on multiple CPU cores). In Python builds with the global interpreter lock (GIL) , only one thread runs Python bytecode at a time, so taking advantage of multiple CPU cores typically involves multiple processes (e.g. multiprocessing ) or native extensions that release the GIL. In free-threaded Python, multiple Python threads can run Python code simultaneously on different cores. parameter ¶ A named entity in a function (or method) definition that specifies an argument (or in some cases, arguments) that the function can accept. There are five kinds of parameter: positional-or-keyword : specifies an argument that can be passed either positionally or as a keyword argument . This is the default kind of parameter, for example foo and bar in the following: def func ( foo , bar = None ): ... positional-only : specifies an argument that can be supplied only by position. Positional-only parameters can be defined by including a / character in the parameter list of the function definition after them, for example posonly1 and posonly2 in the following: def func ( posonly1 , posonly2 , / , positional_or_keyword ): ... keyword-only : specifies an argument that can be supplied only by keyword. Keyword-only parameters can be defined by including a single var-positional parameter or bare * in the parameter list of the function definition before them, for example kw_only1 and kw_only2 in the following: def func ( arg , * , kw_only1 , kw_only2 ): ... var-positional : specifies that an arbitrary sequence of positional arguments can be provided (in addition to any positional arguments already accepted by other parameters). Such a parameter can be defined by prepending the parameter name with * , for example args in the following: def func ( * args , ** kwargs ): ... var-keyword : specifies that arbitrarily many keyword arguments can be provided (in addition to any keyword arguments already accepted by other parameters). Such a parameter can be defined by prepending the parameter name with ** , for example kwargs in the example above. Parameters can specify both optional and required arguments, as well as default values for some optional arguments. See also the argument glossary entry, the FAQ question on the difference between arguments and parameters , the inspect.Parameter class, the Function definitions section, and PEP 362 . path entry ¶ A single location on the import path which the path based finder consults to find modules for importing. path entry finder ¶ A finder returned by a callable on sys.path_hooks (i.e. a path entry hook ) which knows how to locate modules given a path entry . See importlib.abc.PathEntryFinder for the methods that path entry finders implement. path entry hook ¶ A callable on the sys.path_hooks list which returns a path entry finder if it knows how to find modules on a specific path entry . path based finder ¶ One of the default meta path finders which searches an import path for modules. path-like object ¶ An object representing a file system path. A path-like object is either a str or bytes object representing a path, or an object implementing the os.PathLike protocol. An object that supports the os.PathLike protocol can be converted to a str or bytes file system path by calling the os.fspath() function; os.fsdecode() and os.fsencode() can be used to guarantee a str or bytes result instead, respectively. Introduced by PEP 519 . PEP ¶ Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python or its processes or environment. PEPs should provide a concise technical specification and a rationale for proposed features. PEPs are intended to be the primary mechanisms for proposing major new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. See PEP 1 . portion ¶ A set of files in a single directory (possibly stored in a zip file) that contribute to a namespace package, as defined in PEP 420 . positional argument ¶ See argument . provisional API ¶ A provisional API is one which has been deliberately excluded from the standard library’s backwards compatibility guarantees. While major changes to such interfaces are not expected, as long as they are marked provisional, backwards incompatible changes (up to and including removal of the interface) may occur if deemed necessary by core developers. Such changes will not be made | 2026-01-13T08:48:43 |
https://golf.forem.com/privacy#7-retention-of-personal-information | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:43 |
https://golf.forem.com/privacy#c-marketing-and-advertising-our-products-and-services | Privacy Policy - Golf 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 Golf Forem 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 Golf Forem — A community of golfers and golfing enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Golf Forem © 2016 - 2026. Where hackers, sticks, weekend warriors, pros, architects and wannabes come together Log in Create account | 2026-01-13T08:48:43 |
https://docs.python.org/3/reference/simple_stmts.html#nonlocal | 7. Simple statements — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 7. Simple statements 7.1. Expression statements 7.2. Assignment statements 7.2.1. Augmented assignment statements 7.2.2. Annotated assignment statements 7.3. The assert statement 7.4. The pass statement 7.5. The del statement 7.6. The return statement 7.7. The yield statement 7.8. The raise statement 7.9. The break statement 7.10. The continue statement 7.11. The import statement 7.11.1. Future statements 7.12. The global statement 7.13. The nonlocal statement 7.14. The type statement Previous topic 6. Expressions Next topic 8. Compound statements This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Language Reference » 7. Simple statements | Theme Auto Light Dark | 7. Simple statements ¶ A simple statement is comprised within a single logical line. Several simple statements may occur on a single line separated by semicolons. The syntax for simple statements is: simple_stmt : expression_stmt | assert_stmt | assignment_stmt | augmented_assignment_stmt | annotated_assignment_stmt | pass_stmt | del_stmt | return_stmt | yield_stmt | raise_stmt | break_stmt | continue_stmt | import_stmt | future_stmt | global_stmt | nonlocal_stmt | type_stmt 7.1. Expression statements ¶ Expression statements are used (mostly interactively) to compute and write a value, or (usually) to call a procedure (a function that returns no meaningful result; in Python, procedures return the value None ). Other uses of expression statements are allowed and occasionally useful. The syntax for an expression statement is: expression_stmt : starred_expression An expression statement evaluates the expression list (which may be a single expression). In interactive mode, if the value is not None , it is converted to a string using the built-in repr() function and the resulting string is written to standard output on a line by itself (except if the result is None , so that procedure calls do not cause any output.) 7.2. Assignment statements ¶ Assignment statements are used to (re)bind names to values and to modify attributes or items of mutable objects: assignment_stmt : ( target_list "=" )+ ( starred_expression | yield_expression ) target_list : target ( "," target )* [ "," ] target : identifier | "(" [ target_list ] ")" | "[" [ target_list ] "]" | attributeref | subscription | slicing | "*" target (See section Primaries for the syntax definitions for attributeref , subscription , and slicing .) An assignment statement evaluates the expression list (remember that this can be a single expression or a comma-separated list, the latter yielding a tuple) and assigns the single resulting object to each of the target lists, from left to right. Assignment is defined recursively depending on the form of the target (list). When a target is part of a mutable object (an attribute reference, subscription or slicing), the mutable object must ultimately perform the assignment and decide about its validity, and may raise an exception if the assignment is unacceptable. The rules observed by various types and the exceptions raised are given with the definition of the object types (see section The standard type hierarchy ). Assignment of an object to a target list, optionally enclosed in parentheses or square brackets, is recursively defined as follows. If the target list is a single target with no trailing comma, optionally in parentheses, the object is assigned to that target. Else: If the target list contains one target prefixed with an asterisk, called a “starred” target: The object must be an iterable with at least as many items as there are targets in the target list, minus one. The first items of the iterable are assigned, from left to right, to the targets before the starred target. The final items of the iterable are assigned to the targets after the starred target. A list of the remaining items in the iterable is then assigned to the starred target (the list can be empty). Else: The object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets. Assignment of an object to a single target is recursively defined as follows. If the target is an identifier (name): If the name does not occur in a global or nonlocal statement in the current code block: the name is bound to the object in the current local namespace. Otherwise: the name is bound to the object in the global namespace or the outer namespace determined by nonlocal , respectively. The name is rebound if it was already bound. This may cause the reference count for the object previously bound to the name to reach zero, causing the object to be deallocated and its destructor (if it has one) to be called. If the target is an attribute reference: The primary expression in the reference is evaluated. It should yield an object with assignable attributes; if this is not the case, TypeError is raised. That object is then asked to assign the assigned object to the given attribute; if it cannot perform the assignment, it raises an exception (usually but not necessarily AttributeError ). Note: If the object is a class instance and the attribute reference occurs on both sides of the assignment operator, the right-hand side expression, a.x can access either an instance attribute or (if no instance attribute exists) a class attribute. The left-hand side target a.x is always set as an instance attribute, creating it if necessary. Thus, the two occurrences of a.x do not necessarily refer to the same attribute: if the right-hand side expression refers to a class attribute, the left-hand side creates a new instance attribute as the target of the assignment: class Cls : x = 3 # class variable inst = Cls () inst . x = inst . x + 1 # writes inst.x as 4 leaving Cls.x as 3 This description does not necessarily apply to descriptor attributes, such as properties created with property() . If the target is a subscription: The primary expression in the reference is evaluated. It should yield either a mutable sequence object (such as a list) or a mapping object (such as a dictionary). Next, the subscript expression is evaluated. If the primary is a mutable sequence object (such as a list), the subscript must yield an integer. If it is negative, the sequence’s length is added to it. The resulting value must be a nonnegative integer less than the sequence’s length, and the sequence is asked to assign the assigned object to its item with that index. If the index is out of range, IndexError is raised (assignment to a subscripted sequence cannot add new items to a list). If the primary is a mapping object (such as a dictionary), the subscript must have a type compatible with the mapping’s key type, and the mapping is then asked to create a key/value pair which maps the subscript to the assigned object. This can either replace an existing key/value pair with the same key value, or insert a new key/value pair (if no key with the same value existed). For user-defined objects, the __setitem__() method is called with appropriate arguments. If the target is a slicing: The primary expression in the reference is evaluated. It should yield a mutable sequence object (such as a list). The assigned object should be a sequence object of the same type. Next, the lower and upper bound expressions are evaluated, insofar they are present; defaults are zero and the sequence’s length. The bounds should evaluate to integers. If either bound is negative, the sequence’s length is added to it. The resulting bounds are clipped to lie between zero and the sequence’s length, inclusive. Finally, the sequence object is asked to replace the slice with the items of the assigned sequence. The length of the slice may be different from the length of the assigned sequence, thus changing the length of the target sequence, if the target sequence allows it. CPython implementation detail: In the current implementation, the syntax for targets is taken to be the same as for expressions, and invalid syntax is rejected during the code generation phase, causing less detailed error messages. Although the definition of assignment implies that overlaps between the left-hand side and the right-hand side are ‘simultaneous’ (for example a, b = b, a swaps two variables), overlaps within the collection of assigned-to variables occur left-to-right, sometimes resulting in confusion. For instance, the following program prints [0, 2] : x = [ 0 , 1 ] i = 0 i , x [ i ] = 1 , 2 # i is updated, then x[i] is updated print ( x ) See also PEP 3132 - Extended Iterable Unpacking The specification for the *target feature. 7.2.1. Augmented assignment statements ¶ Augmented assignment is the combination, in a single statement, of a binary operation and an assignment statement: augmented_assignment_stmt : augtarget augop ( expression_list | yield_expression ) augtarget : identifier | attributeref | subscription | slicing augop : "+=" | "-=" | "*=" | "@=" | "/=" | "//=" | "%=" | "**=" | ">>=" | "<<=" | "&=" | "^=" | "|=" (See section Primaries for the syntax definitions of the last three symbols.) An augmented assignment evaluates the target (which, unlike normal assignment statements, cannot be an unpacking) and the expression list, performs the binary operation specific to the type of assignment on the two operands, and assigns the result to the original target. The target is only evaluated once. An augmented assignment statement like x += 1 can be rewritten as x = x + 1 to achieve a similar, but not exactly equal effect. In the augmented version, x is only evaluated once. Also, when possible, the actual operation is performed in-place , meaning that rather than creating a new object and assigning that to the target, the old object is modified instead. Unlike normal assignments, augmented assignments evaluate the left-hand side before evaluating the right-hand side. For example, a[i] += f(x) first looks-up a[i] , then it evaluates f(x) and performs the addition, and lastly, it writes the result back to a[i] . With the exception of assigning to tuples and multiple targets in a single statement, the assignment done by augmented assignment statements is handled the same way as normal assignments. Similarly, with the exception of the possible in-place behavior, the binary operation performed by augmented assignment is the same as the normal binary operations. For targets which are attribute references, the same caveat about class and instance attributes applies as for regular assignments. 7.2.2. Annotated assignment statements ¶ Annotation assignment is the combination, in a single statement, of a variable or attribute annotation and an optional assignment statement: annotated_assignment_stmt : augtarget ":" expression [ "=" ( starred_expression | yield_expression )] The difference from normal Assignment statements is that only a single target is allowed. The assignment target is considered “simple” if it consists of a single name that is not enclosed in parentheses. For simple assignment targets, if in class or module scope, the annotations are gathered in a lazily evaluated annotation scope . The annotations can be evaluated using the __annotations__ attribute of a class or module, or using the facilities in the annotationlib module. If the assignment target is not simple (an attribute, subscript node, or parenthesized name), the annotation is never evaluated. If a name is annotated in a function scope, then this name is local for that scope. Annotations are never evaluated and stored in function scopes. If the right hand side is present, an annotated assignment performs the actual assignment as if there was no annotation present. If the right hand side is not present for an expression target, then the interpreter evaluates the target except for the last __setitem__() or __setattr__() call. See also PEP 526 - Syntax for Variable Annotations The proposal that added syntax for annotating the types of variables (including class variables and instance variables), instead of expressing them through comments. PEP 484 - Type hints The proposal that added the typing module to provide a standard syntax for type annotations that can be used in static analysis tools and IDEs. Changed in version 3.8: Now annotated assignments allow the same expressions in the right hand side as regular assignments. Previously, some expressions (like un-parenthesized tuple expressions) caused a syntax error. Changed in version 3.14: Annotations are now lazily evaluated in a separate annotation scope . If the assignment target is not simple, annotations are never evaluated. 7.3. The assert statement ¶ Assert statements are a convenient way to insert debugging assertions into a program: assert_stmt : "assert" expression [ "," expression ] The simple form, assert expression , is equivalent to if __debug__ : if not expression : raise AssertionError The extended form, assert expression1, expression2 , is equivalent to if __debug__ : if not expression1 : raise AssertionError ( expression2 ) These equivalences assume that __debug__ and AssertionError refer to the built-in variables with those names. In the current implementation, the built-in variable __debug__ is True under normal circumstances, False when optimization is requested (command line option -O ). The current code generator emits no code for an assert statement when optimization is requested at compile time. Note that it is unnecessary to include the source code for the expression that failed in the error message; it will be displayed as part of the stack trace. Assignments to __debug__ are illegal. The value for the built-in variable is determined when the interpreter starts. 7.4. The pass statement ¶ pass_stmt : "pass" pass is a null operation — when it is executed, nothing happens. It is useful as a placeholder when a statement is required syntactically, but no code needs to be executed, for example: def f ( arg ): pass # a function that does nothing (yet) class C : pass # a class with no methods (yet) 7.5. The del statement ¶ del_stmt : "del" target_list Deletion is recursively defined very similar to the way assignment is defined. Rather than spelling it out in full details, here are some hints. Deletion of a target list recursively deletes each target, from left to right. Deletion of a name removes the binding of that name from the local or global namespace, depending on whether the name occurs in a global statement in the same code block. Trying to delete an unbound name raises a NameError exception. Deletion of attribute references, subscriptions and slicings is passed to the primary object involved; deletion of a slicing is in general equivalent to assignment of an empty slice of the right type (but even this is determined by the sliced object). Changed in version 3.2: Previously it was illegal to delete a name from the local namespace if it occurs as a free variable in a nested block. 7.6. The return statement ¶ return_stmt : "return" [ expression_list ] return may only occur syntactically nested in a function definition, not within a nested class definition. If an expression list is present, it is evaluated, else None is substituted. return leaves the current function call with the expression list (or None ) as return value. When return passes control out of a try statement with a finally clause, that finally clause is executed before really leaving the function. In a generator function, the return statement indicates that the generator is done and will cause StopIteration to be raised. The returned value (if any) is used as an argument to construct StopIteration and becomes the StopIteration.value attribute. In an asynchronous generator function, an empty return statement indicates that the asynchronous generator is done and will cause StopAsyncIteration to be raised. A non-empty return statement is a syntax error in an asynchronous generator function. 7.7. The yield statement ¶ yield_stmt : yield_expression A yield statement is semantically equivalent to a yield expression . The yield statement can be used to omit the parentheses that would otherwise be required in the equivalent yield expression statement. For example, the yield statements yield < expr > yield from < expr > are equivalent to the yield expression statements ( yield < expr > ) ( yield from < expr > ) Yield expressions and statements are only used when defining a generator function, and are only used in the body of the generator function. Using yield in a function definition is sufficient to cause that definition to create a generator function instead of a normal function. For full details of yield semantics, refer to the Yield expressions section. 7.8. The raise statement ¶ raise_stmt : "raise" [ expression [ "from" expression ]] If no expressions are present, raise re-raises the exception that is currently being handled, which is also known as the active exception . If there isn’t currently an active exception, a RuntimeError exception is raised indicating that this is an error. Otherwise, raise evaluates the first expression as the exception object. It must be either a subclass or an instance of BaseException . If it is a class, the exception instance will be obtained when needed by instantiating the class with no arguments. The type of the exception is the exception instance’s class, the value is the instance itself. A traceback object is normally created automatically when an exception is raised and attached to it as the __traceback__ attribute. You can create an exception and set your own traceback in one step using the with_traceback() exception method (which returns the same exception instance, with its traceback set to its argument), like so: raise Exception ( "foo occurred" ) . with_traceback ( tracebackobj ) The from clause is used for exception chaining: if given, the second expression must be another exception class or instance. If the second expression is an exception instance, it will be attached to the raised exception as the __cause__ attribute (which is writable). If the expression is an exception class, the class will be instantiated and the resulting exception instance will be attached to the raised exception as the __cause__ attribute. If the raised exception is not handled, both exceptions will be printed: >>> try : ... print ( 1 / 0 ) ... except Exception as exc : ... raise RuntimeError ( "Something bad happened" ) from exc ... Traceback (most recent call last): File "<stdin>" , line 2 , in <module> print ( 1 / 0 ) ~~^~~ ZeroDivisionError : division by zero The above exception was the direct cause of the following exception: Traceback (most recent call last): File "<stdin>" , line 4 , in <module> raise RuntimeError ( "Something bad happened" ) from exc RuntimeError : Something bad happened A similar mechanism works implicitly if a new exception is raised when an exception is already being handled. An exception may be handled when an except or finally clause, or a with statement, is used. The previous exception is then attached as the new exception’s __context__ attribute: >>> try : ... print ( 1 / 0 ) ... except : ... raise RuntimeError ( "Something bad happened" ) ... Traceback (most recent call last): File "<stdin>" , line 2 , in <module> print ( 1 / 0 ) ~~^~~ ZeroDivisionError : division by zero During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>" , line 4 , in <module> raise RuntimeError ( "Something bad happened" ) RuntimeError : Something bad happened Exception chaining can be explicitly suppressed by specifying None in the from clause: >>> try : ... print ( 1 / 0 ) ... except : ... raise RuntimeError ( "Something bad happened" ) from None ... Traceback (most recent call last): File "<stdin>" , line 4 , in <module> RuntimeError : Something bad happened Additional information on exceptions can be found in section Exceptions , and information about handling exceptions is in section The try statement . Changed in version 3.3: None is now permitted as Y in raise X from Y . Added the __suppress_context__ attribute to suppress automatic display of the exception context. Changed in version 3.11: If the traceback of the active exception is modified in an except clause, a subsequent raise statement re-raises the exception with the modified traceback. Previously, the exception was re-raised with the traceback it had when it was caught. 7.9. The break statement ¶ break_stmt : "break" break may only occur syntactically nested in a for or while loop, but not nested in a function or class definition within that loop. It terminates the nearest enclosing loop, skipping the optional else clause if the loop has one. If a for loop is terminated by break , the loop control target keeps its current value. When break passes control out of a try statement with a finally clause, that finally clause is executed before really leaving the loop. 7.10. The continue statement ¶ continue_stmt : "continue" continue may only occur syntactically nested in a for or while loop, but not nested in a function or class definition within that loop. It continues with the next cycle of the nearest enclosing loop. When continue passes control out of a try statement with a finally clause, that finally clause is executed before really starting the next loop cycle. 7.11. The import statement ¶ import_stmt : "import" module [ "as" identifier ] ( "," module [ "as" identifier ])* | "from" relative_module "import" identifier [ "as" identifier ] ( "," identifier [ "as" identifier ])* | "from" relative_module "import" "(" identifier [ "as" identifier ] ( "," identifier [ "as" identifier ])* [ "," ] ")" | "from" relative_module "import" "*" module : ( identifier "." )* identifier relative_module : "." * module | "." + The basic import statement (no from clause) is executed in two steps: find a module, loading and initializing it if necessary define a name or names in the local namespace for the scope where the import statement occurs. When the statement contains multiple clauses (separated by commas) the two steps are carried out separately for each clause, just as though the clauses had been separated out into individual import statements. The details of the first step, finding and loading modules, are described in greater detail in the section on the import system , which also describes the various types of packages and modules that can be imported, as well as all the hooks that can be used to customize the import system. Note that failures in this step may indicate either that the module could not be located, or that an error occurred while initializing the module, which includes execution of the module’s code. If the requested module is retrieved successfully, it will be made available in the local namespace in one of three ways: If the module name is followed by as , then the name following as is bound directly to the imported module. If no other name is specified, and the module being imported is a top level module, the module’s name is bound in the local namespace as a reference to the imported module If the module being imported is not a top level module, then the name of the top level package that contains the module is bound in the local namespace as a reference to the top level package. The imported module must be accessed using its full qualified name rather than directly The from form uses a slightly more complex process: find the module specified in the from clause, loading and initializing it if necessary; for each of the identifiers specified in the import clauses: check if the imported module has an attribute by that name if not, attempt to import a submodule with that name and then check the imported module again for that attribute if the attribute is not found, ImportError is raised. otherwise, a reference to that value is stored in the local namespace, using the name in the as clause if it is present, otherwise using the attribute name Examples: import foo # foo imported and bound locally import foo.bar.baz # foo, foo.bar, and foo.bar.baz imported, foo bound locally import foo.bar.baz as fbb # foo, foo.bar, and foo.bar.baz imported, foo.bar.baz bound as fbb from foo.bar import baz # foo, foo.bar, and foo.bar.baz imported, foo.bar.baz bound as baz from foo import attr # foo imported and foo.attr bound as attr If the list of identifiers is replaced by a star ( '*' ), all public names defined in the module are bound in the local namespace for the scope where the import statement occurs. The public names defined by a module are determined by checking the module’s namespace for a variable named __all__ ; if defined, it must be a sequence of strings which are names defined or imported by that module. The names given in __all__ are all considered public and are required to exist. If __all__ is not defined, the set of public names includes all names found in the module’s namespace which do not begin with an underscore character ( '_' ). __all__ should contain the entire public API. It is intended to avoid accidentally exporting items that are not part of the API (such as library modules which were imported and used within the module). The wild card form of import — from module import * — is only allowed at the module level. Attempting to use it in class or function definitions will raise a SyntaxError . When specifying what module to import you do not have to specify the absolute name of the module. When a module or package is contained within another package it is possible to make a relative import within the same top package without having to mention the package name. By using leading dots in the specified module or package after from you can specify how high to traverse up the current package hierarchy without specifying exact names. One leading dot means the current package where the module making the import exists. Two dots means up one package level. Three dots is up two levels, etc. So if you execute from . import mod from a module in the pkg package then you will end up importing pkg.mod . If you execute from ..subpkg2 import mod from within pkg.subpkg1 you will import pkg.subpkg2.mod . The specification for relative imports is contained in the Package Relative Imports section. importlib.import_module() is provided to support applications that determine dynamically the modules to be loaded. Raises an auditing event import with arguments module , filename , sys.path , sys.meta_path , sys.path_hooks . 7.11.1. Future statements ¶ A future statement is a directive to the compiler that a particular module should be compiled using syntax or semantics that will be available in a specified future release of Python where the feature becomes standard. The future statement is intended to ease migration to future versions of Python that introduce incompatible changes to the language. It allows use of the new features on a per-module basis before the release in which the feature becomes standard. future_stmt : "from" "__future__" "import" feature [ "as" identifier ] ( "," feature [ "as" identifier ])* | "from" "__future__" "import" "(" feature [ "as" identifier ] ( "," feature [ "as" identifier ])* [ "," ] ")" feature : identifier A future statement must appear near the top of the module. The only lines that can appear before a future statement are: the module docstring (if any), comments, blank lines, and other future statements. The only feature that requires using the future statement is annotations (see PEP 563 ). All historical features enabled by the future statement are still recognized by Python 3. The list includes absolute_import , division , generators , generator_stop , unicode_literals , print_function , nested_scopes and with_statement . They are all redundant because they are always enabled, and only kept for backwards compatibility. A future statement is recognized and treated specially at compile time: Changes to the semantics of core constructs are often implemented by generating different code. It may even be the case that a new feature introduces new incompatible syntax (such as a new reserved word), in which case the compiler may need to parse the module differently. Such decisions cannot be pushed off until runtime. For any given release, the compiler knows which feature names have been defined, and raises a compile-time error if a future statement contains a feature not known to it. The direct runtime semantics are the same as for any import statement: there is a standard module __future__ , described later, and it will be imported in the usual way at the time the future statement is executed. The interesting runtime semantics depend on the specific feature enabled by the future statement. Note that there is nothing special about the statement: import __future__ [ as name ] That is not a future statement; it’s an ordinary import statement with no special semantics or syntax restrictions. Code compiled by calls to the built-in functions exec() and compile() that occur in a module M containing a future statement will, by default, use the new syntax or semantics associated with the future statement. This can be controlled by optional arguments to compile() — see the documentation of that function for details. A future statement typed at an interactive interpreter prompt will take effect for the rest of the interpreter session. If an interpreter is started with the -i option, is passed a script name to execute, and the script includes a future statement, it will be in effect in the interactive session started after the script is executed. See also PEP 236 - Back to the __future__ The original proposal for the __future__ mechanism. 7.12. The global statement ¶ global_stmt : "global" identifier ( "," identifier )* The global statement causes the listed identifiers to be interpreted as globals. It would be impossible to assign to a global variable without global , although free variables may refer to globals without being declared global. The global statement applies to the entire current scope (module, function body or class definition). A SyntaxError is raised if a variable is used or assigned to prior to its global declaration in the scope. At the module level, all variables are global, so a global statement has no effect. However, variables must still not be used or assigned to prior to their global declaration. This requirement is relaxed in the interactive prompt ( REPL ). Programmer’s note: global is a directive to the parser. It applies only to code parsed at the same time as the global statement. In particular, a global statement contained in a string or code object supplied to the built-in exec() function does not affect the code block containing the function call, and code contained in such a string is unaffected by global statements in the code containing the function call. The same applies to the eval() and compile() functions. 7.13. The nonlocal statement ¶ nonlocal_stmt : "nonlocal" identifier ( "," identifier )* When the definition of a function or class is nested (enclosed) within the definitions of other functions, its nonlocal scopes are the local scopes of the enclosing functions. The nonlocal statement causes the listed identifiers to refer to names previously bound in nonlocal scopes. It allows encapsulated code to rebind such nonlocal identifiers. If a name is bound in more than one nonlocal scope, the nearest binding is used. If a name is not bound in any nonlocal scope, or if there is no nonlocal scope, a SyntaxError is raised. The nonlocal statement applies to the entire scope of a function or class body. A SyntaxError is raised if a variable is used or assigned to prior to its nonlocal declaration in the scope. See also PEP 3104 - Access to Names in Outer Scopes The specification for the nonlocal statement. Programmer’s note: nonlocal is a directive to the parser and applies only to code parsed along with it. See the note for the global statement. 7.14. The type statement ¶ type_stmt : 'type' identifier [ type_params ] "=" expression The type statement declares a type alias, which is an instance of typing.TypeAliasType . For example, the following statement creates a type alias: type Point = tuple [ float , float ] This code is roughly equivalent to: annotation - def VALUE_OF_Point (): return tuple [ float , float ] Point = typing . TypeAliasType ( "Point" , VALUE_OF_Point ()) annotation-def indicates an annotation scope , which behaves mostly like a function, but with several small differences. The value of the type alias is evaluated in the annotation scope. It is not evaluated when the type alias is created, but only when the value is accessed through the type alias’s __value__ attribute (see Lazy evaluation ). This allows the type alias to refer to names that are not yet defined. Type aliases may be made generic by adding a type parameter list after the name. See Generic type aliases for more. type is a soft keyword . Added in version 3.12. See also PEP 695 - Type Parameter Syntax Introduced the type statement and syntax for generic classes and functions. Table of Contents 7. Simple statements 7.1. Expression statements 7.2. Assignment statements 7.2.1. Augmented assignment statements 7.2.2. Annotated assignment statements 7.3. The assert statement 7.4. The pass statement 7.5. The del statement 7.6. The return statement 7.7. The yield statement 7.8. The raise statement 7.9. The break statement 7.10. The continue statement 7.11. The import statement 7.11.1. Future statements 7.12. The global statement 7.13. The nonlocal statement 7.14. The type statement Previous topic 6. Expressions Next topic 8. Compound statements This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Language Reference » 7. Simple statements | 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:43 |
https://legal.x.com/hr/purchaser-terms.html | Uvjeti pružanja usluge kupcu X-ovih usluga Uvjeti pružanja usluge kupcu X-ovih usluga Preuzmi Uvjete pružanja usluge kupcu X-ovih usluga Uvjeti za usluge koje se plaćaju Dodatni uvjeti za X Premium Dodatni uvjeti za Pretplate Preuzmi Uvjete pružanja usluge kupcu X-ovih usluga Uvjeti pružanja usluge kupcu X-ovih usluga goglobalwithtwitterbanner Uvjeti za usluge koje se plaćaju Dodatni uvjeti za X Premium Dodatni uvjeti pretplata na autora sadržaja Dodatni uvjeti za Premium za poslovne korisnike i Premium za tvrtke ili ustanove Uvjeti za usluge koje se plaćaju Dodatni uvjeti za X Premium Dodatni uvjeti pretplata na autora sadržaja Dodatni uvjeti za Premium za poslovne korisnike i Premium za tvrtke ili ustanove Uvjeti pružanja usluge kupcu X-ovih usluga Stupa na snagu: 1. kolovoza 2025. Ako živite izvan Europske unije, država EFTA-e ili Ujedinjenog Kraljevstva, kao i ako živite u Sjedinjenim Američkim Državama, na vas se primjenjuju sljedeći Uvjeti pružanja usluge za kupce X-ovih usluga . Ako živite u Europskoj uniji, državama EFTA-e ili Ujedinjenom Kraljevstvu, na vas se primjenjuju ovi Uvjeti pružanja usluge za kupce X-ovih usluga. Uvjeti pružanja usluge kupcu X-ovih usluga Ako živite izvan Europske unije, država EFTA-e ili Ujedinjenog Kraljevstva, kao i ako živite u Sjedinjenim Državama X vam omogućuje pristup određenim značajkama u zamjenu za plaćanje jednokratne ili ponavljajuće naknade, ovisno o relevantnim značajkama (pojedinačno „ usluga koja se plaća ”, a zajedničkim nazivom „ usluge koje se plaćaju ”). Na primjer, X Premium (kao što je definirano u nastavku) i pretplate pojedinačno se smatraju „uslugom koja se plaća”. U mjeri u kojoj se prijavite za uslugu koja se plaća i/ili je upotrebljavate, vaša upotreba usluga koje se plaćaju i svih pripadnih transakcija podliježu: (i) uvjetima i odredbama navedenima u ovom dokumentu, uključujući primjenjive uvjete i odredbe za svaku kupljenu uslugu koja se plaća, navedene u nastavku (zajedničkim nazivom „ uvjeti pružanja usluge kupcu X-ovih usluga ”) i (ii) primjenjivim uvjetima pružanja usluge platforme X , pravilima o privatnosti platforme X , našim pravilima i pravilnicima te svim na taj način obuhvaćenim pravilnicima (zajedničkim nazivom „ ugovor s korisnikom platforme X ”). Ovi Uvjeti pružanja usluge kupcu X-ovih usluga i prethodno spomenuti ugovor s korisnikom X-a u ovom će dokumentu biti obuhvaćeni zajedničkim nazivom „ uvjeti ”. " X " odnosi se na X entitet koji vam pruža usluge uz plaćanje. Pažljivo pročitajte ove Uvjete pružanja usluge za kupce X-ovih usluga kako biste bili sigurni da razumijete primjenjive uvjete, odredbe i iznimke. AKO ŽIVITE U SJEDINJENIM AMERIČKIM DRŽAVAMA, OVI UVJETI SADRŽE VAŽNE INFORMACIJE KOJE VRIJEDE ZA VAS PRI RJEŠAVANJU SPOROVA, UKLJUČUJUĆI VAŠE ODRICANJE OD PRAVA PODNOŠENJA ZAHTJEVA PUTEM GRUPNE TUŽBE, KAO I OGRANIČENJE VAŠEG PRAVA NA PODNOŠENJE ZAHTJEVA PROTIV X-A VIŠE OD 2 GODINE NAKON RELEVANTNIH DOGAĐAJA, A KOJE UTJEČU NA VAŠA PRAVA I OBVEZE U SLUČAJU BILO KAKVOG SPORA S X-om. POJEDINOSTI O TIM ODREDBAMA POTRAŽITE U ODJELJKU 6 U OKVIRU OPĆIH UVJETA. Prihvaćanje . Upotrebom X-ovih usluga koje se plaćaju ili pristupanjem tim uslugama, izvršenjem plaćanja za te usluge i/ili klikom na gumb za jednokratnu kupnju odnosno ponavljajuća plaćanja pretplate za X-ove usluge koje se plaćaju izražavate svoj pristanak na uvjete. Ako ne razumijete uvjete ili ne prihvaćate bilo koji njihov dio, ne smijete koristiti nikakve usluge koje se plaćaju niti im pristupati. Za kupnju i korištenje usluga koje se plaćaju morate: (i) imati najmanje 18 godina ili biti punoljetni prema zakonima mjerodavnima za vaše prebivalište ili (ii) imati izričit pristanak roditelja ili skrbnika za kupnju i korištenje te usluge koja se plaća. Ako ste roditelj ili zakonski skrbnik i dopuštate svom djetetu (ili djetetu čiji ste skrbnik) kupnju ili korištenje usluge koja se plaća, prihvaćate ove uvjete te potvrđujete da ćete ih se pridržavati i da ste odgovorni za djetetovu aktivnost u okviru usluga koje se plaćaju te da ćete osigurati da se dijete također pridržava ovih uvjeta. U svakom slučaju, kao što je navedeno u članku Tko smije koristiti usluge u Uvjetima pružanja usluge za X, morate imati najmanje 13 godina da biste koristili uslugu X. Ako prihvaćate ove uvjete pružanja usluge kupcu X-ovih usluga i usluge koje se plaćaju koristite u ime tvrtke, organizacije, vlade ili drugog pravnog subjekta, izjavljujete i jamčite da ste za to ovlašteni i da imate ovlasti obvezati taj subjekt ovim uvjetima pružanja usluge kupcu X-ovih usluga te se u tom slučaju riječi „vi” i „vaš” u kontekstu njihove upotrebe u ovim uvjetima pružanja usluge kupcu X-ovih usluga odnose na taj subjekt. Ugovorni subjekt platforme X . Druga ugovorna strana u ovim Uvjetima pružanja usluge kupcu X-ovih usluga jest subjekt nadležan za vaše prebivalište, kao što je navedeno u nastavku. Taj će vam subjekt pružati usluge koje se plaćaju. Nijedan drugi subjekt nema prema vama nikakve obveze prema ovim Uvjetima pružanja usluge kupcu. Vaša lokacija Sjeverna Amerike (uključujući Havaje) ili Južna Amerika Ugovorni subjekt X Corp., sa sjedištem na adresi 865 FM 1209, Building 2, Bastrop, TX 78602, USA Vaša lokacija Sve države koje nisu obuhvaćene dvjema prethodnim lokacijama, uključujući azijsko-pacifičku regiju, Bliski istok, Afriku ili Europu (isključujući zemlje EU-a, države EFTA-e i Ujedinjenu Kraljevinu) Ugovorni subjekt X Global LLC, sa sjedištem na adresi 701 S. Carson St., Suite 200, Carson City, NV 89701, SAD Promjene odredbi, usluga koje se plaćaju i cijena 1. Promjene odredbi. X može povremeno revidirati ove Uvjete pružanja usluge kupcu X-ovih usluga iz razloga koji obuhvaćaju poslovne, financijske ili pravne razloge. Promjene neće biti retroaktivne, a vašu upotrebu usluga koje se plaćaju i sve pripadne transakcije regulirat će najnovija verzija uvjeta pružanja usluge kupcu X-ovih usluga, dostupna na adresi legal.x.com/purchaser-terms . Ako izmijenimo ili revidiramo ove uvjete nakon što ste se ih prihvatili (na primjer, ako se uvjeti izmijene nakon što ste kupili pretplatu), unaprijed ćemo vas obavijestiti o suštinskim revizijama uvjeta. Takva se obavijest može dostaviti elektroničkim putem, uključujući (među ostalim) obavijest u okviru usluge ili e-poštu poslanu na adresu e-pošte povezanu s vašim računom. Nastavljanjem pristupanja ili korištenja usluga koje se plaćaju nakon što izmjene stupe na snagu izražavate svoj pristanak na revidirane uvjete pružanja usluge kupcu X-ovih usluga. Ako ne pristajete na pridržavanje tih ili bilo kojih budućih uvjeta pružanja usluge kupcu X-ovih usluga, nemojte koristiti ili nastavljati koristiti te usluge koje se plaćaju niti im pristupati ili im nastavljati pristupati. Uvjeti pružanja usluge kupcu X-ovih usluga napisani su na engleskom, ali su dostupni njihovi prijevodi na više jezika. X nastoji da prijevodi budu što točniji i vjerniji izvornoj engleskoj verziji. Međutim, u slučaju bilo kakvih odstupanja ili nedosljednosti, prednost imaju uvjeti pružanja usluge kupcu X-ovih usluga na engleskom jeziku. Prihvaćate da engleski bude referentni jezik za tumačenje i konstruiranje uvjeta pružanja usluge kupcu X-ovih usluga. 2. Promjene usluga uz plaćanje. Naše usluge uz plaćanje stalno se razvijaju. Zbog toga se usluge koje se plaćaju mogu povremeno promijeniti prema našem nahođenju iz razloga koji obuhvaćaju poslovne, financijske ili pravne razloge. Možemo (trajno ili privremeno), uz obavijest ili bez nje, vama ili svim korisnicima prestati pružati usluge koje se plaćaju ili bilo koje značajke u okviru usluga koje se plaćaju. X ne snosi odgovornost prema vama ili bilo kojoj trećoj strani zbog bilo kakvih izmjena, obustavljanja ili ukidanja usluga koje se plaćaju. Posebni uvjeti i odredbe (navedeni u nastavku) za određenu uslugu koja se plaća određuju kako možete otkazati pretplatu ili, kada je primjenjivo, zatražiti povrat novca. 3. Promjene cijena. Cijene usluga koje se plaćaju, uključujući ponavljajuće naknade za pretplatu, podložne su povremenim promjenama iz razloga koji obuhvaćaju poslovne, financijske ili pravne razloge. X će u razumnom roku unaprijed objaviti obavijest o svakoj bitnoj promjeni cijene usluga koje se plaćaju. Za pretplatne usluge promjene cijena stupaju na snagu s početkom sljedećeg pretplatnog razdoblja nakon datuma promjene cijene. Ako se ne slažete s promjenom cijene, imate pravo odbiti promjenu otkazivanjem pretplate na odgovarajuću uslugu koja se plaća prije nego što promjena cijene stupi na snagu. Uvjeti plaćanja . X nudi razne opcije plaćanja, koje mogu varirati ovisno o usluzi koja se plaća, vašem uređaju i/ili operacijskom sustavu, vašoj geografskoj lokaciji ili drugim čimbenicima. U dostupnoj mjeri (budući da X može povremeno učiniti dostupnima različite načine kupnje) te opcije plaćanja mogu obuhvaćati mogućnost korištenja funkcije „plaćanja u aplikaciji” koju nude Google ili Apple, kao i plaćanja putem weba i treće strane koja djeluje u svojstvu X-ovog voditelja obrade plaćanja, servisa Stripe ( www.stripe.com; u nastavku teksta „ Stripe ”). Kada izvršite plaćanje, izričito pristajete: (i) platiti cijenu navedenu za tu uslugu koja se plaća, zajedno sa svim dodatnim iznosima primjenjivih poreza, naknada za upotrebu kreditnih kartica, bankovnih naknada, naknada za inozemne transakcije, mjenjačkih naknada i valutnih fluktuacija; i (ii) pridržavati se svih relevantnih uvjeta pružanja usluge, pravila o privatnosti ili drugih pravnih ugovora ili ograničenja (uključujući dodatna dobna ograničenja) koja propisuju Google, Apple ili Stripe (kao treće strane koje djeluju u svojstvu X-ovih voditelja obrade plaćanja) u vezi s vašim korištenjem određenog načina plaćanja (samo za potrebe primjera, ako odaberete plaćanje putem Appleove funkcije kupnje u aplikaciji, pristajete pridržavati se svih relevantnih uvjeta, zahtjeva i/ili ograničenja koje propisuje Apple). Svi privatni osobni podaci koje navedete u vezi s korištenjem usluga koje se plaćaju, uključujući, među ostalim, sve podatke navedene u vezi s plaćanjem, obrađivat će se u skladu s X-ovim pravilima o privatnosti. X može podijeliti vaše podatke za plaćanje s pružateljima usluga plaćanja radi obrade plaćanja, sprječavanja, otkrivanja i istraživanja prijevara ili drugih zabranjenih aktivnosti, olakšavanja rješavanja sporova poput storniranja ili povrata novca te u druge svrhe povezane s prihvaćanjem kreditnih i debitnih kartica ili ACH-a. Sami ste dužni pobrinuti se da vaši bankovni podaci, podaci o kreditnoj ili debitnoj kartici i/ili drugi podaci za plaćanje u svakom trenutku budu ažurni, potpuni i točni. Ako izvršite uplatu za uslugu koja se plaća, možda ćemo primiti informacije o vašoj transakciji, kao što su vrijeme izvršenja, datum isteka ili automatskog obnavljanja pretplate, platforma na kojoj ste izvršili kupnju i drugi podaci. X ne snosi odgovornost ni za kakve pogreške ili kašnjenja koje prouzroče voditelj plaćanja, Appleova trgovina App Store ili Google Play Store, vaša banka, tvrtka koja vam je izdala kreditnu karticu i/ili bilo koja platna mreža. Uvjete plaćanja koji se primjenjuju na određenu uslugu koja se plaća, uključujući način postupanja s obnovama pretplate i druge važne uvjete, potražite u nastavku u pripadnim uvjetima i odredbama za tu uslugu koja se plaća. Primjena i raskid ugovora s korisnikom X-a, nepostojanje mogućnosti povrata novca, veći broj računa za X i ograničenja 1. Vezani ste ugovorom s korisnikom X-a . UVIJEK MORATE POŠTIVATI UGOVOR S KORISNIKOM X-a I PRIDRŽAVATI GA SE. Ugovor s korisnikom X-a uvijek se primjenjuje na vašu upotrebu usluge X, uključujući usluge i značajke koje se plaćaju. Ako ne budete poštivali ugovor s korisnikom X-a ili ga se ne budete pridržavali, odnosno ako X bude smatrao da ga niste poštivali ili ga se pridržavali, to može dovesti do otkazivanja vaših usluga koje se plaćaju. Svako takvo otkazivanje nadovezivat će se, bez ograničenja, na sve radnje koje X može poduzeti protiv vas u skladu s ugovorom s korisnikom X-a. U takvim slučajevima možete izgubiti pogodnosti svojih usluga koje se plaćaju te nećete imati pravo na povrat bilo kojeg iznosa koji ste platili (ili unaprijed platili) za usluge koje se plaćaju. 2. Zbog čega X može ukinuti vaš pristup uslugama koje se plaćaju. X može obustaviti ili ukinuti vaš pristup uslugama koje se plaćaju ili prestati pružati vam sve usluge koje se plaćaju ili dio tih usluga ili poduzeti bilo koju drugu radnju koju smatra prikladnom, uključujući obustavu vašeg računa (bez ikakve odgovornosti) u bilo kojem trenutku i zbog bilo kojeg razloga ili bez razloga, uključujući, među ostalim, bilo koji od sljedećih razloga: a. X smatra, prema isključivo vlastitu nahođenju, da ste prekršili ove uvjete ili da bi vaša upotreba usluga koje se plaćaju prekršila neki zakon. b. Takvo postupanje od X-a traži ili mu ga nalaže neki nadležni sud, regulatorno tijelo ili agencija za provođenje zakona. c. X ima neočekivanih tehničkih ili sigurnosnih problema. d. X vjeruje, prema vlastitom nahođenju, da ste prekršili X Korisnički ugovor; e. X vjeruje, prema vlastitom nahođenju, da sudjelujete u manipulaciji ili drugom ometajućem ili zabranjenom ponašanju općenito ili u vezi s plaćenim uslugama; f. Stvarate rizik ili moguću pravnu izloženost za X; g. Vaš se račun treba ukloniti zbog nezakonitog postupanja. h. Vaš se račun treba ukloniti zbog produljene neaktivnosti, ili i. Naše pružanje plaćenih usluga (u cijelosti ili djelomično) više nije komercijalno održivo (prema vlastitom nahođenju X-a). 3. Sve su transakcije konačne. Sva plaćanja usluga koje se plaćaju konačna su te ne omogućuju povrat novca ili zamjenu, osim u skladu s mjerodavnim pravom. Ne jamčimo prirodu, kvalitetu ni vrijednost usluge koja se plaća ili njezinu dostupnost ili ponudu. Ni za koju neiskorištenu ili djelomično iskorištenu uslugu koja se plaća (na primjer, za djelomično iskorišteno pretplatno razdoblje) ne nude se povrati novca ili krediti. 4. Usluge koje se plaćaju nisu prenosive između računa za X. Svaka kupnja usluge koja se plaća odnosi se samo na jedan račun za X, što znači da će se vaša kupnja odnositi isključivo na račun koji ste koristili kada ste kupili uslugu koja se plaća te se neće odnositi na druge račune kojima možda možete pristupati ili nad kojima imate kontrolu. Ako imate ili kontrolirate više računa i želite pristup uslugama koje se plaćaju putem svakog od računa, morate kupiti uslugu koja se plaća ponaosob za svaki račun. 5. Ograničenja i obveze. a. Uslugu koja se plaća možete kupiti i koristiti samo ako vam zakoni u vašoj državi to dopuštaju i ako živite u državi koju X podržava za pripadnu uslugu koja se plaća. X može, prema vlastitom nahođenju, u određenim državama ograničiti mogućnost pristupa ili kupnje usluge koja se plaća. X zadržava pravo povremene izmjene popisa podržanih država. b. Zadržavamo pravo odbijanja transakcija za usluge koje se plaćaju ili otkazivanja ili ukidanja prodaje ili korištenja usluga koje se plaćaju prema isključivo vlastitu nahođenju. c. Ne smijete dopustiti drugima da vaš račun za X koriste za pristupanje bilo kojoj usluzi koja se plaća, a koju ta osoba nije naručila. d. Ne smijete kupiti ili koristiti uslugu koja se plaća ako ste osoba s kojom osobama iz SAD-a nije dopušteno poslovati zbog ekonomskih sankcija, uključujući, među ostalim, sankcije koje provodi Ured za kontrolu strane imovine u okviru Ministarstva financija Sjedinjenih Država ili bilo koje drugo primjenjivo sankcijsko tijelo („ zabranjena osoba ”). To, među ostalim, uključuje osobe koje se nalaze u sljedećim državama i regijama ili ondje imaju prebivalište: Kuba, Iran, ukrajinske regije Krima, Sjeverna Koreja i Sirija. Izjavljujete i jamčite da niste zabranjena osoba. e. IZJAVLJUJETE DA ĆETE USLUGE KOJE SE PLAĆAJU KORISTITI SAMO U ZAKONITE SVRHE I SAMO U SKLADU S UVJETIMA. Porezi i naknade . Sami snosite odgovornost za sve primjenjive poreze, davanja, carine i naknade povezane s kupnjom usluga koje se plaćaju, uključujući one koje treba platiti X-u ili trećoj strani koja obrađuje plaćanja, i pristajete ih platiti. Ti porezi mogu, među ostalim, obuhvaćati PDV, GST, porez na promet, porez po odbitku i sve druge primjenjive poreze. Ovisno o vašoj lokaciji, X može biti zadužen za prikupljanje i prijavljivanje informacija povezanih s porezima na transakcije koji proizlaze iz vaše kupnje usluga koje se plaćaju. X-u dajete dopuštenje za davanje informacija o vašem računu i vaših osobnih podataka relevantnim poreznim tijelima radi ispunjavanja naših obaveza povezanih s prikupljanjem poreza i poreznim izvješćivanjem. Opći uvjeti 1. Podaci za kontakt. Ako imate pitanja o uslugama koje se plaćaju ili ovim uvjetima, dodatne pojedinosti možete potražiti u X-ovu centru za pomoć za usluge koje se plaćaju . Ako ste već kupili uslugu koja se plaća, možete nas kontaktirati i putem veze za podršku, koja je dostupna u navigacijskom izborniku vašeg računa za X pod postavkama plaćanja ili pretplate. Ako imate dodatnih pitanja, možete nam se obratiti ovdje putem obrasca „Pomoć za značajke koje se plaćaju”. 2. ODRICANJA OD ODGOVORNOSTI. U NAJVEĆOJ MJERI DOPUŠTENOJ MJERODAVNIM PRAVOM USLUGAMA KOJE SE PLAĆAJU PRISTUPATE I KORISTITE IH NA VLASTITU ODGOVORNOST. RAZUMIJETE I PRISTAJETE DA VAM SE USLUGE KOJE SE PLAĆAJU PRUŽAJU „KAKVE JESU” I „KAKO BUDU DOSTUPNE”. X SE ODRIČE SVIH JAMSTAVA I UVJETA, BILO IZRIČITIH ILI PODRAZUMIJEVANIH, POVEZANIH S PRIKLADNOSTI ZA PRODAJU, PRIMJERENOSTI ODREĐENOJ NAMJENI ILI NEPOSTOJANJEM KRŠENJA TUĐIH PRAVA. X NE DAJE NIKAKVO JAMSTVO NI IZJAVU TE SE ODRIČE BILO KAKVE ODGOVORNOSTI I OBAVEZE VEZANE UZ: (I) POTPUNOST, TOČNOST, DOSTUPNOST, PRAVOVREMENOST, SIGURNOST ILI POUZDANOST USLUGA KOJE SE PLAĆAJU I (II) UDOVOLJAVANJE USLUGA KOJE SE PLAĆAJU VAŠIM ZAHTJEVIMA ILI NJIHOVU DOSTUPNOST KOJA BI BILA NEPREKIDNA, SIGURNA I LIŠENA POGREŠAKA. SAMI STE ODGOVORNI ZA KORIŠTENJE USLUGE X, UKLJUČUJUĆI USLUGE KOJE SE PLAĆAJU, I SVEG SADRŽAJA KOJI IZRADITE. 3. OGRANIČENJE ODGOVORNOSTI. U NAJVEĆOJ MJERI DOPUŠTENOJ MJERODAVNIM PRAVOM SUBJEKTI PLATFORME X NE SNOSE ODGOVORNOST NI ZA KAKVU NEIZRAVNU, SLUČAJNU, POSEBNU, POSLJEDIČNU ILI KAZNENU ŠTETU I NI ZA KAKAV GUBITAK DOBITI ILI PRIHODA, BILO DA JE NASTAO IZRAVNO ILI NEIZRAVNO, TE NI ZA KAKAV GUBITAK PODATAKA, UPOTREBE, REPUTACIJE ILI DRUGI NEMATERIJALNI GUBITAK PROIZAŠAO IZ (i) VAŠEG PRISTUPANJA USLUGAMA KOJE SE PLAĆAJU ILI NJIHOVE UPOTREBE ODNOSNO NEMOGUĆNOSTI PRISTUPANJA USLUGAMA KOJE SE PLAĆAJU ILI NJIHOVE UPOTREBE (ii) BILO KAKVOG POSTUPANJA ILI SADRŽAJA BILO KOJE TREĆE STRANE OBJAVLJENOG PUTEM USLUGA KOJE SE PLAĆAJU, UKLJUČUJUĆI, MEĐU OSTALIM, BILO KAKVO KLEVETNIČKO, UVREDLJIVO ILI NEZAKONITO POSTUPANJE DRUGIH KORISNIKA ILI TREĆIH STRANA (iii) BILO KAKVOG SADRŽAJA DOBIVENOG PUTEM USLUGA KOJE SE PLAĆAJU ILI (iv) NEOVLAŠTENOG PRISTUPA, UPOTREBE ILI IZMJENE VAŠIH PRIJENOSA ILI SADRŽAJA. KAKO BI SE OTKLONILE MOGUĆE DVOJBE, DEFINICIJA USLUGA KOJE SE PLAĆAJU OGRANIČENA JE NA ZNAČAJKE KOJE NUDI X I NE OBUHVAĆA NIKAKAV SADRŽAJ KOJEM PRISTUPATE I/ILI S KOJIM STUPATE U INTERAKCIJU UPOTREBOM TIH ZNAČAJKI. NI U KOJEM SLUČAJU UKUPNA ODGOVORNOST SUBJEKATA PLATFORME X NEĆE PREMAŠITI STO AMERIČKIH DOLARA (100,00 USD) ILI IZNOS KOJI STE TIJEKOM PRETHODNIH ŠEST MJESECI EVENTUALNO PLATILI X-u ZA USLUGE KOJE SE PLAĆAJU, A KOJE SU DOVELE DO NASTANKA ZAHTJEVA. OGRANIČENJA OVOG PODODJELJKA PRIMJENJUJU SE NA SVE TEORIJE ODGOVORNOSTI, BILO TEMELJENE NA JAMSTVU, UGOVORU, STATUTU, DELIKTU (UKLJUČUJUĆI NEMAR) ILI DRUGOME, TE BEZ OBZIRA NA TO JESU LI SUBJEKTI PLATFORME X BILI OBAVIJEŠTENI O MOGUĆNOSTI TAKVE ŠTETE, ČAK I AKO SE ZA OVDJE NAVEDENI PRAVNI LIJEK UTVRDI DA NIJE POSLUŽIO SVOJOJ SUŠTINSKOJ SVRSI. „SUBJEKTI PLATFORME X-OVI” OBUHVAĆAJU X, NJEGOVA MATIČNA DRUŠTVA, PODRUŽNICE, POVEZANA DRUŠTVA, DUŽNOSNIKE, DIREKTORE, ZAPOSLENIKE, AGENTE, PREDSTAVNIKE, PARTNERE I DAVATELJE LICENCI. MJERODAVNO PRAVO U VAŠOJ JURISDIKCIJI MOŽDA NE DOPUŠTA ODREĐENA OGRANIČENJA ODGOVORNOSTI. U MJERI KOJU PROPISUJE MJERODAVNO PRAVO U VAŠOJ JURISDIKCIJI PRETHODNO NAVEDENO NE OGRANIČAVA ODGOVORNOST SUBJEKATA PLATFORME X ZA PRIJEVARU, LAŽNO PREDSTAVLJANJE, SMRT ILI TJELESNU OZLJEDU UZROKOVANU NAŠIM NEMAROM, TEŠKIM NEMAROM I/ILI NAMJERNIM POSTUPANJEM. U NAJVEĆOJ MJERI DOPUŠTENOJ MJERODAVNIM PRAVOM MAKSIMALNA UKUPNA ODGOVORNOST SUBJEKATA PLATFORME X TEMELJEM BILO KAKVIH JAMSTAVA KOJA SE NE MOGU ISKLJUČITI OGRANIČENA JE NA STO AMERIČKIH DOLARA (100,00 USD). 4. Obavijest povezana s tvrtkom Apple. U mjeri u kojoj ste kupili ili koristite usluge koje se plaćaju te im pristupate na iOS uređaju, nadalje prihvaćate i pristajete na uvjete ovog članka. Prihvaćate da uvjeti ugovarate isključivo s nama, a ne s Appleom, i da Apple ne snosi odgovornost za usluge koje se plaćaju i njihov sadržaj. Apple nema nikakvu obavezu pružiti bilo kakvu uslugu održavanja i podrške povezanu s uslugama koje se plaćaju. U slučaju da usluge koje se plaćaju nisu usklađene s bilo kojim primjenjivim jamstvom, možete obavijestiti Apple i Apple će vam vratiti iznos primjenjive kupovne cijene za usluge koje se plaćaju. U najvećoj mjeri dopuštenoj mjerodavnim pravom Apple nema nikakvih drugih jamstvenih obaveza povezanih s uslugama koje se plaćaju. Apple ne snosi odgovornost za rješavanje bilo kakvih zahtjeva vas ili bilo koje treće strane povezanih s uslugama koje se plaćaju ili s vašim posjedovanjem i/ili korištenjem usluga koje se plaćaju, uključujući, među ostalim: (i) zahtjeve proizašle iz odgovornosti za proizvod (ii) bilo kakve tvrdnje da usluge koje se plaćaju nisu u skladu s bilo kojim primjenjivim zakonskim ili regulatornim zahtjevom i (iii) zahtjeve proizašle iz zakona o zaštiti potrošača ili sličnih propisa. Apple ne snosi odgovornost za istraživanje, obranu, nagodbu i odbacivanje bilo koje tvrdnje treće strane da usluge koje se plaćaju i/ili vaše posjedovanje i korištenje mobilne aplikacije krše prava intelektualnog vlasništva te treće strane. Pristajete pridržavati se svih primjenjivih uvjeta trećih strana prilikom korištenja usluga koje se plaćaju. Apple i Appleove podružnice uživaju pogodnosti ovih uvjeta u svojstvu treće strane, a nakon što prihvatite uvjete, Apple će imati pravo (te će se smatrati da je to pravo prihvatio) u svojstvu treće strane koja je uživatelj pogodnosti ovih uvjeta nametnuti vam pridržavanje tih uvjeta. Ovim putem izjavljujete i jamčite (i) da se ne nalazite u državi koja je pod embargom vlade SAD-a ili koju je vlada SAD-a označila kao državu koja „podržava teroriste” i (ii) da niste navedeni ni na kojem popisu vlade SAD-a na kojem se navode strane podvrgnute zabranama ili ograničenjima. 5. Sukob. U slučaju sukoba između odredbi ovih uvjeta pružanja usluge kupcu X-ovih usluga i odredbi ugovora s korisnikom X-a odredbe ovih uvjeta pružanja usluge kupcu X-ovih usluga imaju prednost isključivo u pogledu vaše upotrebe usluga koje se plaćaju. 6. RJEŠAVANJE SPOROVA I ODRICANJE OD GRUPNE TUŽBE a. Početno rješavanje sporova. Većina sporova između vas i X-a može se riješiti neformalno. Možete nam se obratiti pismenim putem, obraćanjem Plaćenoj podršci ovdje . Kada nam se obratite, molimo da ukratko opišete prirodu i osnove svojih nedoumica te navedete svoje podatke za kontakt i konkretno željeno rješenje. Strane će uložiti sve napore kroz ovaj postupak podrške kako bi riješile sporove, zahtjeve ili kontroverze koje proizlaze iz ili su povezane s ovim Uvjetima i/ili vašim sudjelovanjem u Programu (pojedinačno " Spor " ili više od jednog " Sporovi "). Vi i mi slažemo se da je sudjelovanje u dobroj vjeri u ovom neformalnom postupku potrebno i mora biti dovršeno kako je gore navedeno prije nego što bilo koja strana može pokrenuti parnicu u vezi s bilo kojim sporom, osim u vezi sa zahtjevima za hitnu privremenu pomoć (" Izuzeti spor "). Ako s vama ne možemo postići dogovoreno rješenje u vezi sa sporom (osim izuzetog spora) u roku od trideset (30) dana od trenutka kada započne neformalno rješavanje spora prema gornjoj odredbi o početnom rješavanju spora, tada ili vi ili mi možemo pokrenuti parnicu. b. Izbor prava i odabir suda . PAŽLJIVO PROČITAJTE OVAJ ČLANAK – ON MOŽE ZNAČAJNO UTJECATI NA VAŠA ZAKONSKA PRAVA, UKLJUČUJUĆI VAŠE PRAVO NA PODNOŠENJE SUDSKE TUŽBE. Za ove uvjete i eventualne sporove između vas i nas mjerodavno je pravo države Teksas, uz iznimku odredbe o izboru prava, bez obzira na bilo koji drugi sporazum između vas i nas koji bi mogao navoditi suprotno. Svi sporovi povezani s ovim uvjetima, uključujući sve sporove, tužbe ili kontroverze pokretat će se isključivo na saveznim ili državnim sudovima koji se nalaze u okrugu Tarrant, Teksas, Sjedinjene Američke Države, a vi pristajete na osobnu nadležnost na tim forumima i odričete se prava na prigovor u vezi s neprimjerenim forumom. Ne dovodeći u pitanje prethodno navedeno, suglasni ste da X može prema vlastitom nahođenju pokrenuti bilo kakvu tužbu, postupak ili spor koji imamo protiv vas na bilo kojem nadležnom sudu u zemlji u kojoj boravite koja ima nadležnost i mjesto za takvu tužbu. Ako ste savezna, državna ili lokalna uprava u Sjedinjenim Američkim Državama u svom službenom svojstvu i zakonski niste u mogućnosti prihvatiti gore navedene klauzule kontrolnog zakona, nadležnosti ili mjesta, te se klauzule ne odnose na vas. Za takva tijela savezne vlade SAD-a ovaj ugovor i sve radnje u vezi s njima bit će regulirani zakonima Sjedinjenih Američkih Država (bez upućivanja na sukob zakona) i, u nedostatku saveznog zakona i u mjeri dopuštenoj saveznim zakonom, zakone države Teksas (isključujući izbor prava). c. IMATE DVIJE GODINE DA PODNESETE TUŽBU PROTIV X-A . Morate podnijeti bilo kakav zahtjev protiv X-a koji proizlazi iz ovih Uvjeta ili je povezan s njima u roku od dvije (2) godine od datuma nastanka događaja ili činjenica koje su dovele do spora, osim ako mjerodavni zakon ne predviđa da se uobičajeni rok zastare za taj zahtjev ne može skratiti sporazumom. Ako ne podnesete zahtjev u tom roku, zauvijek se odričete prava na pokretanje bilo kakvog zahtjeva ili uzroka tužbe, bilo koje vrste ili karaktera, na temelju takvih događaja ili činjenica, a takvi zahtjevi ili uzroci tužbe su trajno zabranjeni, i X neće imati nikakvu odgovornost u vezi s takvim zahtjevom. d. Odricanje od grupne tužbe . U mjeri dopuštenoj zakonom također se odričete prava sudjelovanja kao tužitelj ili član grupe u bilo kojoj planiranoj grupnoj tužbi, kolektivnoj tužbi ili posredničkom postupku. Uvjeti pružanja usluge kupcu X-ovih usluga Ako živite u Europskoj uniji, državi EFTA-e ili Ujedinjenom Kraljevstvu X vam omogućuje pristup određenim značajkama u zamjenu za plaćanje jednokratne ili ponavljajuće naknade, ovisno o relevantnim značajkama (pojedinačno „ usluga koja se plaća ”, a zajedničkim nazivom „ usluge koje se plaćaju ”). Na primjer, X Premium (kao što je definirano u nastavku) i pretplate pojedinačno se smatraju „uslugom koja se plaća”. U mjeri u kojoj se prijavite za uslugu koja se plaća i/ili je upotrebljavate, vaša upotreba usluga koje se plaćaju i svih pripadnih transakcija podliježu: (i) uvjetima i odredbama navedenima u ovom dokumentu, uključujući primjenjive uvjete i odredbe za svaku kupljenu uslugu koja se plaća, navedene u nastavku (zajedničkim nazivom „ uvjeti pružanja usluge kupcu X-ovih usluga ”) i (ii) primjenjivim uvjetima pružanja usluge platforme X , pravilima o privatnosti platforme X , našim pravilima i pravilnicima te svim na taj način obuhvaćenim pravilnicima (zajedničkim nazivom „ ugovor s korisnikom platforme X ”). Ovi Uvjeti pružanja usluge kupcu X-ovih usluga i prethodno spomenuti ugovor s korisnikom X-a u ovom će dokumentu biti obuhvaćeni zajedničkim nazivom „ uvjeti ”. " X " odnosi se na X entitet koji vam pruža usluge uz plaćanje. Pažljivo pročitajte ove uvjete pružanja usluge kupcu X-ovih usluga kako biste bili sigurni da razumijete odgovarajuće odredbe, uvjete i iznimke. AKO ŽIVITE U EUROPSKOJ UNIJI, DRŽAVAMA EFTA-E ILI UJEDINJENOM KRALJEVSTVU, OVI UVJETI SADRŽE VAŽNE INFORMACIJE KOJE SE ODNOSE NA VAS O RJEŠAVANJU SPOROVA, UKLJUČUJUĆI ODRICANJE OD PRAVA NA PODNOŠENJE ZAHTJEVA KAO GRUPNE TUŽBE I OGRANIČENJE VAŠEG PRAVA NA PODNOŠENJE TUŽBI PROTIV X-A VIŠE OD 1 GODINE NAKON ŠTO SU SE DOGODILI RELEVANTNI DOGAĐAJI, KOJI UTJEČU NA VAŠA PRAVA I OBVEZE AKO DOĐE DO BILO KAKVOG SPORA S X-OM. POJEDINOSTI O TIM ODREDBAMA POTRAŽITE U ODJELJKU 6 U OKVIRU OPĆIH UVJETA. Prihvaćanje . Upotrebom X-ovih usluga koje se plaćaju ili pristupanjem tim uslugama, izvršenjem plaćanja za te usluge i/ili klikom na gumb za jednokratnu kupnju odnosno ponavljajuća plaćanja pretplate za X-ove usluge koje se plaćaju izražavate svoj pristanak na uvjete. Ako ne razumijete uvjete ili ne prihvaćate bilo koji njihov dio, ne smijete koristiti nikakve usluge koje se plaćaju niti im pristupati. Za kupnju i korištenje usluga koje se plaćaju morate: (i) imati najmanje 18 godina ili biti punoljetni prema zakonima mjerodavnima za vaše prebivalište ili (ii) imati izričit pristanak roditelja ili skrbnika za kupnju i korištenje te usluge koja se plaća. Ako ste roditelj ili zakonski skrbnik i dopuštate svom djetetu (ili djetetu čiji ste skrbnik) kupnju ili korištenje usluge koja se plaća, prihvaćate ove uvjete te potvrđujete da ćete ih se pridržavati i da ste odgovorni za djetetovu aktivnost u okviru usluga koje se plaćaju te da ćete osigurati da se dijete također pridržava ovih uvjeta. U svakom slučaju, kao što je navedeno u članku Tko smije koristiti usluge u Uvjetima pružanja usluge za X, morate imati najmanje 13 godina da biste koristili uslugu X. Ako prihvaćate ove uvjete pružanja usluge kupcu X-ovih usluga i usluge koje se plaćaju koristite u ime tvrtke, organizacije, vlade ili drugog pravnog subjekta, izjavljujete i jamčite da ste za to ovlašteni i da imate ovlasti obvezati taj subjekt ovim uvjetima pružanja usluge kupcu X-ovih usluga te se u tom slučaju riječi „vi” i „vaš” u kontekstu njihove upotrebe u ovim uvjetima pružanja usluge kupcu X-ovih usluga odnose na taj subjekt. Ugovorni subjekt platforme X . Druga ugovorna strana u ovim Uvjetima pružanja usluge kupcu X-ovih usluga je subjekt nadležan za vaše prebivalište, kao što je navedeno u nastavku. Taj će vam subjekt pružati usluge koje se plaćaju. Nijedan drugi subjekt nema prema vama nikakve obveze prema ovim Uvjetima pružanja usluge kupcu. Vaša lokacija Europska unija, države EFTA-e ili Ujedinjena Kraljevina Ugovorni subjekt X Internet Unlimited Company, sa sjedištem na adresi One Cumberland Place, Fenian Street, Dublin 2, D02 AX07 Ireland Promjene odredbi, usluga koje se plaćaju i cijena 1. Promjene odredbi. X može povremeno revidirati ove Uvjete pružanja usluge kupcu X-ovih usluga na temelju valjane i razumne osnove. Valjana i razumna osnova može uključivati (i) promjenu naših usluga, na primjer zbog tehničkog, sigurnosnog ili operativnog događaja, (ii) otklanjanje tehničkih pogrešaka, (iii) promjenu našeg poslovanja, na primjer zbog promjena pravila, financijskih ili drugih smjernica, (iv) promjenu pravne situacije, na primjer zbog promjene zakona, zahtjeva službenog tijela ili odluke suda i (v) optimizaciju korisničkog iskustva kroz implementaciju novih značajki. Promjene neće biti retroaktivne, a vašu upotrebu usluga koje se plaćaju i sve pripadne transakcije regulirat će najnovija verzija uvjeta pružanja usluge kupcu X-ovih usluga, dostupna na adresi legal.x.com/purchaser-terms . Ako izmijenimo ili revidiramo ove Uvjete nakon što ste na njih pristali (na primjer, ako se ovi uvjeti izmijene nakon što ste kupili pretplatu), obvezujemo se obavijestiti vas do 30 dana (ovisno o konkretnim promjenama) prije stupanja na snagu materijalnih izmjena ovih uvjeta, istovremeno postavljajući razuman rok za korisnika u vezi s promjenama i obavještavajući vas o posljedicama daljnjeg korištenja nakon isteka roka. Takva se obavijest može dostaviti elektroničkim putem, uključujući (među ostalim) obavijest u okviru usluge ili e-poštu poslanu na adresu e-pošte povezanu s vašim računom. U slučaju da nastavite koristiti Plaćene usluge nakon isteka gore navedenog roka, slažete se da ćete biti vezani revidiranim X Uvjetima pružanja usluge kupca. Ako se ne slažete s promjenama Uvjeta pružanja usluge kupcu X-ovih usluga, morat ćete prestati upotrebljavati usluge koje se plaćaju ili im pristupati (ili ih nastaviti upotrebljavati ili im pristupati). Uvjeti pružanja usluge kupcu X-ovih usluga napisani su na engleskom, ali su dostupni njihovi prijevodi na više jezika. X nastoji da prijevodi budu što točniji i vjerniji izvornoj engleskoj verziji. Međutim, u slučaju bilo kakvih odstupanja ili nedosljednosti, prednost imaju uvjeti pružanja usluge kupcu X-ovih usluga na engleskom jeziku. Prihvaćate da engleski bude referentni jezik za tumačenje i konstruiranje uvjeta pružanja usluge kupcu X-ovih usluga. 2. Promjene plaćenih usluga. Naše plaćene usluge i naši proizvodi i usluge neprestano se razvijaju. X može promijeniti plaćene usluge na razumnoj i valjanoj osnovi. Takva valjana i razumna osnova može uključivati (i) tehnički, sigurnosni ili operativni razvoj, (ii) otklanjanje tehničkih pogrešaka, (iii) usklađenost s promijenjenom pravnom situacijom, primjerice zbog promjene zakona, zahtjeva službene agencije ili odluke suda, (iv) optimizaciju korisničkog iskustva kroz implementaciju novih značajki, i (v) promjena u našem poslovanju, na primjer zbog politike, financijskih okolnosti ili drugih promjena smjera. Obavijestit ćemo vas o svim promjenama plaćenih usluga do 30 dana prije nego što stupe na snagu, na primjer putem obavijesti o usluzi ili e-pošte poslane na adresu e-pošte povezanu s vašim računom, navodeći karakteristike i datum stupanja na snagu promjena te vas obavještavajući o vašem eventualnom pravu na raskid pretplate. Rok se može skratiti u slučaju promjena povezanih sa sigurnošću. Sljedeće se neće smatrati promjenama usluga koje se plaćaju u okviru ove odredbe: (i) promjene koje utječu na osnovnu prirodu usluga koje se plaćaju i bitne karakteristike usluge koju pruža X i (ii) trajni prekid pružanja usluga. X ne snosi odgovornost prema vama zbog bilo kakvih izmjena, obustavljanja ili ukidanja usluga koje se plaćaju. Kad je to zakonski propisano, prethodno navedeno ograničenje odgovornosti neće se primjenjivati na (i) naknadu predvidive štete u slučajevima donekle zanemarive povrede obveza, u mjeri u kojoj je njihovo ispunjenje nužno za pravilno izvršenje ugovora i korisnici se mogu osloniti na njihovo ispunjenje (bitne ugovorne obveze), od strane platforme X ili njezinih zakonskih zastupnika ili posrednika, i (ii) odgovornost platforme X za (a) štetu nastalu povredom života, tijela ili zdravlja, kao i za štetu prouzročenu namjernom ili grubom nepažnjom platforme X, njezinih zakonskih zastupnika ili posrednika te (b) štetu zbog nepoštivanja jamstva ili zajamčenih karakteristika ili kao rezultat prijevarno skrivenog nedostatka. Posebni uvjeti i odredbe (uključeni u nastavku) za određenu plaćenu uslugu određuju kako možete otkazati pretplatu ili, ako je primjenjivo, zatražiti povrat novca. 3. Promjene cijena. Cijene plaćenih usluga, uključujući ponavljajuće pretplatničke naknade, podložne su promjenama s vremena na vrijeme zbog promjene troškova koji se odnose na rad, održavanje, tehničku opskrbu, poslovna razmatranja i naknade koje naplaćuju treće strane ili zakonske naknade, prema našem razumnom nahođenju. U slučaju povećanja troškova, X zadržava pravo prilagodbe cijena usluga uz naplatu. X će vas obavijestiti o svim promjenama cijena u pisanom obliku do 30 dana prije nego što stupe na snagu, na primjer putem obavijesti o usluzi ili e-poštom na adresu e-pošte povezanu s vašim računom, navodeći svoja prava i posljedice njihovog neostvarivanja. U slučaju promjene cijene, možete raskinuti pretplatu na primjenjivu plaćenu uslugu ili korisnički ugovor do 24 sata prije početka sljedećeg ciklusa naplate, pod uvjetom da se otkazivanje izvrši u roku od 30 dana od primitka obavijesti. U suprotnom, promjena cijene stupit će na snagu u vrijeme navedeno u obavijesti. Za pretplatničke usluge promjene cijena stupit će na snagu na početku sljedećeg pretplatničkog razdoblja nakon datuma stupanja na snagu promjene cijene. Uvjeti plaćanja . X nudi razne opcije plaćanja, koje mogu varirati ovisno o usluzi koja se plaća, vašem uređaju i/ili operacijskom sustavu, vašoj geografskoj lokaciji ili drugim čimbenicima. U dostupnoj mjeri (budući da X može povremeno učiniti dostupnima različite načine kupnje) te opcije plaćanja mogu obuhvaćati mogućnost korištenja funkcije „plaćanja u aplikaciji” koju nude Google ili Apple, kao i plaćanja putem weba i treće strane koja djeluje u svojstvu X-ovog voditelja obrade plaćanja, servisa Stripe ( www.stripe.com; u nastavku teksta „ Stripe ”). Kada izvršite plaćanje, izričito pristajete: (i) platiti cijenu navedenu za tu uslugu koja se plaća, zajedno sa svim dodatnim iznosima primjenjivih poreza, naknada za upotrebu kreditnih kartica, bankovnih naknada, naknada za inozemne transakcije, mjenjačkih naknada i valutnih fluktuacija; i (ii) pridržavati se svih relevantnih uvjeta pružanja usluge, pravila o privatnosti ili drugih pravnih ugovora ili ograničenja (uključujući dodatna dobna ograničenja) koja propisuju Google, Apple ili Stripe (kao treće strane koje djeluju u svojstvu X-ovih voditelja obrade plaćanja) u vezi s vašim korištenjem određenog načina plaćanja (samo za potrebe primjera, ako odaberete plaćanje putem Appleove funkcije kupnje u aplikaciji, pristajete pridržavati se svih relevantnih uvjeta, zahtjeva i/ili ograničenja koje propisuje Apple). Svi privatni osobni podaci koje navedete u vezi s korištenjem usluga koje se plaćaju, uključujući, među ostalim, sve podatke navedene u vezi s plaćanjem, obrađivat će se u skladu s X-ovim pravilima o privatnosti. X može podijeliti vaše podatke za plaćanje s pružateljima usluga plaćanja radi obrade plaćanja, sprječavanja, otkrivanja i istraživanja prijevara ili drugih zabranjenih aktivnosti, olakšavanja rješavanja sporova poput storniranja ili povrata novca te u druge svrhe povezane s prihvaćanjem kreditnih i debitnih kartica ili ACH-a. Sami ste dužni pobrinuti se da vaši bankovni podaci, podaci o kreditnoj ili debitnoj kartici i/ili drugi podaci za plaćanje u svakom trenutku budu ažurni, potpuni i točni. Ako izvršite uplatu za uslugu koja se plaća, možda ćemo primiti informacije o vašoj transakciji, kao što su vrijeme izvršenja, datum isteka ili automatskog obnavljanja pretplate, platforma na kojoj ste izvršili kupnju i drugi podaci. X ne snosi odgovornost ni za kakve pogreške ili kašnjenja koje prouzroče voditelj plaćanja, Appleova trgovina App Store ili Google Play Store, vaša banka, tvrtka koja vam je izdala kreditnu karticu i/ili bilo koja platna mreža. Uvjete plaćanja koji se primjenjuju na određenu uslugu koja se plaća, uključujući način postupanja s obnovama pretplate i druge važne uvjete, potražite u nastavku u pripadnim uvjetima i odredbama za tu uslugu koja se plaća. Primjena i raskid ugovora s korisnikom X-a, nepostojanje mogućnosti povrata novca, veći broj računa za X i ograničenja 1. Vezani ste ugovorom s korisnikom X-a . UVIJEK MORATE POŠTIVATI UGOVOR S KORISNIKOM X-a I PRIDRŽAVATI GA SE. Ugovor s korisnikom X-a uvijek se primjenjuje na vašu upotrebu usluge X, uključujući usluge i značajke koje se plaćaju. Ako ne budete poštivali ugovor s korisnikom X-a ili ga se ne budete pridržavali, odnosno ako X bude smatrao da ga niste poštivali ili ga se pridržavali, to može dovesti do otkazivanja vaših usluga koje se plaćaju. Svako takvo otkazivanje nadovezivat će se, bez ograničenja, na sve radnje koje X može poduzeti protiv vas u skladu s ugovorom s korisnikom X-a. U takvim slučajevima možete izgubiti pogodnosti svojih usluga koje se plaćaju te nećete imati pravo na povrat bilo kojeg iznosa koji ste platili (ili unaprijed platili) za usluge koje se plaćaju. 2. Zbog čega X može ukinuti vaš pristup uslugama koje se plaćaju. X može obustaviti ili ukinuti vaš pristup uslugama koje se plaćaju ili prestati pružati vam sve usluge koje se plaćaju ili dio tih usluga ili poduzeti bilo koju drugu radnju koju smatra prikladnom, uključujući obustavu vašeg računa (bez ikakve odgovornosti) u bilo kojem trenutku i zbog bilo kojeg razloga ili bez razloga, uključujući, među ostalim, bilo koji od sljedećih razumnih temelja: a. X smatra, prema isključivo vlastitu nahođenju, da ste prekršili ove uvjete ili da bi vaša upotreba usluga koje se plaćaju prekršila neki zakon. b. Takvo postupanje od X-a traži ili mu ga nalaže neki nadležni sud, regulatorno tijelo ili agencija za provođenje zakona. c. X ima neočekivanih tehničkih ili sigurnosnih problema. d. X vjeruje, prema vlastitom razumnom nahođenju, da ste prekršili X korisnički ugovor; e. X vjeruje iz valjanih razloga, kao što je ako sudjelujete u manipulaciji, igranju ili drugom ometajućem ili zabranjenom ponašanju u vezi s plaćenim uslugama; f. Stvarate rizik ili moguću pravnu izloženost za X; g. Vaš se račun treba ukloniti zbog nezakonitog postupanja. h. Vaš se račun treba ukloniti zbog produljene neaktivnosti, ili i. Naše pružanje plaćenih usluga (u cijelosti ili djelomično) više nije komercijalno održivo (prema vlastitom nahođenju X-a). 3. Sve su transakcije konačne. Sva plaćanja usluga koje se plaćaju konačna su te ne omogućuju povrat novca ili zamjenu, osim u skladu s mjerodavnim pravom. Ne jamčimo prirodu, kvalitetu ni vrijednost usluge koja se plaća ili njezinu dostupnost ili ponudu. Ni za koju neiskorištenu ili djelomično iskorištenu uslugu koja se plaća (na primjer, za djelomično iskorišteno pretplatno razdoblje) ne nude se povrati novca ili krediti. 4. Usluge koje se plaćaju nisu prenosive između računa za X. Svaka kupnja usluge koja se plaća odnosi se samo na jedan račun za X, što znači da će se vaša kupnja odnositi isključivo na račun koji ste koristili kada ste kupili uslugu koja se plaća te se neće odnositi na druge račune kojima možda možete pristupati ili nad kojima imate kontrolu. Ako imate ili kontrolirate više računa i želite pristup uslugama koje se plaćaju putem svakog od računa, morate kupiti uslugu koja se plaća ponaosob za svaki račun. 5. Ograničenja i obveze. a. Uslugu koja se plaća možete kupiti i koristiti samo ako vam zakoni u vašoj državi to dopuštaju i ako živite u državi koju X podržava za pripadnu uslugu koja se plaća. X može, prema vlastitom nahođenju, u određenim državama ograničiti mogućnost pristupa ili kupnje usluge koja se plaća. X zadržava pravo povremene izmjene popisa podržanih država. b. Zadržavamo pravo odbijanja transakcija za usluge koje se plaćaju ili otkazivanja ili ukidanja prodaje ili korištenja usluga koje se plaćaju prema isključivo vlastitu nahođenju. c. Ne smijete dopustiti drugima da vaš račun za X koriste za pristupanje bilo kojoj usluzi koja se plaća, a koju ta osoba nije naručila. d. Ne smijete kupiti ili koristiti uslugu koja se plaća ako ste osoba s kojom osobama iz SAD-a nije dopušteno poslovati zbog ekonomskih sankcija, uključujući, među ostalim, sankcije koje provodi Ured za kontrolu strane imovine u okviru Ministarstva financija Sjedinjenih Država ili bilo koje drugo primjenjivo sankcijsko tijelo („ zabranjena osoba ”). To, među ostalim, uključuje osobe koje se nalaze u sljedećim državama i regijama ili ondje imaju prebivalište: Kuba, Iran, ukrajinske regije Krima, Sjeverna Koreja i Sirija. Izjavljujete i jamčite da niste zabranjena osoba. e. IZJAVLJUJETE DA ĆETE USLUGE KOJE SE PLAĆAJU KORISTITI SAMO U ZAKONITE SVRHE I SAMO U SKLADU S UVJETIMA. Porezi i naknade . Sami snosite odgovornost za sve primjenjive poreze, davanja, carine i naknade povezane s kupnjom usluga koje se plaćaju, uključujući one koje treba platiti X-u ili trećoj strani koja obrađuje plaćanja, i pristajete ih platiti. Ti porezi mogu, među ostalim, obuhvaćati PDV, GST, porez na promet, porez po odbitku i sve druge primjenjive poreze. Ovisno o vašoj lokaciji, X može biti zadužen za prikupljanje i prijavljivanje informacija povezanih s porezima na transakcije koji proizlaze iz vaše kupnje usluga koje se plaćaju. X-u dajete dopuštenje za davanje informacija o vašem računu i vaših osobnih podataka relevantnim poreznim tijelima radi ispunjavanja naših obaveza povezanih s prikupljanjem poreza i poreznim izvješćivanjem. Opći uvjeti 1. Podaci za kontakt. Ako imate pitanja o uslugama koje se plaćaju ili ovim uvjetima, dodatne pojedinosti možete potražiti u X-ovu centru za pomoć za usluge koje se plaćaju . Ako ste već kupili uslugu koja se plaća, možete nas kontaktirati i putem veze za podršku, koja je dostupna u navigacijskom izborniku vašeg računa za X pod postavkama plaćanja ili pretplate. Ako imate dodatnih pitanja, možete nam se obratiti ovdje putem obrasca „Pomoć za značajke koje se plaćaju”. 2. ODRICANJA OD ODGOVORNOSTI. U NAJVEĆOJ MJERI DOPUŠTENOJ MJERODAVNIM PRAVOM USLUGAMA KOJE SE PLAĆAJU PRISTUPATE I KORISTITE IH NA VLASTITU ODGOVORNOST. RAZUMIJETE I PRISTAJETE DA VAM SE USLUGE KOJE SE PLAĆAJU PRUŽAJU „KAKVE JESU” I „KAKO BUDU DOSTUPNE”. X SE ODRIČE SVIH JAMSTAVA I UVJETA, BILO IZRIČITIH ILI PODRAZUMIJEVANIH, POVEZANIH S PRIKLADNOSTI ZA PRODAJU, PRIMJERENOSTI ODREĐENOJ NAMJENI ILI NEPOSTOJANJEM KRŠENJA TUĐIH PRAVA. X NE DAJE NIKAKVO JAMSTVO NI IZJAVU TE SE ODRIČE BILO KAKVE ODGOVORNOSTI I OBAVEZE VEZANE UZ: (I) POTPUNOST, TOČNOST, DOSTUPNOST, PRAVOVREMENOST, SIGURNOST ILI POUZDANOST USLUGA KOJE SE PLAĆAJU I (II) UDOVOLJAVANJE USLUGA KOJE SE PLAĆAJU VAŠIM ZAHTJEVIMA ILI NJIHOVU DOSTUPNOST KOJA BI BILA NEPREKIDNA, SIGURNA I LIŠENA POGREŠAKA. SAMI STE ODGOVORNI ZA KORIŠTENJE USLUGE X, UKLJUČUJUĆI USLUGE KOJE SE PLAĆAJU, I SVEG SADRŽAJA KOJI IZRADITE. 3. OGRANIČENJE ODGOVORNOSTI. U NAJVEĆOJ MJERI DOPUŠTENOJ MJERODAVNIM PRAVOM SUBJEKTI PLATFORME X NE SNOSE ODGOVORNOST NI ZA KAKVU NEIZRAVNU, SLUČAJNU, POSEBNU, POSLJEDIČNU ILI KAZNENU ŠTETU I NI ZA KAKAV GUBITAK DOBITI ILI PRIHODA, BILO DA JE NASTAO IZRAVNO ILI NEIZRAVNO, TE NI ZA KAKAV GUBITAK PODATAKA, UPOTREBE, REPUTACIJE ILI DRUGI NEMATERIJALNI GUBITAK PROIZAŠAO IZ (i) VAŠEG PRISTUPANJA USLUGAMA KOJE SE PLAĆAJU ILI NJIHOVE UPOTREBE ODNOSNO NEMOGUĆNOSTI PRISTUPANJA USLUGAMA KOJE SE PLAĆAJU ILI NJIHOVE UPOTREBE (ii) BILO KAKVOG POSTUPANJA ILI SADRŽAJA BILO KOJE TREĆE STRANE OBJAVLJENOG PUTEM USLUGA KOJE SE PLAĆAJU, UKLJUČUJUĆI, MEĐU OSTALIM, BILO KAKVO KLEVETNIČKO, UVREDLJIVO ILI NEZAKONITO POSTUPANJE DRUGIH KORISNIKA ILI TREĆIH STRANA (iii) BILO KAKVOG SADRŽAJA DOBIVENOG PUTEM USLUGA KOJE SE PLAĆAJU ILI (iv) NEOVLAŠTENOG PRISTUPA, UPOTREBE ILI IZMJENE VAŠIH PRIJENOSA ILI SADRŽAJA. KAKO BI SE OTKLONILE MOGUĆE DVOJBE, DEFINICIJA USLUGA KOJE SE PLAĆAJU OGRANIČENA JE NA ZNAČAJKE KOJE NUDI X I NE OBUHVAĆA NIKAKAV SADRŽAJ KOJEM PRISTUPATE I/ILI S KOJIM STUPATE U INTERAKCIJU UPOTREBOM TIH ZNAČAJKI. NI U KOJEM SLUČAJU UKUPNA ODGOVORNOST SUBJEKATA PLATFORME X NEĆE PREMAŠITI STO EURA (100,00 EUR) ILI IZNOS KOJI STE TIJEKOM PRETHODNIH ŠEST MJESECI EVENTUALNO PLATILI X-u ZA USLUGE KOJE SE PLAĆAJU, A KOJE SU DOVELE DO NASTANKA ZAHTJEVA. OGRANIČENJA OVOG PODODJELJKA PRIMJENJUJU SE NA SVE TEORIJE ODGOVORNOSTI, BILO TEMELJENE NA JAMSTVU, UGOVORU, STATUTU, DELIKTU (UKLJUČUJUĆI NEMAR) ILI DRUGOME, TE BEZ OBZIRA NA TO JESU LI SUBJEKTI PLATFORME X BILI OBAVIJEŠTENI O MOGUĆNOSTI TAKVE ŠTETE, ČAK I AKO SE ZA OVDJE NAVEDENI PRAVNI LIJEK UTVRDI DA NIJE POSLUŽIO SVOJOJ SUŠTINSKOJ SVRSI. „SUBJEKTI PLATFORME X-OVI” OBUHVAĆAJU X, NJEGOVA MATIČNA DRUŠTVA, PODRUŽNICE, POVEZANA DRUŠTVA, DUŽNOSNIKE, DIREKTORE, ZAPOSLENIKE, AGENTE, PREDSTAVNIKE, PARTNERE I DAVATELJE LICENCI. MJERODAVNO PRAVO U VAŠOJ JURISDIKCIJI MOŽDA NE DOPUŠTA ODREĐENA OGRANIČENJA ODGOVORNOSTI. U MJERI KOJU PROPISUJE MJERODAVNO PRAVO U VAŠOJ JURISDIKCIJI PRETHODNO NAVEDENO NE OGRANIČAVA ODGOVORNOST SUBJEKATA PLATFORME X ZA PRIJEVARU, LAŽNO PREDSTAVLJANJE, SMRT ILI TJELESNU OZLJEDU UZROKOVANU NAŠIM NEMAROM, TEŠKIM NEMAROM I/ILI NAMJERNIM POSTUPANJEM. U NAJVEĆOJ MJERI DOPUŠTENOJ PRIMJENJIVIM ZAKONOM, MAKSIMALNA UKUPNA ODGOVORNOST X ENTITETA ZA BILO KOJA NEISKLJUČIVA JAMSTVA OGRANIČENA JE NA STO EURA (100,00 €). 4. Obavijest povezana s tvrtkom Apple. U mjeri u kojoj ste kupili ili koristite usluge koje se plaćaju te im pristupate na iOS uređaju, nadalje prihvaćate i pristajete na uvjete ovog članka. Prihvaćate da uvjeti ugovarate isključivo s nama, a ne s Appleom, i da Apple ne snosi odgovornost za usluge koje | 2026-01-13T08:48:43 |
https://fr.react.dev/learn | Démarrage rapide – React React v 18.3.1 Recherche ⌘ Ctrl K Apprendre Référence Communauté Blog DÉMARRAGE Démarrage rapide Tutoriel : Tic-Tac-Toe Penser en React Installation Créer un nouveau projet React Ajouter React à un projet existant Configuration de l’éditeur Utiliser TypeScript Outils de développement React React Compiler - Cette fonctionnalité est disponible dans le dernier Canary APPRENDRE REACT Décrire l’UI Votre premier composant Importer et exporter des composants Écrire du balisage avec JSX JavaScript dans JSX grâce aux accolades Passer des props à un composant Affichage conditionnel Afficher des listes Garder les composants purs Votre UI vue comme un arbre Ajouter de l’interactivité Réagir aux événements L’état : la mémoire d’un composant Rendu et Commit L’état est un instantané Cumuler les mises à jour d’un même état Mettre à jour les objets d’un état Mettre à jour les tableaux d’un état Gérer l’état Réagir à la saisie avec un état Choisir la structure de l’état Partager l’état entre des composants Préserver et réinitialiser l’état Extraire la logique d’état dans un réducteur Transmettre des données en profondeur avec le contexte Mise à l’échelle en combinant réducteur et contexte Échappatoires Référencer des valeurs avec les refs Manipuler le DOM avec des refs Synchroniser grâce aux Effets Vous n’avez pas forcément besoin d’un Effet Cycle de vie des Effets réactifs Séparer les événements des Effets Alléger les dépendances des Effets Réutiliser de la logique grâce aux Hooks personnalisés Cette page est utile ? Apprendre React Démarrage rapide Bienvenue dans la documentation React ! Dans cette page, vous allez découvrir les 80% de concepts React que vous utiliserez sans doute au quotidien. Vous allez apprendre Comment créer et imbriquer des composants Comment ajouter du balisage et des styles Comment afficher des données Comment faire un rendu conditionnel et traiter des listes Comment réagir à des événements et mettre à jour l’affichage Comment partager des données entre composants Créer et imbriquer des composants Les applis React sont constituées de composants . Un composant, c’est un bout d’UI ( User Interface , donc interface utilisateur) avec son comportement et son apparence propres. Un composant peut être aussi petit qu’un bouton, ou aussi grand qu’une page entière. Les composants React sont des fonctions JavaScript qui renvoient du balisage : function MyButton ( ) { return ( < button > Je suis un bouton </ button > ) ; } À présent que vous avez déclaré MyButton , vous pouvez l’imbriquer dans un autre composant : export default function MyApp ( ) { return ( < div > < h1 > Bienvenue dans mon appli </ h1 > < MyButton /> </ div > ) ; } Remarquez que <MyButton /> commence par une majuscule. C’est comme ça que React sait qu’il s’agit d’un composant. Les noms de composants React doivent toujours démarrer par une majuscule, alors que les balises HTML doivent être en minuscules. Voyons ce que ça donne : App.js App.js Réinitialiser Fork function MyButton ( ) { return ( < button > Je suis un bouton </ button > ) ; } export default function MyApp ( ) { return ( < div > < h1 > Bienvenue dans mon appli </ h1 > < MyButton /> </ div > ) ; } Voir plus Les mots-clés export default indiquent le composant principal du fichier. Si vous n’êtes pas habitué·e à certains éléments syntaxiques de JavaScript, le MDN et javascript.info sont d’excellentes références. Écrire du balisage avec JSX La syntaxe de balisage que vous avez vue ci-avant s’appelle JSX . Elle n’est pas à proprement parler obligatoire, mais la plupart des projets React utilisent JSX par confort. Tous les outils que nous recommandons pour le développement en local prennent en charge JSX d’entrée de jeu. JSX est plus exigeant que HTML. Vous devez fermer les balises telles que <br /> . Par ailleurs, votre composant ne peut pas renvoyer plusieurs balises JSX. Il vous faudrait les enrober dans un parent commun, tel qu’un <div>...</div> ou un Fragment <>...</> vide : function AboutPage ( ) { return ( < > < h1 > À propos </ h1 > < p > Bien le bonjour. < br /> Comment ça va ? </ p > </ > ) ; } Si vous avez beaucoup de HTML à migrer vers du JSX, vous pouvez vous aider d’un convertisseur en ligne . Ajouter des styles Dans React, vous précisez une classe CSS avec className . Ça fonctionne exactement comme l’attribut class en HTML : < img className = "avatar" /> Ensuite vous écrivez vos règles CSS dans un fichier CSS distinct : /* Dans votre CSS */ .avatar { border-radius : 50 % ; } React n’impose aucune façon particulière de fournir des fichiers CSS. Le cas le plus simple consiste à utiliser une balise <link> dans votre HTML. Si vous utilisez un outil de build ou un framework, consultez sa documentation pour apprendre comment ajouter un fichier CSS à votre projet. Afficher des données JSX vous permet de mettre du balisage dans du JavaScript. Les accolades servent à « ressortir » dans JavaScript afin d’injecter une variable ou expression dans votre code et de l’afficher à l’utilisateur. Par exemple, ce code affichera user.name : return ( < h1 > { user . name } </ h1 > ) ; Vous pouvez aussi « ressortir dans JavaScript » au sein d’attributs JSX, mais vous devrez utiliser des accolades à la place des guillemets. Par exemple, className="avatar" passe la chaîne "avatar" comme classe CSS, mais src={user.imageUrl} lit d’abord la valeur de l’expression JavaScript user.imageUrl , et ensuite passe cette valeur à l’attribut src : return ( < img className = "avatar" src = { user . imageUrl } /> ) ; Vous pouvez utiliser des expressions plus complexes au sein des accolades JSX, par exemple de la concaténation de chaînes : App.js App.js Réinitialiser Fork const user = { name : 'Hedy Lamarr' , imageUrl : 'https://i.imgur.com/yXOvdOSs.jpg' , imageSize : 90 , } ; export default function Profile ( ) { return ( < > < h1 > { user . name } </ h1 > < img className = "avatar" src = { user . imageUrl } alt = { 'Photo de ' + user . name } style = { { width : user . imageSize , height : user . imageSize } } /> </ > ) ; } Voir plus Dans l’exemple ci-avant, style={{}} ne constitue pas une syntaxe spéciale : c’est un littéral objet {} au sein d’accolades JSX style={} . Vous pouvez utiliser l’attribut style lorsque vos styles dépendent de données dans votre code JavaScript. Affichage conditionnel Dans React, il n’y a pas de syntaxe spéciale pour écrire des conditions. Au lieu de ça, on utilise les mêmes techniques que pour écrire du code JavaScript normal. Par exemple, vous pouvez utiliser une instruction if pour choisir quel bout de JSX inclure : let content ; if ( isLoggedIn ) { content = < AdminPanel /> ; } else { content = < LoginForm /> ; } return ( < div > { content } </ div > ) ; Si vous préférez un style plus compact, vous pouvez utiliser l’ opérateur ternaire conditionnel ? . Contrairement à if , celui-ci marche aussi au sein-même de JSX : < div > { isLoggedIn ? ( < AdminPanel /> ) : ( < LoginForm /> ) } </ div > Si vous n’avez pas besoin de la branche else , vous pouvez utiliser l’ opérateur && logique , plus court : < div > { isLoggedIn && < AdminPanel /> } </ div > Toutes ces façons de faire fonctionnent aussi pour la définition conditionnelle d’attributs. Si certaines de ces syntaxes vous déroutent, vous pouvez toujours commencer par if...else . Afficher des listes Pour afficher des listes de composants vous utiliserez principalement la méthode map() des tableaux , et parfois des boucles for . Par exemple, disons que vous avez un tableau de produits : const products = [ { title : 'Chou' , id : 1 } , { title : 'Ail' , id : 2 } , { title : 'Pomme' , id : 3 } , ] ; Dans ce composant, on utilise la méthode map() pour transformer un tableau de produits en tableau d’éléments <li> : const listItems = products . map ( product => < li key = { product . id } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; Remarquez que <li> a un attribut key . Pour chaque élément d’une liste, vous devriez passer une chaîne de caractères ou un numéro qui l’identifie de façon unique au sein de cette liste. En général, cette clé vient de vos données, par exemple une clé primaire dans la base de données. React utilise ces clés pour comprendre la nature de vos changements : insertion, suppression ou réordonnancement des éléments. App.js App.js Réinitialiser Fork const products = [ { title : 'Chou' , isFruit : false , id : 1 } , { title : 'Ail' , isFruit : false , id : 2 } , { title : 'Pomme' , isFruit : true , id : 3 } , ] ; export default function ShoppingList ( ) { const listItems = products . map ( product => < li key = { product . id } style = { { color : product . isFruit ? 'magenta' : 'darkgreen' } } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; } Voir plus Réagir à des événements Vous pouvez réagir à des événements en utilisant des gestionnaires d’événements dans vos composants : function MyButton ( ) { function handleClick ( ) { alert ( 'Vous avez cliqué !' ) ; } return ( < button onClick = { handleClick } > Cliquez ici </ button > ) ; } Remarquez que onClick={handleClick} n’a pas de parenthèses à la fin ! Prenez garde de ne pas appeler la fonction de gestion d’événement : vous avez seulement besoin de la transmettre . React appellera votre gestionnaire d’événement lorsque l’utilisateur activera le bouton. Mettre à jour l’affichage Le plus souvent, vous voudrez que votre composant « se souvienne » de certaines informations et les affiche. Par exemple, peut-être souhaitez-vous compter le nombre de fois qu’un bouton a été cliqué. Pour cela, il vous faut équiper votre composant d’un état . Commencez par importer useState depuis React : import { useState } from 'react' ; Servez-vous-en pour déclarer une variable d’état dans votre composant : function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; // ... Un appel à useState vous renvoie deux choses : l’état courant ( count ), et une fonction pour le mettre à jour ( setCount ). Vous pouvez leur donner n’importe quels noms, mais la convention largement répandue consiste à écrire [something, setSomething] . La première fois que le bouton est affiché, count est à 0 car vous avez passé 0 à useState() . Lorsque vous souhaitez modifier l’état, appelez setCount() et passez-lui la nouvelle valeur. Cliquer sur ce bouton incrémentera le compteur : function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Cliqué { count } fois </ button > ) ; } React appellera à nouveau la fonction de votre composant. Cette fois, count vaudra 1 . La fois suivante, ce sera 2 . Et ainsi de suite. Si vous affichez le même composant plusieurs fois, chacun a son propre état. Cliquez les différents boutons séparément : App.js App.js Réinitialiser Fork import { useState } from 'react' ; export default function MyApp ( ) { return ( < div > < h1 > Des compteurs indépendants </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Cliqué { count } fois </ button > ) ; } Voir plus Voyez comme chaque bouton « se souvient » de son propre état count et n’affecte pas les autres boutons. Utiliser des Hooks Les fonctions dont le nom commence par use sont appelées Hooks . useState est un Hook fourni directement par React. Vous pouvez trouver les autres Hooks fournis dans la référence de l’API . Vous pouvez aussi créer vos propres Hooks en combinant ceux existants. Les Hooks sont plus contraignants que les autres fonctions. Vous pouvez seulement appeler les Hooks au début du code vos composants (ou d’autres Hooks). Si vous voulez utiliser useState dans une condition ou une boucle, extrayez un composant dédié au besoin et mettez le Hook à l’intérieur. Partager des données entre composants Dans l’exemple précédent, chaque MyButton avait son propre count indépendant, et lorsqu’un bouton était cliqué, seul le count de ce bouton changeait : Au départ, l’état count de chaque MyButton est à 0 Le premier MyButton met à jour son état count à 1 Toutefois, vous aurez régulièrement besoin que vos composants partagent des données et se mettent à jour de façon synchronisée . Afin que les deux composants MyButton affichent le même count et se mettent à jour ensemble, vous allez devoir déplacer l’état depuis les boutons individuels « vers le haut », vers le plus proche composant qui les contienne tous. Dans cet exemple, il s’agit de MyApp : Au départ, l’état count de MyApp vaut 0 , qui est transmis aux deux enfants Au clic, MyApp met à jour son état count à 1 , et le transmet aux deux enfants À présent quand vous cliquez l’un ou l’autre bouton, le count de MyApp change, ce qui altère les deux compteurs dans MyButton . Voici comment exprimer la même chose sous forme de code. Pour commencer, faites remonter l’état de MyButton vers MyApp : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Des compteurs indépendants </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { // ... on a bougé ce code à partir d’ici ... } Ensuite, transmettez l’état vers le bas de MyApp à chaque MyButton , ainsi que le gestionnaire partagé de clics. Vous pouvez passer ces informations à MyButton au moyen d’accolades JSX, comme nous le faisions précédemment pour des balises natives comme <img> : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Des compteurs synchronisés </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } Les informations ainsi transmises vers le bas s’appellent des props . Désormais, le composant MyApp contient l’état state et le gestionnaire d’événement handleClick , et passe ces deux informations comme props à chacun des boutons. Pour finir, modifiez MyButton pour lire les props que le composant parent lui a passées : function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Cliqué { count } fois </ button > ) ; } Lorsque vous cliquez un bouton, le gestionnaire onClick est déclenché. La prop onClick de chaque bouton utilise la fonction handleClick issue de MyApp , c’est donc ce code-là qui s’exécute. Le code appelle setCount(count + 1) , incrémentant la variable d’état count . La nouvelle valeur count est passée comme prop à chaque bouton, de sorte qu’ils affichent tous cette nouvelle valeur. C’est ce qu’on appelle « faire remonter l’état » (“lifting state up”, NdT) . En déplaçant l’état vers le haut, nos composants peuvent le partager. App.js App.js Réinitialiser Fork import { useState } from 'react' ; export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Des compteurs synchronisés </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Cliqué { count } fois </ button > ) ; } Voir plus Et maintenant ? Bravo, vous connaissez désormais les bases de l’écriture de code React ! Allez donc découvrir notre tutoriel pour mettre tout ça en pratique et construire votre première petite appli avec React. Suivant Tutoriel : Tic-Tac-Toe Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Apprendre React Démarrage rapide Installation Décrire l’UI Ajouter de l’interactivité Gérer l’état Échappatoires Référence de l’API API React API React DOM Communauté Code de conduite L’équipe Contributeurs aux docs Remerciements Plus Blog React Native Politique de confidentialité Mentions légales Dans cette page Survol Créer et imbriquer des composants Écrire du balisage avec JSX Ajouter des styles Afficher des données Affichage conditionnel Afficher des listes Réagir à des événements Mettre à jour l’affichage Utiliser des Hooks Partager des données entre composants Et maintenant ? | 2026-01-13T08:48:43 |
https://www.pocketgamer.com/idle-heroes/ | Idle Heroes | Pocket Gamer Our Network Arrow Down PocketGamer.com AppSpy.com 148Apps.com PocketGamer.fr PocketGamer.biz PCGamesInsider.biz The Sims News PocketGamer.fun BlockchainGamer.biz PG Connects BigIndiePitch.com MobileGamesAwards.com U.GG Icy Veins The Sims Resource Fantasy Football Scout GameKnot Addicting Games Arcade Cloud EV.IO Menu PocketGamer.com Facebook X YouTube RSS Search Search Idle Heroes Get Available on: iOS + Android Twitter Facebook Reddit Idle Heroes Articles RSS Top List Best free games to play on your iPhone, iPad or Android Phone in 2026 - Updated By Stephen Gregson-Wood How To Idle Heroes codes (January 2026) By Shaun Walton How To Idle Heroes tier list - Pick the best characters [January 2026] By Mihail Katsoris News Idle Heroes is celebrating Halloween with bucketloads of rewards for everyone By Tanish Botadkar News Idle Heroes to debut new hero, special event, mechanics and optimisation throughout the month By Iwan Morris Top List Best idle games on Android By Cristina Mesesan Right Arrow Game Finder Browse our archive for thousands of game reviews across all mobile and handheld formats How To Idle Heroes quiz answers By Cristina Mesesan | 2026-01-13T08:48:43 |
https://docs.suprsend.com/docs/react-native-ios-push-integration | iOS Push Setup - 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 Push Setup Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React Native iOS Push Setup OpenAI Open in ChatGPT Step-by-step guide to setup APNS iOSpush notifications in your react native app. OpenAI Open in ChatGPT Major Release (V 1.0.0) 🚧 Starting from iOS version v1.0.0, we have introduced explicit push notification permission and option to add images in your notification. Also, introduced background mode for improved tracking of notification delivery. If you are using an iOS version older than v1.0.0 and upgrading to the new version. Please ensure to use the latest integration steps, especially for below methods: Adding Background mode capability (point 3 of capabilities) Calling registerPush method Tracking delivery methods 1 Add capabilities in iOS application Inside Targets select signing and capabilities Click on +capabilities and select Push Notifications and Background Modes In Background Modes, select Remote Notifications option. We use background notifications to receive delivery reports when your app is in quit and background state. Refer doc to know more about background notification 2 Register for push notifications Call registerForPushNotifications method below the SuprSend SDK initialised code which will register the iOS device for push service. If you have AppDelegate.m file then make follow code changes given in AppDelegate.h and AppDelegate.m file. If you have AppDelegate.swift file then make follow code changes given in AppDelegate.swift file. AppDelegate.h AppDelegate.m AppDelegate.swift Copy Ask AI #import <UserNotifications/UserNotifications.h> // Add this @interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, UNUserNotificationCenterDelegate> // Add UNUserNotificationCenterDelegate in the already existing line 3 Asking User to send push notifications There are 2 ways in which your app can prompt the users to allow push notifications on their device: Explicit Authorization Explicit authorization allows you to display alerts, add a badge to the app icon, or play sounds whenever a notification is delivered. In this type of authorization, the request is made the first time user launches your app. If the user denies the request, you can’t send subsequent prompts to send the notification. Explicit authorization is our default authorization method as it automatically sets alert, sound and badge as soon as the user allows this request. Provisional Authorization (Supported in iOS 12.0 and above) Provisional notifications are sent quietly to the users —they don’t interrupt the user with a sound or banner. Also, they will not be shown when your app is in foreground. First time this type of notifications are sent, user is asked to “Keep” or “Turn off” the notifications. If they click on “Keep”, the further notifications continue to be sent Add below code in AppDelegate file for provisional authorization. AppDelegate.m AppDelegate.swift Copy Ask AI [SuprSend.shared configureWithConfiguration:configuration launchOptions:launchOptions]; // init code which is already added at time of initialisation UNAuthorizationOptions options = UNAuthorizationOptionAlert+UNAuthorizationOptionBadge+UNAuthorizationOptionSound; // Add this if (@available(iOS 12.0, *)) { options = options | UNAuthorizationOptionProvisional; } [SuprSend.shared registerForPushNotificationsWithOptions:options]; // Add this 4 Enable sending and tracking of push notifications To enable sending iOS APNS token to SuprSend backend, delivery and tracking of push notification delivery/clicks/dismiss events, add below 4 methods in AppDelegate file after last existing method. AppDelegate.m AppDelegate.swift Copy Ask AI - (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken { NSUInteger dataLength = deviceToken.length; if (dataLength == 0) { return; } const unsigned char *dataBuffer = (const unsigned char *)deviceToken.bytes; NSMutableString *hexString = [NSMutableString stringWithCapacity:(dataLength * 2)]; for (int i = 0; i < dataLength; ++i) { [hexString appendFormat:@"%02x", dataBuffer[i]]; } [SuprSend.shared setPushNotificationTokenWithToken:hexString]; } - (void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler{ if (@available(iOS 14.0, *)) { completionHandler(UNAuthorizationOptionSound | UNNotificationPresentationOptionBanner | UNAuthorizationOptionBadge); } else { completionHandler(UNAuthorizationOptionSound | UNAuthorizationOptionAlert | UNAuthorizationOptionBadge); } } - (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler API_AVAILABLE(ios(7.0)){ [SuprSend.shared application:application didReceiveRemoteNotification:userInfo]; completionHandler(UIBackgroundFetchResultNewData); } - (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(UNNotificationResponse *)response withCompletionHandler:(void(^)(void))completionHandler{ if ([response isSuprSendNotification]) { [SuprSend.shared userNotificationCenter:center didReceive:response]; } completionHandler(); } @end // before this line iOS Push notifications only work on real devices so while developing/testing use real device to test it instead of simulators 5 Adding support for Notification service For better notification status (delivered, seen) tracking this step is needed. In Xcode go to File > New > Target . Select Notification Service Extension from the template list. Then in Next popup give it any product name, select your team, select swift language and click finish. After clicking on “Finish”, a folder will be created with your given product name. Inside that there will be NotificationService.swift file like below. In your project podFile add following snippet at the end of existing code like shown in image. Replace <your notification service name> with name you given to notification service while creating it. After that Run pod install . podFile Copy Ask AI target '<your notification service name>' do pod 'SuprsendCore' pod 'SuprSendSdk' end Replace the content in NotificationService.swift file with below code. In this snippet on line 11, 12 replace values with your workspace key and workspace secret. NotificationService.swift Copy Ask AI import UserNotifications import UIKit class NotificationService : UNNotificationServiceExtension { var contentHandler: ((UNNotificationContent) -> Void ) ? var modifiedNotificationContent: UNMutableNotificationContent ? private func track ( request : UNNotificationRequest, withContentHandler contentHandler : @escaping (UNNotificationContent) -> Void ) { let suprSendConfiguration = SuprSendSDKConfiguration ( withKey : "your workspace key" , secret : "your workspace secret" ) SuprSend. shared . configureWith ( configuration : suprSendConfiguration , launchOptions : [ : ]) SuprSend. shared . didReceive (request, withContentHandler : contentHandler) } override func didReceive ( _ request : UNNotificationRequest, withContentHandler contentHandler : @escaping (UNNotificationContent) -> Void ) { self . contentHandler = contentHandler modifiedNotificationContent = (request. content . mutableCopy () as? UNMutableNotificationContent) track ( request : request, withContentHandler : contentHandler) if let modifiedNotificationContent = modifiedNotificationContent { // Modify the notification content here... // 1 guard let imageURLString = modifiedNotificationContent.userInfo[ "image_url" ] as? String else { contentHandler (modifiedNotificationContent) return } getMediaAttachment ( for : imageURLString) { [ weak self ] image in guard let self = self , let image = image, let fileURL = self . saveImageAttachment ( image : image, forIdentifier : "attachment.png" ) else { contentHandler (modifiedNotificationContent) return } let imageAttachment = try ? UNNotificationAttachment ( identifier : "image" , url : fileURL, options : nil ) if let imageAttachment = imageAttachment { modifiedNotificationContent. attachments = [imageAttachment] } contentHandler (modifiedNotificationContent) } } } override func serviceExtensionTimeWillExpire () { // Called just before the extension will be terminated by the system. // Use this as an opportunity to deliver your "best attempt" at modified content, otherwise the original push payload will be used. if let contentHandler = contentHandler, let bestAttemptContent = modifiedNotificationContent { contentHandler (bestAttemptContent) } } } extension NotificationService { private func saveImageAttachment ( image : UIImage, forIdentifier identifier : String ) -> URL ? { let tempDirectory = URL ( fileURLWithPath : NSTemporaryDirectory ()) let directoryPath = tempDirectory. appendingPathComponent ( ProcessInfo. processInfo . globallyUniqueString , isDirectory : true ) do { try FileManager. default . createDirectory ( at : directoryPath, withIntermediateDirectories : true , attributes : nil ) let fileURL = directoryPath. appendingPathComponent (identifier) guard let imageData = image. pngData () else { return nil } try imageData. write ( to : fileURL) return fileURL } catch { return nil } } private func getMediaAttachment ( for urlString : String , completion : @escaping (UIImage ? ) -> Void ) { // 1 guard let url = URL ( string : urlString) else { completion ( nil ) return } let task = URLSession. shared . dataTask ( with : url) { data, response, error in if error != nil { completion ( nil ) return } guard let data = data else { completion ( nil ) return } guard let image = UIImage ( data : data) else { completion ( nil ) return } completion (image) } task. resume () } } You are now all set to send push notifications. All you have to do is add iOS vendor configuration on SuprSend dashboard and your push notifications will be configured. Please refer vendor integration guide to integrate your apns push service Was this page helpful? Yes No Suggest edits Raise issue Previous Android Push (FCM) Step-by-Step guide to setup FCM Push notifications in react native Android app. Next ⌘ I x github linkedin youtube Powered by | 2026-01-13T08:48:43 |
https://docs.suprsend.com/docs/python-lists | Lists - 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 Python SDK Integrate Python SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Node.js SDK Java SDK Go SDK SuprSend Client SDK 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 Python SDK Lists Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Python SDK Lists OpenAI Open in ChatGPT Manage subscriber lists with Python SDK: create/update list, add/remove/replace users. OpenAI Open in ChatGPT The Lists SDK methods lets you create / manage list of subscribers. You can then send broadcast to all the users in the list or create a workflow that triggers when a new user enters / exits list. Create / Update list You can use supr_client.subscribers_list.create method to create a new list Request Response Copy Ask AI from suprsend import SubscriberListBroadcast,SuprsendAPIException,SuprsendValidationError from suprsend import Suprsend # Initialize SDK supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : data = supr_client.subscriber_lists.create({ "list_id" : "_list_id_" , #Unique identifier for the list "list_name" : "_list_name_" , #readable name of the list (optional) "list_description" : "_some sample description for the list_" }) print (data) except (SuprsendAPIException,SuprsendValidationError) as ex: print (ex) Guidelines on defining the list_id list_id is case-insensitive. Suprsend first converts list_id to lowercase before storing it or doing any sort of comparison on it. list_id can be of max 64 characters. It can contain characters [a-z0-9_-] that is alphanumeric characters, _(underscore) and -(hyphen). Get list data You can get the latest information of a list using supr_client.subscribers_list.get method. Request Response Copy Ask AI from suprsend import SubscriberListBroadcast, SuprsendAPIException, SuprsendValidationError from suprsend import Suprsend supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : data = supr_client.subscriber_lists.get( "_list_id_" ) print (data) except (SuprsendAPIException, SuprsendValidationError) as ex: print (ex) Get all lists To get the data of all the lists created in your workspace, use supr_client.subscribers_list.get_all() method Request Response Copy Ask AI from suprsend import SubscriberListBroadcast,SuprsendAPIException,SuprsendValidationError from suprsend import Suprsend # Initialize SDK supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : const data = supr_client.subscribers_list.get_all() ; print (data) except (SuprsendAPIException,SuprsendValidationError) as ex: print (ex) Add Subscribers to the list Use supr_client.subscribers_list.add() to add list subscribers. There is no limit to the number of subscribers that you can add to a list. Request Response Copy Ask AI from suprsend import SubscriberListBroadcast, SuprsendAPIException, SuprsendValidationError from suprsend import Suprsend # Initialize SDK supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : data = supr_client.subscriber_lists.add( "_list_id_" , [ "_distinct_id1_" , "_distinct_id2_" ]) print (data) except (SuprsendAPIException, SuprsendValidationError) as ex: print (ex) Remove Subscribers from the list You can remove subscribers from the list using supr_client.subscribers_list.remove() Request Response Copy Ask AI from suprsend import SubscriberListBroadcast, SuprsendAPIException, SuprsendValidationError from suprsend import Suprsend # Initialize SDK supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : data = supr_client.subscriber_lists.remove( "_list_id_" , [ "_distinct_id1_" , "_distinct_id2_" ]) print (data) except (SuprsendAPIException, SuprsendValidationError) as ex: print (ex) Delete list You can delete a list using the supr_client.subscribers_list.delete() method. Request Response Copy Ask AI from suprsend import SubscriberListBroadcast, SuprsendAPIException, SuprsendValidationError from suprsend import Suprsend # Initialize SDK supr_client = Suprsend( "workspace_key" , "workspace_secret" ) try : data = supr_client.subscriber_lists.delete( "_list_id_" ) print (data) except (SuprsendAPIException, SuprsendValidationError) as ex: print (ex) Deleting a list is a permanent action and cannot be undone or restored. Replace users in list If you want to refresh a list completely with a new set of users, you can replace users by creating a draft version of the list and updating users in it. Use this method only if you want to completely overwrite the list members. 1 Start Sync to create a draft version of the list This method will create a draft version of the list where you can add the new set of users to replace existing users. Request Copy Ask AI data = supr_client.subscriber_lists.start_sync( "_list_id_" ) 2 Add Subscribers to the draft list You can use this method to add subscribers to the list’s draft version created in Step-1. You’ll get version_id in the start sync response. Request Copy Ask AI data = supr_client.subscriber_lists.add_to_version( "_list_id_" , "01HHCTXXXXXXXXXXX" , [ "_distinct_id1_" , "_distinct_id2_" ]) 3 Remove Subscribers from the draft list You can use this method to remove subscribers from the list’s draft version created in Step-1. You’ll get version_id in the start sync response. Request Copy Ask AI data = supr_client.subscriber_lists.remove_from_version( "_list_id_" , "01HHCTXXXXXXXXXXX" , [ "_distinct_id1_" , "_distinct_id2_" ]) 4 Finish Sync to make the draft version live Once your subscribers are updated in the list, use this method to finish sync and make the draft version updated in the above steps live. Request Copy Ask AI data = supr_client.subscriber_lists.finish_sync( "_list_id_" , "01HHCTXXXXXXXXXXX" ) Delete Draft list You can also delete the draft list if it was created by mistake. Request Copy Ask AI data = supr_client.subscriber_lists.delete_version( "_list_id_" , "01HHCTXXXXXXXXXXX" ) Was this page helpful? Yes No Suggest edits Raise issue Previous Broadcast Trigger broadcast notifications to a list of users with Python SDK. Next ⌘ I x github linkedin youtube Powered by On this page Create / Update list Get list data Get all lists Add Subscribers to the list Remove Subscribers from the list Delete list Replace users in list Delete Draft list | 2026-01-13T08:48:43 |
https://docs.python.org/es/3/ | 3.14.2 Documentation Tema Auto Claro Oscuro Descarga Descarga esta documentación Documentos por versión Python 3.15 (in development) Python 3.14 (stable) Python 3.13 (stable) Python 3.12 (security-fixes) Python 3.11 (security-fixes) Python 3.10 (security-fixes) Python 3.9 (EOL) Python 3.8 (EOL) Python 3.7 (EOL) Python 3.6 (EOL) Python 3.5 (EOL) Python 3.4 (EOL) Python 3.3 (EOL) Python 3.2 (EOL) Python 3.1 (EOL) Python 3.0 (EOL) Python 2.7 (EOL) Python 2.6 (EOL) Todas las versiones Otros recursos Índice PEP Guía para principiantes Listado de libros Charlas audios/videos Python Developer’s Guide Navegación índice módulos | Python » 3.14.2 Documentation » | Tema Auto Claro Oscuro | documentación de Python - 3.14.2 Welcome! This is the official documentation for Python 3.14.2. Documentation sections: ¿Qué hay de nuevo en Python 3.14? Or all "What's new" documents since Python 2.0 Tutorial Start here: a tour of Python's syntax and features Library reference Standard library and builtins Language reference Syntax and language elements Python setup and usage How to install, configure, and use Python Cómos ( HOWTOs ) de Python In-depth topic manuals Installing Python modules Third-party modules and PyPI.org Distributing Python modules Publishing modules for use by other people Extending and embedding For C/C++ programmers Python's C API C API reference Preguntas frecuentes Frequently asked questions (with answers!) Deprecations Deprecated functionality Indices, glossary, and search: Global module index All modules and libraries General index All functions, classes, and terms Glosario Terms explained Página de búsqueda Search this documentation Complete table of contents Lists all sections and subsections Project information: Reporting issues Contributing to docs Download the documentation History and license of Python Derechos de autor Acerca de la documentación Descarga Descarga esta documentación Documentos por versión Python 3.15 (in development) Python 3.14 (stable) Python 3.13 (stable) Python 3.12 (security-fixes) Python 3.11 (security-fixes) Python 3.10 (security-fixes) Python 3.9 (EOL) Python 3.8 (EOL) Python 3.7 (EOL) Python 3.6 (EOL) Python 3.5 (EOL) Python 3.4 (EOL) Python 3.3 (EOL) Python 3.2 (EOL) Python 3.1 (EOL) Python 3.0 (EOL) Python 2.7 (EOL) Python 2.6 (EOL) Todas las versiones Otros recursos Índice PEP Guía para principiantes Listado de libros Charlas audios/videos Python Developer’s Guide « Navegación índice módulos | Python » 3.14.2 Documentation » | Tema Auto Claro Oscuro | © Derechos de autor 2001 Python Software Foundation. Ésta página tiene la licencia Python Software Foundation Versión 2. Ejemplos, guías, y otro código en la documentación están bajo la licencia adicional Zero Clause BSD. Ver Historia y Licencia para más información. La Python Software Foundation es una corporación sin fines de lucro. Por favor dona. Última actualización en ene 13, 2026 (06:25 UTC). Encontraste un bug ? Creado usando Sphinx 8.2.3. | 2026-01-13T08:48:43 |
https://openapi.tools/categories/testing | Testing | 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 . Testing Quickly execute API requests and validate responses on the fly through command line or GUI interfaces. Testing 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:43 |
https://legal.x.com/zh-cn/purchaser-terms.html | X 买家服务条款 X 买家服务条款 下载 X 买家服务条款 付费服务条款 X Premium 附加条款 订阅服务附加条款 下载 X 买家服务条款 X 买家服务条款 goglobalwithtwitterbanner 付费服务条款 X Premium 附加条款 创作者订阅服务附加条款 Premium 商业版与 Premium 组织版附加条款 付费服务条款 X Premium 附加条款 创作者订阅服务附加条款 Premium 商业版与 Premium 组织版附加条款 X 买家服务条款 生效日期：2025 年 8 月 1 日 如果你居住在欧盟、欧洲自由贸易联盟成员国或英国之外， 包括如果你居住在美国，以下 X 买家服务条款 适用于你。 如果你居住在欧盟、欧洲自由贸易联盟成员国或英国， 这些 X 买家服务条款 适用于你。 X 买家服务条款 如果你居住在欧盟、欧洲自由贸易联盟成员国或英国之外，包括如果你居住在美国 X 允许你访问某些功能，以换取适用于相关功能的一次性或经常性费用（每一项都是“ 付费服务 ”，统称为“ 付费服务 ”）。例如，X Premium（定义如下）和订阅服务均被视为“付费服务”。 如果你注册和/或使用付费服务，你对付费服务的使用以及任何相应的交易均须遵守：(i) 此处规定的条款和条件，包括每项付费服务的适用条款和条件，每项如下所列（统称为“ X 买家服务 条款 ”），以及 (ii) 适用的 X 服务条款 、 X 隐私政策 、 X 规则和政策 以及其中包含的所有政策（统称为“ X 用户协议 ”）。本 X 买家服务条款和上述 X 用户协议在本文档中统称为“ 条款 ”。“ X ”是指向你提供付费服务的 X 实体。 请仔细阅读这些 X 买家服务条款，以确保你了解适用的条款、条件和例外情况。如果你居住在美国，这些条款包含适用于你的有关争议解决的重要信息，包括放弃你以集体诉讼方式提出索赔的权利，以及限制你在相关事件发生超过 2 年后向 X 提出索赔的权利，如果你与 X 发生任何争议，这会影响你的权利和义务。请参阅一般条款的 第 6 节 ，了解这些条款的详情。 接受 。 使用或访问 X 提供的付费服务、提交相关付款和/或点击按钮对 X 提供的付费服务进行一次性购买或定期订阅付款，即表示你同意接受本条款的约束。如果你不理解本条款或不接受本条款的任何部分，则不得使用或访问任何付费服务。要购买和使用付费服务，你必须：(i) 年满 18 周岁或达到你所在司法管辖区法律规定的成年年龄，或 (ii) 就购买和使用该付费服务获得你父母或监护人的明确同意。如果你是父母或法定监护人，并且允许你的孩子（或你作为监护人的孩子）购买或使用付费服务，则表示你同意本条款适用于你，你将遵守本条款，并对孩子在付费服务中的活动负责，确保孩子也遵守本条款。在任何情况下，正如 X 服务条款中“谁可以使用服务”部分所述，你必须至少年满 13 周岁方可使用 X 服务。如果你代表公司、组织、政府或其他法律实体接受本 X 买家服务条款并使用付费服务，则你声明并保证自己已获得授权，并有权让该实体受本 X 买家服务条款的约束，在此情况下，本 X 买家服务条款中使用的“你”应表示该实体。 X 缔约实体 。 你与以下所列的与你居住地点相对应的实体签订本 X 买家服务条款。该实体将向你提供付费服务。根据本买家服务条款，任何其他实体均不对你承担任何义务。 你的地点 北美大陆（包括夏威夷）或南美大陆 签约实体 X Corp，办事处地址为 865 FM 1209, Building 2, Bastrop, TX 78602, USA 你的地点 上述两个地点未涵盖的任何国家，包括亚太地区、中东、非洲或欧洲（不包括欧盟国家、欧洲自由贸易联盟成员国和英国） 签约实体 X Global LLC，注册办公地址为 701 S. Carson St.，Suite 200，Carson City，NV 89701，USA 条款、付费服务和定价的变更 1.条款的变更。 X 可能会不时修订本 X 买家服务条款，包括出于任何业务、财务或法律原因。这些更改不具有追溯力，最新版本的 X 买家服务条款（可在 legal.x.com/purchaser-terms 查看）将管理你对付费服务的使用和任何相应的交易。如果我们在你同意后修改或修订这些条款（例如，如果在你购买订阅后修改这些条款），我们将提前通知你这些条款的重大修订。此类通知可通过电子方式提供，包括（但不限于）通过服务通知或电子邮件发送至与你的账号相关的电子邮件地址。在这些修订生效后继续访问或使用付费服务，即表示你同意受修订后的 X 购买者服务条款的约束。如果你不同意遵守这些或任何未来的 X 购买者服务条款，请勿使用或访问（或继续使用或访问）付费服务。 X 买家服务条款以英语编写，但提供多种语言的翻译版本。X 力求让翻译尽可能与英文原版保持一致。但是，如果出现任何差异或不一致，应以 X 买家服务条款的英文版为准。你确认应将英语作为解释和构建 X 买家服务条款的参考语言。 2.付费服务变更。 我们的付费服务不断发展。因此，付费服务可能会不时更改，包括出于任何业务、财务或法律原因，由我们自行决定。我们可能会（永久或暂时）停止向你或用户提供付费服务或付费服务中的任何功能，无论是否另行通知。X 对你或任何第三方的付费服务的任何修改、暂停或终止不承担任何责任。特定付费服务的特定条款和条件（包括以下内容）规定了你如何取消订阅或在适用情况下要求退款。 3. 定价变更。 付费服务的价格（包括经常性订阅费）可能会不时更改，包括出于任何业务、财务或法律原因。X 将提前合理通知付费服务价格的任何重大变化。对于订阅服务，价格更改将在价格更改日期后的下一个订阅期开始时生效。如果你不同意价格变更，你有权在价格变更生效之前取消对适用付费服务的订阅，拒绝该变更。 付款条款 。 X 提供各种付款方式，可能因付费服务、你的设备和/或操作系统、你的地理位置或其他因素而异。在可用的范围内（因为 X 可能会不时提供各种购买方式），这些支付选项可能包括使用 Google 或 Apple 提供的“应用内支付”功能，或使用 X 的第三方支付平台 Stripe（ www.stripe.com ，以下简称“ Stripe ”）进行网络支付。当你付款时，你明确同意：(i) 支付付费服务的价格，以及与适用税费、信用卡费用、银行费用、外汇交易费用、外汇费用和货币波动相关的任何额外金额；以及 (ii) 遵守任何相关服务条款、隐私政策，或 Google, Apple, 或 Stripe（作为 X 的第三方支付平台）就你使用给定付款方式而施加的其他法律协议或限制（包括额外的年龄限制）（仅举例而言，如果你选择通过 Apple 的应用内购买功能付款，则你同意遵守 Apple 规定的任何相关条款、要求和/或限制）。你提供的与使用付费服务相关的任何个人隐私数据，包括但不限于与支付相关的任何数据，将根据 X 隐私政策进行处理。X 可能会与支付服务提供商共享你的支付信息，以处理付款；防止、发现和调查欺诈或其他被禁止的活动；促进争议解决，如退款或退款；以及用于与信用卡、借记卡和 ACH 的接受相关的其他目的。你有责任确保你的银行、信用卡、借记卡和/或其他付款信息始终是最新、完整和准确的。如果你为付费服务付款，我们可能会收到有关你的交易的信息，如付款时间、订阅设置为到期或自动续订的时间、你在哪个平台上进行购买以及其他信息。对于支付平台、Apple 的 App Store 或 Google Play Store、你的银行、信用卡公司和/或任何支付网络所犯的任何错误或延迟，X 概不负责。有关适用于特定付费服务的付款条款，包括如何处理订阅续订和其他重要条款，请参阅下面的每个特定付费服务条款和条件。 X 用户协议的适用、终止、不退款、多个 X 账号以及限制 1.X 用户协议适用于你 。你必须始终遵循并遵守 X 用户协议。X 用户协议始终适用于你对 X 服务（包括付费服务和功能）的使用。你未能遵守 X 用户协议，或者 X 认为你未能遵守 X 用户协议，可能会导致你的付费服务被取消。除此以外，X 还可能会根据 X 用户协议对你采取任何强制措施，而不仅限于取消服务。在这种情况下，你可能会失去付费服务的权益，并且没有资格获得为付费服务支付（或预付）的任何金额的退款。 2.为什么 X 可能会终止你对付费服务的访问？ X 可随时以任何理由或无理由暂停或终止你对付费服务的访问，停止向你提供全部或部分付费服务，或采取其认为适当的任何其他行动，例如冻结你的账号（不承担任何责任），包括但不限于以下任何原因： a. X 自行决定认为你违反了本条款或你对付费服务的使用违反了任何适用法律； b. X 被任何有管辖权的法院、监管机构或执法机构要求或指示这样做； c. X 遇到意外的技术或安全问题； d. X 自行决定认为你违反了 X 用户协议； e. X 自行决定认为你正在进行操纵或其他具有破坏性或被禁止的行为（通常情况下或与付费服务相关）； f. 你为 X 制造了风险或可能的法律风险; g. 你的账号因存在违法行为应被删除； h. 你的账号因长期闲置而应被删除；或者 i. 我们向你提供付费服务（全部或部分）不再具有商业可行性（由 X 自行决定）。 3.所有交易均为最终交易。 除适用法律要求外，所有付费服务的付款均为最终交易，不可退款或换货。我们对付费服务的性质、质量或价值或其可用性或供应不做任何保证。对于任何未使用或部分使用的付费服务（例如，已部分使用的订阅期），不提供退款或信用额度。 4.付费服务不可在 X 账号之间转让。 每次购买付费服务都适用于单个 X 账号，这意味着你的购买将仅适用于在购买付费服务时所使用的账号，而不适用于你可能有权访问或控制的其他账号。如果你拥有或控制多个账号，并且希望在每个账号上使用付费服务，则必须为每个账号单独购买付费服务。 5.限制和义务。 a. 只有你所在国家/地区的法律允许你使用付费服务，并且 X 在你所居住的国家/地区支持适用的付费服务，你才能购买和使用付费服务。X 可以自行决定在某些国家/地区限制对付费服务的访问或购买。X 保留随时修改支持的国家/地区列表的权利。 b. 我们保留自行决定拒绝付费服务交易、取消或中止付费服务销售或使用的权利。 c. 你不得允许他人使用你的 X 账号访问其并未订购的任何付费服务。 d. 如果你是受到经济制裁（包括但不限于美国财政部外国资产控制办公室或任何其他适用的制裁机构实施的制裁）而不允许与美国人进行交易的人员（“" 受禁制人士 "”），则你不得购买或使用付费服务。这包括但不限于位于以下国家和地区或通常居住在以下国家和地区的人员：古巴、伊朗、乌克兰克里米亚地区、朝鲜和叙利亚。你声明并保证自己并非受禁制人士。 e. 你声明自己只会出于合法目的且仅按照条款使用付费服务。 税费 。 你有责任并同意支付与购买付费服务相关的任何适用税款、关税和费用，包括需要支付给 X 或第三方支付处理机构的费用。这些税项可能包括但不限于增值税、消费税、销售税、预扣税和任何其他适用税项。根据你所在的地点，X 可能会负责收集并报告与你购买付费服务所产生的交易税相关的信息。你授权 X 向相关税务机关提供你的账号和个人信息，以履行我们的征税和报税义务。 一般条款 1.联系信息。 如果你对付费服务或这些条款有任何疑问，你可以查看 X 付费服务帮助中心 了解更多详细信息。如果你已经购买付费服务，则还可以在 X 账号的付款或订阅设置下通过导航菜单中的支持链接与我们联系。如果你还有其他疑问，则可通过使用 这里 的“付费功能帮助”表格与我们联系。 2.免责声明。 在适用法律允许的最大范围内，你需自行承担访问和使用付费服务的风险。你理解并同意，付费服务是在“原样”和“可用”的基础上提供给你的。X 对适销性、特定用途的适用性或非侵权性不提供任何明示或暗示的保证和条件。X 对以下方面不作任何保证或陈述，亦不承担任何责任和义务：(I) 付费服务的完整性、准确性、可用性、及时性、安全性或可靠性；(II) 付费服务是否能够满足你的要求，或者是否可以不间断、安全或无错误地提供。你对使用 X 服务（包括付费服务）以及你提供的任何内容负责。 3.责任限制。在适用法律允许的最大范围内，X 实体对由于以下原因导致的任何间接、附带、特殊、后果性或惩罚性损害或任何利润或收入损失（无论是直接还是间接发生）或任何数据、使用、商誉或其他无形损失概不承担责任：(i) 你访问或使用或无法访问或使用付费服务；(ii) 任何第三方通过付费服务发布的任何行为或内容，包括但不限于其他用户或第三方的任何诽谤性、攻击性或非法行为；(iii) 从付费服务中获得的任何内容；或 (iv) 未经授权访问、使用或更改你的传输或内容。为避免疑义，付费服务的定义仅限于 X 提供的功能，不包括你在使用这些功能时访问和/或与之交互的任何内容。在任何情况下，X 实体的总责任均不得超过一百美元 (U.S. $100.00)，或你在过去六个月内就引起索赔的付费服务向 X 支付的金额（如有），两者以较高者为准。本小节的限制适用于任何责任理论，无论是基于保证、合同、法规、侵权行为（包括疏忽）还是其他，也无论 X 实体是否已被告知任何此类损害的可能性，即使本文所述的补救措施被发现未能达到其基本目的。“X 实体”是指 X、其母公司、附属公司、相关公司、管理人员、董事、员工、代理、代表、合作伙伴和许可方。 你所在司法管辖区的适用法律可能不允许某些责任限制。在你所在司法管辖区适用法律要求的范围内，上述规定并不限制 X 实体对欺诈、欺诈性虚假陈述、因我们的疏忽、重大疏忽和/或故意行为而造成的死亡或人身伤害的责任。在适用法律允许的最大范围内，X 实体对任何非排他性保证的最大累计责任仅限于一百美元 (US$100.00)。 4. 关于 Apple 的通知。 如果你购买了付费服务或在 iOS 设备上使用或访问付费服务，你进一步承认并同意本节的条款。你确认这些条款仅适用于你和我们之间，而非与 Apple 之间，并且 Apple 不对付费服务及其内容负责。Apple 没有义务提供与付费服务相关的任何维护与支持服务。如果付费服务未能遵守任何适用的保证，则你可以通知 Apple，而 Apple 将按照付费服务的任何适用购买价格向你退款；并且，在适用法律允许的最大范围内，Apple 对于付费服务不承担任何其他保证义务。Apple 对于你或任何第三方提出的与付费服务或你拥有和/或使用付费服务有关的任何索赔概不承担责任，包括但不限于：(i) 产品责任索赔；(ii) 关于付费服务不符合任何适用法律或法规要求的任何索赔；以及 (iii) 根据消费者保护法或类似法律提出的索赔。对于任何第三方声称付费服务和/或你拥有和使用移动应用程序侵犯该第三方知识产权，Apple 不负责调查、辩护、和解和解除责任。你同意在使用付费服务时遵守任何适用的第三方条款。Apple 及其子公司是本条款的第三方受益人，一旦你接受本条款，Apple 将有权（并将被视为已接受该权利）作为本条款第三方受益人对你强制执行本条款。你特此声明并保证 (i) 你所在的国家/地区未受到美国政府的禁运，也未被美国政府指定为“支持恐怖主义”的国家/地区；(ii) 你未被列入美国政府的任何禁止或限制名单。 5.冲突。 如果本 X 买家服务条款的规定与 X 用户协议的规定发生冲突，则仅在你使用付费服务时以本 X 买家服务条款的规定为准。 6. 争议解决和集体诉讼豁免 a. 初始争议解决 。 你和 X 之间的大多数争议都可以通过非正式方式解决。你可以在 此处 致信付费支持团队与我们联系。当你联系我们时，请简要说明你所关注问题的性质和依据、你的联系信息以及你所寻求的具体救济。双方应通过此支持流程尽最大努力解决因本条款和/或你参与本计划而引起的或与之相关的纠纷、索赔或争议（单独称为“ 争议 ”，或多个称为“ 争议 ”）。你和我们同意，在任何一方就任何争议提起诉讼之前，必须按照上述规定真诚地参与此非正式流程，并且必须按照上述方式完成，但紧急禁令救济请求（“ 豁免争议 ”）除外。如果自根据上述“初步争议解决”条款开始非正式争议解决之日起的三十 (30) 日内，我们无法与你就争议解决（豁免争议除外）达成一致，则你或我们方均可提起诉讼。 b. 法律选择和法院管辖选择 。 请仔细阅读本节 — 它可能会对你的法律权利产生重大影响，包括你向法院提起诉讼的权利。 德克萨斯州的法律（不包括其法律条款的选择）将管辖这些条款以及你与我们之间产生的任何争议，尽管你与我们之间可能存在任何相反的协议。与这些条款相关的所有争议，包括由这些条款引起或与之相关的任何争议、索赔或争议，将仅提交至位于美国德克萨斯州塔兰特县的联邦或州法院，你同意这些法院的属人管辖权，并放弃对不便论坛的任何异议。在不影响上述规定的情况下，你同意，X 可以自行决定将我们对你提出的任何索赔、诉讼因由或争议提交到你居住的国家/地区对索赔具有管辖权和审判地的任何主管法院。 如果你以官方身份代表美国联邦、州或地方政府实体，且在法律上无法接受上述管辖法律、管辖权或地点条款，则这些条款不适用于你。对于此类美国联邦政府实体，本协议及与之相关的任何行动将受美利坚合众国法律管辖（不考虑法律冲突），并且，在没有联邦法律的情况下，在联邦法律允许的范围内，受德克萨斯州法律管辖（不包括法律选择）。 c. 你有两年的时间向 X 提出索赔。 你必须在引起争议的事件或事实发生之日起两（2）年内向 X 提出因本条款引起或与之相关的任何索赔，除非适用法律规定该索赔的正常诉讼时效不得通过协议缩短。如果未能在此期限内提出索赔，则你将永远放弃基于此类事件或事实提出任何种类或性质的索赔或诉因的权利，且此类索赔或诉因将被永久禁止，X 将不对此类索赔承担任何责任。 d. 集体诉讼豁免 。 在法律允许的范围内，你还放弃作为原告或集体成员参与任何所谓的集体诉讼、集体诉讼或代表诉讼程序的权利。 X 买家服务条款 如果你居住在欧盟、欧洲自由贸易联盟成员国或英国 X 允许你访问某些功能，以换取适用于相关功能的一次性或经常性费用（每一项都是“ 付费服务 ”，统称为“ 付费服务 ”）。例如，X Premium（定义如下）和订阅服务均被视为“付费服务”。 如果你注册和/或使用付费服务，你对付费服务的使用以及任何相应的交易均须遵守：(i) 此处规定的条款和条件，包括每项付费服务的适用条款和条件，每项如下所列（统称为“ X 买家服务 条款 ”），以及 (ii) 适用的 X 服务条款 、 X 隐私政策 、 X 规则和政策 以及其中包含的所有政策（统称为“ X 用户协议 ”）。本 X 买家服务条款和上述 X 用户协议在本文档中统称为“ 条款 ”。“ X ”是指向你提供付费服务的 X 实体。 请仔细阅读这些 X 买家服务条款，以确保你了解适用的条款、条件和例外情况。如果你居住在欧盟、欧洲自由贸易联盟国家或英国，这些条款包含适用于你的有关争议解决的重要信息，包括放弃你作为集体诉讼提出索赔的权利，以及限制你在相关事件发生后超过 1 年向 X 提出索赔的权利，如果与 X 发生任何争议，这会影响你的权利和义务。请参阅一般条款的 第 6 节 ，了解这些条款的详情。 接受 。 使用或访问 X 提供的付费服务、提交相关付款和/或点击按钮对 X 提供的付费服务进行一次性购买或定期订阅付款，即表示你同意接受本条款的约束。如果你不理解本条款或不接受本条款的任何部分，则不得使用或访问任何付费服务。要购买和使用付费服务，你必须：(i) 年满 18 周岁或达到你所在司法管辖区法律规定的成年年龄，或 (ii) 就购买和使用该付费服务获得你父母或监护人的明确同意。如果你是父母或法定监护人，并且允许你的孩子（或你作为监护人的孩子）购买或使用付费服务，则表示你同意本条款适用于你，你将遵守本条款，并对孩子在付费服务中的活动负责，确保孩子也遵守本条款。在任何情况下，正如 X 服务条款中“谁可以使用服务”部分所述，你必须至少年满 13 周岁方可使用 X 服务。如果你代表公司、组织、政府或其他法律实体接受本 X 买家服务条款并使用付费服务，则你声明并保证自己已获得授权，并有权让该实体受本 X 买家服务条款的约束，在此情况下，本 X 买家服务条款中使用的“你”应表示该实体。 X 缔约实体 。 你与以下所列的与你居住地点相对应的实体签订本 X 买家服务条款。该实体将向你提供付费服务。根据本买家服务条款，任何其他实体均不对你承担任何义务。 你的地点 欧盟、欧洲自由贸易联盟成员国或英国 签约实体 X Internet Unlimited Company，注册办公地址为 One Cumberland Place，Fenian Street，Dublin 2，D02 AX07 Ireland 条款、付费服务和定价的变更 1.条款的变更。 X 可能会出于有效且合理的依据不时修订本 X 买家服务条款。有效且合理的依据可能包括：（i）我们的服务发生变化，例如由于技术、安全相关或运营发展，（ii）消除技术错误，（iii）我们的业务发生变化，例如由于政策、财务或其他方向性变化，（iv）法律状况发生变化，例如由于法律变化，官方机构的要求或法院的裁决，以及（v）通过实施新功能来优化用户体验。这些更改不具有追溯力，最新版本的 X 买家服务条款（可在 legal.x.com/purchaser-terms 查看）将管理你对付费服务的使用和任何相应的交易。如果我们在你同意后修改或修订这些条款（例如，如果在你购买订阅后修改这些条款），我们承诺在这些条款的重大修订生效前提前最多 30 天（取决于具体变更）通知你，同时为用户设定关于变更的合理截止日期，并通知你在截止日期届满后继续使用的后果。此类通知可通过电子方式提供，包括（但不限于）通过服务通知或电子邮件发送至与你的账号相关的电子邮件地址。如果你在上述期限届满后继续使用付费服务，则你同意受修订后的 X 购买者服务条款的约束。如果你不同意对 X 买家服务条款的变更，你将必须停止使用或访问（或继续使用或访问）付费服务。 X 买家服务条款以英语编写，但提供多种语言的翻译版本。X 力求让翻译尽可能与英文原版保持一致。但是，如果出现任何差异或不一致，应以 X 买家服务条款的英文版为准。你确认应将英语作为解释和构建 X 买家服务条款的参考语言。 2.对付费服务的更改。 我们的付费服务以及我们的产品和服务不断发展。X 可能会出于合理且有效的依据变更付费服务。此类有效且合理的依据可能包括（i）技术、安全相关或运营发展，（ii）消除技术错误，（iii）遵守变化的法律情况，例如由于法律变化、官方机构的要求或法院的决定，（iv）通过实施新功能优化用户体验，以及（v）我们的业务发生变化，例如由于政策、财务状况或其他方向性变化。我们将在付费服务的任何变更生效前最多 30 天通知你，例如通过服务通知或发送至与你账号关联的电子邮件地址的电子邮件，说明变更的特点和生效日期，并告知你最终的订阅终止权利。如果发生与安全相关的变更，截止日期可能会缩短。以下内容不应被视为本条款所指的付费服务变更：(i) 影响付费服务的基本性质和 X 应提供服务的基本特征的变更，以及 (ii) 服务的永久终止。X 不对付费服务的任何修改、暂停或中止承担任何责任。在法律要求的范围内，上述责任限制不适用于：(i) 因 X 或其法定代表人或代理人轻微过失违反义务（其履行对合同的适当执行至关重要且用户可依赖其履行（基本合同义务））而造成的可预见损害的赔偿；以及 (ii) X 对以下方面的责任：(a) 因生命、身体或健康损害造成的损失，以及因 X 及其法定代表人或代理人的故意或重大过失造成的损失；(b) 因不遵守保证或担保特性或因欺诈性隐瞒缺陷造成的损失。特定付费服务的特定条款和条件（包括下面）指定了你如何取消订阅或寻求退款（如适用）。 3. 定价变更。 付费服务的价格（包括经常性订阅费）可能会因与运营、维护、技术供应、业务考虑相关的成本以及第三方收取的费用或法定费用的变化而不时发生变化，具体由我们合理酌情决定。如果成本增加，X 保留调整收费服务价格的权利。X 将在任何价格变更生效前最多 30 天以书面形式通知你，例如通过服务通知或发送至与你账号关联的电子邮件地址的电子邮件，说明你的权利以及不行使这些权利的后果。如果价格发生变化，你可以在下一个计费周期开始前 24 小时终止对适用付费服务或用户协议的订阅，前提是在收到通知后 30 天内取消。否则，价格变动将在通知中指定的时间生效。对于订阅服务，价格变动将在价格变动生效日期后的下一个订阅期开始时生效。 付款条款 。 X 提供各种付款方式，可能因付费服务、你的设备和/或操作系统、你的地理位置或其他因素而异。在可用的范围内（因为 X 可能会不时提供各种购买方式），这些支付选项可能包括使用 Google 或 Apple 提供的“应用内支付”功能，或使用 X 的第三方支付平台 Stripe（ www.stripe.com ，以下简称“ Stripe ”）进行网络支付。当你付款时，你明确同意：(i) 支付付费服务的价格，以及与适用税费、信用卡费用、银行费用、外汇交易费用、外汇费用和货币波动相关的任何额外金额；以及 (ii) 遵守任何相关服务条款、隐私政策，或 Google, Apple, 或 Stripe（作为 X 的第三方支付平台）就你使用给定付款方式而施加的其他法律协议或限制（包括额外的年龄限制）（仅举例而言，如果你选择通过 Apple 的应用内购买功能付款，则你同意遵守 Apple 规定的任何相关条款、要求和/或限制）。你提供的与使用付费服务相关的任何个人隐私数据，包括但不限于与支付相关的任何数据，将根据 X 隐私政策进行处理。X 可能会与支付服务提供商共享你的支付信息，以处理付款；防止、发现和调查欺诈或其他被禁止的活动；促进争议解决，如退款或退款；以及用于与信用卡、借记卡和 ACH 的接受相关的其他目的。你有责任确保你的银行、信用卡、借记卡和/或其他付款信息始终是最新、完整和准确的。如果你为付费服务付款，我们可能会收到有关你的交易的信息，如付款时间、订阅设置为到期或自动续订的时间、你在哪个平台上进行购买以及其他信息。对于支付平台、Apple 的 App Store 或 Google Play Store、你的银行、信用卡公司和/或任何支付网络所犯的任何错误或延迟，X 概不负责。有关适用于特定付费服务的付款条款，包括如何处理订阅续订和其他重要条款，请参阅下面的每个特定付费服务条款和条件。 X 用户协议的适用、终止、不退款、多个 X 账号以及限制 1.X 用户协议适用于你 。你必须始终遵循并遵守 X 用户协议。X 用户协议始终适用于你对 X 服务（包括付费服务和功能）的使用。你未能遵守 X 用户协议，或者 X 认为你未能遵守 X 用户协议，可能会导致你的付费服务被取消。除此以外，X 还可能会根据 X 用户协议对你采取任何强制措施，而不仅限于取消服务。在这种情况下，你可能会失去付费服务的权益，并且没有资格获得为付费服务支付（或预付）的任何金额的退款。 2.为什么 X 可能会终止你对付费服务的访问？ X 可随时以任何理由或无理由暂停或终止你对付费服务的访问，停止向你提供全部或部分付费服务，或采取其认为适当的任何其他行动，例如冻结你的账号（不承担任何责任），包括但不限于以下任何合理依据： a. X 自行决定认为你违反了本条款或你对付费服务的使用违反了任何适用法律； b. X 被任何有管辖权的法院、监管机构或执法机构要求或指示这样做； c. X 遇到意外的技术或安全问题； d.X 根据其唯一合理的判断认为你违反了 X 用户协议; e. X 有正当理由认为，例如你正在进行与付费服务相关的操纵、欺诈或其他具有破坏性或被禁止的行为； f. 你为 X 制造了风险或可能的法律风险; g. 你的账号因存在违法行为应被删除； h. 你的账号因长期闲置而应被删除；或者 i. 我们向你提供付费服务（全部或部分）不再具有商业可行性（由 X 自行决定）。 3.所有交易均为最终交易。 除适用法律要求外，所有付费服务的付款均为最终交易，不可退款或换货。我们对付费服务的性质、质量或价值或其可用性或供应不做任何保证。对于任何未使用或部分使用的付费服务（例如，已部分使用的订阅期），不提供退款或信用额度。 4.付费服务不可在 X 账号之间转让。 每次购买付费服务都适用于单个 X 账号，这意味着你的购买将仅适用于在购买付费服务时所使用的账号，而不适用于你可能有权访问或控制的其他账号。如果你拥有或控制多个账号，并且希望在每个账号上使用付费服务，则必须为每个账号单独购买付费服务。 5.限制和义务。 a. 只有你所在国家/地区的法律允许你使用付费服务，并且 X 在你所居住的国家/地区支持适用的付费服务，你才能购买和使用付费服务。X 可以自行决定在某些国家/地区限制对付费服务的访问或购买。X 保留随时修改支持的国家/地区列表的权利。 b. 我们保留自行决定拒绝付费服务交易、取消或中止付费服务销售或使用的权利。 c. 你不得允许他人使用你的 X 账号访问其并未订购的任何付费服务。 d. 如果你是受到经济制裁（包括但不限于美国财政部外国资产控制办公室或任何其他适用的制裁机构实施的制裁）而不允许与美国人进行交易的人员（“" 受禁制人士 "”），则你不得购买或使用付费服务。这包括但不限于位于以下国家和地区或通常居住在以下国家和地区的人员：古巴、伊朗、乌克兰克里米亚地区、朝鲜和叙利亚。你声明并保证自己并非受禁制人士。 e. 你声明自己只会出于合法目的且仅按照条款使用付费服务。 税费 。 你有责任并同意支付与购买付费服务相关的任何适用税款、关税和费用，包括需要支付给 X 或第三方支付处理机构的费用。这些税项可能包括但不限于增值税、消费税、销售税、预扣税和任何其他适用税项。根据你所在的地点，X 可能会负责收集并报告与你购买付费服务所产生的交易税相关的信息。你授权 X 向相关税务机关提供你的账号和个人信息，以履行我们的征税和报税义务。 一般条款 1.联系信息。 如果你对付费服务或这些条款有任何疑问，你可以查看 X 付费服务帮助中心 了解更多详细信息。如果你已经购买付费服务，则还可以在 X 账号的付款或订阅设置下通过导航菜单中的支持链接与我们联系。如果你还有其他疑问，则可通过使用 这里 的“付费功能帮助”表格与我们联系。 2.免责声明。 在适用法律允许的最大范围内，你需自行承担访问和使用付费服务的风险。你理解并同意，付费服务是在“原样”和“可用”的基础上提供给你的。X 对适销性、特定用途的适用性或非侵权性不提供任何明示或暗示的保证和条件。X 对以下方面不作任何保证或陈述，亦不承担任何责任和义务：(I) 付费服务的完整性、准确性、可用性、及时性、安全性或可靠性；(II) 付费服务是否能够满足你的要求，或者是否可以不间断、安全或无错误地提供。你对使用 X 服务（包括付费服务）以及你提供的任何内容负责。 3.责任限制。在适用法律允许的最大范围内，X 实体对由于以下原因导致的任何间接、附带、特殊、后果性或惩罚性损害或任何利润或收入损失（无论是直接还是间接发生）或任何数据、使用、商誉或其他无形损失概不承担责任：(i) 你访问或使用或无法访问或使用付费服务；(ii) 任何第三方通过付费服务发布的任何行为或内容，包括但不限于其他用户或第三方的任何诽谤性、攻击性或非法行为；(iii) 从付费服务中获得的任何内容；或 (iv) 未经授权访问、使用或更改你的传输或内容。为避免疑义，付费服务的定义仅限于 X 提供的功能，不包括你在使用这些功能时访问和/或与之交互的任何内容。在任何情况下，X 实体的总责任均不得超过一百欧元（€100.00）或你在过去六个月内为引起索赔的付费服务向 X 支付的金额（如有），以较高者为准。本小节的限制适用于任何责任理论，无论是基于保证、合同、法规、侵权行为（包括疏忽）还是其他，也无论 X 实体是否已被告知任何此类损害的可能性，即使本文所述的补救措施被发现未能达到其基本目的。“X 实体”是指 X、其母公司、附属公司、相关公司、管理人员、董事、员工、代理、代表、合作伙伴和许可方。 你所在司法管辖区的适用法律可能不允许某些责任限制。在你所在司法管辖区适用法律要求的范围内，上述规定并不限制 X 实体对欺诈、欺诈性虚假陈述、因我们的疏忽、重大疏忽和/或故意行为而造成的死亡或人身伤害的责任。在适用法律允许的最大范围内，X 实体对任何非排他性保证的最大总责任限于一百欧元（€100.00）。 4. 关于 Apple 的通知。 如果你购买了付费服务或在 iOS 设备上使用或访问付费服务，你进一步承认并同意本节的条款。你确认这些条款仅适用于你和我们之间，而非与 Apple 之间，并且 Apple 不对付费服务及其内容负责。Apple 没有义务提供与付费服务相关的任何维护与支持服务。如果付费服务未能遵守任何适用的保证，则你可以通知 Apple，而 Apple 将按照付费服务的任何适用购买价格向你退款；并且，在适用法律允许的最大范围内，Apple 对于付费服务不承担任何其他保证义务。Apple 对于你或任何第三方提出的与付费服务或你拥有和/或使用付费服务有关的任何索赔概不承担责任，包括但不限于：(i) 产品责任索赔；(ii) 关于付费服务不符合任何适用法律或法规要求的任何索赔；以及 (iii) 根据消费者保护法或类似法律提出的索赔。对于任何第三方声称付费服务和/或你拥有和使用移动应用程序侵犯该第三方知识产权，Apple 不负责调查、辩护、和解和解除责任。你同意在使用付费服务时遵守任何适用的第三方条款。Apple 及其子公司是本条款的第三方受益人，一旦你接受本条款，Apple 将有权（并将被视为已接受该权利）作为本条款第三方受益人对你强制执行本条款。你特此声明并保证 (i) 你所在的国家/地区未受到美国政府的禁运，也未被美国政府指定为“支持恐怖主义”的国家/地区；(ii) 你未被列入美国政府的任何禁止或限制名单。 5.冲突。 如果本 X 买家服务条款的规定与 X 用户协议的规定发生冲突，则仅在你使用付费服务时以本 X 买家服务条款的规定为准。 6. 争议解决和集体诉讼豁免 a. 初步争议解决 。 你和 X 之间的大多数争议都可以通过非正式途径来解决。你可以在 此处 致信付费支持团队与我们联系。当你联系我们时，请简要说明你所关注问题的性质和依据、你的联系信息以及你所寻求的具体救济。双方应通过此支持流程尽最大努力解决因本条款和/或你参与本计划而引起的或与之相关的纠纷、索赔或争议（单独称为“ 争议 ”，或多个称为“ 争议 ”）。你和我们均同意，需要诚心诚意地参与这一非正式程序，并且必须按照上述规定完成，然后任何一方才能就任何争议提起诉讼，但紧急禁令救济请求除外（“ 豁免争议 ”）。如果自根据上述“初步争议解决”条款开始非正式争议解决之日起的三十 (30) 日内，我们无法与你就争议解决（豁免争议除外）达成一致，则你或我们方均可提起诉讼。 b. 法律选择和法院管辖选择 。 请仔细阅读本节 — 它可能会对你的法律权利产生重大影响，包括你向法院提起诉讼的权利。 在法律允许的范围内，与这些条款或服务相关的所有争议，包括由这些条款引起或与之相关的任何争议、索赔或争端，将专门提交给爱尔兰有管辖权的法院，而不考虑法律条款冲突，并受爱尔兰法律管辖，尽管你与我们之间可能存在任何相反的协议。在不影响前述条款的前提下，你同意 X 可自行决定将我们对你提出的任何索赔、诉讼事由或争议提交至你所在国家/地区对该索赔具有管辖权和审判权的法院。 c. 你有一年的时间对 X 提出索赔 。 除非适用法律规定不得通过协议缩短索赔的正常诉讼时效，否则你必须在引起争议的事件或事实发生之日起一 (1) 年内向 X 提出因本条款引起或与之相关的任何索赔。如果未能在此期限内提出索赔，则你将永远放弃基于此类事件或事实提出任何种类或性质的索赔或诉因的权利，且此类索赔或诉因将被永久禁止，X 将不对此类索赔承担任何责任。 d. 集体诉讼豁免 。 在法律允许的范围内，你还放弃作为原告或集体成员参与任何所谓的集体诉讼、集体诉讼或代表诉讼程序的权利。 X Premium 条款和条件 通过参加 X 的定期订阅服务（“ X Premium ”），即表示你同意你的参与将受这些条款的约束，包括以下 X Premium 条款和条件（这些条款和条件可能会不时修订）： 1. X Premium 描述。 X Premium 是 X 的一项定期订阅服务，提供某些功能、特权和/或服务，如 本文 所述。你对 X Premium 的订阅将根据条款（包括这些 X Premium 条款和条件）自动续订，直至取消。 a. X Premium 层级 。 X Premium 订阅者可以从多个层级中进行选择。每个层级都有不同的功能和价格。每个层级都有包年和包月定价。某些功能可能要求账号通过认证，并在账号个人资料中公开显示对勾标记。你可在 帮助中心 找到有关层级的具体信息。 2. 注册和管理你的账号、付款流程和定价、自动续订。 a. 注册 。 你必须登录你的 X 账号才能注册 X Premium。当你注册 X Premium 时，你可以通过以下方式注册并付款：(i) Apple 应用内购买（如果你使用基于 iOS 的设备注册），(ii) Google 应用内购买（如果你使用 Android 设备注册），或 (iii) 使用 X 的第三方支付合作伙伴 Stripe（如果你使用网页浏览器在 www.x.com 注册）。 b. 管理你的账号 。 你用于注册和支付 X Premium 订阅的方法决定了你管理账号的方式。如果你使用 Apple 的应用内购买注册并支付了 X Premium，则可以使用 Apple App Store 管理订阅。如果你使用 Google 的应用内购买注册并支付了 X Premium，则可以使用 Google Play Store 管理订阅。如果你使用 X 的支付平台 Stripe 注册并支付了 X Premium，你可以在 Stripe 上管理订阅，登录 www.x.com 后，可以通过 X 网站在 X Premium 设置中访问该订阅。有关管理你的 X Premium 账号和订阅 X Premium 的更多信息，你可以查看 关于 X Premium 和 X Premium 帮助 页面，以及我们的帮助中心有关 付费服务支持 的信息。 c. 付款流程和定价 。 X Premium 订阅的价格由 X 设定。如果你购买 X Premium 订阅，则需要定期提前支付订阅费。当你订阅 X Premium 时，你明确同意你授权定期付款，并且付款将按照你选择的付款方式进行，直到你或 X 取消适用的 X Premium 订阅。你的付款信息将在每个订阅期开始时自动处理。手机续订处理时长可能最多需要 3 天。如果你的付款信息被拒绝，你必须为你的 X Premium 订阅提供新的付款信息，否则你的订阅将被取消。如果你提供了新的付款信息，并且你的付款账号已成功充值，则你的新 X Premium 订阅期将基于原始续订日期，而不是成功充值的日期。任何部分订阅期均不退款或退款，包括某些功能、福利和/或服务被修改或中断的情况。订阅计划是预付的，不可退还（除非法律要求），并在每个订阅期结束时自动续订，除非按照以下取消程序取消订阅。 d. 升级或降级 。 目前仅支持在 iOS、Android 和 Web 上进行升级和降级。 在 iOS 上，如果你升级到价格更高的层级，并且是从之前订阅的平台（即 iOS）切换层级，则之前订阅剩余时间的部分将按比例进行退款。如果你降级到其他层级，则订阅和相关功能将保留到当前计费周期结束，然后再切换为新的订阅层级。降级时，除非法律要求，否则你不会收到之前订阅的任何部分的退款。降级时，你将从当前账单周期结束时开始按照新层级的价格付费。 在网络上，如果你升级到价格更高的层级，则之前订阅的剩余时间将记入你的账号，而如果是从之前订阅的平台（即网络）转换层级，则剩余时间将自动用于未来的付款。你的新订阅将立即开始。如果你降级到另一个等级，则当前的订阅和相关功能将立即切换到新的订阅层级。除非法律要求，否则你不会收到之前订阅的任何部分的退款。你还将立即被收取新层级的费用。 在 Google Play 商店的安卓版本上，如果你从之前订阅的平台升级到更高价格的层级（即安卓平台），则一旦你支付了新的价格，订阅就会立即从新产品开始算起。剩余时间将按比例计算并记入你的账号。如果你降级到另一个层级，则订阅将立即从新产品开始，而下一个账单日期将根据前一个层级的剩余价值进行延迟，并将其用于抵扣价格更高的计划的费用。 3. 取消你的订阅。 你可以随时取消 X Premium 订阅。如果你使用 Apple 的应用内购买购买了 X Premium 订阅，则你只能通过 Apple App Store 取消订阅，登录 X iOS 应用，即可在 X Premium 设置中操作。如果你使用 Google 的应用内购买购买了 X Premium 订阅，则你只能通过 Google Play Store 取消订阅，登录 X Android 应用，即可在 X Premium 设置中操作。如果你是使用 X 的支付平台 Stripe 来购买的 X Premium 订阅，则你只能通过 Stripe 取消订阅，登录 www.x.com ，即可通过 X 网站中的订阅设置来访问 Stripe。无论你的订阅是如何购买的，除非你在订阅期结束前至少 24 小时取消，否则你的订阅将自动续订。如果你取消订阅，你的订阅将从你取消时起一直保持活动状态，直到当前订阅期结束。除非� | 2026-01-13T08:48:43 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#in-the-kitchen | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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:43 |
https://highlight.io/#features | highlight.io: The open source monitoring platform. Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up Your browser does not support the video tag. Your browser does not support the video tag. The open source, fullstack Monitoring Platform. Get started Live demo Request a Demo Call Session Replay Error Monitoring Logging Traces Dashboards Self-Hosting Explore Our Features Session Replay Error Monitoring Logging Traces Dashboards Self-Hosting Session Replay Session Replay Understand the real reason why bugs are happening in your web application. Learn More Console and Network Recording Comprehensive Session Search Powerful Privacy Controls Error Monitoring Error Monitoring Get notified of the exceptions across your app before they become problematic. Learn More Custom Error Grouping Customizable Alerting Rules Powered by Open Telemetry Logging Logging Search for and set alerts for logs being written throughout your stack. Learn More Customizable Log Alerts Widespread SDK Support Powered by Clickhouse Traces Traces Get performance insights on requests and transactions throughout your web application stack. Learn More Powerful Visualization Capabilities Distributed Tracing Support OpenTelemetry Support Dashboards & APM Dashboards & APM Visualize and analyze your observability data on a single pane. Learn More Customizable dashboards Performance visualizations User analytics Self-Hosting highlight.io Self-Hosting highlight.io Interested in self-hosting highlight? Spin up highlight.io in docker with just a few commands. Learn More git clone --recurse-submodules https://github.com/highlight/highlight; cd docker; ./run-hobby.sh; Our customers Highlight powers forward-thinking companies. More about our customers → Don't take our word. Read our customer review section → Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Web application monitoring for today's developer. A cohesive view of your entire stack. A natural pairing between your errors, session replay, logs and more. Understand the “what”, “why” and “how” of your full-stack web application. Get started for free Support for all the modern frameworks. We support all the fancy new frameworks and our platform is powered by open source, scalable technologies. View all frameworks Integrations with your favorite tools. Connect your favorite issue tracker, support tool, or even analytics software and we’ll give you a way to push and pull data in the right places. View all integrations Built with compliance and security. Whether its SOC 2, HIPAA, or ISO, highlight.io can work with your stack. Contact us at security@highlight.io for more information. Read our docs Master OpenTelemetry with our Free Comprehensive Course From fundamentals to advanced implementations, learn how OpenTelemetry can transform your engineering team's observability practices. Ideal for engineering leaders and developers building production-ready monitoring solutions. Start Learning Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:43 |
https://explore.transifex.com/python-doc/python-newest/ | Python localization | Transifex Search Public Projects Log In SIGN UP Explore / Python documentation translations / Python Python Project for translating the latest non-alpha version of Python documentation. This could be the latest beta, release candidate or stable. docs.python.org/3.14 Spread the word 64 Languages Chinese (China) 100 % Swedish 97 % Portuguese (Portugal) 90 % Russian 78 % Portuguese (Brazil) 66 % Japanese 49 % Ukrainian 48 % Spanish (Spain) 21 % Polish 12 % French 11 % Indonesian 10 % Persian 6 % Korean 5 % Chinese 3 % Chinese (Taiwan) 2 % Arabic 1 % Azerbaijani 1 % Hungarian 1 % Turkish 1 % Spanish 1 % German 1 % Czech 1 % Spanish (Argentina) 0 % English (United States) 0 % Kyrgyz 0 % Bengali (Bangladesh) 0 % Pashto 0 % Spanish (Colombia) 0 % Italian (Italy) 0 % Ukrainian (Ukraine) 0 % Albanian (Albania) 0 % Indonesian (Indonesia) 0 % Korean (Korea) 0 % Lao (Laos) 0 % Marathi (India) 0 % Sinhala (Sri Lanka) 0 % Spanish (Latin America) 0 % Central Atlas Tamazight 0 % Chinese (Mandarin) 0 % Arabic (Egypt) 0 % Chinese Simplified 0 % Chinese (Singapore) 0 % Arabic (Iraq) 0 % Bengali 0 % Bengali (India) 0 % Catalan 0 % Danish 0 % Greek 0 % English (United Kingdom) 0 % Estonian 0 % Finnish 0 % Hindi 0 % Georgian 0 % Lithuanian 0 % Malay 0 % Burmese 0 % Norwegian Bokmål 0 % Nepali 0 % Dutch 0 % Portuguese 0 % Romanian 0 % Urdu 0 % Vietnamese 0 % Chinese (Hong Kong) 0 % Source language English Date created September 15, 2025 Number of contributors 2.21K Total words to translate 1.63M Last activity 16 hours ago JOIN THIS PROJECT Got a localisation project? Do it with Transifex , free forever. Transifex Developer Hub Blog Community Status Contact | 2026-01-13T08:48:43 |
https://react.dev/learn | Quick Start – React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog GET STARTED Quick Start Tutorial: Tic-Tac-Toe Thinking in React Installation Creating a React App Build a React App from Scratch Add React to an Existing Project Setup Editor Setup Using TypeScript React Developer Tools React Compiler Introduction Installation Incremental Adoption Debugging and Troubleshooting LEARN REACT Describing the UI Your First Component Importing and Exporting Components Writing Markup with JSX JavaScript in JSX with Curly Braces Passing Props to a Component Conditional Rendering Rendering Lists Keeping Components Pure Your UI as a Tree Adding Interactivity Responding to Events State: A Component's Memory Render and Commit State as a Snapshot Queueing a Series of State Updates Updating Objects in State Updating Arrays in State Managing State Reacting to Input with State Choosing the State Structure Sharing State Between Components Preserving and Resetting State Extracting State Logic into a Reducer Passing Data Deeply with Context Scaling Up with Reducer and Context Escape Hatches Referencing Values with Refs Manipulating the DOM with Refs Synchronizing with Effects You Might Not Need an Effect Lifecycle of Reactive Effects Separating Events from Effects Removing Effect Dependencies Reusing Logic with Custom Hooks Is this page useful? Learn React Quick Start Welcome to the React documentation! This page will give you an introduction to 80% of the React concepts that you will use on a daily basis. You will learn How to create and nest components How to add markup and styles How to display data How to render conditions and lists How to respond to events and update the screen How to share data between components Creating and nesting components React apps are made out of components . A component is a piece of the UI (user interface) that has its own logic and appearance. A component can be as small as a button, or as large as an entire page. React components are JavaScript functions that return markup: function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } Now that you’ve declared MyButton , you can nest it into another component: export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Notice that <MyButton /> starts with a capital letter. That’s how you know it’s a React component. React component names must always start with a capital letter, while HTML tags must be lowercase. Have a look at the result: App.js App.js Reload Clear Fork function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Show more The export default keywords specify the main component in the file. If you’re not familiar with some piece of JavaScript syntax, MDN and javascript.info have great references. Writing markup with JSX The markup syntax you’ve seen above is called JSX . It is optional, but most React projects use JSX for its convenience. All of the tools we recommend for local development support JSX out of the box. JSX is stricter than HTML. You have to close tags like <br /> . Your component also can’t return multiple JSX tags. You have to wrap them into a shared parent, like a <div>...</div> or an empty <>...</> wrapper: function AboutPage ( ) { return ( < > < h1 > About </ h1 > < p > Hello there. < br /> How do you do? </ p > </ > ) ; } If you have a lot of HTML to port to JSX, you can use an online converter. Adding styles In React, you specify a CSS class with className . It works the same way as the HTML class attribute: < img className = "avatar" /> Then you write the CSS rules for it in a separate CSS file: /* In your CSS */ .avatar { border-radius : 50 % ; } React does not prescribe how you add CSS files. In the simplest case, you’ll add a <link> tag to your HTML. If you use a build tool or a framework, consult its documentation to learn how to add a CSS file to your project. Displaying data JSX lets you put markup into JavaScript. Curly braces let you “escape back” into JavaScript so that you can embed some variable from your code and display it to the user. For example, this will display user.name : return ( < h1 > { user . name } </ h1 > ) ; You can also “escape into JavaScript” from JSX attributes, but you have to use curly braces instead of quotes. For example, className="avatar" passes the "avatar" string as the CSS class, but src={user.imageUrl} reads the JavaScript user.imageUrl variable value, and then passes that value as the src attribute: return ( < img className = "avatar" src = { user . imageUrl } /> ) ; You can put more complex expressions inside the JSX curly braces too, for example, string concatenation : App.js App.js Reload Clear Fork const user = { name : 'Hedy Lamarr' , imageUrl : 'https://i.imgur.com/yXOvdOSs.jpg' , imageSize : 90 , } ; export default function Profile ( ) { return ( < > < h1 > { user . name } </ h1 > < img className = "avatar" src = { user . imageUrl } alt = { 'Photo of ' + user . name } style = { { width : user . imageSize , height : user . imageSize } } /> </ > ) ; } Show more In the above example, style={{}} is not a special syntax, but a regular {} object inside the style={ } JSX curly braces. You can use the style attribute when your styles depend on JavaScript variables. Conditional rendering In React, there is no special syntax for writing conditions. Instead, you’ll use the same techniques as you use when writing regular JavaScript code. For example, you can use an if statement to conditionally include JSX: let content ; if ( isLoggedIn ) { content = < AdminPanel /> ; } else { content = < LoginForm /> ; } return ( < div > { content } </ div > ) ; If you prefer more compact code, you can use the conditional ? operator. Unlike if , it works inside JSX: < div > { isLoggedIn ? ( < AdminPanel /> ) : ( < LoginForm /> ) } </ div > When you don’t need the else branch, you can also use a shorter logical && syntax : < div > { isLoggedIn && < AdminPanel /> } </ div > All of these approaches also work for conditionally specifying attributes. If you’re unfamiliar with some of this JavaScript syntax, you can start by always using if...else . Rendering lists You will rely on JavaScript features like for loop and the array map() function to render lists of components. For example, let’s say you have an array of products: const products = [ { title : 'Cabbage' , id : 1 } , { title : 'Garlic' , id : 2 } , { title : 'Apple' , id : 3 } , ] ; Inside your component, use the map() function to transform an array of products into an array of <li> items: const listItems = products . map ( product => < li key = { product . id } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; Notice how <li> has a key attribute. For each item in a list, you should pass a string or a number that uniquely identifies that item among its siblings. Usually, a key should be coming from your data, such as a database ID. React uses your keys to know what happened if you later insert, delete, or reorder the items. App.js App.js Reload Clear Fork const products = [ { title : 'Cabbage' , isFruit : false , id : 1 } , { title : 'Garlic' , isFruit : false , id : 2 } , { title : 'Apple' , isFruit : true , id : 3 } , ] ; export default function ShoppingList ( ) { const listItems = products . map ( product => < li key = { product . id } style = { { color : product . isFruit ? 'magenta' : 'darkgreen' } } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; } Show more Responding to events You can respond to events by declaring event handler functions inside your components: function MyButton ( ) { function handleClick ( ) { alert ( 'You clicked me!' ) ; } return ( < button onClick = { handleClick } > Click me </ button > ) ; } Notice how onClick={handleClick} has no parentheses at the end! Do not call the event handler function: you only need to pass it down . React will call your event handler when the user clicks the button. Updating the screen Often, you’ll want your component to “remember” some information and display it. For example, maybe you want to count the number of times a button is clicked. To do this, add state to your component. First, import useState from React: import { useState } from 'react' ; Now you can declare a state variable inside your component: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; // ... You’ll get two things from useState : the current state ( count ), and the function that lets you update it ( setCount ). You can give them any names, but the convention is to write [something, setSomething] . The first time the button is displayed, count will be 0 because you passed 0 to useState() . When you want to change state, call setCount() and pass the new value to it. Clicking this button will increment the counter: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } React will call your component function again. This time, count will be 1 . Then it will be 2 . And so on. If you render the same component multiple times, each will get its own state. Click each button separately: App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } Show more Notice how each button “remembers” its own count state and doesn’t affect other buttons. Using Hooks Functions starting with use are called Hooks . useState is a built-in Hook provided by React. You can find other built-in Hooks in the API reference. You can also write your own Hooks by combining the existing ones. Hooks are more restrictive than other functions. You can only call Hooks at the top of your components (or other Hooks). If you want to use useState in a condition or a loop, extract a new component and put it there. Sharing data between components In the previous example, each MyButton had its own independent count , and when each button was clicked, only the count for the button clicked changed: Initially, each MyButton ’s count state is 0 The first MyButton updates its count to 1 However, often you’ll need components to share data and always update together . To make both MyButton components display the same count and update together, you need to move the state from the individual buttons “upwards” to the closest component containing all of them. In this example, it is MyApp : Initially, MyApp ’s count state is 0 and is passed down to both children On click, MyApp updates its count state to 1 and passes it down to both children Now when you click either button, the count in MyApp will change, which will change both of the counts in MyButton . Here’s how you can express this in code. First, move the state up from MyButton into MyApp : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { // ... we're moving code from here ... } Then, pass the state down from MyApp to each MyButton , together with the shared click handler. You can pass information to MyButton using the JSX curly braces, just like you previously did with built-in tags like <img> : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } The information you pass down like this is called props . Now the MyApp component contains the count state and the handleClick event handler, and passes both of them down as props to each of the buttons. Finally, change MyButton to read the props you have passed from its parent component: function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } When you click the button, the onClick handler fires. Each button’s onClick prop was set to the handleClick function inside MyApp , so the code inside of it runs. That code calls setCount(count + 1) , incrementing the count state variable. The new count value is passed as a prop to each button, so they all show the new value. This is called “lifting state up”. By moving state up, you’ve shared it between components. App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } Show more Next Steps By now, you know the basics of how to write React code! Check out the Tutorial to put them into practice and build your first mini-app with React. Next Tutorial: Tic-Tac-Toe Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms On this page Overview Creating and nesting components Writing markup with JSX Adding styles Displaying data Conditional rendering Rendering lists Responding to events Updating the screen Using Hooks Sharing data between components Next Steps | 2026-01-13T08:48:43 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#ambiguous-terms | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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:43 |
https://support.google.com/accounts/answer/32050 | Clear cache & cookies - Computer - Google Account Help Skip to main content Google Account Help Sign in Google Help Help Center Community Google Account Privacy Policy Terms of Service Submit feedback Send feedback on... This help content & information General Help Center experience Next Help Center Community Improve your Google Account Google Account Troubleshoot issues with Google Accounts Clear cache & cookies Clear cache & cookies When you use a browser, like Chrome, it saves some information from websites in its cache and cookies. Clearing them fixes certain problems, like loading or formatting issues on sites. In Chrome On your computer, open Chrome. At the top right, click More Delete browsing data . Choose a time range, like Last hour or All time . Select the types of information you want to remove. Click Delete data . If you delete cookies while signed in to Chrome, Chrome refreshes the Google cookies that keep you signed in. This happens so that Chrome can continue to work as you expect. To delete Google cookies, sign out of Chrome first. Tips: To sign out of your Google Account on all websites, sign out of Chrome. In the address bar, to quickly reach the Delete browsing data dialog, type “Delete browsing data” and then, tap the Action chip . Learn Chrome Actions to quickly complete tasks . Learn how to change more cookie settings in Chrome . For example, you can delete cookies for a specific site. In other browsers If you use Safari, Firefox, or another browser, check its support site for instructions. What happens after you clear this info After you clear cache and cookies: Some settings on sites get deleted. For example, if you were signed in, you’ll need to sign in again. If you turn sync on in Chrome , you’ll stay signed into the Google Account you’re syncing to in order to delete your data across all your devices. Some sites can seem slower because content, like images, needs to load again. How cache & cookies work Cookies are files created by sites you visit. They make your online experience easier by saving browsing data. The cache remembers parts of pages, like images, to help them open faster during your next visit. Computer Android iPhone & iPad More Need more help? Try these next steps: Post to the help community Get answers from community members true Troubleshoot issues with Google Accounts 1 of 8 Turn cookies on or off 2 of 8 Clear cache & cookies 3 of 8 Check for an account that exists 4 of 8 Stay signed in or out of your Google Account 5 of 8 Common issues 6 of 8 Find your password-assistance email 7 of 8 How a conflicting account is created 8 of 8 About conflicting accounts Welcome to your Google Account! We see you have a new Google Account! Learn how to improve your experience with your Google Account checklist. ©2026 Google Privacy Policy Terms of Service Language català‎ dansk‎ Deutsch‎ eesti‎ español‎ español (Latinoamérica)‎ Filipino‎ français‎ Gaeilge‎ hrvatski‎ Indonesia‎ italiano‎ latviešu‎ lietuvių‎ magyar‎ Malti‎ Melayu‎ Nederlands‎ norsk‎ polski‎ português‎ português (Brasil)‎ română‎ slovenčina‎ slovenščina‎ suomi‎ svenska‎ Tiếng Việt‎ Türkçe‎ íslenska‎ č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); | 2026-01-13T08:48:43 |
https://docs.python.org/3/reference/simple_stmts.html#pass | 7. Simple statements — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 7. Simple statements 7.1. Expression statements 7.2. Assignment statements 7.2.1. Augmented assignment statements 7.2.2. Annotated assignment statements 7.3. The assert statement 7.4. The pass statement 7.5. The del statement 7.6. The return statement 7.7. The yield statement 7.8. The raise statement 7.9. The break statement 7.10. The continue statement 7.11. The import statement 7.11.1. Future statements 7.12. The global statement 7.13. The nonlocal statement 7.14. The type statement Previous topic 6. Expressions Next topic 8. Compound statements This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Language Reference » 7. Simple statements | Theme Auto Light Dark | 7. Simple statements ¶ A simple statement is comprised within a single logical line. Several simple statements may occur on a single line separated by semicolons. The syntax for simple statements is: simple_stmt : expression_stmt | assert_stmt | assignment_stmt | augmented_assignment_stmt | annotated_assignment_stmt | pass_stmt | del_stmt | return_stmt | yield_stmt | raise_stmt | break_stmt | continue_stmt | import_stmt | future_stmt | global_stmt | nonlocal_stmt | type_stmt 7.1. Expression statements ¶ Expression statements are used (mostly interactively) to compute and write a value, or (usually) to call a procedure (a function that returns no meaningful result; in Python, procedures return the value None ). Other uses of expression statements are allowed and occasionally useful. The syntax for an expression statement is: expression_stmt : starred_expression An expression statement evaluates the expression list (which may be a single expression). In interactive mode, if the value is not None , it is converted to a string using the built-in repr() function and the resulting string is written to standard output on a line by itself (except if the result is None , so that procedure calls do not cause any output.) 7.2. Assignment statements ¶ Assignment statements are used to (re)bind names to values and to modify attributes or items of mutable objects: assignment_stmt : ( target_list "=" )+ ( starred_expression | yield_expression ) target_list : target ( "," target )* [ "," ] target : identifier | "(" [ target_list ] ")" | "[" [ target_list ] "]" | attributeref | subscription | slicing | "*" target (See section Primaries for the syntax definitions for attributeref , subscription , and slicing .) An assignment statement evaluates the expression list (remember that this can be a single expression or a comma-separated list, the latter yielding a tuple) and assigns the single resulting object to each of the target lists, from left to right. Assignment is defined recursively depending on the form of the target (list). When a target is part of a mutable object (an attribute reference, subscription or slicing), the mutable object must ultimately perform the assignment and decide about its validity, and may raise an exception if the assignment is unacceptable. The rules observed by various types and the exceptions raised are given with the definition of the object types (see section The standard type hierarchy ). Assignment of an object to a target list, optionally enclosed in parentheses or square brackets, is recursively defined as follows. If the target list is a single target with no trailing comma, optionally in parentheses, the object is assigned to that target. Else: If the target list contains one target prefixed with an asterisk, called a “starred” target: The object must be an iterable with at least as many items as there are targets in the target list, minus one. The first items of the iterable are assigned, from left to right, to the targets before the starred target. The final items of the iterable are assigned to the targets after the starred target. A list of the remaining items in the iterable is then assigned to the starred target (the list can be empty). Else: The object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets. Assignment of an object to a single target is recursively defined as follows. If the target is an identifier (name): If the name does not occur in a global or nonlocal statement in the current code block: the name is bound to the object in the current local namespace. Otherwise: the name is bound to the object in the global namespace or the outer namespace determined by nonlocal , respectively. The name is rebound if it was already bound. This may cause the reference count for the object previously bound to the name to reach zero, causing the object to be deallocated and its destructor (if it has one) to be called. If the target is an attribute reference: The primary expression in the reference is evaluated. It should yield an object with assignable attributes; if this is not the case, TypeError is raised. That object is then asked to assign the assigned object to the given attribute; if it cannot perform the assignment, it raises an exception (usually but not necessarily AttributeError ). Note: If the object is a class instance and the attribute reference occurs on both sides of the assignment operator, the right-hand side expression, a.x can access either an instance attribute or (if no instance attribute exists) a class attribute. The left-hand side target a.x is always set as an instance attribute, creating it if necessary. Thus, the two occurrences of a.x do not necessarily refer to the same attribute: if the right-hand side expression refers to a class attribute, the left-hand side creates a new instance attribute as the target of the assignment: class Cls : x = 3 # class variable inst = Cls () inst . x = inst . x + 1 # writes inst.x as 4 leaving Cls.x as 3 This description does not necessarily apply to descriptor attributes, such as properties created with property() . If the target is a subscription: The primary expression in the reference is evaluated. It should yield either a mutable sequence object (such as a list) or a mapping object (such as a dictionary). Next, the subscript expression is evaluated. If the primary is a mutable sequence object (such as a list), the subscript must yield an integer. If it is negative, the sequence’s length is added to it. The resulting value must be a nonnegative integer less than the sequence’s length, and the sequence is asked to assign the assigned object to its item with that index. If the index is out of range, IndexError is raised (assignment to a subscripted sequence cannot add new items to a list). If the primary is a mapping object (such as a dictionary), the subscript must have a type compatible with the mapping’s key type, and the mapping is then asked to create a key/value pair which maps the subscript to the assigned object. This can either replace an existing key/value pair with the same key value, or insert a new key/value pair (if no key with the same value existed). For user-defined objects, the __setitem__() method is called with appropriate arguments. If the target is a slicing: The primary expression in the reference is evaluated. It should yield a mutable sequence object (such as a list). The assigned object should be a sequence object of the same type. Next, the lower and upper bound expressions are evaluated, insofar they are present; defaults are zero and the sequence’s length. The bounds should evaluate to integers. If either bound is negative, the sequence’s length is added to it. The resulting bounds are clipped to lie between zero and the sequence’s length, inclusive. Finally, the sequence object is asked to replace the slice with the items of the assigned sequence. The length of the slice may be different from the length of the assigned sequence, thus changing the length of the target sequence, if the target sequence allows it. CPython implementation detail: In the current implementation, the syntax for targets is taken to be the same as for expressions, and invalid syntax is rejected during the code generation phase, causing less detailed error messages. Although the definition of assignment implies that overlaps between the left-hand side and the right-hand side are ‘simultaneous’ (for example a, b = b, a swaps two variables), overlaps within the collection of assigned-to variables occur left-to-right, sometimes resulting in confusion. For instance, the following program prints [0, 2] : x = [ 0 , 1 ] i = 0 i , x [ i ] = 1 , 2 # i is updated, then x[i] is updated print ( x ) See also PEP 3132 - Extended Iterable Unpacking The specification for the *target feature. 7.2.1. Augmented assignment statements ¶ Augmented assignment is the combination, in a single statement, of a binary operation and an assignment statement: augmented_assignment_stmt : augtarget augop ( expression_list | yield_expression ) augtarget : identifier | attributeref | subscription | slicing augop : "+=" | "-=" | "*=" | "@=" | "/=" | "//=" | "%=" | "**=" | ">>=" | "<<=" | "&=" | "^=" | "|=" (See section Primaries for the syntax definitions of the last three symbols.) An augmented assignment evaluates the target (which, unlike normal assignment statements, cannot be an unpacking) and the expression list, performs the binary operation specific to the type of assignment on the two operands, and assigns the result to the original target. The target is only evaluated once. An augmented assignment statement like x += 1 can be rewritten as x = x + 1 to achieve a similar, but not exactly equal effect. In the augmented version, x is only evaluated once. Also, when possible, the actual operation is performed in-place , meaning that rather than creating a new object and assigning that to the target, the old object is modified instead. Unlike normal assignments, augmented assignments evaluate the left-hand side before evaluating the right-hand side. For example, a[i] += f(x) first looks-up a[i] , then it evaluates f(x) and performs the addition, and lastly, it writes the result back to a[i] . With the exception of assigning to tuples and multiple targets in a single statement, the assignment done by augmented assignment statements is handled the same way as normal assignments. Similarly, with the exception of the possible in-place behavior, the binary operation performed by augmented assignment is the same as the normal binary operations. For targets which are attribute references, the same caveat about class and instance attributes applies as for regular assignments. 7.2.2. Annotated assignment statements ¶ Annotation assignment is the combination, in a single statement, of a variable or attribute annotation and an optional assignment statement: annotated_assignment_stmt : augtarget ":" expression [ "=" ( starred_expression | yield_expression )] The difference from normal Assignment statements is that only a single target is allowed. The assignment target is considered “simple” if it consists of a single name that is not enclosed in parentheses. For simple assignment targets, if in class or module scope, the annotations are gathered in a lazily evaluated annotation scope . The annotations can be evaluated using the __annotations__ attribute of a class or module, or using the facilities in the annotationlib module. If the assignment target is not simple (an attribute, subscript node, or parenthesized name), the annotation is never evaluated. If a name is annotated in a function scope, then this name is local for that scope. Annotations are never evaluated and stored in function scopes. If the right hand side is present, an annotated assignment performs the actual assignment as if there was no annotation present. If the right hand side is not present for an expression target, then the interpreter evaluates the target except for the last __setitem__() or __setattr__() call. See also PEP 526 - Syntax for Variable Annotations The proposal that added syntax for annotating the types of variables (including class variables and instance variables), instead of expressing them through comments. PEP 484 - Type hints The proposal that added the typing module to provide a standard syntax for type annotations that can be used in static analysis tools and IDEs. Changed in version 3.8: Now annotated assignments allow the same expressions in the right hand side as regular assignments. Previously, some expressions (like un-parenthesized tuple expressions) caused a syntax error. Changed in version 3.14: Annotations are now lazily evaluated in a separate annotation scope . If the assignment target is not simple, annotations are never evaluated. 7.3. The assert statement ¶ Assert statements are a convenient way to insert debugging assertions into a program: assert_stmt : "assert" expression [ "," expression ] The simple form, assert expression , is equivalent to if __debug__ : if not expression : raise AssertionError The extended form, assert expression1, expression2 , is equivalent to if __debug__ : if not expression1 : raise AssertionError ( expression2 ) These equivalences assume that __debug__ and AssertionError refer to the built-in variables with those names. In the current implementation, the built-in variable __debug__ is True under normal circumstances, False when optimization is requested (command line option -O ). The current code generator emits no code for an assert statement when optimization is requested at compile time. Note that it is unnecessary to include the source code for the expression that failed in the error message; it will be displayed as part of the stack trace. Assignments to __debug__ are illegal. The value for the built-in variable is determined when the interpreter starts. 7.4. The pass statement ¶ pass_stmt : "pass" pass is a null operation — when it is executed, nothing happens. It is useful as a placeholder when a statement is required syntactically, but no code needs to be executed, for example: def f ( arg ): pass # a function that does nothing (yet) class C : pass # a class with no methods (yet) 7.5. The del statement ¶ del_stmt : "del" target_list Deletion is recursively defined very similar to the way assignment is defined. Rather than spelling it out in full details, here are some hints. Deletion of a target list recursively deletes each target, from left to right. Deletion of a name removes the binding of that name from the local or global namespace, depending on whether the name occurs in a global statement in the same code block. Trying to delete an unbound name raises a NameError exception. Deletion of attribute references, subscriptions and slicings is passed to the primary object involved; deletion of a slicing is in general equivalent to assignment of an empty slice of the right type (but even this is determined by the sliced object). Changed in version 3.2: Previously it was illegal to delete a name from the local namespace if it occurs as a free variable in a nested block. 7.6. The return statement ¶ return_stmt : "return" [ expression_list ] return may only occur syntactically nested in a function definition, not within a nested class definition. If an expression list is present, it is evaluated, else None is substituted. return leaves the current function call with the expression list (or None ) as return value. When return passes control out of a try statement with a finally clause, that finally clause is executed before really leaving the function. In a generator function, the return statement indicates that the generator is done and will cause StopIteration to be raised. The returned value (if any) is used as an argument to construct StopIteration and becomes the StopIteration.value attribute. In an asynchronous generator function, an empty return statement indicates that the asynchronous generator is done and will cause StopAsyncIteration to be raised. A non-empty return statement is a syntax error in an asynchronous generator function. 7.7. The yield statement ¶ yield_stmt : yield_expression A yield statement is semantically equivalent to a yield expression . The yield statement can be used to omit the parentheses that would otherwise be required in the equivalent yield expression statement. For example, the yield statements yield < expr > yield from < expr > are equivalent to the yield expression statements ( yield < expr > ) ( yield from < expr > ) Yield expressions and statements are only used when defining a generator function, and are only used in the body of the generator function. Using yield in a function definition is sufficient to cause that definition to create a generator function instead of a normal function. For full details of yield semantics, refer to the Yield expressions section. 7.8. The raise statement ¶ raise_stmt : "raise" [ expression [ "from" expression ]] If no expressions are present, raise re-raises the exception that is currently being handled, which is also known as the active exception . If there isn’t currently an active exception, a RuntimeError exception is raised indicating that this is an error. Otherwise, raise evaluates the first expression as the exception object. It must be either a subclass or an instance of BaseException . If it is a class, the exception instance will be obtained when needed by instantiating the class with no arguments. The type of the exception is the exception instance’s class, the value is the instance itself. A traceback object is normally created automatically when an exception is raised and attached to it as the __traceback__ attribute. You can create an exception and set your own traceback in one step using the with_traceback() exception method (which returns the same exception instance, with its traceback set to its argument), like so: raise Exception ( "foo occurred" ) . with_traceback ( tracebackobj ) The from clause is used for exception chaining: if given, the second expression must be another exception class or instance. If the second expression is an exception instance, it will be attached to the raised exception as the __cause__ attribute (which is writable). If the expression is an exception class, the class will be instantiated and the resulting exception instance will be attached to the raised exception as the __cause__ attribute. If the raised exception is not handled, both exceptions will be printed: >>> try : ... print ( 1 / 0 ) ... except Exception as exc : ... raise RuntimeError ( "Something bad happened" ) from exc ... Traceback (most recent call last): File "<stdin>" , line 2 , in <module> print ( 1 / 0 ) ~~^~~ ZeroDivisionError : division by zero The above exception was the direct cause of the following exception: Traceback (most recent call last): File "<stdin>" , line 4 , in <module> raise RuntimeError ( "Something bad happened" ) from exc RuntimeError : Something bad happened A similar mechanism works implicitly if a new exception is raised when an exception is already being handled. An exception may be handled when an except or finally clause, or a with statement, is used. The previous exception is then attached as the new exception’s __context__ attribute: >>> try : ... print ( 1 / 0 ) ... except : ... raise RuntimeError ( "Something bad happened" ) ... Traceback (most recent call last): File "<stdin>" , line 2 , in <module> print ( 1 / 0 ) ~~^~~ ZeroDivisionError : division by zero During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>" , line 4 , in <module> raise RuntimeError ( "Something bad happened" ) RuntimeError : Something bad happened Exception chaining can be explicitly suppressed by specifying None in the from clause: >>> try : ... print ( 1 / 0 ) ... except : ... raise RuntimeError ( "Something bad happened" ) from None ... Traceback (most recent call last): File "<stdin>" , line 4 , in <module> RuntimeError : Something bad happened Additional information on exceptions can be found in section Exceptions , and information about handling exceptions is in section The try statement . Changed in version 3.3: None is now permitted as Y in raise X from Y . Added the __suppress_context__ attribute to suppress automatic display of the exception context. Changed in version 3.11: If the traceback of the active exception is modified in an except clause, a subsequent raise statement re-raises the exception with the modified traceback. Previously, the exception was re-raised with the traceback it had when it was caught. 7.9. The break statement ¶ break_stmt : "break" break may only occur syntactically nested in a for or while loop, but not nested in a function or class definition within that loop. It terminates the nearest enclosing loop, skipping the optional else clause if the loop has one. If a for loop is terminated by break , the loop control target keeps its current value. When break passes control out of a try statement with a finally clause, that finally clause is executed before really leaving the loop. 7.10. The continue statement ¶ continue_stmt : "continue" continue may only occur syntactically nested in a for or while loop, but not nested in a function or class definition within that loop. It continues with the next cycle of the nearest enclosing loop. When continue passes control out of a try statement with a finally clause, that finally clause is executed before really starting the next loop cycle. 7.11. The import statement ¶ import_stmt : "import" module [ "as" identifier ] ( "," module [ "as" identifier ])* | "from" relative_module "import" identifier [ "as" identifier ] ( "," identifier [ "as" identifier ])* | "from" relative_module "import" "(" identifier [ "as" identifier ] ( "," identifier [ "as" identifier ])* [ "," ] ")" | "from" relative_module "import" "*" module : ( identifier "." )* identifier relative_module : "." * module | "." + The basic import statement (no from clause) is executed in two steps: find a module, loading and initializing it if necessary define a name or names in the local namespace for the scope where the import statement occurs. When the statement contains multiple clauses (separated by commas) the two steps are carried out separately for each clause, just as though the clauses had been separated out into individual import statements. The details of the first step, finding and loading modules, are described in greater detail in the section on the import system , which also describes the various types of packages and modules that can be imported, as well as all the hooks that can be used to customize the import system. Note that failures in this step may indicate either that the module could not be located, or that an error occurred while initializing the module, which includes execution of the module’s code. If the requested module is retrieved successfully, it will be made available in the local namespace in one of three ways: If the module name is followed by as , then the name following as is bound directly to the imported module. If no other name is specified, and the module being imported is a top level module, the module’s name is bound in the local namespace as a reference to the imported module If the module being imported is not a top level module, then the name of the top level package that contains the module is bound in the local namespace as a reference to the top level package. The imported module must be accessed using its full qualified name rather than directly The from form uses a slightly more complex process: find the module specified in the from clause, loading and initializing it if necessary; for each of the identifiers specified in the import clauses: check if the imported module has an attribute by that name if not, attempt to import a submodule with that name and then check the imported module again for that attribute if the attribute is not found, ImportError is raised. otherwise, a reference to that value is stored in the local namespace, using the name in the as clause if it is present, otherwise using the attribute name Examples: import foo # foo imported and bound locally import foo.bar.baz # foo, foo.bar, and foo.bar.baz imported, foo bound locally import foo.bar.baz as fbb # foo, foo.bar, and foo.bar.baz imported, foo.bar.baz bound as fbb from foo.bar import baz # foo, foo.bar, and foo.bar.baz imported, foo.bar.baz bound as baz from foo import attr # foo imported and foo.attr bound as attr If the list of identifiers is replaced by a star ( '*' ), all public names defined in the module are bound in the local namespace for the scope where the import statement occurs. The public names defined by a module are determined by checking the module’s namespace for a variable named __all__ ; if defined, it must be a sequence of strings which are names defined or imported by that module. The names given in __all__ are all considered public and are required to exist. If __all__ is not defined, the set of public names includes all names found in the module’s namespace which do not begin with an underscore character ( '_' ). __all__ should contain the entire public API. It is intended to avoid accidentally exporting items that are not part of the API (such as library modules which were imported and used within the module). The wild card form of import — from module import * — is only allowed at the module level. Attempting to use it in class or function definitions will raise a SyntaxError . When specifying what module to import you do not have to specify the absolute name of the module. When a module or package is contained within another package it is possible to make a relative import within the same top package without having to mention the package name. By using leading dots in the specified module or package after from you can specify how high to traverse up the current package hierarchy without specifying exact names. One leading dot means the current package where the module making the import exists. Two dots means up one package level. Three dots is up two levels, etc. So if you execute from . import mod from a module in the pkg package then you will end up importing pkg.mod . If you execute from ..subpkg2 import mod from within pkg.subpkg1 you will import pkg.subpkg2.mod . The specification for relative imports is contained in the Package Relative Imports section. importlib.import_module() is provided to support applications that determine dynamically the modules to be loaded. Raises an auditing event import with arguments module , filename , sys.path , sys.meta_path , sys.path_hooks . 7.11.1. Future statements ¶ A future statement is a directive to the compiler that a particular module should be compiled using syntax or semantics that will be available in a specified future release of Python where the feature becomes standard. The future statement is intended to ease migration to future versions of Python that introduce incompatible changes to the language. It allows use of the new features on a per-module basis before the release in which the feature becomes standard. future_stmt : "from" "__future__" "import" feature [ "as" identifier ] ( "," feature [ "as" identifier ])* | "from" "__future__" "import" "(" feature [ "as" identifier ] ( "," feature [ "as" identifier ])* [ "," ] ")" feature : identifier A future statement must appear near the top of the module. The only lines that can appear before a future statement are: the module docstring (if any), comments, blank lines, and other future statements. The only feature that requires using the future statement is annotations (see PEP 563 ). All historical features enabled by the future statement are still recognized by Python 3. The list includes absolute_import , division , generators , generator_stop , unicode_literals , print_function , nested_scopes and with_statement . They are all redundant because they are always enabled, and only kept for backwards compatibility. A future statement is recognized and treated specially at compile time: Changes to the semantics of core constructs are often implemented by generating different code. It may even be the case that a new feature introduces new incompatible syntax (such as a new reserved word), in which case the compiler may need to parse the module differently. Such decisions cannot be pushed off until runtime. For any given release, the compiler knows which feature names have been defined, and raises a compile-time error if a future statement contains a feature not known to it. The direct runtime semantics are the same as for any import statement: there is a standard module __future__ , described later, and it will be imported in the usual way at the time the future statement is executed. The interesting runtime semantics depend on the specific feature enabled by the future statement. Note that there is nothing special about the statement: import __future__ [ as name ] That is not a future statement; it’s an ordinary import statement with no special semantics or syntax restrictions. Code compiled by calls to the built-in functions exec() and compile() that occur in a module M containing a future statement will, by default, use the new syntax or semantics associated with the future statement. This can be controlled by optional arguments to compile() — see the documentation of that function for details. A future statement typed at an interactive interpreter prompt will take effect for the rest of the interpreter session. If an interpreter is started with the -i option, is passed a script name to execute, and the script includes a future statement, it will be in effect in the interactive session started after the script is executed. See also PEP 236 - Back to the __future__ The original proposal for the __future__ mechanism. 7.12. The global statement ¶ global_stmt : "global" identifier ( "," identifier )* The global statement causes the listed identifiers to be interpreted as globals. It would be impossible to assign to a global variable without global , although free variables may refer to globals without being declared global. The global statement applies to the entire current scope (module, function body or class definition). A SyntaxError is raised if a variable is used or assigned to prior to its global declaration in the scope. At the module level, all variables are global, so a global statement has no effect. However, variables must still not be used or assigned to prior to their global declaration. This requirement is relaxed in the interactive prompt ( REPL ). Programmer’s note: global is a directive to the parser. It applies only to code parsed at the same time as the global statement. In particular, a global statement contained in a string or code object supplied to the built-in exec() function does not affect the code block containing the function call, and code contained in such a string is unaffected by global statements in the code containing the function call. The same applies to the eval() and compile() functions. 7.13. The nonlocal statement ¶ nonlocal_stmt : "nonlocal" identifier ( "," identifier )* When the definition of a function or class is nested (enclosed) within the definitions of other functions, its nonlocal scopes are the local scopes of the enclosing functions. The nonlocal statement causes the listed identifiers to refer to names previously bound in nonlocal scopes. It allows encapsulated code to rebind such nonlocal identifiers. If a name is bound in more than one nonlocal scope, the nearest binding is used. If a name is not bound in any nonlocal scope, or if there is no nonlocal scope, a SyntaxError is raised. The nonlocal statement applies to the entire scope of a function or class body. A SyntaxError is raised if a variable is used or assigned to prior to its nonlocal declaration in the scope. See also PEP 3104 - Access to Names in Outer Scopes The specification for the nonlocal statement. Programmer’s note: nonlocal is a directive to the parser and applies only to code parsed along with it. See the note for the global statement. 7.14. The type statement ¶ type_stmt : 'type' identifier [ type_params ] "=" expression The type statement declares a type alias, which is an instance of typing.TypeAliasType . For example, the following statement creates a type alias: type Point = tuple [ float , float ] This code is roughly equivalent to: annotation - def VALUE_OF_Point (): return tuple [ float , float ] Point = typing . TypeAliasType ( "Point" , VALUE_OF_Point ()) annotation-def indicates an annotation scope , which behaves mostly like a function, but with several small differences. The value of the type alias is evaluated in the annotation scope. It is not evaluated when the type alias is created, but only when the value is accessed through the type alias’s __value__ attribute (see Lazy evaluation ). This allows the type alias to refer to names that are not yet defined. Type aliases may be made generic by adding a type parameter list after the name. See Generic type aliases for more. type is a soft keyword . Added in version 3.12. See also PEP 695 - Type Parameter Syntax Introduced the type statement and syntax for generic classes and functions. Table of Contents 7. Simple statements 7.1. Expression statements 7.2. Assignment statements 7.2.1. Augmented assignment statements 7.2.2. Annotated assignment statements 7.3. The assert statement 7.4. The pass statement 7.5. The del statement 7.6. The return statement 7.7. The yield statement 7.8. The raise statement 7.9. The break statement 7.10. The continue statement 7.11. The import statement 7.11.1. Future statements 7.12. The global statement 7.13. The nonlocal statement 7.14. The type statement Previous topic 6. Expressions Next topic 8. Compound statements This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Language Reference » 7. Simple statements | 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:43 |
https://forem.com/eriadura | SAMUEL ADENIJI - 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 Follow User actions SAMUEL ADENIJI I am a website developer and a game developer Location Nigeria Joined Joined on May 30, 2024 Email address samuel.adeniji2012@gmail.com github website Education Codingal online class Pronouns Mr Work website developer More info about @eriadura 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 4 Week Community Wellness Streak Keep contributing to discussions by posting at least 2 comments per week for 4 straight weeks. Unlock the 8 Week Badge next. Got it Close 2 Week Community Wellness Streak Keep the community conversation going! Post at least 2 comments for 2 straight weeks and unlock the 4 Week Badge. 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 Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close GitHub Repositories my-portfolio HTML • 1 star google-analysis pgai A suite of tools to develop RAG, semantic search, and other AI applications more easily with PostgreSQL Fork website HTML java-script js HTML form forem For empowering community 🌱 Fork file HTML • 1 star eriadura Config files for my GitHub profile. brief-on-javascript HTML MY-PROJECT This is my portfolio as a website desginer HTML • 1 star Json-and-JS-Asynchronous HTML • 1 star Html-Css-Java .github Fork -my-plugins A curated list of Budibase plugins 🔌 including data sources and components. Fork Skills/Languages My skill are html an Ai developer Currently learning I am currently learning java script and css Currently hacking on I am currently working on a app called "G graphics" Available for I am available for collaboration or discussion Post 10 posts published Comment 33 comments written Tag 74 tags followed Webinar for an avishaar SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 13 '24 Webinar for an avishaar # webdev # tutorial Comments Add Comment 1 min read Want to connect with SAMUEL ADENIJI? Create an account to connect with SAMUEL ADENIJI. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in This is another competition from avishkaar SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 4 '24 This is another competition from avishkaar Comments Add Comment 1 min read This is a robotic competition in india SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 2 '24 This is a robotic competition in india # webdev # programming # ai Comments Add Comment 1 min read This is a robotic competition in india SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 2 '24 This is a robotic competition in india # webdev # programming # ai Comments Add Comment 1 min read This is a robotic competition in india SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 2 '24 This is a robotic competition in india # webdev # programming # ai Comments Add Comment 1 min read This is a video cip of ict as a transformational tool 10:08 SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Oct 30 '24 This is a video cip of ict as a transformational tool Comments Add Comment 1 min read https://samueladeniji2012.wixsite.com/fasolin-blog SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Oct 27 '24 https://samueladeniji2012.wixsite.com/fasolin-blog # devchallenge # wixstudiochallenge # webdev # javascript Comments Add Comment 1 min read How To Add Chat Bot To Your Website SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Oct 27 '24 How To Add Chat Bot To Your Website # webdev # tutorial # ai # learning Comments Add Comment 1 min read how to create a binary treenode with python SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Sep 21 '24 how to create a binary treenode with python Comments Add Comment 1 min read My name is Adeniji Samuel I want to design an AI machine SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow May 30 '24 My name is Adeniji Samuel I want to design an AI machine # webdev # beginners # javascript # programming 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 — 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:43 |
https://highlight.io/compare/highlight-vs-heap | highlight.io: The open source monitoring platform. Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up Explore highlight.io The Open Source Heap alternative Session replay of your frontend, fullstack error monitoring, and powerful logging. Get started for free Live demo Highlight.io vs Heap A detailed comparison of Heap and Highlight.io General Unlimited Team Members Support Ticket Integrations Self-hosted Options Analytics Integrations Self-serve Setup Session Replay Session Commenting Session Sharing Privacy SDKs Embedded, fullstack error monitoring Canvas & WebGL Recording Shadow DOM Recording Error Monitoring Embedded Session Replay Error Sharing Support for Backend SDKs Agent-less architecture Logging Frontend logging Backend logging Embedded replay and stacktraces Agent-less architecture What makes us different? Highlight.io is open source and transparent Highlight.io is built with transparency at its core, with a permissive license . Not only do we work in the open, but we also expose what we're working on, on our roadmap . The fact that Highlight.io is open source also makes it easy to integrate and build your own tools on-top of it, an advantage closed-source products like Heap can't offer. Highlight.io constantly ships new features At Highlight.io, we ship quickly. We update our changelog with a recap of new features biweekly, and we share when these features are completed in our public roadmap . Plus, our community keeps pushing us to do more, so we're constantly adding new integrations . We work hard to keep Highlight.io ahead of the curve, and we're not afraid to show off our secret sauce. Full-stack Observability While Heap provides a comprehensive set of separate features for session replay, it does not support logging and has limited features for error monitoring. Highlight.io enables teams to monitor and optimize their entire tech stack, pairing server-side infrastructure with your frontend web applications. This makes Highlight.io a more comprehensive solution for developers who need to monitor their entire tech stack, in a simple, easy to implement solution. Master OpenTelemetry with our Free Comprehensive Course From fundamentals to advanced implementations, learn how OpenTelemetry can transform your engineering team's observability practices. Ideal for engineering leaders and developers building production-ready monitoring solutions. Start Learning Our customers Highlight powers forward-thinking companies. More about our customers → Don't take our word. Read our customer review section → Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:43 |
https://tr.react.dev/ | React React v 19.2 Search ⌘ Ctrl K Öğren Referans Topluluk Blog React Web ve yerel (native) kullanıcı arayüzü için kütüphane React'ı öğrenin API Tanımları Bileşenlerden kullanıcı arayüzleri oluşturun React, bileşen adı verilen birbirinden ayrı parçalardan kullanıcı arayüzü oluşturmanızı sağlar. Thumbnail , LikeButton ve Video gibi kendi React bileşenlerinizi oluşturabilirsiniz. Ardından bunları birleştirerek tam ekranlara, sayfalara ve uygulamalara çevirebilirsiniz. Video.js function Video ( { video } ) { return ( < div > < Thumbnail video = { video } /> < a href = { video . url } > < h3 > { video . title } </ h3 > < p > { video . description } </ p > </ a > < LikeButton video = { video } /> </ div > ) ; } My video Video description İster tek başınıza ister diğer binlerce geliştirici ile çalışın, React kullanmak aynı hissettirir. React diğer insanlar, gruplar veya organizasyonlar tarafından yazılmış bileşenleri sorunsuz bir şekilde birleştirebilmeniz için tasarlanmıştır. Kod ve işaretleme kullanarak bileşenler yazın React bileşenleri aslında JavaScript fonksiyonlarıdır. Bazı içerikleri koşullu olarak göstermek mi istiyorsunuz? Bir if ifadesi kullanın. Bir liste mi göstermek istiyorsunuz? Dizi map() fonksiyonunu deneyin. React öğrenmek programlamayı öğrenmektir. VideoList.js function VideoList ( { videos , emptyHeading } ) { const count = videos . length ; let heading = emptyHeading ; if ( count > 0 ) { const noun = count > 1 ? 'Videos' : 'Video' ; heading = count + ' ' + noun ; } return ( < section > < h2 > { heading } </ h2 > { videos . map ( video => < Video key = { video . id } video = { video } /> ) } </ section > ) ; } 3 Videos First video Video description Second video Video description Third video Video description Bu işaretleme sözdizimine JSX denir. React tarafından popüler hale getirilen bir JavaScript sözdizimi uzantısıdır. JSX işaretlemesini ilgili render etme mantığına yakın yerleştirmek, React bileşenlerini oluşturmayı, bakımını ve silmeyi kolaylaştırır. İhtiyacınız olan her yere interaktivite ekleyin React bileşenleri veri alır ve ekranda görüntülenecek olanı döndürür. Kullanıcı girişi gibi bir etkileşime yanıt olarak bileşenlere yeni veri yollayabilirsiniz. React daha sonra ekranı yeni veriyle eşleşecek şekilde günceller. SearchableVideoList.js import { useState } from 'react' ; function SearchableVideoList ( { videos } ) { const [ searchText , setSearchText ] = useState ( '' ) ; const foundVideos = filterVideos ( videos , searchText ) ; return ( < > < SearchInput value = { searchText } onChange = { newText => setSearchText ( newText ) } /> < VideoList videos = { foundVideos } emptyHeading = { `No matches for “ ${ searchText } ”` } /> </ > ) ; } example.com / videos.html React Videos A brief history of React Search 5 Videos React: The Documentary The origin story of React Rethinking Best Practices Pete Hunt (2013) Introducing React Native Tom Occhino (2015) Introducing React Hooks Sophie Alpert and Dan Abramov (2018) Introducing Server Components Dan Abramov and Lauren Tan (2020) Tüm sayfanızı React ile oluşturmak zorunda değilsiniz. Mevcut HTML sayfanıza React ekleyin ve interaktif React bileşenlerini herhangi bir yerde render edin. Sayfanıza React ekleyin Bir framework ile tam özellikli geliştirmeler yapın React bir kütüphanedir. Bileşenleri bir araya getirmenizi sağlar, ancak yönlendirme (routing) ve veri çekme (data fetching) işlemlerini nasıl yapmanız gerektiğini belirlemez. React ile tam bir uygulama oluşturmak için, tam yığın (full-stack) React framework’ü olarak Next.js veya React Router kullanmanızı öneririz. confs/[slug].js import { db } from './database.js' ; import { Suspense } from 'react' ; async function ConferencePage ( { slug } ) { const conf = await db . Confs . find ( { slug } ) ; return ( < ConferenceLayout conf = { conf } > < Suspense fallback = { < TalksLoading /> } > < Talks confId = { conf . id } /> </ Suspense > </ ConferenceLayout > ) ; } async function Talks ( { confId } ) { const talks = await db . Talks . findAll ( { confId } ) ; const videos = talks . map ( talk => talk . video ) ; return < SearchableVideoList videos = { videos } /> ; } example.com / confs/react-conf-2021 React Conf 2021 React Conf 2019 Search 19 Videos React Conf React 18 Keynote The React Team React Conf React 18 for App Developers Shruti Kapoor React Conf Streaming Server Rendering with Suspense Shaundai Person React Conf The First React Working Group Aakansha Doshi React Conf React Developer Tooling Brian Vaughn React Conf React without memo Xuan Huang (黄玄) React Conf React Docs Keynote Rachel Nabors React Conf Things I Learnt from the New React Docs Debbie O'Brien React Conf Learning in the Browser Sarah Rainsberger React Conf The ROI of Designing with React Linton Ye React Conf Interactive Playgrounds with React Delba de Oliveira React Conf Re-introducing Relay Robert Balicki React Conf React Native Desktop Eric Rozell and Steven Moyes React Conf On-device Machine Learning for React Native Roman Rädle React Conf React 18 for External Store Libraries Daishi Kato React Conf Building Accessible Components with React 18 Diego Haz React Conf Accessible Japanese Form Components with React Tafu Nakazaki React Conf UI Tools for Artists Lyle Troxell React Conf Hydrogen + React 18 Helen Lin React aynı zamanda bir mimaridir. Onu kullanan framework'leri, sunucuda çalışan asenkron bileşenlerde veya hatta derleme sırasında veri çekmenize olanak tanır. Bir dosyadan veya veritabanından veri okuyun ve bunu interaktif bileşenlerinize aktarın. Bir framework ile başlamayı öğren Her platformdan en iyisini kullanın İnsanlar web ve yerel (native) uygulamaları farklı nedenlerden dolayı seviyor. React, aynı becerileri kullanarak hem web uygulamaları hem de yerel (native) uygulamalar oluşturmanıza olanak tanır. Her platformun benzersiz güçlerine dayanarak, arayüzlerinizin her platformda doğru hissettirmesine izin verir. example.com Web'e sadık kalın İnsanlar web sayfalarının hızlı yüklenmesini bekliyorlar. Sunucuda, React, veri çekmeye devam ederken HTML akışını başlatmanıza olanak tanır ve JavaScript kodu yüklenmeden önce kalan içeriği aşamalı olarak doldurur. İstemcide, React, arayüzünüzü renderlama sırasında bile standart web API'lerini kullanarak bileşenlerin etkileşimli olmasını sağlar. 3:09 PM Gerçekten yerel (native) olun. İnsanlar yerel (native) uygulamaların kendi platformları gibi görünüp hisettirmelerini bekliyorlar. React Native ve Expo , React ile Android, iOS ve daha fazlası için uygulama oluşturmanıza olanak tanır. Arayüzleri yerel (native) gibi gözükür ve hissettirir, çünkü gerçekten öyleler. Bu bir web görünümü (webview) değil. React bileşenleriniz, platform tarafından sağlanan gerçek Android ve iOS viewlarını render eder. React ile web ve yerel (native) geliştirici olabilirsiniz. Takımınız, kullanıcı deneyimini feda etmeden birçok platforma uygulama yapabilir. Organizasyonunuz, platform farklılıklarını bağdaştırabilir ve baştan sona tüm özelliklere sahip olan takımlar oluşturabilir. Yerel (native) platformlar için oluşturun Gelecek hazır olduğunda yükseltin React değişikliklere dikkatle yaklaşır. Her React güncellemesi, milyarlarca kullanıcısı olan iş kritik yüzeylerde test edilir. Meta'daki 100.000'den fazla React bileşeni, her geçiş stratejisini doğrulamaya yardımcı olur. React ekibi her zaman React'i geliştirmek için araştırmalar yapıyor. Bazı araştırmaların sonucu yıllar sonra fayda sağlar. React'in araştırma fikirlerinin üretim ortamına taşınma olasılığı düşüktür. Sadece kanıtlanmış yaklaşımlar React'in bir parçası olur. Daha fazla React haberi okuyun Son React Haberleri Additional Vulnerabilities in RSC December 11, 2025 Vulnerability in React Server Components December 3, 2025 React Conf 2025 Recap October 16, 2025 React Compiler v1.0 October 7, 2025 Daha fazla React haberi okuyun Milyonlarca kişilik bir topluluğa katılın Yalnız değilsiniz. Dünya genelinden her ay iki milyondan fazla geliştirici React dokümantasyonunu ziyaret ediyor. React, insanların ve takımların hemfikir olabileceği bir şeydir. Bu yüzden React bir kütüphane, bir mimari veya hatta bir ekosistemden daha fazlasıdır. React, bir topluluktur. Yardım isteyebileceğiniz, fırsatlar bulabileceğiniz ve yeni arkadaşlar edinebileceğiniz bir yerdir. Burada hem geliştiricilerle hem de tasarımcılarla, acemilerle ve uzmanlarla, araştırmacılarla ve sanatçılarla, öğretmenlerle ve öğrencilerle tanışacaksınız. Arka planlarımız çok farklı olabilir, ancak React, hepimizin birlikte kullanıcı arayüzleri oluşturmasına olanak tanır. React topluluğuna hoş geldiniz Başlayın Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 React Öğrenin Quick Start Installation Kullanıcı Arayüzünü Tanımlama Etkileşim Ekleme State'i Yönetmek Kaçış Yolları API Referansı React APIs React DOM APIs Topluluk Davranış Kuralları Takımla Tanışın Dokümantasyona Katkıda Bulunanlar Katkıda Bulunanlar Daha Fazlası Blog React Native Gizliik Şartlar | 2026-01-13T08:48:43 |
https://highlight.io/ | highlight.io: The open source monitoring platform. Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up Your browser does not support the video tag. Your browser does not support the video tag. The open source, fullstack Monitoring Platform. Get started Live demo Request a Demo Call Session Replay Error Monitoring Logging Traces Dashboards Self-Hosting Explore Our Features Session Replay Error Monitoring Logging Traces Dashboards Self-Hosting Session Replay Session Replay Understand the real reason why bugs are happening in your web application. Learn More Console and Network Recording Comprehensive Session Search Powerful Privacy Controls Error Monitoring Error Monitoring Get notified of the exceptions across your app before they become problematic. Learn More Custom Error Grouping Customizable Alerting Rules Powered by Open Telemetry Logging Logging Search for and set alerts for logs being written throughout your stack. Learn More Customizable Log Alerts Widespread SDK Support Powered by Clickhouse Traces Traces Get performance insights on requests and transactions throughout your web application stack. Learn More Powerful Visualization Capabilities Distributed Tracing Support OpenTelemetry Support Dashboards & APM Dashboards & APM Visualize and analyze your observability data on a single pane. Learn More Customizable dashboards Performance visualizations User analytics Self-Hosting highlight.io Self-Hosting highlight.io Interested in self-hosting highlight? Spin up highlight.io in docker with just a few commands. Learn More git clone --recurse-submodules https://github.com/highlight/highlight; cd docker; ./run-hobby.sh; Our customers Highlight powers forward-thinking companies. More about our customers → Don't take our word. Read our customer review section → Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Web application monitoring for today's developer. A cohesive view of your entire stack. A natural pairing between your errors, session replay, logs and more. Understand the “what”, “why” and “how” of your full-stack web application. Get started for free Support for all the modern frameworks. We support all the fancy new frameworks and our platform is powered by open source, scalable technologies. View all frameworks Integrations with your favorite tools. Connect your favorite issue tracker, support tool, or even analytics software and we’ll give you a way to push and pull data in the right places. View all integrations Built with compliance and security. Whether its SOC 2, HIPAA, or ISO, highlight.io can work with your stack. Contact us at security@highlight.io for more information. Read our docs Master OpenTelemetry with our Free Comprehensive Course From fundamentals to advanced implementations, learn how OpenTelemetry can transform your engineering team's observability practices. Ideal for engineering leaders and developers building production-ready monitoring solutions. Start Learning Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:43 |
https://reactjs.org/docs/getting-started.html#adding-styles | Quick Start – React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog GET STARTED Quick Start Tutorial: Tic-Tac-Toe Thinking in React Installation Creating a React App Build a React App from Scratch Add React to an Existing Project Setup Editor Setup Using TypeScript React Developer Tools React Compiler Introduction Installation Incremental Adoption Debugging and Troubleshooting LEARN REACT Describing the UI Your First Component Importing and Exporting Components Writing Markup with JSX JavaScript in JSX with Curly Braces Passing Props to a Component Conditional Rendering Rendering Lists Keeping Components Pure Your UI as a Tree Adding Interactivity Responding to Events State: A Component's Memory Render and Commit State as a Snapshot Queueing a Series of State Updates Updating Objects in State Updating Arrays in State Managing State Reacting to Input with State Choosing the State Structure Sharing State Between Components Preserving and Resetting State Extracting State Logic into a Reducer Passing Data Deeply with Context Scaling Up with Reducer and Context Escape Hatches Referencing Values with Refs Manipulating the DOM with Refs Synchronizing with Effects You Might Not Need an Effect Lifecycle of Reactive Effects Separating Events from Effects Removing Effect Dependencies Reusing Logic with Custom Hooks Is this page useful? Learn React Quick Start Welcome to the React documentation! This page will give you an introduction to 80% of the React concepts that you will use on a daily basis. You will learn How to create and nest components How to add markup and styles How to display data How to render conditions and lists How to respond to events and update the screen How to share data between components Creating and nesting components React apps are made out of components . A component is a piece of the UI (user interface) that has its own logic and appearance. A component can be as small as a button, or as large as an entire page. React components are JavaScript functions that return markup: function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } Now that you’ve declared MyButton , you can nest it into another component: export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Notice that <MyButton /> starts with a capital letter. That’s how you know it’s a React component. React component names must always start with a capital letter, while HTML tags must be lowercase. Have a look at the result: App.js App.js Reload Clear Fork function MyButton ( ) { return ( < button > I'm a button </ button > ) ; } export default function MyApp ( ) { return ( < div > < h1 > Welcome to my app </ h1 > < MyButton /> </ div > ) ; } Show more The export default keywords specify the main component in the file. If you’re not familiar with some piece of JavaScript syntax, MDN and javascript.info have great references. Writing markup with JSX The markup syntax you’ve seen above is called JSX . It is optional, but most React projects use JSX for its convenience. All of the tools we recommend for local development support JSX out of the box. JSX is stricter than HTML. You have to close tags like <br /> . Your component also can’t return multiple JSX tags. You have to wrap them into a shared parent, like a <div>...</div> or an empty <>...</> wrapper: function AboutPage ( ) { return ( < > < h1 > About </ h1 > < p > Hello there. < br /> How do you do? </ p > </ > ) ; } If you have a lot of HTML to port to JSX, you can use an online converter. Adding styles In React, you specify a CSS class with className . It works the same way as the HTML class attribute: < img className = "avatar" /> Then you write the CSS rules for it in a separate CSS file: /* In your CSS */ .avatar { border-radius : 50 % ; } React does not prescribe how you add CSS files. In the simplest case, you’ll add a <link> tag to your HTML. If you use a build tool or a framework, consult its documentation to learn how to add a CSS file to your project. Displaying data JSX lets you put markup into JavaScript. Curly braces let you “escape back” into JavaScript so that you can embed some variable from your code and display it to the user. For example, this will display user.name : return ( < h1 > { user . name } </ h1 > ) ; You can also “escape into JavaScript” from JSX attributes, but you have to use curly braces instead of quotes. For example, className="avatar" passes the "avatar" string as the CSS class, but src={user.imageUrl} reads the JavaScript user.imageUrl variable value, and then passes that value as the src attribute: return ( < img className = "avatar" src = { user . imageUrl } /> ) ; You can put more complex expressions inside the JSX curly braces too, for example, string concatenation : App.js App.js Reload Clear Fork const user = { name : 'Hedy Lamarr' , imageUrl : 'https://i.imgur.com/yXOvdOSs.jpg' , imageSize : 90 , } ; export default function Profile ( ) { return ( < > < h1 > { user . name } </ h1 > < img className = "avatar" src = { user . imageUrl } alt = { 'Photo of ' + user . name } style = { { width : user . imageSize , height : user . imageSize } } /> </ > ) ; } Show more In the above example, style={{}} is not a special syntax, but a regular {} object inside the style={ } JSX curly braces. You can use the style attribute when your styles depend on JavaScript variables. Conditional rendering In React, there is no special syntax for writing conditions. Instead, you’ll use the same techniques as you use when writing regular JavaScript code. For example, you can use an if statement to conditionally include JSX: let content ; if ( isLoggedIn ) { content = < AdminPanel /> ; } else { content = < LoginForm /> ; } return ( < div > { content } </ div > ) ; If you prefer more compact code, you can use the conditional ? operator. Unlike if , it works inside JSX: < div > { isLoggedIn ? ( < AdminPanel /> ) : ( < LoginForm /> ) } </ div > When you don’t need the else branch, you can also use a shorter logical && syntax : < div > { isLoggedIn && < AdminPanel /> } </ div > All of these approaches also work for conditionally specifying attributes. If you’re unfamiliar with some of this JavaScript syntax, you can start by always using if...else . Rendering lists You will rely on JavaScript features like for loop and the array map() function to render lists of components. For example, let’s say you have an array of products: const products = [ { title : 'Cabbage' , id : 1 } , { title : 'Garlic' , id : 2 } , { title : 'Apple' , id : 3 } , ] ; Inside your component, use the map() function to transform an array of products into an array of <li> items: const listItems = products . map ( product => < li key = { product . id } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; Notice how <li> has a key attribute. For each item in a list, you should pass a string or a number that uniquely identifies that item among its siblings. Usually, a key should be coming from your data, such as a database ID. React uses your keys to know what happened if you later insert, delete, or reorder the items. App.js App.js Reload Clear Fork const products = [ { title : 'Cabbage' , isFruit : false , id : 1 } , { title : 'Garlic' , isFruit : false , id : 2 } , { title : 'Apple' , isFruit : true , id : 3 } , ] ; export default function ShoppingList ( ) { const listItems = products . map ( product => < li key = { product . id } style = { { color : product . isFruit ? 'magenta' : 'darkgreen' } } > { product . title } </ li > ) ; return ( < ul > { listItems } </ ul > ) ; } Show more Responding to events You can respond to events by declaring event handler functions inside your components: function MyButton ( ) { function handleClick ( ) { alert ( 'You clicked me!' ) ; } return ( < button onClick = { handleClick } > Click me </ button > ) ; } Notice how onClick={handleClick} has no parentheses at the end! Do not call the event handler function: you only need to pass it down . React will call your event handler when the user clicks the button. Updating the screen Often, you’ll want your component to “remember” some information and display it. For example, maybe you want to count the number of times a button is clicked. To do this, add state to your component. First, import useState from React: import { useState } from 'react' ; Now you can declare a state variable inside your component: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; // ... You’ll get two things from useState : the current state ( count ), and the function that lets you update it ( setCount ). You can give them any names, but the convention is to write [something, setSomething] . The first time the button is displayed, count will be 0 because you passed 0 to useState() . When you want to change state, call setCount() and pass the new value to it. Clicking this button will increment the counter: function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } React will call your component function again. This time, count will be 1 . Then it will be 2 . And so on. If you render the same component multiple times, each will get its own state. Click each button separately: App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < button onClick = { handleClick } > Clicked { count } times </ button > ) ; } Show more Notice how each button “remembers” its own count state and doesn’t affect other buttons. Using Hooks Functions starting with use are called Hooks . useState is a built-in Hook provided by React. You can find other built-in Hooks in the API reference. You can also write your own Hooks by combining the existing ones. Hooks are more restrictive than other functions. You can only call Hooks at the top of your components (or other Hooks). If you want to use useState in a condition or a loop, extract a new component and put it there. Sharing data between components In the previous example, each MyButton had its own independent count , and when each button was clicked, only the count for the button clicked changed: Initially, each MyButton ’s count state is 0 The first MyButton updates its count to 1 However, often you’ll need components to share data and always update together . To make both MyButton components display the same count and update together, you need to move the state from the individual buttons “upwards” to the closest component containing all of them. In this example, it is MyApp : Initially, MyApp ’s count state is 0 and is passed down to both children On click, MyApp updates its count state to 1 and passes it down to both children Now when you click either button, the count in MyApp will change, which will change both of the counts in MyButton . Here’s how you can express this in code. First, move the state up from MyButton into MyApp : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update separately </ h1 > < MyButton /> < MyButton /> </ div > ) ; } function MyButton ( ) { // ... we're moving code from here ... } Then, pass the state down from MyApp to each MyButton , together with the shared click handler. You can pass information to MyButton using the JSX curly braces, just like you previously did with built-in tags like <img> : export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } The information you pass down like this is called props . Now the MyApp component contains the count state and the handleClick event handler, and passes both of them down as props to each of the buttons. Finally, change MyButton to read the props you have passed from its parent component: function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } When you click the button, the onClick handler fires. Each button’s onClick prop was set to the handleClick function inside MyApp , so the code inside of it runs. That code calls setCount(count + 1) , incrementing the count state variable. The new count value is passed as a prop to each button, so they all show the new value. This is called “lifting state up”. By moving state up, you’ve shared it between components. App.js App.js Reload Clear Fork import { useState } from 'react' ; export default function MyApp ( ) { const [ count , setCount ] = useState ( 0 ) ; function handleClick ( ) { setCount ( count + 1 ) ; } return ( < div > < h1 > Counters that update together </ h1 > < MyButton count = { count } onClick = { handleClick } /> < MyButton count = { count } onClick = { handleClick } /> </ div > ) ; } function MyButton ( { count , onClick } ) { return ( < button onClick = { onClick } > Clicked { count } times </ button > ) ; } Show more Next Steps By now, you know the basics of how to write React code! Check out the Tutorial to put them into practice and build your first mini-app with React. Next Tutorial: Tic-Tac-Toe Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms On this page Overview Creating and nesting components Writing markup with JSX Adding styles Displaying data Conditional rendering Rendering lists Responding to events Updating the screen Using Hooks Sharing data between components Next Steps | 2026-01-13T08:48:43 |
https://docs.python.org/3/license.html#bsd0 | 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:43 |
https://docs.python.org/3/license.html#zlib | 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:43 |
https://docs.python.org/3/license.html#expat | 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:43 |
https://aws.amazon.com/blogs/developer/category/devops/aws-net-development/ | AWS .NET Development | 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 .NET Development 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 […] Introducing the AWS .NET Distributed Cache Provider for DynamoDB (Preview) by Alex Shovlin on 06 JUL 2023 in .NET , Announcements , AWS .NET Development Permalink Share We are happy to announce the preview release of the AWS .NET Distributed Cache Provider for DynamoDB. This library enables Amazon DynamoDB to be used as the storage for ASP.NET Core’s distributed cache framework. A cache can improve the performance of an application; an external cache allows the data to be shared across application servers […] AWS announces a streamlined deployment experience for .NET applications by Irene Kors and Norm Johanson on 06 JUL 2022 in .NET , Announcements , AWS .NET Development , AWS SDK for .NET , AWS Toolkit for Visual Studio , Developer Tools , Visual Studio Permalink Share We are happy to announce the general availability of a new deployment experience in both the Visual Studio and the .NET CLI. This follows the preview announcement from last year. The new deployment experience focuses on the type of application you want to deploy instead of individual AWS services by providing intelligent compute recommendations. You […] 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 […] 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 […] Tips & Tricks: Debugging your C# CDK project in Visual Studio by Philip Pittle on 20 DEC 2021 in .NET , AWS .NET Development , AWS Cloud Development Kit , AWS SDK for .NET , AWS Toolkit for Visual Studio , Technical How-to , Visual Studio Permalink Share NOTE: This post assumes the reader has some familiarity with the AWS Cloud Development Kit (CDK). To get started with the AWS CDK, please visit the AWS CDK Developer Guide and follow the AWS CDK for .NET workshop. The AWS CDK is an an open-source Infrastructure-as-Code (IaC) framework that allows developers to model and provision […] .NET at re:Invent 2021 by Josh Hurley on 22 NOV 2021 in .NET , Amazon CloudWatch , AWS .NET Development , AWS Lambda , AWS re:Invent , AWS SDK for .NET , AWS Serverless Application Model , AWS X-Ray , DevOps , Graviton Permalink Share Running .NET applications on AWS has never been better and our sessions at re:Invent this year reflect that excitement. All our sessions are for builders who want real-world insights and coding examples they can immediately apply in their applications. We also have a virtual option for those who cannot make it to Las Vegas. This […] .NET 6 on AWS by Josh Hurley on 17 NOV 2021 in .NET , Announcements , AWS .NET Development , AWS SDK for .NET , Developer Tools , Programing Language Permalink Share Congratulations to all the development teams and community involved in the .NET 6 GA release. .NET developers here at AWS are excited about the performance improvements in JIT compilation, Garbage Collection, JSON processing, and many other areas of the new release. We’re also excited about the new features including the Minimal API Framework, new data […] ← 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;f | 2026-01-13T08:48:43 |
https://www.youtube.com/watch?v=-7odLW_hG7s&list=PLNG_1j3cPCaZZ7etkzWA7JfdmKWT0pMsa&index=8 | Things I learnt from the new React docs - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xf2599ac4f2ed6d75"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtYc1NBZTFEd1pMTSjnjZjLBjIKCgJLUhIEGgAgYWLfAgrcAjE1LllUPURFOVRzQV9KNDNkaDJNZjcyZnU3SzhDRDQyUENBX0Zvck5ZUjFFM1ZVYXVxSGVrMXY3ZlhUeHlZMkNNQmMzS3NKeUUxVFBpTDNfWHRtNzA0ZzRwYS1CTUJlb3Z2azI0VWVOT1VqQ0hDYzF0ZUdVY0hCY2VPSEI1c0IzOTJNZU1WX25ld1Nhd0N6VkpUeGxPMHF4ZHpwOHB4WklwS2M3eUN2RGhFYnp5NF8ycmVFdEpIQ3c1LU9zVHJjS3k5YXBINGhJLUNidk9CSVhWZ3ZjQ1ZaLXBIMkNNWlplMVdOcVNHUlgtalp5OUw0RGNjWk4xVW5pOXpfVmJvdnV6OEN6MTQtRm56ZU1NY0JLR05nZ3lvUWZjUjRKaWl5eTBXUFpSMzVOU2FUTmxreW16NnhCUE4yVU5Tc3czR3dOT3pMSndaMzJuakoxbGlpWFc5d1p2eEd0MGlkUQ%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRmG5ccTtqulahvNai_AwTSJKrPziXr865HkHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","messageRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","continuationItemRenderer","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","adsEngagementPanelContentRenderer","engagementPanelTitleHeaderRenderer","chipBarViewModel","chipViewModel","sectionListRenderer","macroMarkersListRenderer","macroMarkersListItemRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtYc1NBZTFEd1pMTSjnjZjLBjIKCgJLUhIEGgAgYWLfAgrcAjE1LllUPURFOVRzQV9KNDNkaDJNZjcyZnU3SzhDRDQyUENBX0Zvck5ZUjFFM1ZVYXVxSGVrMXY3ZlhUeHlZMkNNQmMzS3NKeUUxVFBpTDNfWHRtNzA0ZzRwYS1CTUJlb3Z2azI0VWVOT1VqQ0hDYzF0ZUdVY0hCY2VPSEI1c0IzOTJNZU1WX25ld1Nhd0N6VkpUeGxPMHF4ZHpwOHB4WklwS2M3eUN2RGhFYnp5NF8ycmVFdEpIQ3c1LU9zVHJjS3k5YXBINGhJLUNidk9CSVhWZ3ZjQ1ZaLXBIMkNNWlplMVdOcVNHUlgtalp5OUw0RGNjWk4xVW5pOXpfVmJvdnV6OEN6MTQtRm56ZU1NY0JLR05nZ3lvUWZjUjRKaWl5eTBXUFpSMzVOU2FUTmxreW16NnhCUE4yVU5Tc3czR3dOT3pMSndaMzJuakoxbGlpWFc5d1p2eEd0MGlkUQ%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwju2_72kIiSAxUYTjgFHU0PBm4yDHJlbGF0ZWQtYXV0b0i7t4T_1qWH3fsBmgEFCAMQ-B3KAQRCkpKN","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X-WEQflCL0\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X-WEQflCL0","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwju2_72kIiSAxUYTjgFHU0PBm4yDHJlbGF0ZWQtYXV0b0i7t4T_1qWH3fsBmgEFCAMQ-B3KAQRCkpKN","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X-WEQflCL0\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X-WEQflCL0","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwju2_72kIiSAxUYTjgFHU0PBm4yDHJlbGF0ZWQtYXV0b0i7t4T_1qWH3fsBmgEFCAMQ-B3KAQRCkpKN","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X-WEQflCL0\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X-WEQflCL0","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Things I learnt from the new React docs"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 8,356회"},"shortViewCount":{"simpleText":"조회수 8.3천회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CLgCEMyrARgAIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCy03b2RMV19oRzdzGmBFZ3N0TjI5a1RGZGZhRWMzYzBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHkwM2IyUk1WMTlvUnpkekwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CLgCEMyrARgAIhMI7tv-9pCIkgMVGE44BR1NDwZu"}}],"trackingParams":"CLgCEMyrARgAIhMI7tv-9pCIkgMVGE44BR1NDwZu","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"194","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMMCEKVBIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},{"innertubeCommand":{"clickTrackingParams":"CMMCEKVBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMQCEPqGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMQCEPqGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"-7odLW_hG7s"},"likeParams":"Cg0KCy03b2RMV19oRzdzIAAyDAjojZjLBhCkyZGwAQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CMQCEPqGBCITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}}}}}}}]}},"accessibilityText":"다른 사용자 194명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMMCEKVBIhMI7tv-9pCIkgMVGE44BR1NDwZu","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"195","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMICEKVBIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},{"innertubeCommand":{"clickTrackingParams":"CMICEKVBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"-7odLW_hG7s"},"removeLikeParams":"Cg0KCy03b2RMV19oRzdzGAAqDAjojZjLBhDc3ZKwAQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 194명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMICEKVBIhMI7tv-9pCIkgMVGE44BR1NDwZu","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CLgCEMyrARgAIhMI7tv-9pCIkgMVGE44BR1NDwZu","isTogglingDisabled":true}},"likeStatusEntityKey":"EgstN29kTFdfaEc3cyA-KAE%3D","likeStatusEntity":{"key":"EgstN29kTFdfaEc3cyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMACEKiPCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}},{"innertubeCommand":{"clickTrackingParams":"CMACEKiPCSITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMECEPmGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMECEPmGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"-7odLW_hG7s"},"dislikeParams":"Cg0KCy03b2RMV19oRzdzEAAiDAjojZjLBhDMmJSwAQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CMECEPmGBCITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMACEKiPCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL8CEKiPCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}},{"innertubeCommand":{"clickTrackingParams":"CL8CEKiPCSITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"-7odLW_hG7s"},"removeLikeParams":"Cg0KCy03b2RMV19oRzdzGAAqDAjojZjLBhDEt5SwAQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL8CEKiPCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CLgCEMyrARgAIhMI7tv-9pCIkgMVGE44BR1NDwZu","isTogglingDisabled":true}},"dislikeEntityKey":"EgstN29kTFdfaEc3cyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgstN29kTFdfaEc3cyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CL0CEOWWARgCIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},{"innertubeCommand":{"clickTrackingParams":"CL0CEOWWARgCIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgstN29kTFdfaEc3c6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CL0CEOWWARgCIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CL4CEI5iIhMI7tv-9pCIkgMVGE44BR1NDwZu","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CL0CEOWWARgCIhMI7tv-9pCIkgMVGE44BR1NDwZu","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CLsCEOuQCSITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLwCEPuGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D-7odLW_hG7s\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLwCEPuGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-7odLW_hG7s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-7odLW_hG7s","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fbba1d2d6fe11bbb\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLwCEPuGBCITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}}}}}},"trackingParams":"CLsCEOuQCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLkCEOuQCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}},{"innertubeCommand":{"clickTrackingParams":"CLkCEOuQCSITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLoCEPuGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D-7odLW_hG7s\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLoCEPuGBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-7odLW_hG7s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-7odLW_hG7s","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fbba1d2d6fe11bbb\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLoCEPuGBCITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLkCEOuQCSITCO7b_vaQiJIDFRhOOAUdTQ8Gbg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CLgCEMyrARgAIhMI7tv-9pCIkgMVGE44BR1NDwZu","dateText":{"simpleText":"2021. 12. 9."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"4년 전"}},"simpleText":"4년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"React Conf","navigationEndpoint":{"clickTrackingParams":"CLcCEOE5IhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CLcCEOE5IhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 3.43만명"}},"simpleText":"구독자 3.43만명"},"trackingParams":"CLcCEOE5IhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UC1hOCRBN2mnXgN5reSoO3pQ","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CKkCEJsrIhMI7tv-9pCIkgMVGE44BR1NDwZuKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLYCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CLUCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CK4CEJf5ASITCO7b_vaQiJIDFRhOOAUdTQ8Gbg==","command":{"clickTrackingParams":"CK4CEJf5ASITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CK4CEJf5ASITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CLQCEOy1BBgDIhMI7tv-9pCIkgMVGE44BR1NDwZuMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRCkpKN","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggBGAAgBFITCgIIAxILLTdvZExXX2hHN3MYAA%3D%3D"}},"trackingParams":"CLQCEOy1BBgDIhMI7tv-9pCIkgMVGE44BR1NDwZu","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CLMCEO21BBgEIhMI7tv-9pCIkgMVGE44BR1NDwZuMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRCkpKN","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggDGAAgBFITCgIIAxILLTdvZExXX2hHN3MYAA%3D%3D"}},"trackingParams":"CLMCEO21BBgEIhMI7tv-9pCIkgMVGE44BR1NDwZu","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CK8CENuLChgFIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CK8CENuLChgFIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLACEMY4IhMI7tv-9pCIkgMVGE44BR1NDwZu","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CLICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuMgV3YXRjaMoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILLTdvZExXX2hHN3MYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CLICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLECEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CK8CENuLChgFIhMI7tv-9pCIkgMVGE44BR1NDwZu"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CKkCEJsrIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CK0CEP2GBCITCO7b_vaQiJIDFRhOOAUdTQ8GbjIJc3Vic2NyaWJlygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D-7odLW_hG7s%26continue_action%3DQUFFLUhqbnF3eldzaFJOeUVtNTlseVBQQk1WM1kya1VvUXxBQ3Jtc0tsM2oyeUZPZzN2VFA3LWR6WXpEZUtBajhVb1UzWE9lNG1Ocm91REF3NjZScG1KTWM4dWtmekdjb3Vjd0k4NV9zNy1KU1BPRkVwTklBcU1hRTY4RGV4c3dKcGNRaEdxNW1GTnczWmsxMXdLZ0otSDR0Ujl3N3dKWm5EZkMtWVRzZWh1aTBQNGJlMDFOYnJtTE9QOHh4VHNCX1NBSTJVSzljZlQxaFpOU1hoMllETWh6ZmhKZktGMjJWOWlsS284RjY1SEN6OTY\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CK0CEP2GBCITCO7b_vaQiJIDFRhOOAUdTQ8GbsoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=-7odLW_hG7s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"-7odLW_hG7s","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=fbba1d2d6fe11bbb\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbnF3eldzaFJOeUVtNTlseVBQQk1WM1kya1VvUXxBQ3Jtc0tsM2oyeUZPZzN2VFA3LWR6WXpEZUtBajhVb1UzWE9lNG1Ocm91REF3NjZScG1KTWM4dWtmekdjb3Vjd0k4NV9zNy1KU1BPRkVwTklBcU1hRTY4RGV4c3dKcGNRaEdxNW1GTnczWmsxMXdLZ0otSDR0Ujl3N3dKWm5EZkMtWVRzZWh1aTBQNGJlMDFOYnJtTE9QOHh4VHNCX1NBSTJVSzljZlQxaFpOU1hoMllETWh6ZmhKZktGMjJWOWlsS284RjY1SEN6OTY","idamTag":"66429"}},"trackingParams":"CK0CEP2GBCITCO7b_vaQiJIDFRhOOAUdTQ8Gbg=="}}}}}},"subscribedEntityKey":"EhhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CKkCEJsrIhMI7tv-9pCIkgMVGE44BR1NDwZuKPgdMgV3YXRjaMoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"EgIIAxgAIgstN29kTFdfaEc3cw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CKkCEJsrIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKkCEJsrIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKoCEMY4IhMI7tv-9pCIkgMVGE44BR1NDwZu","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKwCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuKPgdMgV3YXRjaMoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILLTdvZExXX2hHN3MYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKwCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKsCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CKgCEM2rARgBIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CKgCEM2rARgBIhMI7tv-9pCIkgMVGE44BR1NDwZu","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CKgCEM2rARgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKgCEM2rARgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CKgCEM2rARgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CKgCEM2rARgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Debbie O'Brien","styleRuns":[{"startIndex":0,"length":14,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":14,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"messageRenderer":{"text":{"runs":[{"text":"댓글이 사용 중지되었습니다. "},{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CKcCEJY7GAAiEwju2_72kIiSAxUYTjgFHU0PBm7KAQRCkpKN","commandMetadata":{"webCommandMetadata":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko"}}}]},"trackingParams":"CKcCEJY7GAAiEwju2_72kIiSAxUYTjgFHU0PBm4="}}],"trackingParams":"CKYCELsvGAMiEwju2_72kIiSAxUYTjgFHU0PBm4=","sectionIdentifier":"comment-item-section"}}],"trackingParams":"CKUCELovIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/wIyHSOugGGw/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBHedqZDD83uaS6ASEH48KTXZGyoA","width":168,"height":94},{"url":"https://i.ytimg.com/vi/wIyHSOugGGw/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDzfx8HJK4SN2LylzXXyLENwrhbjw","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"11:53","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"wIyHSOugGGw","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"11분 53초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CKQCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"wIyHSOugGGw","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKQCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CKMCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"wIyHSOugGGw"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKMCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJwCENTEDBgAIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CKICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"wIyHSOugGGw","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CKICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["wIyHSOugGGw"],"params":"CAQ%3D"}},"videoIds":["wIyHSOugGGw"],"videoCommand":{"clickTrackingParams":"CKICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=wIyHSOugGGw","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"wIyHSOugGGw","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh26d.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=c08c8748eba0186c\u0026ip=1.208.108.242\u0026initcwndbps=4492500\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKICEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CKECEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJwCENTEDBgAIhMI7tv-9pCIkgMVGE44BR1NDwZu"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"Every React Concept Explained in 12 Minutes"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/f6JRugd0pxGhDtbPy8TZXpGsTMn3oWX3k2_uxmwNv0TGEAumkezVGISaIQOHTo3cP5iOwXbjfw=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"Code Bootcamp 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCENTEDBgAIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/@TheCodeBootcamp","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC-kHm7pG884IYQiYwqJWv9A","canonicalBaseUrl":"/@TheCodeBootcamp"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"Code Bootcamp"}}]},{"metadataParts":[{"text":{"content":"조회수 158만회"}},{"text":{"content":"1년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CJ0CEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CKACEP6YBBgAIhMI7tv-9pCIkgMVGE44BR1NDwZu","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CKACEP6YBBgAIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKACEP6YBBgAIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"wIyHSOugGGw","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CKACEP6YBBgAIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["wIyHSOugGGw"],"params":"CAQ%3D"}},"videoIds":["wIyHSOugGGw"],"videoCommand":{"clickTrackingParams":"CKACEP6YBBgAIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=wIyHSOugGGw","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"wIyHSOugGGw","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh26d.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=c08c8748eba0186c\u0026ip=1.208.108.242\u0026initcwndbps=4492500\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJ8CEJSsCRgBIhMI7tv-9pCIkgMVGE44BR1NDwZu","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJ8CEJSsCRgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJ8CEJSsCRgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgt3SXlIU091Z0dHdw%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJ0CEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgt3SXlIU091Z0dHdw%3D%3D","commands":[{"clickTrackingParams":"CJ0CEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJ4CEI5iIhMI7tv-9pCIkgMVGE44BR1NDwZu","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJ0CEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"wIyHSOugGGw","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJwCENTEDBgAIhMI7tv-9pCIkgMVGE44BR1NDwZu","visibility":{"types":"12"}}},"accessibilityContext":{"label":"Every React Concept Explained in 12 Minutes 11분 53초"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCENTEDBgAIhMI7tv-9pCIkgMVGE44BR1NDwZuMgdyZWxhdGVkSLu3hP_WpYfd-wGaAQUIARD4HcoBBEKSko0=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=wIyHSOugGGw","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"wIyHSOugGGw","nofollow":true,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh26d.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=c08c8748eba0186c\u0026ip=1.208.108.242\u0026initcwndbps=4492500\u0026mt=1768293662\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/5X-WEQflCL0/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLD0UP--yGbR_cEKMOJwxnBhJP5Ctg","width":168,"height":94},{"url":"https://i.ytimg.com/vi/5X-WEQflCL0/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB0P1PW3CYbZ8TaRKqydhPmsWRw1w","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"10:44","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"5X-WEQflCL0","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"10분 44초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"5X-WEQflCL0","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJsCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJoCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"5X-WEQflCL0"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJoCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJMCENTEDBgBIhMI7tv-9pCIkgMVGE44BR1NDwZu"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJkCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJkCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"5X-WEQflCL0","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJkCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["5X-WEQflCL0"],"params":"CAQ%3D"}},"videoIds":["5X-WEQflCL0"],"videoCommand":{"clickTrackingParams":"CJkCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X-WEQflCL0","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X-WEQflCL0","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e57f961107e508bd\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJkCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJgCEPBbIhMI7tv-9pCIkgMVGE44BR1NDwZu","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJMCENTEDBgBIhMI7tv-9pCIkgMVGE44BR1NDwZu"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"Learning in the Browser"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJMCENTEDBgBIhMI7tv-9pCIkgMVGE44BR1NDwZuygEEQpKSjQ==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회수 6.2천회"}},{"text":{"content":"4년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CJQCEPBbIhMI7tv-9pCIkgMVGE44BR | 2026-01-13T08:48:43 |
https://docs.suprsend.com/reference/cli-event-list | List Events - 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 List Events Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Event List Events OpenAI Open in ChatGPT List all events in your workspace. OpenAI Open in ChatGPT Syntax Copy Ask AI suprsend event list [flags] Flags Flag Description Default -h, --help Show help for the command – -l, --limit int Limit the number of events to list 20 -f, --offset int Offset into the list of events 0 -w, --workspace string Workspace to list events from staging Example Copy Ask AI # List events in staging workspace (default) suprsend event list # List events in production workspace suprsend event list --workspace production # List events with limit and offset suprsend event list --limit 10 --offset 5 Was this page helpful? Yes No Suggest edits Raise issue Previous Pull Events Fetch events from SuprSend workspace to local directory Next ⌘ I x github linkedin youtube Powered by On this page Syntax Flags Example | 2026-01-13T08:48:43 |
https://forem.com/eriadura | SAMUEL ADENIJI - 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 Follow User actions SAMUEL ADENIJI I am a website developer and a game developer Location Nigeria Joined Joined on May 30, 2024 Email address samuel.adeniji2012@gmail.com github website Education Codingal online class Pronouns Mr Work website developer More info about @eriadura 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 4 Week Community Wellness Streak Keep contributing to discussions by posting at least 2 comments per week for 4 straight weeks. Unlock the 8 Week Badge next. Got it Close 2 Week Community Wellness Streak Keep the community conversation going! Post at least 2 comments for 2 straight weeks and unlock the 4 Week Badge. 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 Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close GitHub Repositories my-portfolio HTML • 1 star google-analysis pgai A suite of tools to develop RAG, semantic search, and other AI applications more easily with PostgreSQL Fork website HTML java-script js HTML form forem For empowering community 🌱 Fork file HTML • 1 star eriadura Config files for my GitHub profile. brief-on-javascript HTML MY-PROJECT This is my portfolio as a website desginer HTML • 1 star Json-and-JS-Asynchronous HTML • 1 star Html-Css-Java .github Fork -my-plugins A curated list of Budibase plugins 🔌 including data sources and components. Fork Skills/Languages My skill are html an Ai developer Currently learning I am currently learning java script and css Currently hacking on I am currently working on a app called "G graphics" Available for I am available for collaboration or discussion Post 10 posts published Comment 33 comments written Tag 74 tags followed Webinar for an avishaar SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 13 '24 Webinar for an avishaar # webdev # tutorial Comments Add Comment 1 min read Want to connect with SAMUEL ADENIJI? Create an account to connect with SAMUEL ADENIJI. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in This is another competition from avishkaar SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 4 '24 This is another competition from avishkaar Comments Add Comment 1 min read This is a robotic competition in india SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 2 '24 This is a robotic competition in india # webdev # programming # ai Comments Add Comment 1 min read This is a robotic competition in india SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 2 '24 This is a robotic competition in india # webdev # programming # ai Comments Add Comment 1 min read This is a robotic competition in india SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Nov 2 '24 This is a robotic competition in india # webdev # programming # ai Comments Add Comment 1 min read This is a video cip of ict as a transformational tool 10:08 SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Oct 30 '24 This is a video cip of ict as a transformational tool Comments Add Comment 1 min read https://samueladeniji2012.wixsite.com/fasolin-blog SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Oct 27 '24 https://samueladeniji2012.wixsite.com/fasolin-blog # devchallenge # wixstudiochallenge # webdev # javascript Comments Add Comment 1 min read How To Add Chat Bot To Your Website SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Oct 27 '24 How To Add Chat Bot To Your Website # webdev # tutorial # ai # learning Comments Add Comment 1 min read how to create a binary treenode with python SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow Sep 21 '24 how to create a binary treenode with python Comments Add Comment 1 min read My name is Adeniji Samuel I want to design an AI machine SAMUEL ADENIJI SAMUEL ADENIJI SAMUEL ADENIJI Follow May 30 '24 My name is Adeniji Samuel I want to design an AI machine # webdev # beginners # javascript # programming 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 — 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:43 |
https://www.youtube.com/watch?v=oxDfrke8rZg&list=PLNG_1j3cPCaZZ7etkzWA7JfdmKWT0pMsa&index=5 | React Developer Tooling - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x11d96fee35d1e669"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtzYXZRdUtOMmp2RSjnjZjLBjIKCgJLUhIEGgAgKGLfAgrcAjE1LllUPU1VRTA5X3o5X3BOR25scHZQWWUtSWpjXzdnM2hGSUdGNFROQ29oOW5DTkc5RjluaXdwSlY3VGlaN0E3WTE5VHo5TVZ0SV9lOGp4Z1NyN2VTeDhwYWFybTlxZGQxb1FEYU4zUHBUYlFxOTlDeG9hb3piMGppMWkzajBmMG50MzNTUUZuTVQ0cGVTbGRZelZ4dWY4S2REX3lSOW5DRndIX2N6ZjZCQzNlbEo2dXlWekNpamc5NndNSDgzLU9mQmw4VHJpQjR2cEFzeDRqa29zN1FtSjJEZTQwN3pURjMxRDU5ZFo2MDZqeU5Sd04tZEQtcHU1MGxXYTFTSG5ZdXl2Qm5haUlOLXFnS2kteDRqZ3hnRHNmT1ZUMlJwdi01dW1NOF9lX2xYUHUyb2RONkRaWFA1VFVsOURwWHdPbVdwZXp2SzJaS3Ewa0N2X1FGbXB5WWQ3Mjd5dw%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZR32VXf5sw25a58atYGfwpDfKBMhiXr86P46HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","messageRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","continuationItemRenderer","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","adsEngagementPanelContentRenderer","engagementPanelTitleHeaderRenderer","chipBarViewModel","chipViewModel","sectionListRenderer","macroMarkersListRenderer","macroMarkersInfoItemRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtzYXZRdUtOMmp2RSjnjZjLBjIKCgJLUhIEGgAgKGLfAgrcAjE1LllUPU1VRTA5X3o5X3BOR25scHZQWWUtSWpjXzdnM2hGSUdGNFROQ29oOW5DTkc5RjluaXdwSlY3VGlaN0E3WTE5VHo5TVZ0SV9lOGp4Z1NyN2VTeDhwYWFybTlxZGQxb1FEYU4zUHBUYlFxOTlDeG9hb3piMGppMWkzajBmMG50MzNTUUZuTVQ0cGVTbGRZelZ4dWY4S2REX3lSOW5DRndIX2N6ZjZCQzNlbEo2dXlWekNpamc5NndNSDgzLU9mQmw4VHJpQjR2cEFzeDRqa29zN1FtSjJEZTQwN3pURjMxRDU5ZFo2MDZqeU5Sd04tZEQtcHU1MGxXYTFTSG5ZdXl2Qm5haUlOLXFnS2kteDRqZ3hnRHNmT1ZUMlJwdi01dW1NOF9lX2xYUHUyb2RONkRaWFA1VFVsOURwWHdPbVdwZXp2SzJaS3Ewa0N2X1FGbXB5WWQ3Mjd5dw%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwiTx_72kIiSAxWK2DQHHeXsGTYyDHJlbGF0ZWQtYXV0b0iY2_K95PW3iKMBmgEFCAMQ-B3KAQRP5Ka2","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FXqX7oof0I4\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FXqX7oof0I4","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiTx_72kIiSAxWK2DQHHeXsGTYyDHJlbGF0ZWQtYXV0b0iY2_K95PW3iKMBmgEFCAMQ-B3KAQRP5Ka2","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FXqX7oof0I4\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FXqX7oof0I4","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiTx_72kIiSAxWK2DQHHeXsGTYyDHJlbGF0ZWQtYXV0b0iY2_K95PW3iKMBmgEFCAMQ-B3KAQRP5Ka2","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=FXqX7oof0I4\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"FXqX7oof0I4","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"React Developer Tooling"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 20,341회"},"shortViewCount":{"simpleText":"조회수 2만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CLECEMyrARgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC294RGZya2U4clpnGmBFZ3R2ZUVSbWNtdGxPSEphWjBBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDI5NFJHWnlhMlU0Y2xwbkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CLECEMyrARgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}}],"trackingParams":"CLECEMyrARgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"369","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLwCEKVBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},{"innertubeCommand":{"clickTrackingParams":"CLwCEKVBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL0CEPqGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL0CEPqGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"oxDfrke8rZg"},"likeParams":"Cg0KC294RGZya2U4clpnIAAyCwjpjZjLBhCmkKQu"}},"idamTag":"66426"}},"trackingParams":"CL0CEPqGBCITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}}}}}}}]}},"accessibilityText":"다른 사용자 369명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLwCEKVBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"370","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLsCEKVBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},{"innertubeCommand":{"clickTrackingParams":"CLsCEKVBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"oxDfrke8rZg"},"removeLikeParams":"Cg0KC294RGZya2U4clpnGAAqCwjpjZjLBhCmtaUu"}}}]}},"accessibilityText":"다른 사용자 369명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLsCEKVBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CLECEMyrARgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtveERmcmtlOHJaZyA-KAE%3D","likeStatusEntity":{"key":"EgtveERmcmtlOHJaZyA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLkCEKiPCSITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}},{"innertubeCommand":{"clickTrackingParams":"CLkCEKiPCSITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLoCEPmGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLoCEPmGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"oxDfrke8rZg"},"dislikeParams":"Cg0KC294RGZya2U4clpnEAAiCwjpjZjLBhD-iKgu"}},"idamTag":"66425"}},"trackingParams":"CLoCEPmGBCITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLkCEKiPCSITCJPH_vaQiJIDFYrYNAcd5ewZNg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLgCEKiPCSITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}},{"innertubeCommand":{"clickTrackingParams":"CLgCEKiPCSITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"oxDfrke8rZg"},"removeLikeParams":"Cg0KC294RGZya2U4clpnGAAqCwjpjZjLBhCywagu"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLgCEKiPCSITCJPH_vaQiJIDFYrYNAcd5ewZNg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CLECEMyrARgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isTogglingDisabled":true}},"dislikeEntityKey":"EgtveERmcmtlOHJaZyA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtveERmcmtlOHJaZyD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLYCEOWWARgCIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},{"innertubeCommand":{"clickTrackingParams":"CLYCEOWWARgCIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtveERmcmtlOHJaZ6ABAQ%3D%3D","commands":[{"clickTrackingParams":"CLYCEOWWARgCIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CLcCEI5iIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLYCEOWWARgCIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CLQCEOuQCSITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLUCEPuGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DoxDfrke8rZg\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLUCEPuGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=oxDfrke8rZg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"oxDfrke8rZg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a310dfae47bcad98\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLUCEPuGBCITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}}}}}},"trackingParams":"CLQCEOuQCSITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CLICEOuQCSITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}},{"innertubeCommand":{"clickTrackingParams":"CLICEOuQCSITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CLMCEPuGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DoxDfrke8rZg\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CLMCEPuGBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=oxDfrke8rZg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"oxDfrke8rZg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a310dfae47bcad98\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CLMCEPuGBCITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CLICEOuQCSITCJPH_vaQiJIDFYrYNAcd5ewZNg==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CLECEMyrARgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","dateText":{"simpleText":"2021. 12. 9."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"4년 전"}},"simpleText":"4년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"React Conf","navigationEndpoint":{"clickTrackingParams":"CLACEOE5IhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CLACEOE5IhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 3.43만명"}},"simpleText":"구독자 3.43만명"},"trackingParams":"CLACEOE5IhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UC1hOCRBN2mnXgN5reSoO3pQ","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CKICEJsrIhMIk8f-9pCIkgMVitg0Bx3l7Bk2KPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"React Conf을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CK8CEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CK4CEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. React Conf 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CKcCEJf5ASITCJPH_vaQiJIDFYrYNAcd5ewZNg==","command":{"clickTrackingParams":"CKcCEJf5ASITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKcCEJf5ASITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CK0CEOy1BBgDIhMIk8f-9pCIkgMVitg0Bx3l7Bk2MhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRP5Ka2","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggBGAAgBFITCgIIAxILb3hEZnJrZThyWmcYAA%3D%3D"}},"trackingParams":"CK0CEOy1BBgDIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CKwCEO21BBgEIhMIk8f-9pCIkgMVitg0Bx3l7Bk2MhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRP5Ka2","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFESAggDGAAgBFITCgIIAxILb3hEZnJrZThyWmcYAA%3D%3D"}},"trackingParams":"CKwCEO21BBgEIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CKgCENuLChgFIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKgCENuLChgFIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKkCEMY4IhMIk8f-9pCIkgMVitg0Bx3l7Bk2","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2MgV3YXRjaMoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILb3hEZnJrZThyWmcYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKoCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CKgCENuLChgFIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CKICEJsrIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKYCEP2GBCITCJPH_vaQiJIDFYrYNAcd5ewZNjIJc3Vic2NyaWJlygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DoxDfrke8rZg%26continue_action%3DQUFFLUhqbEZaZFRIN0hiRnhsbHlyempadGpGbnRiamFEZ3xBQ3Jtc0tud1pZMVppTHBtczk5Q3Rkd1lNc0hjcDZoVk5xYmNuRUxTNWlDeUxPd2pLWXFFU3RjV0U1d0pIbTNGRy04aVdfMlV0eG16OGpnTmhYeDZGUWl6dXYySFFPOXEyUTNfWWRiZjF5OTdNUGs2N29FbnNjRDZYUDJfVVpLZ3RBWERTVWJxVW05QjJUQml0b0psREZTOUFnV0lfUk1HanFfRXVvdnhxZl9nNWJlcnlhWi0wbVdoblRvT2pPbWNUeWZIaWVIZnBCb28\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKYCEP2GBCITCJPH_vaQiJIDFYrYNAcd5ewZNsoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=oxDfrke8rZg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"oxDfrke8rZg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a310dfae47bcad98\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbEZaZFRIN0hiRnhsbHlyempadGpGbnRiamFEZ3xBQ3Jtc0tud1pZMVppTHBtczk5Q3Rkd1lNc0hjcDZoVk5xYmNuRUxTNWlDeUxPd2pLWXFFU3RjV0U1d0pIbTNGRy04aVdfMlV0eG16OGpnTmhYeDZGUWl6dXYySFFPOXEyUTNfWWRiZjF5OTdNUGs2N29FbnNjRDZYUDJfVVpLZ3RBWERTVWJxVW05QjJUQml0b0psREZTOUFnV0lfUk1HanFfRXVvdnhxZl9nNWJlcnlhWi0wbVdoblRvT2pPbWNUeWZIaWVIZnBCb28","idamTag":"66429"}},"trackingParams":"CKYCEP2GBCITCJPH_vaQiJIDFYrYNAcd5ewZNg=="}}}}}},"subscribedEntityKey":"EhhVQzFoT0NSQk4ybW5YZ041cmVTb08zcFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CKICEJsrIhMIk8f-9pCIkgMVitg0Bx3l7Bk2KPgdMgV3YXRjaMoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"EgIIAxgAIgtveERmcmtlOHJaZw%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CKICEJsrIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CKICEJsrIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CKMCEMY4IhMIk8f-9pCIkgMVitg0Bx3l7Bk2","dialogMessages":[{"runs":[{"text":"React Conf"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CKUCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2KPgdMgV3YXRjaMoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UC1hOCRBN2mnXgN5reSoO3pQ"],"params":"CgIIAxILb3hEZnJrZThyWmcYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CKUCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CKQCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CKECEM2rARgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CKECEM2rARgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CKECEM2rARgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CKECEM2rARgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CKECEM2rARgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CKECEM2rARgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Brian Vaughn","styleRuns":[{"startIndex":0,"length":12,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":12,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"messageRenderer":{"text":{"runs":[{"text":"댓글이 사용 중지되었습니다. "},{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CKACEJY7GAAiEwiTx_72kIiSAxWK2DQHHeXsGTbKAQRP5Ka2","commandMetadata":{"webCommandMetadata":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://support.google.com/youtube/answer/9706180?hl=ko"}}}]},"trackingParams":"CKACEJY7GAAiEwiTx_72kIiSAxWK2DQHHeXsGTY="}}],"trackingParams":"CJ8CELsvGAMiEwiTx_72kIiSAxWK2DQHHeXsGTY=","sectionIdentifier":"comment-item-section"}}],"trackingParams":"CJ4CELovIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/lhVGdErZuN4/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDU_yP89n_HMVZhq03K2rNXCwnJNw","width":168,"height":94},{"url":"https://i.ytimg.com/vi/lhVGdErZuN4/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLCD4lkK0S1E7DiUckvFWDd8FDFgiA","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"19:35","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"lhVGdErZuN4","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"19분 35초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CJ0CEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"lhVGdErZuN4","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJ0CEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJwCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"lhVGdErZuN4"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJwCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJUCENTEDBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"lhVGdErZuN4","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["lhVGdErZuN4"],"params":"CAQ%3D"}},"videoIds":["lhVGdErZuN4"],"videoCommand":{"clickTrackingParams":"CJsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=lhVGdErZuN4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"lhVGdErZuN4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=961546744ad9b8de\u0026ip=1.208.108.242\u0026initcwndbps=3965000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJsCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJoCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CJUCENTEDBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"Re-introducing Relay"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/uWYRwTF365L_lSs_3372-KSTENlGKJ6_T2enkHjewwy_mL7-AVDgFxm_8kRLdD5mHI6ga2Y1wzQ=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"React Conf 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJUCENTEDBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/@ReactConfOfficial","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UC1hOCRBN2mnXgN5reSoO3pQ","canonicalBaseUrl":"/@ReactConfOfficial"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"React Conf"}}]},{"metadataParts":[{"text":{"content":"조회수 2.5만회"}},{"text":{"content":"4년 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CJYCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJkCEP6YBBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJkCEP6YBBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJkCEP6YBBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"lhVGdErZuN4","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJkCEP6YBBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["lhVGdErZuN4"],"params":"CAQ%3D"}},"videoIds":["lhVGdErZuN4"],"videoCommand":{"clickTrackingParams":"CJkCEP6YBBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=lhVGdErZuN4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"lhVGdErZuN4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=961546744ad9b8de\u0026ip=1.208.108.242\u0026initcwndbps=3965000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJgCEJSsCRgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJgCEJSsCRgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJgCEJSsCRgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtsaFZHZEVyWnVONA%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJYCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtsaFZHZEVyWnVONA%3D%3D","commands":[{"clickTrackingParams":"CJYCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJcCEI5iIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJYCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"lhVGdErZuN4","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CJUCENTEDBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","visibility":{"types":"12"}}},"accessibilityContext":{"label":"Re-introducing Relay 19분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CJUCENTEDBgAIhMIk8f-9pCIkgMVitg0Bx3l7Bk2MgdyZWxhdGVkSJjb8r3k9beIowGaAQUIARD4HcoBBE_kprY=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=lhVGdErZuN4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"lhVGdErZuN4","nofollow":true,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=961546744ad9b8de\u0026ip=1.208.108.242\u0026initcwndbps=3965000\u0026mt=1768293662\u0026oweuc="}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/5LrDIWkK_Bc/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLCQa6ylyiE2Ej-bFV42ocf31tc-Sw","width":168,"height":94},{"url":"https://i.ytimg.com/vi/5LrDIWkK_Bc/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB1CQ6pqiWnWiKmQaPvOLHdC7vWKQ","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"13:08","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"5LrDIWkK_Bc","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"13분 8초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CJQCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"5LrDIWkK_Bc","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJQCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CJMCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"5LrDIWkK_Bc"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJMCEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CIwCENTEDBgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CJICEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CJICEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"5LrDIWkK_Bc","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CJICEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["5LrDIWkK_Bc"],"params":"CAQ%3D"}},"videoIds":["5LrDIWkK_Bc"],"videoCommand":{"clickTrackingParams":"CJICEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5LrDIWkK_Bc","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5LrDIWkK_Bc","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e4bac321690afc17\u0026ip=1.208.108.242\u0026initcwndbps=3965000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJICEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CJECEPBbIhMIk8f-9pCIkgMVitg0Bx3l7Bk2","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CIwCENTEDBgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"Learn useContext In 13 Minutes"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/ytc/AIdro_nO3F7DfVXaf6wsHPS_hF327ggeWUCwZSELb5DCWBL1aw=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"Web Dev Simplified 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CIwCENTEDBgBIhMIk8f-9pCIkgMVitg0Bx3l7Bk2ygEET-Smtg==","commandMetadata":{"webCommandMetadata":{"url":"/@WebDevSimplified","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCFbNIlppjAuEX4znoulh0Cw","canonicalBaseUrl":"/@WebDevSimplified"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"Web Dev Simplified","styleRuns":[{"startIndex":18,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4289374890},{"key":"USER_INTERFACE_THEME_LIGHT","value":4284506208}]}}}],"attachmentRuns":[{"startIndex":18,"length":0,"element | 2026-01-13T08:48:43 |
https://docs.python.org/3/license.html#xml-remote-procedure-calls | 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:43 |
https://share.transistor.fm/s/8f8b74c8#copya | APIs You Won't Hate | Maybe GraphQL isn't so terrible? A conversation with Marc-Andre Giroux 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 June 12, 2020 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 Phil and Matt talk with Marc-Andre Giroux, a developer working at Github who helps maintain their REST and GraphQL APIs. Show Notes A quick note before we get started: We recorded this episode back in April of 2020 when everyone was quarantining and making bread to post on instagram. Fast forward to now, in June, American cities, and cities around the world are joining in, protesting the systemic racism that has long been an issue in our societies. While our energy and focus turned to current events, editing this episode took a seat on the backburner. That said, we have it ready… but it couldn’t be released at a worse time. Three white dudes talking about APIs while our friends in other communities are fighting injustices that have long kept them down seems to be a bit tone deaf, and we know that, recognize that and commit ourselves to being involved. There are a lot of conversations we want to have around this topic both in the API world, and outside of it. We don’t want this episode to take away from the discussions going on around such important and heavy topics, but we hope this can serve as a way for you to take a break while you travel to and from a protest. If you are going to protest please be safe, drink as much water as you can to stay hydrated in the heat and know that things are changing for the better. To all the Black API developers out there: we see you, we're fighting with you, and we want you to know that we're listening. From all of us at APIs You Won't Hate: Black lives matter. Recorded back in April, Matt and Phil are joined by Marc-Andre Giroux to talk about the APIs he works on at Github and his fascination of GraphQL. Marc-Andre recently released a book titled " Production Ready GraphQL " where he talks about schema design, tooling, architecture and more. We take a dive into knowing when GraphQL is the right tool for the job, versus when to use REST and talk a little about the whole quarantine thing that was happening. Sponsors: Stoplight makes it possible for us to bring you this podcast while we nerd out about APIs. Check them out for their tooling around documentation with Studio, an app that makes API documentation an absolute joy to work with. Twitter: https://twitter.com/__xuorig__ Book: Production Ready GraphQL APIs You Wont Hate Jobs Board: https://apisyouwonthate.com/jobs APIs You Wont Hate Slack: https://apisyouwonthate.com/community 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. 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:43 |
https://docs.python.org/3/license.html#history-and-license | 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:43 |
https://docs.python.org/3/tutorial/controlflow.html#documentation-strings | 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:43 |
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:43 |
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/class | HTML class global attribute - HTML | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTML Reference Global attributes class Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) HTML class global attribute The class global attribute is a list of the classes of the element, separated by ASCII whitespace . In this article Try it Syntax Description Specifications Browser compatibility See also Try it <p>Narrator: This is the beginning of the play.</p> <p class="note editorial">Above point sounds a bit obvious. Remove/rewrite?</p> <p>Narrator: I must warn you now folks that this beginning is very exciting.</p> <p class="note">[Lights go up and wind blows; Caspian enters stage right]</p> .note { font-style: italic; font-weight: bold; } .editorial { background: rgb(255 0 0 / 0.25); padding: 10px; } .editorial::before { content: "Editor: "; } Syntax The class attribute is a list of class values separated by ASCII whitespace . Each class value may contain any Unicode characters (except, of course, ASCII whitespace). However, when used in CSS selectors, either from JavaScript using APIs like Document.querySelector() or in CSS stylesheets, class attribute values must be valid CSS identifiers . This means that if a class attribute value is not a valid CSS identifier (for example, my?class or 1234 ) then it must be escaped before being used in a selector, either using the CSS.escape() method or manually . For this reason, it's recommended that developers choose values for class attributes that are valid CSS identifiers that don't require escaping. Description Classes allow CSS and JavaScript to select and access specific elements via the class selectors or functions like the document.getElementsByClassName() . Though the specification doesn't put requirements on the name of classes, web developers are encouraged to use names that describe the semantic purpose of the element, rather than the presentation of the element. For example, attribute to describe an attribute rather than italics , although an element of this class may be presented by italics . Semantic names remain logical even if the presentation of the page changes. Specifications Specification HTML # classes Browser compatibility Enable JavaScript to view this browser compatibility table. See also All global attributes . element.className element.classList Introduction to CSS Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Nov 6, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTML Guides Cheatsheet Comments Constraint validation Content categories Date and time formats Microdata Microformats Quirks and standards modes Responsive images How to Define terms with HTML Use data attributes Use cross-origin images Add a hitmap on top of an image Author fast-loading HTML pages Add JavaScript Reference Elements <a> <abbr> <acronym> Deprecated <address> <area> <article> <aside> <audio> <b> <base> <bdi> <bdo> <big> Deprecated <blockquote> <body> <br> <button> <canvas> <caption> <center> Deprecated <cite> <code> <col> <colgroup> <data> <datalist> <dd> <del> <details> <dfn> <dialog> <dir> Deprecated <div> <dl> <dt> <em> <embed> <fencedframe> Experimental <fieldset> <figcaption> <figure> <font> Deprecated <footer> <form> <frame> Deprecated <frameset> Deprecated <h1> <head> <header> <hgroup> <hr> <html> <i> <iframe> <img> <input> <ins> <kbd> <label> <legend> <li> <link> <main> <map> <mark> <marquee> Deprecated <menu> <meta> <meter> <nav> <nobr> Deprecated <noembed> Deprecated <noframes> Deprecated <noscript> <object> <ol> <optgroup> <option> <output> <p> <param> Deprecated <picture> <plaintext> Deprecated <pre> <progress> <q> <rb> Deprecated <rp> <rt> <rtc> Deprecated <ruby> <s> <samp> <script> <search> <section> <select> <selectedcontent> Experimental <slot> <small> <source> <span> <strike> Deprecated <strong> <style> <sub> <summary> <sup> <table> <tbody> <td> <template> <textarea> <tfoot> <th> <thead> <time> <title> <tr> <track> <tt> Deprecated <u> <ul> <var> <video> <wbr> <xmp> Deprecated Attributes accept autocomplete capture content crossorigin dirname disabled elementtiming fetchpriority for form max maxlength min minlength multiple pattern placeholder readonly rel required size step Global attributes accesskey anchor Experimental Non-standard autocapitalize autocorrect autofocus class contenteditable data-* dir draggable enterkeyhint exportparts hidden id inert inputmode is itemid itemprop itemref itemscope itemtype lang nonce part popover slot spellcheck style tabindex title translate virtualkeyboardpolicy Experimental writingsuggestions Attributes by element <input> type <input type="button"> <input type="checkbox"> <input type="color"> <input type="date"> <input type="datetime-local"> <input type="email"> <input type="file"> <input type="hidden"> <input type="image"> <input type="month"> <input type="number"> <input type="password"> <input type="radio"> <input type="range"> <input type="reset"> <input type="search"> <input type="submit"> <input type="tel"> <input type="text"> <input type="time"> <input type="url"> <input type="week"> <script> type importmap speculationrules Experimental <meta> name color-scheme referrer robots theme-color viewport <meta> http-equiv Attribute values rel keywords rel="alternate stylesheet" rel="compression-dictionary" Experimental rel="dns-prefetch" rel="manifest" rel="me" rel="modulepreload" rel="noopener" rel="noreferrer" rel="preconnect" rel="prefetch" rel="preload" rel="prerender" Non-standard Deprecated Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:43 |
https://www.pocketgamer.com/mobile-legends-bang-bang/ | Mobile Legends: Bang Bang | Pocket Gamer Our Network Arrow Down PocketGamer.com AppSpy.com 148Apps.com PocketGamer.fr PocketGamer.biz PCGamesInsider.biz The Sims News PocketGamer.fun BlockchainGamer.biz PG Connects BigIndiePitch.com MobileGamesAwards.com U.GG Icy Veins The Sims Resource Fantasy Football Scout GameKnot Addicting Games Arcade Cloud EV.IO Menu PocketGamer.com Facebook X YouTube RSS Search Search Mobile Legends: Bang Bang Get PG Awards 2024 Nominee! Publisher: shanghai moonton Technology Co Ltd | Available on: iOS + Android Twitter Facebook Reddit Mobile Legends: Bang Bang Articles RSS How To Today's Mobile Legends: Bang Bang redeem codes (January 2026) By Shaun Walton How To Mobile Legends Bang Bang tier list: Best Heroes by role [January 2026] By Mihail Katsoris Top List Best MOBA games for iPhone and iPad (iOS) By Jon Mundy Top List Best MOBA games for Android phones and tablets By Jon Mundy News Mobile Legends: Bang Bang brings new format to Esports World cup 2025 entry By Iwan Morris News Mobile Legends: Bang Bang reveals overhauled tournament format for the Mid Season Cup at the 2025 Esports World Cup By Tanish Botadkar Right Arrow Game Finder Browse our archive for thousands of game reviews across all mobile and handheld formats News Mobile Legends: Bang Bang is bringing back the Mid Season Cup to Riyadh for the 2025 Esports World Cup By Tanish Botadkar News Mobile Legends: Bang Bang is gearing up for the Women’s Invitational Esports World Cup 2025 By Tanish Botadkar News ByteDance is transferring US publishing to Skystone in major shake-up By Iwan Morris News Mobile Legends: Bang Bang's first female-focused qualifier in Philippines arrives with Athena League By Iwan Morris Top List Top 13 best phone games to play with friends far away By Ivan Spasojevic Feature The Pocket Gamer Podcast Episode 18 - The Big Snap, The BBC and the survival of survival games By Dann Sullivan News Mobile Legends: Bang Bang to return for Esports World Cup in 2025 By Iwan Morris News Mobile Legends: Bang Bang sees Team Vitality esports club acquire top female team Bigetron Era By Iwan Morris News Registration for the Mobile Legends: Bang Bang 2024 NACT Spring Season is now open By Jack Brassell News Mobile Legends: Bang Bang will be featured at the Esports World Cup in Riyadh, Saudi Arabia this summer By Catherine Dellosa News Mobile Legends: Bang Bang unveils its esports roadmap for 2024 By Tanish Botadkar News Mobile Legends: Bang Bang North America will hold an intercollegiate tournament in the US, with registration now ongoing By Catherine Dellosa News Mobile Legends: Bang Bang will hold an all-female tournament via the Skyesports SEA Championship this month By Catherine Dellosa How To Who is the strongest Fanny user in Mobile Legends? By Alina Novichenko Update Mobile Legends: Bang Bang getting tons of cosmetics courtesy of new season pass By Connor Derrick Update Mobile Legends: Bang Bang North America adds in-game events and celebrity-driven promotional campaign during 515 event By Catherine Dellosa Walkthrough Mobile Legends Melissa best build, emblems and combos By Suchit Mohanty Walkthrough Mobile Legends Kagura best build, emblems and combos By Suchit Mohanty Walkthrough Mobile Legends Hayabusa best build, emblems and combos By Suchit Mohanty Walkthrough Mobile Legends Patch 1.6.24 complete notes By Suchit Mohanty How To How to secure Mobile Legends BB account By Suchit Mohanty Walkthrough Mobile Legends Patch 1.6.18 - We have leaks of the upcoming update By Suchit Mohanty News Mobile Legends: Bang Bang is hosting the final event for the North American Qualifier this weekend By Tanish Botadkar News Mobile Legends: Bang Bang announces North America Qualifiers for the M3 World Championship By Tanish Botadkar Next | 2026-01-13T08:48:43 |
https://dev.to/t/beginners/page/3#promotional-rules | Beginners Page 3 - 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 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 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How Speed Finally Made My Character Feel Alive Dinesh Dinesh Dinesh Follow Jan 12 How Speed Finally Made My Character Feel Alive # gamedev # unrealengine # beginners # animation Comments Add Comment 2 min read Unlocking the Power of Inheritance in Python Visakh Vijayan Visakh Vijayan Visakh Vijayan Follow Jan 12 Unlocking the Power of Inheritance in Python # beginners # programming # python # tutorial Comments Add Comment 2 min read **More Than a Bootcamp: Why I Chose the German 'Umschulung' Path into Tech** Ali-Funk Ali-Funk Ali-Funk Follow Jan 11 **More Than a Bootcamp: Why I Chose the German 'Umschulung' Path into Tech** # watercooler # career # devops # beginners Comments Add Comment 3 min read EU Digital Omnibus: New Requirements for Websites and Online Services Mehwish Malik Mehwish Malik Mehwish Malik Follow Jan 12 EU Digital Omnibus: New Requirements for Websites and Online Services # webdev # ai # beginners # productivity 17 reactions Comments Add Comment 3 min read Who is Krishna Mohan Kumar? | Full Stack Developer & B.Tech CSE Student Krishna Mohan Kumar Krishna Mohan Kumar Krishna Mohan Kumar Follow Jan 12 Who is Krishna Mohan Kumar? | Full Stack Developer & B.Tech CSE Student # webdev # beginners # portfolio # google Comments Add Comment 1 min read Sharing: How to Build Competitiveness and Soft Skills, and Write a Good Resume Evan Lin Evan Lin Evan Lin Follow Jan 11 Sharing: How to Build Competitiveness and Soft Skills, and Write a Good Resume # learning # beginners # writing # career Comments Add Comment 9 min read Sharing a Talk: "How to Build Your Own Open Source Project" Evan Lin Evan Lin Evan Lin Follow Jan 11 Sharing a Talk: "How to Build Your Own Open Source Project" # beginners # opensource # softwaredevelopment Comments Add Comment 7 min read Sharing: "How to Build Your Own Open Source Project" Evan Lin Evan Lin Evan Lin Follow Jan 11 Sharing: "How to Build Your Own Open Source Project" # beginners # opensource # tutorial Comments Add Comment 11 min read Singleton vs Observer Pattern: When and Why to Use Each Arun Teja Arun Teja Arun Teja Follow Jan 11 Singleton vs Observer Pattern: When and Why to Use Each # architecture # beginners # javascript Comments Add Comment 3 min read Singleton vs Observer Pattern: When and Why to Use Each Arun Teja Arun Teja Arun Teja Follow Jan 11 Singleton vs Observer Pattern: When and Why to Use Each # architecture # beginners # javascript Comments Add Comment 3 min read Observer Pattern Explained Simply With JavaScript Examples Arun Teja Arun Teja Arun Teja Follow Jan 11 Observer Pattern Explained Simply With JavaScript Examples # designpatterns # javascript # beginners # programming Comments Add Comment 3 min read The Non-Drinker's Guide to Clustering Algorithms 🎉 Seenivasa Ramadurai Seenivasa Ramadurai Seenivasa Ramadurai Follow Jan 11 The Non-Drinker's Guide to Clustering Algorithms 🎉 # algorithms # beginners # datascience # machinelearning Comments Add Comment 2 min read My First Beginner Projects Vivash Kshitiz Vivash Kshitiz Vivash Kshitiz Follow Jan 12 My First Beginner Projects # discuss # beginners # python # learning Comments Add Comment 1 min read Accounting 101: Learn how to build financial applications Favor Onuoha Favor Onuoha Favor Onuoha Follow Jan 11 Accounting 101: Learn how to build financial applications # beginners # fintech Comments Add Comment 10 min read Sitemaps & robots.txt: The Secret to Faster, Smarter Scraping Muhammad Ikramullah Khan Muhammad Ikramullah Khan Muhammad Ikramullah Khan Follow Jan 11 Sitemaps & robots.txt: The Secret to Faster, Smarter Scraping # webdev # programming # python # beginners Comments Add Comment 10 min read [TIL][Android] Common Android Studio Project Opening Issues Evan Lin Evan Lin Evan Lin Follow Jan 11 [TIL][Android] Common Android Studio Project Opening Issues # help # beginners # android # kotlin Comments Add Comment 2 min read APCSCamp 2021: How to Learn Programming and Intern at LINE Evan Lin Evan Lin Evan Lin Follow Jan 11 APCSCamp 2021: How to Learn Programming and Intern at LINE # learning # beginners # career # programming Comments Add Comment 10 min read LINE Platform and Messaging API Introduction - 2022 Evan Lin Evan Lin Evan Lin Follow Jan 11 LINE Platform and Messaging API Introduction - 2022 # beginners # api # tutorial # programming Comments Add Comment 3 min read Digital Certificate Wallet: Beginner's Guide Evan Lin Evan Lin Evan Lin Follow Jan 11 Digital Certificate Wallet: Beginner's Guide # beginners # security # privacy # mobile Comments Add Comment 2 min read JSON vs. XML for APIs: Key Differences Explained for Beginners CodeItBro CodeItBro CodeItBro Follow Jan 11 JSON vs. XML for APIs: Key Differences Explained for Beginners # webdev # programming # beginners # tutorial Comments Add Comment 10 min read My first post lol bhennyhayman bhennyhayman bhennyhayman Follow Jan 11 My first post lol # webdev # javascript # beginners Comments Add Comment 1 min read AWS IAM basics explained with real examples Sahinur Sahinur Sahinur Follow Jan 11 AWS IAM basics explained with real examples # aws # beginners # security Comments Add Comment 5 min read AWS Pricing Models Explained: (A Beginner's Guide) chandra penugonda chandra penugonda chandra penugonda Follow Jan 11 AWS Pricing Models Explained: (A Beginner's Guide) # beginners # tutorial # cloud # aws Comments Add Comment 8 min read Turning Database Schemas into Diagrams & Docs — Open for Early Feedback Rushikesh Bodakhe Rushikesh Bodakhe Rushikesh Bodakhe Follow Jan 11 Turning Database Schemas into Diagrams & Docs — Open for Early Feedback # webdev # programming # ai # beginners 1 reaction Comments Add Comment 1 min read HTTP Caching Explained (The Way I Learned It in Production) Nishar Arif Nishar Arif Nishar Arif Follow Jan 11 HTTP Caching Explained (The Way I Learned It in Production) # beginners # webdev # tutorial # performance 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:43 |
https://www.stackaid.us | StackAid - Fund all your open source dependencies Fund all your open source dependencies StackAid is a simple way to donate to all the open source software projects you depend on. By subscribing to StackAid, we'll distribute your subscription fee among your projects' direct and indirect dependencies. Join our growing community which has raised $14,934 for 2,034 organizations and 4,338 individual projects. Get Started How does StackAid work for my project? See for yourself. Copy and paste your package.json or edit the one below to get a breakdown of how your dependencies would be funded. { "name": "@stackaid/web", "version": "0.1.0", "dependencies": { "@datadog/datadog-api-client": "^1.0.0", "@fortawesome/fontawesome-svg-core": "^6.1.2", "@fortawesome/free-brands-svg-icons": "^6.1.2", "@fortawesome/free-regular-svg-icons": "^6.1.2", "@fortawesome/free-solid-svg-icons": "^6.1.2", "@fortawesome/pro-light-svg-icons": "^6.1.2", "@fortawesome/pro-regular-svg-icons": "^6.1.2", "@google-cloud/storage": "^6.7.0", "@next/mdx": "^12.2.5", "@octokit/webhooks-methods": "^2.0.0", "@vercel/analytics": "^0.1.11", "bootstrap": "^5.1.0", "date-fns": "^2.28.0", "dotenv": "^10.0.0", "eslint-config-next": "^13.4.2", "got": "^11.8.2", "graphql": "^15.4.0", "graphql-tag": "^2.12.5", "graphqurl": "^1.0.1", "lodash": "^4.17.21", "next": "^13.4.2", "next-auth": "^4.3.3", "nookies": "^2.5.2", "octokit": "^1.7.1", "postmark": "^3.0.1", "prism-react-renderer": "^1.2.1", "react": "^18.2.0", "react-bootstrap": "^2.0.0-beta.5", "react-dom": "^18.2.0", "react-simple-code-editor": "^0.11.0", "sass": "^1.38.0", "semver": "^7.3.5", "stripe": "^8.178.0", "veritas-env": "^0.0.10" }, "devDependencies": { "@graphql-codegen/cli": "^2.1.1", "@graphql-codegen/introspection": "^2.1.0", "@graphql-codegen/typescript": "^2.1.2", "@graphql-codegen/typescript-document-nodes": "^2.1.2", "@graphql-codegen/typescript-operations": "^2.1.2", "@types/async": "^3.2.10", "@types/jest": "^27.0.3", "@types/lodash": "^4.14.172", "@types/react": "^17.0.11", "@types/semver": "^7.3.8", "async": "^3.2.2", "eslint": "^7.28.0", "jest": "^27.4.3", "js-yaml": "^3.14.1", "prettier": "^2.6.2", "typescript": "^4.5.5", "yargs": "^17.3.0" } } 1 { 2 "name" : "@stackaid/web" , 3 "version" : "0.1.0" , 4 "dependencies" : { 5 "@datadog/datadog-api-client" : "^1.0.0" , 6 "@fortawesome/fontawesome-svg-core" : "^6.1.2" , 7 "@fortawesome/free-brands-svg-icons" : "^6.1.2" , 8 "@fortawesome/free-regular-svg-icons" : "^6.1.2" , 9 "@fortawesome/free-solid-svg-icons" : "^6.1.2" , 10 "@fortawesome/pro-light-svg-icons" : "^6.1.2" , 11 "@fortawesome/pro-regular-svg-icons" : "^6.1.2" , 12 "@google-cloud/storage" : "^6.7.0" , 13 "@next/mdx" : "^12.2.5" , 14 "@octokit/webhooks-methods" : "^2.0.0" , 15 "@vercel/analytics" : "^0.1.11" , 16 "bootstrap" : "^5.1.0" , 17 "date-fns" : "^2.28.0" , 18 "dotenv" : "^10.0.0" , 19 "eslint-config-next" : "^13.4.2" , 20 "got" : "^11.8.2" , 21 "graphql" : "^15.4.0" , 22 "graphql-tag" : "^2.12.5" , 23 "graphqurl" : "^1.0.1" , 24 "lodash" : "^4.17.21" , 25 "next" : "^13.4.2" , 26 "next-auth" : "^4.3.3" , 27 "nookies" : "^2.5.2" , 28 "octokit" : "^1.7.1" , 29 "postmark" : "^3.0.1" , 30 "prism-react-renderer" : "^1.2.1" , 31 "react" : "^18.2.0" , 32 "react-bootstrap" : "^2.0.0-beta.5" , 33 "react-dom" : "^18.2.0" , 34 "react-simple-code-editor" : "^0.11.0" , 35 "sass" : "^1.38.0" , 36 "semver" : "^7.3.5" , 37 "stripe" : "^8.178.0" , 38 "veritas-env" : "^0.0.10" 39 } , 40 "devDependencies" : { 41 "@graphql-codegen/cli" : "^2.1.1" , 42 "@graphql-codegen/introspection" : "^2.1.0" , 43 "@graphql-codegen/typescript" : "^2.1.2" , 44 "@graphql-codegen/typescript-document-nodes" : "^2.1.2" , 45 "@graphql-codegen/typescript-operations" : "^2.1.2" , 46 "@types/async" : "^3.2.10" , 47 "@types/jest" : "^27.0.3" , 48 "@types/lodash" : "^4.14.172" , 49 "@types/react" : "^17.0.11" , 50 "@types/semver" : "^7.3.8" , 51 "async" : "^3.2.2" , 52 "eslint" : "^7.28.0" , 53 "jest" : "^27.4.3" , 54 "js-yaml" : "^3.14.1" , 55 "prettier" : "^2.6.2" , 56 "typescript" : "^4.5.5" , 57 "yargs" : "^17.3.0" 58 } 59 } Copy and paste your package.json above Run A team of each contributing /mo directly funds 34 projects and indirectly funds 407 projects DefinitelyTyped/DefinitelyTyped ( 2 ) $59 /yr ├ frenic/csstype $2 /yr └ facebook/jest $2 /yr prettier/prettier $54 /yr facebook/jest ( 1 ) $49 /yr └ sindresorhus/import-local $2 /yr graphql/graphql-js $47 /yr facebook/react ( 1 ) $46 /yr └ zertosh/loose-envify $2 /yr lodash/lodash $45 /yr FortAwesome/Font-Awesome $44 /yr wescarr/veritas ( 1 ) $42 /yr └ babel/babel $2 /yr npm/node-semver ( 2 ) $41 /yr ├ isaacs/node-lru-cache $2 /yr └ tapjs/node-tap $2 /yr sass/dart-sass ( 3 ) $38 /yr ├ paulmillr/chokidar $2 /yr ├ immutable-js/immutable-js $2 /yr └ 7rulnik/source-map-js $2 /yr Microsoft/TypeScript ( 14 ) $37 /yr ├ chalk/chalk $2 /yr ├ DefinitelyTyped/DefinitelyTyped $2 /yr ├ sindresorhus/del $2 /yr ├ eslint/eslint $2 /yr ├ import-js/eslint-plugin-import $2 /yr └ 9 more eslint/eslint ( 79 ) $34 /yr ├ ajv-validator/ajv < $1 /yr ├ babel/babel < $1 /yr ├ babel/babel-loader < $1 /yr ├ chaijs/chai < $1 /yr ├ chalk/chalk < $1 /yr └ 74 more maticzav/nookies ( 5 ) $33 /yr ├ jshttp/cookie $2 /yr ├ DefinitelyTyped/DefinitelyTyped $2 /yr ├ zeit/next.js $2 /yr ├ nfriedly/set-cookie-parser $2 /yr └ terser/terser $2 /yr react-bootstrap/react-bootstrap ( 7 ) $29 /yr ├ babel/babel $2 /yr ├ react-bootstrap/dom-helpers $2 /yr ├ zertosh/invariant $2 /yr ├ facebook/prop-types $2 /yr ├ react-bootstrap/prop-types-extra $2 /yr └ 2 more motdotla/dotenv ( 8 ) $28 /yr ├ dwyl/decache $2 /yr ├ Microsoft/dtslint $2 /yr ├ flowtype/flow-bin $2 /yr ├ tapjs/node-tap $2 /yr ├ sinonjs/sinon $2 /yr └ 3 more yargs/yargs ( 24 ) $25 /yr ├ bcoe/c8 < $1 /yr ├ chaijs/chai < $1 /yr ├ chalk/chalk < $1 /yr ├ davglass/cpr < $1 /yr ├ kentcdodds/cross-env < $1 /yr └ 19 more nodeca/js-yaml ( 11 ) $22 /yr ├ TooTallNate/ansi.js $2 /yr ├ nodeca/argparse $2 /yr ├ bestiejs/benchmark.js $2 /yr ├ browserify/browserify $2 /yr ├ codemirror/CodeMirror $2 /yr └ 6 more caolan/async ( 28 ) $22 /yr ├ babel/babel < $1 /yr ├ 59naga/babel-plugin-add-module-exports < $1 /yr ├ istanbuljs/babel-plugin-istanbul < $1 /yr ├ babel/babelify < $1 /yr ├ bestiejs/benchmark.js < $1 /yr └ 23 more twbs/bootstrap ( 14 ) $22 /yr ├ bundlewatch/bundlewatch $2 /yr ├ clean-css/clean-css-cli $2 /yr ├ kentcdodds/cross-env $2 /yr ├ sindresorhus/globby $2 /yr ├ karma-runner/karma-browserstack-launcher $2 /yr └ 9 more DataDog/datadog-api-client-typescript ( 17 ) $22 /yr ├ LinusU/buffer-from $1 /yr ├ chaijs/chai $1 /yr ├ lquixada/cross-fetch $1 /yr ├ DefinitelyTyped/DefinitelyTyped $1 /yr ├ stefanpenner/es6-promise $1 /yr └ 12 more date-fns/date-fns ( 48 ) $22 /yr ├ babel/babel < $1 /yr ├ babel/babel-eslint < $1 /yr ├ babel/babel-loader < $1 /yr ├ 59naga/babel-plugin-add-module-exports < $1 /yr ├ kentcdodds/cloc < $1 /yr └ 43 more sindresorhus/got ( 37 ) $22 /yr ├ avajs/ava < $1 /yr ├ axios/axios < $1 /yr ├ bestiejs/benchmark.js < $1 /yr ├ szmarczak/cacheable-lookup < $1 /yr ├ lukechilds/cacheable-request < $1 /yr └ 32 more dotansimha/graphql-code-generator ( 19 ) $22 /yr ├ sindresorhus/auto-bind $1 /yr ├ babel/babel $1 /yr ├ chalk/chalk $1 /yr ├ paulmillr/chokidar $1 /yr ├ davidtheclark/cosmiconfig $1 /yr └ 14 more apollographql/graphql-tag ( 11 ) $22 /yr ├ chaijs/chai $2 /yr ├ DefinitelyTyped/DefinitelyTyped $2 /yr ├ graphql/graphql-js $2 /yr ├ mochajs/mocha $2 /yr ├ evanw/node-source-map-support $2 /yr └ 6 more hasura/graphqurl ( 17 ) $22 /yr ├ oclif/cli-ux $1 /yr ├ oclif/command $1 /yr ├ oclif/config $1 /yr ├ oclif/errors $1 /yr ├ eslint/eslint $1 /yr └ 12 more nextauthjs/next-auth ( 26 ) $22 /yr ├ postcss/autoprefixer < $1 /yr ├ babel/babel < $1 /yr ├ jmm/babel-plugin-jsx-pragmatic < $1 /yr ├ developit/babel-preset-preact < $1 /yr ├ open-cli-tools/concurrently < $1 /yr └ 21 more vercel/next.js ( 103 ) $22 /yr ├ hapijs/accept < $1 /yr ├ acornjs/acorn < $1 /yr ├ ampproject/amp-toolbox < $1 /yr ├ IonicaBizau/anser < $1 /yr ├ zeit/arg < $1 /yr └ 98 more googleapis/nodejs-storage ( 30 ) $22 /yr ├ mysticatea/abort-controller < $1 /yr ├ vercel/async-retry < $1 /yr ├ jshttp/compressible < $1 /yr ├ DefinitelyTyped/DefinitelyTyped < $1 /yr ├ mafintosh/duplexify < $1 /yr └ 25 more octokit/octokit.js ( 16 ) $22 /yr ├ octokit/app.js $1 /yr ├ pikapkg/builders $1 /yr ├ octokit/core.js $1 /yr ├ DefinitelyTyped/DefinitelyTyped $1 /yr ├ wheresrhys/fetch-mock $1 /yr └ 11 more ActiveCampaign/postmark.js ( 11 ) $22 /yr ├ axios/axios $2 /yr ├ chaijs/chai $2 /yr ├ DefinitelyTyped/DefinitelyTyped $2 /yr ├ motdotla/dotenv $2 /yr ├ mochajs/mocha $2 /yr └ 6 more FormidableLabs/prism-react-renderer ( 16 ) $22 /yr ├ babel/babel $1 /yr ├ kentcdodds/babel-plugin-macros $1 /yr ├ flowtype/flow-bin $1 /yr ├ sindresorhus/globby $1 /yr ├ typicode/husky $1 /yr └ 11 more satya164/react-simple-code-editor ( 13 ) $22 /yr ├ release-it/conventional-changelog $2 /yr ├ dmnd/dedent $2 /yr ├ DefinitelyTyped/DefinitelyTyped $2 /yr ├ sindresorhus/del-cli $2 /yr ├ eslint/eslint $2 /yr └ 8 more stripe/stripe-node ( 16 ) $22 /yr ├ chaijs/chai $1 /yr ├ domenic/chai-as-promised $1 /yr ├ DefinitelyTyped/DefinitelyTyped $1 /yr ├ eslint/eslint $1 /yr ├ prettier/eslint-config-prettier $1 /yr └ 11 more octokit/webhooks-methods.js ( 11 ) $22 /yr ├ pikapkg/builders $2 /yr ├ DefinitelyTyped/DefinitelyTyped $2 /yr ├ facebook/jest $2 /yr ├ pikapkg/pack $2 /yr ├ prettier/prettier $2 /yr └ 6 more Start funding your dependencies. Claim open source projects. Get Started How does StackAid allocate funds? You choose the total amount you want to donate each month among all your dependencies. The subscription amount you choose is divided evenly across all your direct dependencies, but it's also shared with your indirect dependencies. That is, each of your direct dependencies automatically shares up to 5% with each of its dependencies, but they never share more than half of their original allocation. Let's use a simple example: { "dependencies": { "bootstrap": "^5.1.0", "sass": "^1.38.0" } } 1 { 2 "dependencies" : { 3 "bootstrap" : "^5.1.0" , 4 "sass" : "^1.38.0" 5 } 6 } With a StackAid subscription of $20/month, bootstrap and sass are both allocated $10/month because they split the amount. But then they share that with their dependencies. Because sass has 3 dependencies, each of those get 5% of the amount given to sass . So each sass dependency gets $0.50/mo ($6/yr) and sass is left with $8.50/mo ($102/yr). Because bootstrap has over 20 dependencies, giving them each 5% wouldn't be fair to bootstrap , so just 50% of the bootstrap allocation is divided equally among its dependencies and bootstrap keeps $5/mo ($60/yr). Here's the allocation breakdown for this example: sass/dart-sass ( 3 ) $102 /yr ├ paulmillr/chokidar $6 /yr ├ immutable-js/immutable-js $6 /yr └ 7rulnik/source-map-js $6 /yr twbs/bootstrap ( 14 ) $60 /yr ├ bundlewatch/bundlewatch $4 /yr ├ clean-css/clean-css-cli $4 /yr ├ kentcdodds/cross-env $4 /yr ├ sindresorhus/globby $4 /yr ├ karma-runner/karma-browserstack-launcher $4 /yr └ 9 more You'll notice above that sass earns $1/yr more than expected. This is because bootstrap also depends on sass so it receives an indirect dependency allocation from bootstrap . Why do we need StackAid? The problem with open source funding today isn't a lack of means or desire to support projects. The problem is decision paralysis, figuring out how much to fund each project and the mechanics of paying each one. For example, even if you have a small project, it could have a dozen dependencies and many more indirect dependencies. So if you decide to fund your direct dependencies, here are the questions you then have to answer: How much should I give to each project? How do I go about funding each project? Assuming you've figured out those questions, you might still be wondering if this is workable. Will everyone else, especially the dependencies you fund, go to this effort to fund their dependencies? Probably not. How much does it cost? Subscriptions start at $15/month. How do you make money? When you add your project dependencies, StackAid is treated as an implicit direct dependency. StackAid is on equal footing, but unlike those dependencies, StackAid's allocation is capped at 7.5%. In the example above, StackAid would receive $1.50/mo. How does StackAid figure out my dependencies? StackAid's GitHub app searches your repositories for package dependency files. For example, for JavaScript projects we look for package.json files. Is StackAid only for Node.js/npm based projects? No, you can use our GitHub action to automatically generate and publish a stackaid.json file which lists your dependencies. You can of course manually curate the list of projects you want to fund. For example, if you wanted to allocate money to the Linux kernel and Node.js, then you would add these two repositories to your stackaid.json file: { "version": 1, "dependencies": [ { "source": "https://github.com/torvalds/linux" }, { "source": "https://github.com/nodejs/node" } ] } 1 { 2 "version" : 1 , 3 "dependencies" : [ 4 { "source" : "https://github.com/torvalds/linux" } , 5 { "source" : "https://github.com/nodejs/node" } 6 ] 7 } We are working on bringing the same level of automated discovery and integration for Node.js projects to other ecosystems. Can I use StackAid without giving read access to my source? Yes, we recommend setting up a new repository that's just meant to be shared with StackAid and then use our GitHub action to automatically publish your dependencies there for discovery. How does my open source project get paid by StackAid? Owners of open source projects can claim their repositories by installing the StackAid GitHub app. As part of the claiming process, owners can associate one or more Stripe accounts with each repository they own to receive payments. Once a month the money allocated for each repository is split evenly among the associated Stripe accounts. Stripe accounts can belong to a single person or an organization that has its own rules for how the money will be put to use. Note: If your projects are not registered with StackAid, we will make every attempt possible to pay allocated funds on existing platforms such as GitHub, Open Collective, Patreon, etc. What happens when an open source project hasn't claimed their allocation? A project's allocations accumulate for 2 months. If the project is not claimed by then, an automatic reallocation happens and the amount is redistributed to the other dependencies that are claimed. Reallocation occurs on a per subscription basis. Note: During the Beta period we will not run reallocation to give projects more time to claim their funds. How do you know this model works? While it’s easy to understand how a single subscription is distributed, it’s hard to tell if this is fair and meaningful. We had the same question, so we built a simulation of 5,000 subscribers for a year. The bottom line is that the long tail is pretty fat. Popular projects do well, but StackAid funds many more projects that would otherwise get overlooked. Start funding your dependencies. Claim open source projects. Get Started Projects Supporters About Blog Mastodon Contact Help Privacy Terms | 2026-01-13T08:48:43 |
https://parenting.forem.com/privacy#1-what-does-this-privacy-policy-apply-to | 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:43 |
https://developer.mozilla.org/en-US/docs/web/javascript/reference/statements/export | export - JavaScript | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web JavaScript Reference Statements and declarations export Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) export Baseline Widely available This feature is well established and works across many devices and browser versions. It’s been available across browsers since May 2018. Learn more See full compatibility Report feedback The export declaration is used to export values from a JavaScript module. Exported values can then be imported into other programs with the import declaration or dynamic import . The value of an imported binding is subject to change in the module that exports it — when a module updates the value of a binding that it exports, the update will be visible in its imported value. In order to use the export declaration in a source file, the file must be interpreted by the runtime as a module . In HTML, this is done by adding type="module" to the <script> tag, or by being imported by another module. Modules are automatically interpreted in strict mode . In this article Syntax Description Examples Specifications Browser compatibility See also Syntax js // Exporting declarations export let name1, name2/*, … */; // also var export const name1 = 1, name2 = 2/*, … */; // also var, let export function functionName() { /* … */ } export class ClassName { /* … */ } export function* generatorFunctionName() { /* … */ } export const { name1, name2: bar } = o; export const [ name1, name2 ] = array; // Export list export { name1, /* …, */ nameN }; export { variable1 as name1, variable2 as name2, /* …, */ nameN }; export { variable1 as "string name" }; export { name1 as default /*, … */ }; // Default exports export default expression; export default function functionName() { /* … */ } export default class ClassName { /* … */ } export default function* generatorFunctionName() { /* … */ } export default function () { /* … */ } export default class { /* … */ } export default function* () { /* … */ } // Aggregating modules export * from "module-name"; export * as name1 from "module-name"; export { name1, /* …, */ nameN } from "module-name"; export { import1 as name1, import2 as name2, /* …, */ nameN } from "module-name"; export { default, /* …, */ } from "module-name"; export { default as name1 } from "module-name"; nameN Identifier to be exported (so that it can be imported via import in another script). If you use an alias with as , the actual exported name can be specified as a string literal, which may not be a valid identifier. Description Every module can have two different types of export, named export and default export . You can have multiple named exports per module but only one default export. Each type corresponds to one of the above syntax. Named exports: js // export features declared elsewhere export { myFunction2, myVariable2 }; // export individual features (can export var, let, // const, function, class) export let myVariable = Math.sqrt(2); export function myFunction() { // … } After the export keyword, you can use let , const , and var declarations, as well as function or class declarations. You can also use the export { name1, name2 } syntax to export a list of names declared elsewhere. Note that export {} does not export an empty object — it's a no-op declaration that exports nothing (an empty name list). You cannot use export on a using or await using declaration. You can, however, export a variable that was declared elsewhere using using or await using . Doing so is still strongly discouraged, because the variable is disposed as soon as the module finishes executing, causing all importers to receive a value that's already disposed. js export using resource1 = getResource(); // SyntaxError // Allowed by syntax but discouraged using resource2 = getResource(); export { resource2 }; Export declarations are not subject to temporal dead zone rules. You can declare that the module exports X before the name X itself is declared. js export { x }; const x = 1; // This works, because `export` is only a declaration, but doesn't // utilize the value of `x`. Default exports: js // export feature declared elsewhere as default export { myFunction as default }; // This is equivalent to: export default myFunction; // export individual features as default export default function () { /* … */ } export default class { /* … */ } Note: Names for export declarations must be distinct from each other. Having exports with duplicate names or using more than one default export will result in a SyntaxError and prevent the module from being evaluated. The export default syntax allows any expression. js export default 1 + 1; As a special case, functions and classes are exported as declarations , not expressions, and these declarations can be anonymous. This means functions will be hoisted. js // Works because `foo` is a function declaration, // not a function expression foo(); export default function foo() { console.log("Hi"); } // It's still technically a declaration, but it's allowed // to be anonymous export default function () { console.log("Hi"); } Named exports are useful when you need to export several values. When importing this module, named exports must be referred to by the exact same name (optionally renaming it with as ), but the default export can be imported with any name. For example: js // file test.js const k = 12; export default k; js // some other file import m from "./test"; // note that we have the freedom to use import m instead of import k, because k was default export console.log(m); // 12 You can also rename named exports to avoid naming conflicts: js export { myFunction as function1, myVariable as variable }; You can rename a name to something that's not a valid identifier by using a string literal. For example: js export { myFunction as "my-function" }; Re-exporting / Aggregating A module can also "relay" values exported from other modules without the hassle of writing two separate import/export statements. This is often useful when creating a single module concentrating various exports from various modules (usually called a "barrel module"). This can be achieved with the "export from" syntax: js export { default as function1, function2 } from "bar.js"; Which is comparable to a combination of import and export, except that function1 and function2 do not become available inside the current module: js import { default as function1, function2 } from "bar.js"; export { function1, function2 }; Most of the "import from" syntaxes have "export from" counterparts. js export { x } from "mod"; export { x as v } from "mod"; export * as ns from "mod"; There is also export * from "mod" , although there's no import * from "mod" . This re-exports all named exports from mod as the named exports of the current module, but the default export of mod is not re-exported. If there are two wildcard exports statements that implicitly re-export the same name, neither one is re-exported. js // -- mod1.js -- export const a = 1; // -- mod2.js -- export const a = 3; // -- barrel.js -- export * from "./mod1.js"; export * from "./mod2.js"; // -- main.js -- import * as ns from "./barrel.js"; console.log(ns.a); // undefined Attempting to import the duplicate name directly will throw an error. js import { a } from "./barrel.js"; // SyntaxError: The requested module './barrel.js' contains conflicting star exports for name 'a' The following is syntactically invalid despite its import equivalent: js export DefaultExport from "bar.js"; // Invalid The correct way of doing this is to rename the export: js export { default as DefaultExport } from "bar.js"; The "export from" syntax allows the as token to be omitted, which makes the default export still re-exported as default export. js export { default, function2 } from "bar.js"; export from supports all features that import supports — for example, import attributes : js export { default } from "./data.json" with { type: "json" }; Examples Using named exports In a module my-module.js , we could include the following code: js // module "my-module.js" function cube(x) { return x * x * x; } const foo = Math.PI + Math.SQRT2; const graph = { options: { color: "white", thickness: "2px", }, draw() { console.log("From graph draw function"); }, }; export { cube, foo, graph }; Then in the top-level module included in your HTML page, we could have: js import { cube, foo, graph } from "./my-module.js"; graph.options = { color: "blue", thickness: "3px", }; graph.draw(); // Logs "From graph draw function" console.log(cube(3)); // 27 console.log(foo); // 4.555806215962888 It is important to note the following: You need to include this script in your HTML with a <script> element of type="module" , so that it gets recognized as a module and dealt with appropriately. You can't run JS modules via a file:// URL — you'll get CORS errors. You need to run it via an HTTP server. Using the default export If we want to export a single value representing an entire module, we could use a default export: js // module "cube.js" export default function cube(x) { return x * x * x; } Then, in another script, it is straightforward to import the default export: js import cube from "./cube.js"; console.log(cube(3)); // 27 Using export from Let's take an example where we have the following hierarchy: childModule1.js : exporting myFunction and myVariable childModule2.js : exporting MyClass parentModule.js : acting as an aggregator (and doing nothing else) top level module: consuming the exports of parentModule.js This is what it would look like using code snippets: js // In childModule1.js function myFunction() { console.log("Hello!"); } const myVariable = 1; export { myFunction, myVariable }; js // In childModule2.js class MyClass { constructor(x) { this.x = x; } } export { MyClass }; js // In parentModule.js // Only aggregating the exports from childModule1 and childModule2 // to re-export them export { myFunction, myVariable } from "childModule1.js"; export { MyClass } from "childModule2.js"; js // In top-level module // We can consume the exports from a single module since parentModule // "collected"/"bundled" them in a single source import { myFunction, myVariable, MyClass } from "parentModule.js"; Specifications Specification ECMAScript® 2026 Language Specification # sec-exports Browser compatibility Enable JavaScript to view this browser compatibility table. See also import JavaScript modules guide ES6 in Depth: Modules on hacks.mozilla.org (2015) ES modules: A cartoon deep-dive on hacks.mozilla.org (2018) Exploring JS, Ch.16: Modules by Dr. Axel Rauschmayer Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Jul 29, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar JavaScript Tutorials and guides JavaScript Guide Introduction Grammar and types Control flow and error handling Loops and iteration Functions Expressions and operators Numbers and strings Representing dates & times Regular expressions Indexed collections Keyed collections Working with objects Using classes Using promises JavaScript typed arrays Iterators and generators Resource management Internationalization JavaScript modules Intermediate Language overview JavaScript data structures Equality comparisons and sameness Enumerability and ownership of properties Closures Advanced Inheritance and the prototype chain Meta programming Memory Management References Built-in objects AggregateError Array ArrayBuffer AsyncDisposableStack AsyncFunction AsyncGenerator AsyncGeneratorFunction AsyncIterator Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date decodeURI() decodeURIComponent() DisposableStack encodeURI() encodeURIComponent() Error escape() Deprecated eval() EvalError FinalizationRegistry Float16Array Float32Array Float64Array Function Generator GeneratorFunction globalThis Infinity Int8Array Int16Array Int32Array InternalError Non-standard Intl isFinite() isNaN() Iterator JSON Map Math NaN Number Object parseFloat() parseInt() Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String SuppressedError Symbol SyntaxError Temporal TypedArray TypeError Uint8Array Uint8ClampedArray Uint16Array Uint32Array undefined unescape() Deprecated URIError WeakMap WeakRef WeakSet Expressions & operators Addition (+) Addition assignment (+=) Assignment (=) async function expression async function* expression await Bitwise AND (&) Bitwise AND assignment (&=) Bitwise NOT (~) Bitwise OR (|) Bitwise OR assignment (|=) Bitwise XOR (^) Bitwise XOR assignment (^=) class expression Comma operator (,) Conditional (ternary) operator Decrement (--) delete Destructuring Division (/) Division assignment (/=) Equality (==) Exponentiation (**) Exponentiation assignment (**=) function expression function* expression Greater than (>) Greater than or equal (>=) Grouping operator ( ) import.meta import.meta.resolve() import() in Increment (++) Inequality (!=) instanceof Left shift (<<) Left shift assignment (<<=) Less than (<) Less than or equal (<=) Logical AND (&&) Logical AND assignment (&&=) Logical NOT (!) Logical OR (||) Logical OR assignment (||=) Multiplication (*) Multiplication assignment (*=) new new.target null Nullish coalescing assignment (??=) Nullish coalescing operator (??) Object initializer Operator precedence Optional chaining (?.) Property accessors Remainder (%) Remainder assignment (%=) Right shift (>>) Right shift assignment (>>=) Spread syntax (...) Strict equality (===) Strict inequality (!==) Subtraction (-) Subtraction assignment (-=) super this typeof Unary negation (-) Unary plus (+) Unsigned right shift (>>>) Unsigned right shift assignment (>>>=) void operator yield yield* Statements & declarations async function async function* await using Block statement break class const continue debugger do...while Empty statement export Expression statement for for await...of for...in for...of function function* if...else import Import attributes Labeled statement let return switch throw try...catch using var while with Deprecated Functions Arrow function expressions Default parameters get Method definitions Rest parameters set The arguments object [Symbol.iterator]() callee Deprecated length Classes constructor extends Private elements Public class fields static Static initialization blocks Regular expressions Backreference: \1, \2 Capturing group: (...) Character class escape: \d, \D, \w, \W, \s, \S Character class: [...], [^...] Character escape: \n, \u{...} Disjunction: | Input boundary assertion: ^, $ Literal character: a, b Lookahead assertion: (?=...), (?!...) Lookbehind assertion: (?<=...), (?<!...) Modifier: (?ims-ims:...) Named backreference: \k<name> Named capturing group: (?<name>...) Non-capturing group: (?:...) Quantifier: *, +, ?, {n}, {n,}, {n,m} Unicode character class escape: \p{...}, \P{...} Wildcard: . Word boundary assertion: \b, \B Errors AggregateError: No Promise in Promise.any was resolved Error: Permission denied to access property "x" InternalError: too much recursion RangeError: argument is not a valid code point RangeError: BigInt division by zero RangeError: BigInt negative exponent RangeError: form must be one of 'NFC', 'NFD', 'NFKC', or 'NFKD' RangeError: invalid array length RangeError: invalid date RangeError: precision is out of range RangeError: radix must be an integer RangeError: repeat count must be less than infinity RangeError: repeat count must be non-negative RangeError: x can't be converted to BigInt because it isn't an integer ReferenceError: "x" is not defined ReferenceError: assignment to undeclared variable "x" ReferenceError: can't access lexical declaration 'X' before initialization ReferenceError: must call super constructor before using 'this' in derived class constructor ReferenceError: super() called twice in derived class constructor SyntaxError: 'arguments'/'eval' can't be defined or assigned to in strict mode code SyntaxError: "0"-prefixed octal literals are deprecated SyntaxError: "use strict" not allowed in function with non-simple parameters SyntaxError: "x" is a reserved identifier SyntaxError: \ at end of pattern SyntaxError: a declaration in the head of a for-of loop can't have an initializer SyntaxError: applying the 'delete' operator to an unqualified name is deprecated SyntaxError: arguments is not valid in fields SyntaxError: await is only valid in async functions, async generators and modules SyntaxError: await/yield expression can't be used in parameter SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions SyntaxError: character class escape cannot be used in class range in regular expression SyntaxError: continue must be inside loop SyntaxError: duplicate capture group name in regular expression SyntaxError: duplicate formal argument x SyntaxError: for-in loop head declarations may not have initializers SyntaxError: function statement requires a name SyntaxError: functions cannot be labelled SyntaxError: getter and setter for private name #x should either be both static or non-static SyntaxError: getter functions must have no arguments SyntaxError: identifier starts immediately after numeric literal SyntaxError: illegal character SyntaxError: import declarations may only appear at top level of a module SyntaxError: incomplete quantifier in regular expression SyntaxError: invalid assignment left-hand side SyntaxError: invalid BigInt syntax SyntaxError: invalid capture group name in regular expression SyntaxError: invalid character in class in regular expression SyntaxError: invalid class set operation in regular expression SyntaxError: invalid decimal escape in regular expression SyntaxError: invalid identity escape in regular expression SyntaxError: invalid named capture reference in regular expression SyntaxError: invalid property name in regular expression SyntaxError: invalid range in character class SyntaxError: invalid regexp group SyntaxError: invalid regular expression flag "x" SyntaxError: invalid unicode escape in regular expression SyntaxError: JSON.parse: bad parsing SyntaxError: label not found SyntaxError: missing : after property id SyntaxError: missing ) after argument list SyntaxError: missing ) after condition SyntaxError: missing ] after element list SyntaxError: missing } after function body SyntaxError: missing } after property list SyntaxError: missing = in const declaration SyntaxError: missing formal parameter SyntaxError: missing name after . operator SyntaxError: missing variable name SyntaxError: negated character class with strings in regular expression SyntaxError: new keyword cannot be used with an optional chain SyntaxError: nothing to repeat SyntaxError: numbers out of order in {} quantifier. SyntaxError: octal escape sequences can't be used in untagged template literals or in strict mode code SyntaxError: parameter after rest parameter SyntaxError: private fields can't be deleted SyntaxError: property name __proto__ appears more than once in object literal SyntaxError: raw bracket is not allowed in regular expression with unicode flag SyntaxError: redeclaration of formal parameter "x" SyntaxError: reference to undeclared private field or method #x SyntaxError: rest parameter may not have a default SyntaxError: return not in function SyntaxError: setter functions must have one argument SyntaxError: string literal contains an unescaped line break SyntaxError: super() is only valid in derived class constructors SyntaxError: tagged template cannot be used with optional chain SyntaxError: Unexpected '#' used outside of class body SyntaxError: Unexpected token SyntaxError: unlabeled break must be inside loop or switch SyntaxError: unparenthesized unary expression can't appear on the left-hand side of '**' SyntaxError: use of super property/member accesses only valid within methods or eval code within methods SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed TypeError: 'x' is not iterable TypeError: "x" is (not) "y" TypeError: "x" is not a constructor TypeError: "x" is not a function TypeError: "x" is not a non-null object TypeError: "x" is read-only TypeError: already executing generator TypeError: BigInt value can't be serialized in JSON TypeError: calling a builtin X constructor without new is forbidden TypeError: can't access/set private field or method: object is not the right class TypeError: can't assign to property "x" on "y": not an object TypeError: can't convert BigInt to number TypeError: can't convert x to BigInt TypeError: can't define property "x": "obj" is not extensible TypeError: can't delete non-configurable array element TypeError: can't redefine non-configurable property "x" TypeError: can't set prototype of this object TypeError: can't set prototype: it would cause a prototype chain cycle TypeError: cannot use 'in' operator to search for 'x' in 'y' TypeError: class constructors must be invoked with 'new' TypeError: cyclic object value TypeError: derived class constructor returned invalid value x TypeError: getting private setter-only property TypeError: Initializing an object twice is an error with private fields/methods TypeError: invalid 'instanceof' operand 'x' TypeError: invalid Array.prototype.sort argument TypeError: invalid assignment to const "x" TypeError: Iterator/AsyncIterator constructor can't be used directly TypeError: matchAll/replaceAll must be called with a global RegExp TypeError: More arguments needed TypeError: null/undefined has no properties TypeError: property "x" is non-configurable and can't be deleted TypeError: Reduce of empty array with no initial value TypeError: setting getter-only property "x" TypeError: WeakSet key/WeakMap value 'x' must be an object or an unregistered symbol TypeError: X.prototype.y called on incompatible type URIError: malformed URI sequence Warning: -file- is being assigned a //# sourceMappingURL, but already has one Warning: unreachable code after return statement Misc JavaScript technologies overview Execution model Lexical grammar Iteration protocols Strict mode Template literals Trailing commas Deprecated features Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:48:43 |
https://docs.suprsend.com/docs/inbox-overview#integrating-suprsend-inbox | Overview - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Notification Inbox Overview Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Notification Inbox Overview OpenAI Open in ChatGPT Learn about features and benefits of SuprSend’s notification inbox, with link to live demo and git repository. OpenAI Open in ChatGPT A notification inbox is a centralized place for all your in-app notifications, offering several advantages over other notification channels. With a notification inbox, users can receive real-time transactional updates related to payment reminders, software updates, new features, etc. within the app. You can use SuprSend Inbox to easily integrate feeds, inboxes, and toasts into your product. Check Live demo in Inbox Playground Benefits of notification inbox over other communication channels Real-time updates: A notification inbox delivers real-time updates to users, providing timely and relevant information. 100% deliverability: Notifications sent through a notification inbox have a high deliverability rate and are perfect for sending important updates and messages. Flexibility in message design: There is no limitation to the type and length of content that you can send with Inbox. Hence, the messages can be designed as per your requirement. Plus, you can add any type of click action to inbox message components which offer great flexibility in driving user engagement. Integrating SuprSend inbox With SuprSend Inbox, You can effortlessly add a beautifully designed, highly functional inbox to your product in an hour. There is no infrastructure required at your end to manage and store inbox notifications, and for state management such as read, seen, and archive tracking You get ready components to handle any use such as showing toast, showing profile avatar in your notification, handling different click actions in your notification component, etc. Inbox messages are completely secure with HMAC encoded user identification to safeguard them from unauthorized access. This means you can use it to send sensitive information related to payments, billing, account updates, etc. You can customize it to match your brand style using pre-defined UI customization options or build your headless UI using hooks SDKs are available in all common languages React (Web) Angular (Web) React Native (App) Flutter (App) Was this page helpful? Yes No Suggest edits Raise issue Previous Multi Tabs Learn how to set up stores to filter and display notifications in separate inbox tabs such as Read, Unread, and more. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of notification inbox over other communication channels Integrating SuprSend inbox | 2026-01-13T08:48:43 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#chunking | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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:43 |
https://dev.to/szabgab/perl-weekly-755-does-tiobe-help-perl-a4b#main-content | Perl 🐪 Weekly #755 - Does TIOBE help 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 12 • Originally published at perlweekly.com Perl 🐪 Weekly #755 - Does TIOBE help 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 755 Hi there! Dave Cross has an article showing position of Perl on the TIOBE index. As I don't see any up-tick in new subscribers to the Perl Weekly nor do I see any increase in the MetaCPAN activity I keep track of, I doubt that the changes in the position reflects actual changes in the market. However I wonder, could the TIOBE index have an impact on the interest in Perl? How and when could we see that? Speaking of the MetaCPAN report , I'd love if someone sent a PR to the Perl Weekly that would generates same graphs using these numbers. Here is the issue for it. And another comment related to those stats. I just noticed that the No CI column went up from 30-40% to 80-90% in recent weeks. I wonder why? Is it because some changes in the way I am collecting the data or are those real changes? Is it real change? I also just noticed some negative numbers in the No VCS (%) column. That's not good. I guess I have to investigate this. Maybe during one of the Perl code reading and open source contribution events. Enjoy your week! -- Your editor: Gabor Szabo. Announcements New York Perlmongers (NY.PM) New York Perlmongers ( NY.PM ) has a new mailing-list organized as a Google Group. Sign up here . (Note: we are not doing unrequested transfers from our previous mailing list.) NY.PM social event: Thursday, January 15, 6:00 pm EST at Barcade, 148 West 24 St, Manhattan: send-off for a long-time member returning to the U.K. ANNOUNCE: Perl.Wiki V 1.37 Get it, as usual, from his Wiki Haven . Articles Marlin Racing Which of the 7 OOP frameworks of Perl is the fastest? The Perl Claude Agent It's a library that brings the agentic capabilities of Claude Code into your Perl applications. Manwar sending a Pull-Request to JQ::Lite This video was recorded during the most recent Perl code reading and open source contribution event. For links check out the OSDC Perl page and join us at our next event! Perl in the TIOBE Index See also the discussion . DBIx::Class::Async - UPDATE Discussion nfo - a user-friendly info reader Why do you need Perl for this? - asks the first commenter. convert string to regex Allowing your users to put regexes in a configuration file. Is it a good idea? How to do it? MetaCPAN perlmodules.net is (was) down for 1-2 weeks Is the MetaCPAN API changing? The ElasticSearch upgrade on MetaCPAN impaceted a number of other web site, but it seems things are working again. Perl This week in PSC (210) | 2026-01-05 The Weekly Challenge The Weekly Challenge by Mohammad Sajid Anwar will help you step out of your comfort-zone. You can even win prize money of $50 by participating in the weekly challenge. We pick one champion at the end of the month from among all of the contributors during the month, thanks to the sponsor Lance Wicks. The Weekly Challenge - 356 Welcome to a new week with a couple of fun tasks "Kolakoski Sequence" and "Who Wins". 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 - 355 Enjoy a quick recap of last week's contributions by Team PWC dealing with the "Thousand Separator" and "Mountain Array" tasks in Perl and Raku. You will find plenty of solutions to keep you busy. Mountain Separator The post demonstrates an idiomatic and compact use of Raku for typical programming challenges. It balances expressive language features with clarity, though readers unfamiliar with hyperoperators and the pipeline style might need supplemental explanation. Perl Weekly Challenge: Week 355 Technically solid, readable, and well-structured. The solutions are both correct and practical, illustrating good problem decomposition and Perl/Raku coding style. Separated Mountains Efficient and idiomatic Perl for the thousand separator using a classic unpack pattern.️ A formally defined mountain array solution with vectorised and language-diverse implementations. number formatting and sorting This is a well‑engineered, comprehensive, and professionally presented technical write‑up that goes beyond minimal solutions to showcase how to solve the Weekly Challenge across ecosystems. It favors clarity and breadth over micro‑optimizations, making it valuable for learners and polyglot developers alike. Perl Weekly Challenge 355 The solutions for Weekly Challenge #355 are technically strong, correct, and efficient. Task 2 (Mountain Array) leverages PDL for vectorized comparisons, producing a concise, single-pass check for mountain arrays while correctly handling edge cases such as plateaus and short arrays. Thousand Mountains This is technically excellent, showing a high level of Perl proficiency, algorithmic awareness, and performance consciousness. Both tasks are solved correctly, with multiple alternative implementations explored and benchmarked, demonstrating a thoughtful and professional approach rather than a "just pass the tests" mentality. Oh to live on Array Mountain… This post is a strong, well-executed multi-language technical write-up that emphasizes algorithmic reasoning, clarity of transformation, and comparative programming paradigms over minimalism or raw performance. Thousands of mountains This submission demonstrates strong problem understanding, solid algorithmic choices, and pragmatic Perl coding. The solutions are intentionally explicit, readable, and correct, favoring clarity and single-pass logic over clever one-liners. Both tasks are handled with approaches that scale reasonably and align well with Perl’s strengths. The Weekly Challenge #355 This submission is technically strong, correct, and deliberately written for clarity and maintainability rather than brevity. It reflects an experienced Perl programmer who values explicit logic, readable structure, and thorough documentation. Mountains by the Thousand This is a thoughtful, well-structured solution to both Weekly Challenge tasks, with a clear emphasis on explicit logic and state-based reasoning rather than relying on library tricks. Roger demonstrates good cross-language fluency and a solid grasp of algorithm design. Commify every mountain This post delivers clean, pragmatic, and idiomatic solutions to both tasks in The Weekly Challenge #355. It emphasizes using the right tool for the job, clarity, and efficiency over algorithmic novelty. Weekly collections NICEPERL's lists Great CPAN modules released last week . Events Perl Maven online: Live Open Source contribution January 24, 2025 Boston.pm - online February 10, 2025 German Perl/Raku Workshop 2026 in Berlin March 16-18, 2025 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 #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:43 |
https://x.com/shlomiatar/status/1822381556142362734 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:43 |
https://dev.to/t/communication/page/7 | Communication 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 # communication Follow Hide Tips for talking effectively with your children at every age. Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Ambiguity hurts communication. And we should care about it Carlos Gándara Carlos Gándara Carlos Gándara Follow Dec 13 '20 Ambiguity hurts communication. And we should care about it # communication 8 reactions Comments 2 comments 4 min read Here's Why Remote Work Needs Asynchronous Communication Thomas De Moor Thomas De Moor Thomas De Moor Follow Dec 29 '20 Here's Why Remote Work Needs Asynchronous Communication # remoteworking # communication # remote # beginners 8 reactions Comments 1 comment 3 min read Let’s be clear on what a domain is SinnerSchrader Engineers SinnerSchrader Engineers SinnerSchrader Engineers Follow for Studio M - Song Dec 4 '20 Let’s be clear on what a domain is # domain # strategy # communication 5 reactions Comments Add Comment 2 min read 16 - ABC's of success: Authenticity, Balance and Communication with Bill Conyea Friends That Code podcast Friends That Code podcast Friends That Code podcast Follow Dec 3 '20 16 - ABC's of success: Authenticity, Balance and Communication with Bill Conyea # management # career # communication # startup 4 reactions Comments Add Comment 1 min read Violent communication Philipp Giese Philipp Giese Philipp Giese Follow Nov 30 '20 Violent communication # career # communication # speaking 3 reactions Comments 3 comments 5 min read Communication for Developers Luka Baramishvili Luka Baramishvili Luka Baramishvili Follow Nov 11 '20 Communication for Developers # webdev # thecollablab # juniordevelopers # communication 22 reactions Comments Add Comment 6 min read What I learned about communication from getting my husband's car fixed - and how that relates to web dev! 𝐍𝐚𝐭𝐚𝐥𝐢𝐞 𝐝𝐞 𝐖𝐞𝐞𝐫𝐝 𝐍𝐚𝐭𝐚𝐥𝐢𝐞 𝐝𝐞 𝐖𝐞𝐞𝐫𝐝 𝐍𝐚𝐭𝐚𝐥𝐢𝐞 𝐝𝐞 𝐖𝐞𝐞𝐫𝐝 Follow Nov 8 '20 What I learned about communication from getting my husband's car fixed - and how that relates to web dev! # communication # clients # management 9 reactions Comments 2 comments 5 min read Interview Guide for Software Developers - Part 2: Ace the Coding Interview Udara Weerasinghege Udara Weerasinghege Udara Weerasinghege Follow Nov 3 '20 Interview Guide for Software Developers - Part 2: Ace the Coding Interview # interview # jobsearch # programming # communication 2 reactions Comments Add Comment 5 min read Code comments are a sign that something's off Alex Bunardzic Alex Bunardzic Alex Bunardzic Follow Oct 29 '20 Code comments are a sign that something's off # softwaredevelopment # codecomments # communication # collaboration 4 reactions Comments 17 comments 6 min read Selling Refactoring Vaidotas Piekus Vaidotas Piekus Vaidotas Piekus Follow Oct 21 '20 Selling Refactoring # javascript # refactoring # communication 3 reactions Comments Add Comment 3 min read How to Listen Better in a Remote Environment Thomas De Moor Thomas De Moor Thomas De Moor Follow for X-Team Oct 27 '20 How to Listen Better in a Remote Environment # communication # career # productivity # remote 17 reactions Comments Add Comment 5 min read Low-Bandwidth Communication bob.ts bob.ts bob.ts Follow Sep 8 '20 Low-Bandwidth Communication # watercooler # communication # remote # career 7 reactions Comments Add Comment 2 min read In case of doubt, ask for clarification Dan Lebrero Dan Lebrero Dan Lebrero Follow Sep 6 '20 In case of doubt, ask for clarification # humour # communication # softskills 8 reactions Comments Add Comment 1 min read Managing Technical Debt in Software Aman Agrawal Aman Agrawal Aman Agrawal Follow for Coolblue Aug 31 '20 Managing Technical Debt in Software # techdebt # heuristics # communication # agile 6 reactions Comments 1 comment 9 min read The art of giving and receiving feedback 💌 Ségolène Alquier Ségolène Alquier Ségolène Alquier Follow Aug 17 '20 The art of giving and receiving feedback 💌 # management # communication # team # tips 54 reactions Comments 4 comments 3 min read Reasons why you Should be recruited for an Internship interviewcrackerforyou interviewcrackerforyou interviewcrackerforyou Follow Aug 13 '20 Reasons why you Should be recruited for an Internship # communication # hiring # purposeofinternship # recruiters 3 reactions Comments Add Comment 5 min read Communication Tips for Engineers Mischa Spiegelmock Mischa Spiegelmock Mischa Spiegelmock Follow Aug 4 '20 Communication Tips for Engineers # communication 32 reactions Comments Add Comment 4 min read Start naming your test doubles correctly Chris James Chris James Chris James Follow Jul 30 '20 Start naming your test doubles correctly # testing # tdd # communication # mocking 10 reactions Comments Add Comment 4 min read The Two Most Important Traits for Working on Anything with Anyone Christian Christian Christian Follow Jul 26 '20 The Two Most Important Traits for Working on Anything with Anyone # teamwork # essentialism # communication # webdev 4 reactions Comments Add Comment 3 min read Git, Linters and SourceLevel: how tools enable a more inclusive language and diverse culture Weverton Timoteo Weverton Timoteo Weverton Timoteo Follow for SourceLevel Jul 22 '20 Git, Linters and SourceLevel: how tools enable a more inclusive language and diverse culture # developmenttools # git # communication # inclusivelanguage 6 reactions Comments Add Comment 4 min read How to Ask Better Questions Thomas De Moor Thomas De Moor Thomas De Moor Follow for X-Team Jul 21 '20 How to Ask Better Questions # growth # communication # beginners # productivity 10 reactions Comments 1 comment 4 min read Remote Team: The Top Secret to Good Communication Saheed Oladosu Saheed Oladosu Saheed Oladosu Follow Jul 5 '20 Remote Team: The Top Secret to Good Communication # communication # productivity # career # webdev 4 reactions Comments Add Comment 3 min read Slow Down and Get Noticed Michael D. Callaghan Michael D. Callaghan Michael D. Callaghan Follow Jul 1 '20 Slow Down and Get Noticed # career # communication # business 4 reactions Comments Add Comment 5 min read Asking better questions Josefine Schfr Josefine Schfr Josefine Schfr Follow Jun 15 '20 Asking better questions # beginners # questions # womenintech # communication 10 reactions Comments Add Comment 3 min read DIRECT - The seven core topics of remote team communication Jochen Lillich Jochen Lillich Jochen Lillich Follow Jun 5 '20 DIRECT - The seven core topics of remote team communication # teamwork # remote # communication 6 reactions Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV 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:43 |
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:43 |
https://highlight.io/frameworks | highlight.io: The open source monitoring platform. Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up Find the framework you need. Use your favorite frameworks with highlight.io. Frameworks React.js Set up highlight.io with your React application. Next.js Set up highlight.io with your Next application. Remix Set up highlight.io with your Remix application. Vue.js Set up highlight.io with your Vue application. Angular Set up highlight.io with your Angular application. Gatsby.js Set up highlight.io with your Gatsby application. SvelteKit Set up highlight.io with your SvelteKit application. Error Monitoring Go Set up error monitoring in Go with Chi, Fiber, and more. Javascript Set up error monitoring in JS with Express, Node, and more. Python Set up error monitoring in Python with Django, Flask, and more. Ruby Set up error monitoring in Ruby on Rails. Rust Set up error monitoring in Rust. Logging Go Set up logging in Go with Fiber, Logrus, and more. Javascript Set up logging in JS with Nest, Winston, and more. Python Set up logging in Python with Loguru. Ruby Set up logging in Ruby on Rails. Rust Set up logging in Rust. Protocols cURL Set up highlight.io log ingestion over HTTPS. File Set up log ingestion using an OpenTelemetry collector with the filelog receiver. Fluent Forward Set up highlight.io log ingestion via Fluent Forward. Are we missing anything? Reach out if you want support for another framework! Get in Touch Our customers Highlight powers forward-thinking companies. More about our customers → Don't take our word. Read our customer review section → Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Highlight helps us catch bugs that would otherwise go undetected and makes it easy to replicate and debug them. Max Musing , Founder & CEO Highlight weaves together the incredible, varied, and complex interactions of our users into something understandable and actionable. Kai Hess , Founding Product Designer I love Highlight because not only does it help me debug more quickly, but it gives me insight into how customers are actually using our product. Meryl Dakin , Founding Software Engineer Highlight has helped us win over several customers by making it possible for us to provide hands-on support, based on a detailed understanding of what each user was doing. Neil Raina , CTO Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:43 |
https://youtube.com/t/privacy | .gb_yb{font:13px/27px Roboto,Arial,sans-serif;z-index:986}@-webkit-keyframes gb__a{0%{opacity:0}50%{opacity:1}}@keyframes gb__a{0%{opacity:0}50%{opacity:1}}.gb_R{display:none}.gb_Q{-webkit-background-size:32px 32px;background-size:32px 32px;border:0;border-radius:50%;display:block;margin:0px;position:relative;height:32px;width:32px;z-index:0}.gb_kb{background-color:#e8f0fe;border:1px solid rgba(32,33,36,.08);position:relative}.gb_kb.gb_Q{height:30px;width:30px}.gb_kb.gb_Q:hover,.gb_kb.gb_Q:active{-webkit-box-shadow:none;box-shadow:none}.gb_lb{background:#fff;border:none;border-radius:50%;bottom:2px;-webkit-box-shadow:0px 1px 2px 0px rgba(60,64,67,0.3),0px 1px 3px 1px rgba(60,64,67,0.15);box-shadow:0px 1px 2px 0px rgba(60,64,67,0.3),0px 1px 3px 1px rgba(60,64,67,0.15);height:14px;margin:2px;position:absolute;right:0;width:14px;line-height:normal;z-index:1}.gb_mb{color:#1f71e7;font:400 22px/32px Google Sans,Roboto,Helvetica,Arial,sans-serif;text-align:center;text-transform:uppercase}@media (-webkit-min-device-pixel-ratio:1.25),(min-device-pixel-ratio:1.25),(min-resolution:1.25dppx){.gb_Q::before,.gb_nb::before{display:inline-block;-webkit-transform:scale(.5);-ms-transform:scale(.5);transform:scale(.5);-webkit-transform-origin:left 0;-ms-transform-origin:left 0;transform-origin:left 0}.gb_4 .gb_nb::before{-webkit-transform:scale(scale(.416666667));-ms-transform:scale(scale(.416666667));transform:scale(scale(.416666667))}}.gb_Q:hover,.gb_Q:focus{-webkit-box-shadow:0 1px 0 rgba(0,0,0,.15);box-shadow:0 1px 0 rgba(0,0,0,.15)}.gb_Q:active{-webkit-box-shadow:inset 0 2px 0 rgba(0,0,0,.15);box-shadow:inset 0 2px 0 rgba(0,0,0,.15)}.gb_Q:active::after{background:rgba(0,0,0,.1);border-radius:50%;content:"";display:block;height:100%}.gb_ob{cursor:pointer;line-height:40px;min-width:30px;opacity:.75;overflow:hidden;vertical-align:middle;text-overflow:ellipsis}.gb_B.gb_ob{width:auto}.gb_ob:hover,.gb_ob:focus{opacity:.85}.gb_pb .gb_ob,.gb_pb .gb_qb{line-height:26px}#gb#gb.gb_pb a.gb_ob,.gb_pb .gb_qb{font-size:11px;height:auto}.gb_rb{border-top:4px solid #000;border-left:4px dashed transparent;border-right:4px dashed transparent;display:inline-block;margin-left:6px;opacity:.75;vertical-align:middle}.gb_0a:hover .gb_rb{opacity:.85}.gb_Xa>.gb_z{padding:3px 3px 3px 4px}.gb_sb.gb_jb{color:#fff}.gb_2 .gb_ob,.gb_2 .gb_rb{opacity:1}#gb#gb.gb_2.gb_2 a.gb_ob,#gb#gb .gb_2.gb_2 a.gb_ob{color:#fff}.gb_2.gb_2 .gb_rb{border-top-color:#fff;opacity:1}.gb_la .gb_Q:hover,.gb_2 .gb_Q:hover,.gb_la .gb_Q:focus,.gb_2 .gb_Q:focus{-webkit-box-shadow:0 1px 0 rgba(0,0,0,0.15),0 1px 2px rgba(0,0,0,0.2);box-shadow:0 1px 0 rgba(0,0,0,0.15),0 1px 2px rgba(0,0,0,0.2)}.gb_tb .gb_z,.gb_ub .gb_z{position:absolute;right:1px}.gb_z.gb_1,.gb_vb.gb_1,.gb_0a.gb_1{-webkit-box-flex:0;-webkit-flex:0 1 auto;flex:0 1 auto}.gb_wb.gb_xb .gb_ob{width:30px!important}.gb_P{height:40px;position:absolute;right:-5px;top:-5px;width:40px}.gb_yb .gb_P,.gb_zb .gb_P{right:0;top:0}.gb_Vc.gb_he:focus-visible{outline:1px solid #202124;border-radius:4px}.gb_2c .gb_Vc.gb_he:focus-visible{outline-color:#f1f3f4}.gb_Tc{display:inline-block;position:relative;overflow:hidden;top:2px;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.gb_de{max-width:100%}.gb_ee .gb_Tc{display:none}.gb_Kd .gb_Uc{line-height:normal;position:relative;padding-left:16px}.gb_rd.gb_sd .gb_Uc{padding-left:0}.gb_rd .gb_Uc{padding-left:12px}.gb_Vc{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-box;display:-webkit-flex;display:flex;outline:none;text-decoration:none}.gb_Vc.gb_fe{direction:ltr}.gb_Vc.gb_fe .gb_Qd{padding-left:8px;padding-right:0}.gb_e .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_clr_74x24px.svg);background-repeat:no-repeat;background-position:center;-webkit-background-size:contain;background-size:contain;content:"";display:inline-block;height:24px;width:74px}.gb_Vc .gb_ge{height:24px;width:74px}.gb_Vc .gb_ge,.gb_Vc{vertical-align:middle}.gb_Vc .gb_ge{display:inline-block;outline:none}.gb_8a{display:inline-block;vertical-align:middle}.gb_Zc{border:none;display:block;visibility:hidden}img.gb_0c{border:0;vertical-align:middle}.gb_3a:not(.gb_H) .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_surface_dark_74x24px.svg)}.gb_2a:not(.gb_H) .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_on_surface_dark_74x24px.svg)}.gb_e.gb_bd .gb_Vc .gb_ge::before,.gb_e.gb_H .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_light_clr_74x24px.svg)}.gb_2a.gb_H .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_on_surface_light_74x24px.svg)}@media screen and (-ms-high-contrast:black-on-white){.gb_e .gb_2c .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_dark_clr_74x24px.svg)}}@media screen and (-ms-high-contrast:white-on-black){.gb_9d .gb_Vc .gb_ge::before{background-image:url(https://www.gstatic.com/images/branding/googlelogo/svg/googlelogo_light_clr_74x24px.svg)}}.gb_8a{background-repeat:no-repeat}.gb_Qd{display:block;font-family:"Product Sans",Arial,sans-serif;font-size:22px;line-height:48px;overflow:hidden;padding-left:8px;position:relative;text-overflow:ellipsis;top:-1.5px;vertical-align:middle}.gb_rd .gb_Qd{padding-left:4px}.gb_rd .gb_Qd.gb_ie{padding-left:0}.gb_0c.gb_ae{padding-right:4px}.gb_bd .gb_qd.gb_Qd{opacity:1}.gb_de:focus .gb_Qd{text-decoration:underline}.gb_je img.gb_0c{margin-bottom:4px}.gb_ke{display:none}.gb_1c{border-radius:50%;-moz-outline-radius:50%;display:inline-block;margin:0 4px;padding:12px;overflow:hidden;vertical-align:middle;cursor:pointer;height:24px;width:24px;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-box-flex:0;-webkit-flex:0 0 auto;flex:0 0 auto}.gb_9a .gb_1c{margin:0 4px 0 0}.gb_1c:focus:not(:focus-visible){outline:none}.gb_1c:focus-visible{outline:1px solid #202124;outline-offset:-1px}.gb_2c .gb_1c:focus-visible{outline:1px solid #f1f3f4}.gb_1c:focus:focus-visible,.gb_1c:focus-visible,.gb_1c:focus,.gb_1c:focus:hover{background-color:rgba(60,64,67,.1)}.gb_1c:active{background-color:rgba(60,64,67,.12);outline:none}.gb_1c:hover{background-color:rgba(60,64,67,.08);outline:none}.gb_2c .gb_1c:hover{background-color:rgba(232,234,237,.08)}.gb_2c .gb_1c:focus,.gb_2c .gb_1c:focus:hover{background-color:rgba(232,234,237,.1)}.gb_2c .gb_1c:active{background-color:rgba(232,234,237,.12)}.gb_3c{display:none}.gb_4c{-webkit-transform:none;-ms-transform:none;transform:none}.gb_5c{display:none}.gb_6c{background-color:#fff;bottom:0;color:#000;height:calc(100vh - 100%);overflow-y:auto;overflow-x:hidden;position:absolute;top:100%;z-index:990;will-change:visibility;visibility:hidden;display:-webkit-box;display:-webkit-flex;display:flex;-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column;-webkit-transition:visibility 0s linear .25s,-webkit-transform .25s cubic-bezier(.4,0,.2,1);transition:visibility 0s linear .25s,-webkit-transform .25s cubic-bezier(.4,0,.2,1);transition:transform .25s cubic-bezier(.4,0,.2,1),visibility 0s linear .25s;transition:transform .25s cubic-bezier(.4,0,.2,1),visibility 0s linear .25s,-webkit-transform .25s cubic-bezier(.4,0,.2,1)}.gb_6c.gb_7c{height:inherit}.gb_6c.gb_8c.gb_9c,.gb_6c.gb_8c.gb_9c:hover{overflow:visible}.gb_6c.gb_9a{width:264px;-webkit-transform:translateX(-264px);-ms-transform:translateX(-264px);transform:translateX(-264px)}.gb_6c:not(.gb_9a){width:280px;-webkit-transform:translateX(-280px);-ms-transform:translateX(-280px);transform:translateX(-280px)}.gb_ad .gb_6c{width:195px}.gb_6c.gb_5a{-webkit-transform:translateX(0);-ms-transform:translateX(0);transform:translateX(0);visibility:visible;-webkit-box-shadow:0 0 16px rgba(0,0,0,.28);box-shadow:0 0 16px rgba(0,0,0,.28);-webkit-transition:visibility 0s linear 0s,-webkit-transform .25s cubic-bezier(.4,0,.2,1);transition:visibility 0s linear 0s,-webkit-transform .25s cubic-bezier(.4,0,.2,1);transition:transform .25s cubic-bezier(.4,0,.2,1),visibility 0s linear 0s;transition:transform .25s cubic-bezier(.4,0,.2,1),visibility 0s linear 0s,-webkit-transform .25s cubic-bezier(.4,0,.2,1)}.gb_6c.gb_bd{background-color:rgb(32,33,36);color:#e8eaed}.gb_cd.gb_dd{background-color:transparent;-webkit-box-shadow:0 0;box-shadow:0 0}.gb_cd.gb_dd>:not(.gb_ed){display:none}.gb_ed{display:-webkit-box;display:-webkit-flex;display:flex;-webkit-box-flex:1;-webkit-flex:1 1 auto;flex:1 1 auto;-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column}.gb_ed>.gb_fd{-webkit-box-flex:1;-webkit-flex:1 0 auto;flex:1 0 auto}.gb_ed>.gb_gd{-webkit-box-flex:0;-webkit-flex:0 0 auto;flex:0 0 auto}.gb_hd{list-style:none;margin-top:0;margin-bottom:0;padding:8px 0}.gb_6c:not(.gb_cd) .gb_hd:first-child{padding:0 0 8px 0}.gb_hd:not(:last-child){border-bottom:1px solid #ddd}.gb_bd .gb_hd:not(:last-child){border-bottom:1px solid #5f6368}.gb_bd .gb_id .gb_jd{background-color:rgb(32,33,36);border-bottom:1px solid #5f6368}.gb_kd{cursor:pointer}.gb_ld:empty{display:none}.gb_kd,.gb_ld{display:block;min-height:40px;padding-bottom:4px;padding-top:4px;font-family:Roboto,Helvetica,Arial,sans-serif;color:rgba(0,0,0,.87)}.gb_bd .gb_kd{color:#e8eaed}.gb_bd .gb_ld{color:#9aa0a6}.gb_6c.gb_9a .gb_kd,.gb_6c:not(.gb_9a) .gb_ld{padding-left:16px}.gb_6c:not(.gb_9a) .gb_kd,.gb_6c:not(.gb_9a) .gb_ld{padding-left:24px}.gb_kd:hover{background:rgba(0,0,0,.12)}.gb_bd .gb_kd:hover{background:rgba(232,234,237,.08)}.gb_kd.gb_hb{background:rgba(0,0,0,.12);font-weight:bold;color:rgba(0,0,0,.87)}.gb_bd .gb_kd.gb_hb{background:rgba(232,234,237,.12);color:rgba(255,255,255,.87)}.gb_kd .gb_md{text-decoration:none;display:inline-block;width:100%}.gb_kd .gb_md:focus{outline:none}.gb_kd .gb_nd,.gb_ld{padding-left:32px;display:inline-block;line-height:40px;vertical-align:top;width:176px;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.gb_ad .gb_kd .gb_nd,.gb_ad .gb_ld{padding-left:16px;width:138px}.gb_ed.gb_da .gb_md:focus .gb_nd{text-decoration:underline}.gb_kd .gb_od{height:24px;width:24px;float:left;margin-top:8px;vertical-align:middle}.gb_id>*{display:block;min-height:48px}.gb_Ha.gb_9a .gb_id>*{padding-top:4px;padding-bottom:4px;padding-left:16px}.gb_Ha:not(.gb_9a) .gb_id>*{padding-top:8px;padding-bottom:8px;padding-left:24px}.gb_Ha:not(.gb_9a) .gb_rd .gb_Tc{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-box;display:-webkit-flex;display:flex}.gb_id .gb_Tc{display:table-cell;height:48px;vertical-align:middle}.gb_id .gb_jd{background-color:#f5f5f5;display:block}.gb_id .gb_jd .gb_vd{float:right}.gb_Ha.gb_9a .gb_id .gb_jd{padding:4px}.gb_Ha:not(.gb_9a) .gb_id .gb_jd{padding:8px}.gb_id .gb_ob{width:40px}.gb_id .gb_rb{position:absolute;right:0;top:50%}.gb_6c.gb_le{-webkit-overflow-scrolling:touch}.gb_6c .gb_de{text-decoration:none}.gb_6c .gb_Qd{display:inline;white-space:normal;word-break:break-all;word-break:break-word}body.gb_me [data-ogpc]{-webkit-transition:margin-left .25s cubic-bezier(.4,0,.2,1),visibility 0s linear .25s;transition:margin-left .25s cubic-bezier(.4,0,.2,1),visibility 0s linear .25s}body.gb_me.gb_ne [data-ogpc]{-webkit-transition:margin-left .25s cubic-bezier(.4,0,.2,1),visibility 0s linear 0s;transition:margin-left .25s cubic-bezier(.4,0,.2,1),visibility 0s linear 0s}body [data-ogpc]{margin-left:0}body.gb_ne [data-ogpc]{margin-left:280px}.gb_oe{cursor:pointer;padding:13px}.gb_pe{background-color:rgba(0,0,0,.1);-webkit-box-shadow:inset 1px 1px 3px rgba(0,0,0,.24);box-shadow:inset 1px 1px 3px rgba(0,0,0,.24);width:34px;height:17px;border-radius:8px;position:relative;-webkit-transition:background-color ease .15s;transition:background-color ease .15s}.gb_oe[aria-pressed=true] .gb_pe{background-color:rgba(255,255,255,.1)}.gb_qe{position:absolute;width:25px;height:25px;border-radius:50%;-webkit-box-shadow:0 0 2px rgba(0,0,0,.12),0 2px 4px rgba(0,0,0,.24);box-shadow:0 0 2px rgba(0,0,0,.12),0 2px 4px rgba(0,0,0,.24);top:-4px;-webkit-transform:translateX(-12px);-ms-transform:translateX(-12px);transform:translateX(-12px);background-color:white;-webkit-transition:-webkit-transform ease .15s;transition:-webkit-transform ease .15s;transition:transform ease .15s;transition:transform ease .15s,-webkit-transform ease .15s}.gb_oe[aria-pressed=true] .gb_qe{-webkit-transform:translateX(20px);-ms-transform:translateX(20px);transform:translateX(20px)}.gb_qe img{position:absolute;margin:5px;width:15px;height:15px}.gb_re{line-height:0;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none}.gb_1d>.gb_re:only-child{float:right}.gb_re .gb_se{display:inline-block}.gb_re .gb_Ed{cursor:pointer}.gb_re .gb_Ed img{opacity:.54;width:24px;height:24px;padding:10px}.gb_2c .gb_re .gb_Ed img{opacity:1}.gb_j{text-align:right}.gb_se{text-align:initial}.gb_re .gb_te,.gb_re .gb_ue{display:table-cell;height:48px;vertical-align:middle}.gb_re .gb_te:not(.gb_ve){overflow:hidden}.gb_we{padding-left:16px}.gb_we:not(.gb_9a){padding-left:24px}.gb_xe{color:black;opacity:.54}.gb_ye{background:white;-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);overflow-y:hidden;position:absolute;right:24px;top:48px}a.gb_Va{border-radius:100px;background:#0b57d0;background:var(--gm3-sys-color-primary,#0b57d0);-webkit-box-sizing:border-box;box-sizing:border-box;color:#fff;color:var(--gm3-sys-color-on-primary,#fff);display:inline-block;font-size:14px;font-weight:500;min-height:40px;outline:none;padding:10px 24px;text-align:center;text-decoration:none;white-space:normal;line-height:18px;position:relative}a.gb_Wa{border-radius:100px;border:1px solid;border-color:#747775;border-color:var(--gm3-sys-color-outline,#747775);background:none;-webkit-box-sizing:border-box;box-sizing:border-box;color:#0b57d0;color:var(--gm3-sys-color-primary,#0b57d0);display:inline-block;font-size:14px;font-weight:500;min-height:40px;outline:none;padding:10px 24px;text-align:center;text-decoration:none;white-space:normal;line-height:18px;position:relative}.gb_1a.gb_H a.gb_Va,.gb_2a.gb_H a.gb_Va,.gb_3a.gb_H a.gb_Va{background:#c2e7ff;background:var(--gm3-sys-color-secondary-fixed,#c2e7ff);color:#001d35;color:var(--gm3-sys-color-on-secondary-fixed,#001d35)}.gb_Ha.gb_H a.gb_Wa{color:#a8c7fa;color:var(--gm3-sys-color-primary,#a8c7fa)}a.gb_Od{padding:10px 12px;margin:12px 16px 12px 10px;min-width:85px}@media (max-width:640px){a.gb_Od{min-width:75px}}.gb_Ha,.gb_Dd{font-family:"Google Sans Text",Roboto,Helvetica,Arial,sans-serif;font-style:normal}.gb_Ha.gb_1a{color:#1f1f1f;color:var(--og-bar-color,var(--gm3-sys-color-on-surface,#1f1f1f))}.gb_Ha.gb_1a.gb_Pd{background:#fff;background:var(--og-bar-background,var(--gm3-sys-color-background,#fff))}.gb_Ha.gb_1a .gb_pd.gb_qd,.gb_Ha.gb_1a a.gb_Z,.gb_Ha.gb_1a span.gb_Z{color:#1f1f1f;color:var(--og-link-color,var(--gm3-sys-color-on-surface,#1f1f1f))}.gb_Ha.gb_1a .gb_rd .gb_Qd,.gb_Ha.gb_1a .gb_id .gb_Qd{color:#1f1f1f;color:var(--og-logo-color,var(--gm3-sys-color-on-surface,#1f1f1f))}.gb_Ha.gb_1a svg{color:#444746;color:var(--og-svg-color,var(--gm3-sys-color-on-surface-variant,#444746))}@media (forced-colors:active) and (prefers-color-scheme:dark){.gb_Ha svg,.gb_Ha.gb_1a svg,.gb_Ha.gb_H svg{color:white}}.gb_Ha.gb_H.gb_1a{color:#e3e3e3;color:var(--og-bar-color,var(--gm3-sys-color-on-surface,#e3e3e3))}.gb_Ha.g | 2026-01-13T08:48:43 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#celebrate-those-incremental-improvements | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking 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 Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 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:43 |
https://docs.python.org/3/library/stdtypes.html#string-methods | Built-in Types — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents Built-in Types Truth Value Testing Boolean Operations — and , or , not Comparisons Numeric Types — int , float , complex Bitwise Operations on Integer Types Additional Methods on Integer Types Additional Methods on Float Additional Methods on Complex Hashing of numeric types Boolean Type - bool Iterator Types Generator Types Sequence Types — list , tuple , range Common Sequence Operations Immutable Sequence Types Mutable Sequence Types Lists Tuples Ranges Text and Binary Sequence Type Methods Summary Text Sequence Type — str String Methods Formatted String Literals (f-strings) Debug specifier Conversion specifier Format specifier Template String Literals (t-strings) printf -style String Formatting Binary Sequence Types — bytes , bytearray , memoryview Bytes Objects Bytearray Objects Bytes and Bytearray Operations printf -style Bytes Formatting Memory Views Set Types — set , frozenset Mapping Types — dict Dictionary view objects Context Manager Types Type Annotation Types — Generic Alias , Union Generic Alias Type Standard Generic Classes Special Attributes of GenericAlias objects Union Type Other Built-in Types Modules Classes and Class Instances Functions Methods Code Objects Type Objects The Null Object The Ellipsis Object The NotImplemented Object Internal Objects Special Attributes Integer string conversion length limitation Affected APIs Configuring the limit Recommended configuration Previous topic Built-in Constants Next topic Built-in Exceptions This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Standard Library » Built-in Types | Theme Auto Light Dark | Built-in Types ¶ The following sections describe the standard types that are built into the interpreter. The principal built-in types are numerics, sequences, mappings, classes, instances and exceptions. Some collection classes are mutable. The methods that add, subtract, or rearrange their members in place, and don’t return a specific item, never return the collection instance itself but None . Some operations are supported by several object types; in particular, practically all objects can be compared for equality, tested for truth value, and converted to a string (with the repr() function or the slightly different str() function). The latter function is implicitly used when an object is written by the print() function. Truth Value Testing ¶ Any object can be tested for truth value, for use in an if or while condition or as operand of the Boolean operations below. By default, an object is considered true unless its class defines either a __bool__() method that returns False or a __len__() method that returns zero, when called with the object. [ 1 ] If one of the methods raises an exception when called, the exception is propagated and the object does not have a truth value (for example, NotImplemented ). Here are most of the built-in objects considered false: constants defined to be false: None and False zero of any numeric type: 0 , 0.0 , 0j , Decimal(0) , Fraction(0, 1) empty sequences and collections: '' , () , [] , {} , set() , range(0) Operations and built-in functions that have a Boolean result always return 0 or False for false and 1 or True for true, unless otherwise stated. (Important exception: the Boolean operations or and and always return one of their operands.) Boolean Operations — and , or , not ¶ These are the Boolean operations, ordered by ascending priority: Operation Result Notes x or y if x is true, then x , else y (1) x and y if x is false, then x , else y (2) not x if x is false, then True , else False (3) Notes: This is a short-circuit operator, so it only evaluates the second argument if the first one is false. This is a short-circuit operator, so it only evaluates the second argument if the first one is true. not has a lower priority than non-Boolean operators, so not a == b is interpreted as not (a == b) , and a == not b is a syntax error. Comparisons ¶ There are eight comparison operations in Python. They all have the same priority (which is higher than that of the Boolean operations). Comparisons can be chained arbitrarily; for example, x < y <= z is equivalent to x < y and y <= z , except that y is evaluated only once (but in both cases z is not evaluated at all when x < y is found to be false). This table summarizes the comparison operations: Operation Meaning < strictly less than <= less than or equal > strictly greater than >= greater than or equal == equal != not equal is object identity is not negated object identity Unless stated otherwise, objects of different types never compare equal. The == operator is always defined but for some object types (for example, class objects) is equivalent to is . The < , <= , > and >= operators are only defined where they make sense; for example, they raise a TypeError exception when one of the arguments is a complex number. Non-identical instances of a class normally compare as non-equal unless the class defines the __eq__() method. Instances of a class cannot be ordered with respect to other instances of the same class, or other types of object, unless the class defines enough of the methods __lt__() , __le__() , __gt__() , and __ge__() (in general, __lt__() and __eq__() are sufficient, if you want the conventional meanings of the comparison operators). The behavior of the is and is not operators cannot be customized; also they can be applied to any two objects and never raise an exception. Two more operations with the same syntactic priority, in and not in , are supported by types that are iterable or implement the __contains__() method. Numeric Types — int , float , complex ¶ There are three distinct numeric types: integers , floating-point numbers , and complex numbers . In addition, Booleans are a subtype of integers. Integers have unlimited precision. Floating-point numbers are usually implemented using double in C; information about the precision and internal representation of floating-point numbers for the machine on which your program is running is available in sys.float_info . Complex numbers have a real and imaginary part, which are each a floating-point number. To extract these parts from a complex number z , use z.real and z.imag . (The standard library includes the additional numeric types fractions.Fraction , for rationals, and decimal.Decimal , for floating-point numbers with user-definable precision.) Numbers are created by numeric literals or as the result of built-in functions and operators. Unadorned integer literals (including hex, octal and binary numbers) yield integers. Numeric literals containing a decimal point or an exponent sign yield floating-point numbers. Appending 'j' or 'J' to a numeric literal yields an imaginary number (a complex number with a zero real part) which you can add to an integer or float to get a complex number with real and imaginary parts. The constructors int() , float() , and complex() can be used to produce numbers of a specific type. Python fully supports mixed arithmetic: when a binary arithmetic operator has operands of different numeric types, the operand with the “narrower” type is widened to that of the other, where integer is narrower than floating point. Arithmetic with complex and real operands is defined by the usual mathematical formula, for example: x + complex ( u , v ) = complex ( x + u , v ) x * complex ( u , v ) = complex ( x * u , x * v ) A comparison between numbers of different types behaves as though the exact values of those numbers were being compared. [ 2 ] All numeric types (except complex) support the following operations (for priorities of the operations, see Operator precedence ): Operation Result Notes Full documentation x + y sum of x and y x - y difference of x and y x * y product of x and y x / y quotient of x and y x // y floored quotient of x and y (1)(2) x % y remainder of x / y (2) -x x negated +x x unchanged abs(x) absolute value or magnitude of x abs() int(x) x converted to integer (3)(6) int() float(x) x converted to floating point (4)(6) float() complex(re, im) a complex number with real part re , imaginary part im . im defaults to zero. (6) complex() c.conjugate() conjugate of the complex number c divmod(x, y) the pair (x // y, x % y) (2) divmod() pow(x, y) x to the power y (5) pow() x ** y x to the power y (5) Notes: Also referred to as integer division. For operands of type int , the result has type int . For operands of type float , the result has type float . In general, the result is a whole integer, though the result’s type is not necessarily int . The result is always rounded towards minus infinity: 1//2 is 0 , (-1)//2 is -1 , 1//(-2) is -1 , and (-1)//(-2) is 0 . Not for complex numbers. Instead convert to floats using abs() if appropriate. Conversion from float to int truncates, discarding the fractional part. See functions math.floor() and math.ceil() for alternative conversions. float also accepts the strings “nan” and “inf” with an optional prefix “+” or “-” for Not a Number (NaN) and positive or negative infinity. Python defines pow(0, 0) and 0 ** 0 to be 1 , as is common for programming languages. The numeric literals accepted include the digits 0 to 9 or any Unicode equivalent (code points with the Nd property). See the Unicode Standard for a complete list of code points with the Nd property. All numbers.Real types ( int and float ) also include the following operations: Operation Result math.trunc(x) x truncated to Integral round(x[, n]) x rounded to n digits, rounding half to even. If n is omitted, it defaults to 0. math.floor(x) the greatest Integral <= x math.ceil(x) the least Integral >= x For additional numeric operations see the math and cmath modules. Bitwise Operations on Integer Types ¶ Bitwise operations only make sense for integers. The result of bitwise operations is calculated as though carried out in two’s complement with an infinite number of sign bits. The priorities of the binary bitwise operations are all lower than the numeric operations and higher than the comparisons; the unary operation ~ has the same priority as the other unary numeric operations ( + and - ). This table lists the bitwise operations sorted in ascending priority: Operation Result Notes x | y bitwise or of x and y (4) x ^ y bitwise exclusive or of x and y (4) x & y bitwise and of x and y (4) x << n x shifted left by n bits (1)(2) x >> n x shifted right by n bits (1)(3) ~x the bits of x inverted Notes: Negative shift counts are illegal and cause a ValueError to be raised. A left shift by n bits is equivalent to multiplication by pow(2, n) . A right shift by n bits is equivalent to floor division by pow(2, n) . Performing these calculations with at least one extra sign extension bit in a finite two’s complement representation (a working bit-width of 1 + max(x.bit_length(), y.bit_length()) or more) is sufficient to get the same result as if there were an infinite number of sign bits. Additional Methods on Integer Types ¶ The int type implements the numbers.Integral abstract base class . In addition, it provides a few more methods: int. bit_length ( ) ¶ Return the number of bits necessary to represent an integer in binary, excluding the sign and leading zeros: >>> n = - 37 >>> bin ( n ) '-0b100101' >>> n . bit_length () 6 More precisely, if x is nonzero, then x.bit_length() is the unique positive integer k such that 2**(k-1) <= abs(x) < 2**k . Equivalently, when abs(x) is small enough to have a correctly rounded logarithm, then k = 1 + int(log(abs(x), 2)) . If x is zero, then x.bit_length() returns 0 . Equivalent to: def bit_length ( self ): s = bin ( self ) # binary representation: bin(-37) --> '-0b100101' s = s . lstrip ( '-0b' ) # remove leading zeros and minus sign return len ( s ) # len('100101') --> 6 Added in version 3.1. int. bit_count ( ) ¶ Return the number of ones in the binary representation of the absolute value of the integer. This is also known as the population count. Example: >>> n = 19 >>> bin ( n ) '0b10011' >>> n . bit_count () 3 >>> ( - n ) . bit_count () 3 Equivalent to: def bit_count ( self ): return bin ( self ) . count ( "1" ) Added in version 3.10. int. to_bytes ( length = 1 , byteorder = 'big' , * , signed = False ) ¶ Return an array of bytes representing an integer. >>> ( 1024 ) . to_bytes ( 2 , byteorder = 'big' ) b'\x04\x00' >>> ( 1024 ) . to_bytes ( 10 , byteorder = 'big' ) b'\x00\x00\x00\x00\x00\x00\x00\x00\x04\x00' >>> ( - 1024 ) . to_bytes ( 10 , byteorder = 'big' , signed = True ) b'\xff\xff\xff\xff\xff\xff\xff\xff\xfc\x00' >>> x = 1000 >>> x . to_bytes (( x . bit_length () + 7 ) // 8 , byteorder = 'little' ) b'\xe8\x03' The integer is represented using length bytes, and defaults to 1. An OverflowError is raised if the integer is not representable with the given number of bytes. The byteorder argument determines the byte order used to represent the integer, and defaults to "big" . If byteorder is "big" , the most significant byte is at the beginning of the byte array. If byteorder is "little" , the most significant byte is at the end of the byte array. The signed argument determines whether two’s complement is used to represent the integer. If signed is False and a negative integer is given, an OverflowError is raised. The default value for signed is False . The default values can be used to conveniently turn an integer into a single byte object: >>> ( 65 ) . to_bytes () b'A' However, when using the default arguments, don’t try to convert a value greater than 255 or you’ll get an OverflowError . Equivalent to: def to_bytes ( n , length = 1 , byteorder = 'big' , signed = False ): if byteorder == 'little' : order = range ( length ) elif byteorder == 'big' : order = reversed ( range ( length )) else : raise ValueError ( "byteorder must be either 'little' or 'big'" ) return bytes (( n >> i * 8 ) & 0xff for i in order ) Added in version 3.2. Changed in version 3.11: Added default argument values for length and byteorder . classmethod int. from_bytes ( bytes , byteorder = 'big' , * , signed = False ) ¶ Return the integer represented by the given array of bytes. >>> int . from_bytes ( b ' \x00\x10 ' , byteorder = 'big' ) 16 >>> int . from_bytes ( b ' \x00\x10 ' , byteorder = 'little' ) 4096 >>> int . from_bytes ( b ' \xfc\x00 ' , byteorder = 'big' , signed = True ) -1024 >>> int . from_bytes ( b ' \xfc\x00 ' , byteorder = 'big' , signed = False ) 64512 >>> int . from_bytes ([ 255 , 0 , 0 ], byteorder = 'big' ) 16711680 The argument bytes must either be a bytes-like object or an iterable producing bytes. The byteorder argument determines the byte order used to represent the integer, and defaults to "big" . If byteorder is "big" , the most significant byte is at the beginning of the byte array. If byteorder is "little" , the most significant byte is at the end of the byte array. To request the native byte order of the host system, use sys.byteorder as the byte order value. The signed argument indicates whether two’s complement is used to represent the integer. Equivalent to: def from_bytes ( bytes , byteorder = 'big' , signed = False ): if byteorder == 'little' : little_ordered = list ( bytes ) elif byteorder == 'big' : little_ordered = list ( reversed ( bytes )) else : raise ValueError ( "byteorder must be either 'little' or 'big'" ) n = sum ( b << i * 8 for i , b in enumerate ( little_ordered )) if signed and little_ordered and ( little_ordered [ - 1 ] & 0x80 ): n -= 1 << 8 * len ( little_ordered ) return n Added in version 3.2. Changed in version 3.11: Added default argument value for byteorder . int. as_integer_ratio ( ) ¶ Return a pair of integers whose ratio is equal to the original integer and has a positive denominator. The integer ratio of integers (whole numbers) is always the integer as the numerator and 1 as the denominator. Added in version 3.8. int. is_integer ( ) ¶ Returns True . Exists for duck type compatibility with float.is_integer() . Added in version 3.12. Additional Methods on Float ¶ The float type implements the numbers.Real abstract base class . float also has the following additional methods. classmethod float. from_number ( x ) ¶ Class method to return a floating-point number constructed from a number x . 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.from_number(x) delegates to x.__float__() . If __float__() is not defined then it falls back to __index__() . Added in version 3.14. float. as_integer_ratio ( ) ¶ Return a pair of integers whose ratio is exactly equal to the original float. The ratio is in lowest terms and has a positive denominator. Raises OverflowError on infinities and a ValueError on NaNs. float. is_integer ( ) ¶ Return True if the float instance is finite with integral value, and False otherwise: >>> ( - 2.0 ) . is_integer () True >>> ( 3.2 ) . is_integer () False Two methods support conversion to and from hexadecimal strings. Since Python’s floats are stored internally as binary numbers, converting a float to or from a decimal string usually involves a small rounding error. In contrast, hexadecimal strings allow exact representation and specification of floating-point numbers. This can be useful when debugging, and in numerical work. float. hex ( ) ¶ Return a representation of a floating-point number as a hexadecimal string. For finite floating-point numbers, this representation will always include a leading 0x and a trailing p and exponent. classmethod float. fromhex ( s ) ¶ Class method to return the float represented by a hexadecimal string s . The string s may have leading and trailing whitespace. Note that float.hex() is an instance method, while float.fromhex() is a class method. A hexadecimal string takes the form: [ sign ] [ '0x' ] integer [ '.' fraction ] [ 'p' exponent ] where the optional sign may by either + or - , integer and fraction are strings of hexadecimal digits, and exponent is a decimal integer with an optional leading sign. Case is not significant, and there must be at least one hexadecimal digit in either the integer or the fraction. This syntax is similar to the syntax specified in section 6.4.4.2 of the C99 standard, and also to the syntax used in Java 1.5 onwards. In particular, the output of float.hex() is usable as a hexadecimal floating-point literal in C or Java code, and hexadecimal strings produced by C’s %a format character or Java’s Double.toHexString are accepted by float.fromhex() . Note that the exponent is written in decimal rather than hexadecimal, and that it gives the power of 2 by which to multiply the coefficient. For example, the hexadecimal string 0x3.a7p10 represents the floating-point number (3 + 10./16 + 7./16**2) * 2.0**10 , or 3740.0 : >>> float . fromhex ( '0x3.a7p10' ) 3740.0 Applying the reverse conversion to 3740.0 gives a different hexadecimal string representing the same number: >>> float . hex ( 3740.0 ) '0x1.d380000000000p+11' Additional Methods on Complex ¶ The complex type implements the numbers.Complex abstract base class . complex also has the following additional methods. classmethod complex. from_number ( x ) ¶ Class method to convert a number to a complex number. For a general Python object x , complex.from_number(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__() . Added in version 3.14. Hashing of numeric types ¶ For numbers x and y , possibly of different types, it’s a requirement that hash(x) == hash(y) whenever x == y (see the __hash__() method documentation for more details). For ease of implementation and efficiency across a variety of numeric types (including int , float , decimal.Decimal and fractions.Fraction ) Python’s hash for numeric types is based on a single mathematical function that’s defined for any rational number, and hence applies to all instances of int and fractions.Fraction , and all finite instances of float and decimal.Decimal . Essentially, this function is given by reduction modulo P for a fixed prime P . The value of P is made available to Python as the modulus attribute of sys.hash_info . CPython implementation detail: Currently, the prime used is P = 2**31 - 1 on machines with 32-bit C longs and P = 2**61 - 1 on machines with 64-bit C longs. Here are the rules in detail: If x = m / n is a nonnegative rational number and n is not divisible by P , define hash(x) as m * invmod(n, P) % P , where invmod(n, P) gives the inverse of n modulo P . If x = m / n is a nonnegative rational number and n is divisible by P (but m is not) then n has no inverse modulo P and the rule above doesn’t apply; in this case define hash(x) to be the constant value sys.hash_info.inf . If x = m / n is a negative rational number define hash(x) as -hash(-x) . If the resulting hash is -1 , replace it with -2 . The particular values sys.hash_info.inf and -sys.hash_info.inf are used as hash values for positive infinity or negative infinity (respectively). For a complex number z , the hash values of the real and imaginary parts are combined by computing hash(z.real) + sys.hash_info.imag * hash(z.imag) , reduced modulo 2**sys.hash_info.width so that it lies in range(-2**(sys.hash_info.width - 1), 2**(sys.hash_info.width - 1)) . Again, if the result is -1 , it’s replaced with -2 . To clarify the above rules, here’s some example Python code, equivalent to the built-in hash, for computing the hash of a rational number, float , or complex : import sys , math def hash_fraction ( m , n ): """Compute the hash of a rational number m / n. Assumes m and n are integers, with n positive. Equivalent to hash(fractions.Fraction(m, n)). """ P = sys . hash_info . modulus # Remove common factors of P. (Unnecessary if m and n already coprime.) while m % P == n % P == 0 : m , n = m // P , n // P if n % P == 0 : hash_value = sys . hash_info . inf else : # Fermat's Little Theorem: pow(n, P-1, P) is 1, so # pow(n, P-2, P) gives the inverse of n modulo P. hash_value = ( abs ( m ) % P ) * pow ( n , P - 2 , P ) % P if m < 0 : hash_value = - hash_value if hash_value == - 1 : hash_value = - 2 return hash_value def hash_float ( x ): """Compute the hash of a float x.""" if math . isnan ( x ): return object . __hash__ ( x ) elif math . isinf ( x ): return sys . hash_info . inf if x > 0 else - sys . hash_info . inf else : return hash_fraction ( * x . as_integer_ratio ()) def hash_complex ( z ): """Compute the hash of a complex number z.""" hash_value = hash_float ( z . real ) + sys . hash_info . imag * hash_float ( z . imag ) # do a signed reduction modulo 2**sys.hash_info.width M = 2 ** ( sys . hash_info . width - 1 ) hash_value = ( hash_value & ( M - 1 )) - ( hash_value & M ) if hash_value == - 1 : hash_value = - 2 return hash_value Boolean Type - bool ¶ Booleans represent truth values. The bool type has exactly two constant instances: True and False . The built-in function bool() converts any value to a boolean, if the value can be interpreted as a truth value (see section Truth Value Testing above). For logical operations, use the boolean operators and , or and not . When applying the bitwise operators & , | , ^ to two booleans, they return a bool equivalent to the logical operations “and”, “or”, “xor”. However, the logical operators and , or and != should be preferred over & , | and ^ . Deprecated since version 3.12: The use of the bitwise inversion operator ~ is deprecated and will raise an error in Python 3.16. bool is a subclass of int (see Numeric Types — int, float, complex ). In many numeric contexts, False and True behave like the integers 0 and 1, respectively. However, relying on this is discouraged; explicitly convert using int() instead. Iterator Types ¶ Python supports a concept of iteration over containers. This is implemented using two distinct methods; these are used to allow user-defined classes to support iteration. Sequences, described below in more detail, always support the iteration methods. One method needs to be defined for container objects to provide iterable support: container. __iter__ ( ) ¶ Return an iterator object. The object is required to support the iterator protocol described below. If a container supports different types of iteration, additional methods can be provided to specifically request iterators for those iteration types. (An example of an object supporting multiple forms of iteration would be a tree structure which supports both breadth-first and depth-first traversal.) This method corresponds to the tp_iter slot of the type structure for Python objects in the Python/C API. The iterator objects themselves are required to support the following two methods, which together form the iterator protocol : iterator. __iter__ ( ) ¶ Return the iterator object itself. This is required to allow both containers and iterators to be used with the for and in statements. This method corresponds to the tp_iter slot of the type structure for Python objects in the Python/C API. iterator. __next__ ( ) ¶ Return the next item from the iterator . If there are no further items, raise the StopIteration exception. This method corresponds to the tp_iternext slot of the type structure for Python objects in the Python/C API. Python defines several iterator objects to support iteration over general and specific sequence types, dictionaries, and other more specialized forms. The specific types are not important beyond their implementation of the iterator protocol. Once an iterator’s __next__() method raises StopIteration , it must continue to do so on subsequent calls. Implementations that do not obey this property are deemed broken. Generator Types ¶ Python’s generator s provide a convenient way to implement the iterator protocol. If a container object’s __iter__() method is implemented as a generator, it will automatically return an iterator object (technically, a generator object) supplying the __iter__() and __next__() methods. More information about generators can be found in the documentation for the yield expression . Sequence Types — list , tuple , range ¶ There are three basic sequence types: lists, tuples, and range objects. Additional sequence types tailored for processing of binary data and text strings are described in dedicated sections. Common Sequence Operations ¶ The operations in the following table are supported by most sequence types, both mutable and immutable. The collections.abc.Sequence ABC is provided to make it easier to correctly implement these operations on custom sequence types. This table lists the sequence operations sorted in ascending priority. In the table, s and t are sequences of the same type, n , i , j and k are integers and x is an arbitrary object that meets any type and value restrictions imposed by s . The in and not in operations have the same priorities as the comparison operations. The + (concatenation) and * (repetition) operations have the same priority as the corresponding numeric operations. [ 3 ] Operation Result Notes x in s True if an item of s is equal to x , else False (1) x not in s False if an item of s is equal to x , else True (1) s + t the concatenation of s and t (6)(7) s * n or n * s equivalent to adding s to itself n times (2)(7) s[i] i th item of s , origin 0 (3)(8) s[i:j] slice of s from i to j (3)(4) s[i:j:k] slice of s from i to j with step k (3)(5) len(s) length of s min(s) smallest item of s max(s) largest item of s Sequences of the same type also support comparisons. In particular, tuples and lists are compared lexicographically by comparing corresponding elements. This means that to compare equal, every element must compare equal and the two sequences must be of the same type and have the same length. (For full details see Comparisons in the language reference.) Forward and reversed iterators over mutable sequences access values using an index. That index will continue to march forward (or backward) even if the underlying sequence is mutated. The iterator terminates only when an IndexError or a StopIteration is encountered (or when the index drops below zero). Notes: While the in and not in operations are used only for simple containment testing in the general case, some specialised sequences (such as str , bytes and bytearray ) also use them for subsequence testing: >>> "gg" in "eggs" True Values of n less than 0 are treated as 0 (which yields an empty sequence of the same type as s ). Note that items in the sequence s are not copied; they are referenced multiple times. This often haunts new Python programmers; consider: >>> lists = [[]] * 3 >>> lists [[], [], []] >>> lists [ 0 ] . append ( 3 ) >>> lists [[3], [3], [3]] What has happened is that [[]] is a one-element list containing an empty list, so all three elements of [[]] * 3 are references to this single empty list. Modifying any of the elements of lists modifies this single list. You can create a list of different lists this way: >>> lists = [[] for i in range ( 3 )] >>> lists [ 0 ] . append ( 3 ) >>> lists [ 1 ] . append ( 5 ) >>> lists [ 2 ] . append ( 7 ) >>> lists [[3], [5], [7]] Further explanation is available in the FAQ entry How do I create a multidimensional list? . If i or j is negative, the index is relative to the end of sequence s : len(s) + i or len(s) + j is substituted. But note that -0 is still 0 . The slice of s from i to j is defined as the sequence of items with index k such that i <= k < j . If i is omitted or None , use 0 . If j is omitted or None , use len(s) . If i or j is less than -len(s) , use 0 . If i or j is greater than len(s) , use len(s) . If i is greater than or equal to j , the slice is empty. The slice of s from i to j with step k is defined as the sequence of items with index x = i + n*k such that 0 <= n < (j-i)/k . In other words, the indices are i , i+k , i+2*k , i+3*k and so on, stopping when j is reached (but never including j ). When k is positive, i and j are reduced to len(s) if they are greater. When k is negative, i and j are reduced to len(s) - 1 if they are greater. If i or j are omitted or None , they become “end” values (which end depends on the sign of k ). Note, k cannot be zero. If k is None , it is treated like 1 . Concatenating immutable sequences always results in a new object. This means that building up a sequence by repeated concatenation will have a quadratic runtime cost in the total sequence length. To get a linear runtime cost, you must switch to one of the alternatives below: if concatenating str objects, you can build a list and use str.join() at the end or else write to an io.StringIO instance and retrieve its value when complete if concatenating bytes objects, you can similarly use bytes.join() or io.BytesIO , or you can do in-place concatenation with a bytearray object. bytearray objects are mutable and have an efficient overallocation mechanism if concatenating tuple objects, extend a list instead for other types, investigate the relevant class documentation Some sequence types (such as range ) only support item sequences that follow specific patterns, and hence don’t support sequence concatenation or repetition. An IndexError is raised if i is outside the sequence range. Sequence Methods Sequence types also support the following methods: sequence. count ( value , / ) ¶ Return the total number of occurrences of value in sequence . sequence. index ( value[, start[, stop] ) ¶ Return the index of the first occurrence of value in sequence . Raises ValueError if value is not found in sequence . The start or stop arguments allow for efficient searching of subsections of the sequence, beginning at start and ending at stop . This is roughly equivalent to start + sequence[start:stop].index(value) , only without copying any data. Caution Not all sequence types support passing the start and stop arguments. Immutable Sequence Types ¶ The only operation that immutable sequence types generally implement that is not also implemented by mutable sequence types is support for the hash() built-in. This support allows immutable sequences, such as tuple instances, to be used as dict keys and stored in set and frozenset instances. Attempting to hash an immutable sequence that contains unhashable values will result in TypeError . Mutable Sequence Types ¶ The operations in the following table are defined on mutable sequence types. The collections.abc.MutableSequence ABC is provided to make it easier to correctly implement these operations on custom sequence types. In the table s is an instance of a mutable sequence type, t is any iterable object and x is an arbitrary object that meets any type and value restrictions imposed by s (for example, bytearray only accepts integers that meet the value restriction 0 <= x <= 255 ). Operation Result Notes s[i] = x item i of s is replaced by x del s[i] removes item i of s s[i:j] = t slice of s from i to j is replaced by the contents of the iterable t del s[i:j] removes the elements of s[i:j] from the list (same as s[i:j] = [] ) s[i:j:k] = t the elements of s[i:j:k] are replaced by those of t (1) del s[i:j:k] removes the elements of s[i:j:k] from the list s += t extends s with the contents of t (for the most part the same as s[len(s):len(s)] = t ) s *= n updates s with its contents repeated n times (2) Notes: If k is not equal to 1 , t must have the same length as the slice it is replacing. The value n is an integer, or an object implementing __index__() . Zero and negative values of n clear the sequence. Items in the sequence are not copied; they are referenced multiple times, as explained for s * n under Common Sequence Operations . Mutable Sequence Methods Mutable sequence types also support the following methods: sequence. append ( value , / ) ¶ Append value to the end of the sequence This is equivalent to writing seq[len(seq):len(seq)] = [value] . sequence. clear ( ) ¶ Added in version 3.3. Remove all items from sequence . This is equivalent to writing del sequence[:] . sequence. copy ( ) ¶ Added in version 3.3. Create a shallow copy of sequence . This is equivalent to writing sequence[:] . Hint The copy() method is not part of the MutableSequence ABC , but most concrete mutable sequence types provide it. sequence. extend ( iterable , / ) ¶ Extend sequence with the contents of iterable . For the most part, this is the same as writing seq[len(seq):len(seq)] = iterable . sequence. insert ( index , value , / ) ¶ Insert value into sequence at the given index . This is equivalent to writing sequence[index:index] = [value] . sequence. pop ( index = -1 , / ) ¶ Retrieve the item at index and also removes it from sequence . By default, the last item in sequence is removed and returned. sequence. remove ( value , / ) ¶ Remove the first item from sequence where sequence[i] == value . Raises ValueError if value is not found in sequence . sequence. reverse ( ) ¶ Reverse the items of sequence in place. This method maintains economy of space when reversing a large sequence. To remind users that it operates by side-effect, it returns None . Lists ¶ Lists are mutable sequences, typically used to store collections of homogeneous items (where the precise degree of similarity will vary by application). class list ( iterable = () , / ) ¶ Lists may be constructed in several ways: Using a pair of square brackets to denote the empty list: [] Using square brackets, separating items with commas: [a] , [a, b, c] Using a list comprehension: [x for x in iterable] Using the type constructor: list() or list(iterable) The constructor builds a list whose items are the same and in the same order as iterable ’s items. iterable may be either a sequence, a container that supports iteration, or an iterator object. If iterable is already a list, a copy is made and returned, similar to iterable[:] . For example, list('abc') returns ['a', 'b', 'c'] and list( (1, 2, 3) ) returns [1, 2, 3] . If no argument is given, the constructor creates a new empty list, [] . Many other operations also produce lists, including the sorted() built-in. Lists implement all of the common and mutable sequence operations. Lists also provide the following additional method: sort ( * , key = None , reverse = False ) ¶ This method sorts the list in place, using only < comparisons between items. Exceptions are not suppressed - if any comparison operations fail, the entire sort operation will fail (and the list will likely be left in a partially modified state). sort() accepts two arguments that can only be passed by keyword ( keyword-only arguments ): key specifies a function of one argument that is used to extract a comparison key from each list element (for example, key=str.lower ). The key corresponding to each item in the list is calculated once and then used for the entire sorting process. The default value of None means that list items are sorted directly without calculating a separate key value. The functools.cmp_to_key() utility is available to convert a 2.x style cmp function to a key function. reverse is a boolean value. If set to True , then the list elements are sorted as if each comparison were reversed. This method modifies the sequence in place for economy of space when sorting a large sequence. To remind users that it operates by side effect, it does not return the sorted sequence (use sorted() to explicitly request a new sorted list instance). The sort() method is guaranteed to be stable. A sort is stable if it guarantees not to change the relative order of elements that compare equal — this is helpful for sorting in multiple passes (for example, sort by department, then by salary grade). For sorting examples and a brief sorting tutorial, see Sorting Techniques . CPython implementation detail: While a list is being sorted, the effect of attempting to mutate, or even inspect, the list is undefined. The C implementation of Python makes the list appear empty for the duration, and raises ValueError if it can detect that the list has been mutated during a sort. Thread safety Reading a single element from a list is atomic : lst [ i ] # list.__getitem__ The following methods traverse the list and use atomic reads of each item to perform their function. That means that they may return results affected by concurrent modifications: item in lst lst . index ( item ) lst . count ( item ) All of the above methods/operations are also lock-free. They do not block concurrent modifications. Other operations that hold a lock will not block these from observing intermediate states. All other operations from here on block using the per-object lock. Writing a single item via lst[i] = x is safe to call from multiple threads and will not corrupt the list. The following operations return new objects and appear atomic to other threads: lst1 + lst2 # concatenates two lists into a new list x * lst # repeats lst x times into a new list lst . copy () # returns a shallow copy of the list Methods that only operate on a single elements with no shifting required are atomic : lst . append ( x ) # append to the end of the list, no shifting required lst . pop () # pop element from the end of the list, no shifting required The clear() method is also atomic . Other threads cannot observe elements being removed. The sort() method is not atomic . Other threads cannot observe intermediate states during sorting, but the list appears empty for the duration of the sort. The following operations may allow lock-free operations to observe intermediate states since they modify multiple elements in place: lst . insert ( idx , item ) # shifts elements lst . pop ( idx ) # idx not at the end of the list, shifts elements lst *= x # copies elements in place The remove() method may allow concurrent modifications since element comparison may execute arbitrary Python code (via __eq__() ). extend() is safe to call from multiple threads. However, its guarantees depend on the iterable passed to it. If it is a list , a tuple , a set , a frozenset , a dict or a dictionary view object (but not their subclasses), the extend operation is safe from concurrent modifications to the iterable. Otherwise, an iterator is created which can be concurrently modified by another thread. The same applies to inplace concatenation of a list with other iterables when using lst += iterable . Similarly, assigning to a list slice with lst[i:j] = iterable is safe to call from multiple threads, but iterable is only locked when it is also a list (but not its subclasses). Operations that involve multiple accesses, as well as iteration, are never atomic. For example: # NOT atomic: read-modify-write lst [ i ] = lst [ i ] + 1 # NOT atomic: check-then-act if lst : item = lst . pop () # NOT thread-safe: iteration while modifying for item in lst : process ( item ) # another thread may modify lst Consider external synchronization when sharing list instances across threads. See Python support for free threading for more information. Tuples ¶ Tuples are immutable sequences, typically used to store collections of heterogeneous data (such as the 2-tuples produced by the enumerate() built-in). Tuples are also used for cases where an immutable sequence of homogeneous data is needed (such as allowing storage in a set or dict instance). class tuple ( iterable = () , / ) ¶ Tuples may be constructed in a number of ways: Using a pair of parentheses to denote the empty tuple: () Using a trailing comma for a singleton tuple: a, or (a,) Separating items with commas: a, b, c or (a, b, c) Using the tuple() built-in: tuple() or tuple(iterable) The constructor builds a tuple whose items are the same and in the same order as iterable ’s items. iterable may be either a sequence, a container that supports iteration, or an iterator object. If iterable is already a tuple, it is returned unchanged. For example, tuple('abc') returns ('a', 'b', 'c') and tuple( [1, 2, 3] ) returns (1, 2, 3) . If no argument is given, the constructor creates a new empty tuple, () . Note that it is actually the comma which makes a tuple, not the parentheses. The parentheses are optional, except in the empty tuple case, or when they are needed to avoid syntactic ambiguity. For example, f(a, b, c) is a function call with three arguments, while f((a, b, c)) is a function call with a 3-tuple as the sole argument. Tuples implement all of the common sequence operations. For heterogeneous collections of data where access by name is clearer than access by index, collections.namedtuple() may be a more appropriate choice than a simple tuple object. Ranges ¶ The range type represents an immutable sequence of numbers and is commonly used for looping a specific number of times in for loops. class range ( stop , / ) ¶ class range ( start , stop , step = 1 , / ) The arguments to the range constructor must be integers (either built-in int or any object that implements the __index__() special method). If the step argument is omitted, it defaults to 1 . If the start argument is omitted, it defaults to 0 . If step is zero, ValueError is raised. For a positive step , the contents of a range r are determined by the formula r[i] = start + step*i where i >= 0 and r[i] < stop . For a negative step , the contents of the range are still determined by the formula r[i] = start + step*i , but the constraints are i >= 0 and r[i] > stop . A range object will be empty if r[0] does not meet the value constraint. Ranges do support negative indices, but these are interpreted as indexing from the end of the sequence determined by the positive indices. Ranges containing absolute values larger than sys.maxsize are permitted but some features (such as len() ) may raise OverflowError . Range examples: >>> list ( range ( 10 )) [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] >>> list ( range ( 1 , 11 )) [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] >>> list ( range ( 0 , 30 , 5 )) [0, 5, 10, 15, 20, 25] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( 0 , - 10 , - 1 )) [0, -1, -2, -3, -4, -5, -6, -7, -8, -9] >>> list ( range ( 0 )) [] >>> list ( range ( 1 , 0 )) [] Ranges implement all of the common sequence operations except concatenation and repetition (due to the fact that range objects can only represent sequences that follow a strict pattern and repetition and concatenation will usually violate that pattern). start ¶ The value of the start parameter (or 0 if the parameter was not supplied) stop ¶ The value of the stop parameter step ¶ The value of the step parameter (or 1 if the parameter was not supplied) The advantage of the range type over a regular list or tuple is that a range object will always take the same (small) amount of memory, no matter the size of the range it represents (as it only stores the start , stop and step values, calculating individual items and subranges as needed). Range objects implement the collections.abc.Sequence ABC, and provide features such as containment tests, element index lookup, slicing and support for negative indices (see Sequence Types — list, tuple, range ): >>> r = range ( 0 , 20 , 2 ) >>> r range(0, 20, 2) >>> 11 in r False >>> 10 in r True >>> r . index ( 10 ) 5 >>> r [ 5 ] 10 >>> r [: 5 ] range(0, 10, 2) >>> r [ - 1 ] 18 Testing range objects for equality with == and != compares them as sequences. That is, two range objects are considered equal if they represent the same sequence of values. (Note that two range objects that compare equal might have different start , stop and step attributes, for example range(0) == range(2, 1, 3) or range(0, 3, 2) == range(0, 4, 2) .) Changed in version 3.2: Implement the Sequence ABC. Support slicing and negative indices. Test int objects for membership in constant time instead of iterating through all items. Changed in version 3.3: Define ‘==’ and ‘!=’ to compare range objects based on the sequence of values they define (instead of comparing based on object identity). Added the start , stop and step attributes. See also The linspace recipe shows how to implement a lazy version of range suitable for floating-point applications. Text and Binary Sequence Type Methods Summary ¶ The following table summarizes the text and binary sequence types methods by category. Category str methods bytes and bytearray methods Formatting str.format() str.format_map() f-strings printf-style String Formatting printf-style Bytes Formatting Searching and Replacing str.find() str.rfind() bytes.find() bytes.rfind() str.index() str.rindex() bytes.index() bytes.rindex() str.startswith() bytes.startswith() str.endswith() bytes.endswith() str.count() bytes.count() str.replace() bytes.replace() Splitting and Joining str.split() str.rsplit() bytes.split() bytes.rsplit() str.splitlines() bytes.splitlines() str.partition() bytes.partition() str.rpartition() bytes.rpartition() str.join() bytes.join() String Classification str.isalpha() bytes.isalpha() str.isdecimal() str.isdigit() bytes.isdigit() str.isnumeric() str.isalnum() bytes.isalnum() str.isidentifier() str.islower() bytes.islower() str.isupper() bytes.isupper() str.istitle() bytes.istitle() str.isspace() bytes.isspace() str.isprintable() Case Manipulation str.lower() bytes.lower() str.upper() bytes.upper() str.casefold() str.capitalize() bytes.capitalize() str.title() bytes.title() str.swapcase() bytes.swapcase() Padding and Stripping str.ljust() str.rjust() bytes.ljust() bytes.rjust() str.center() bytes.center() str.expandtabs() bytes.expandtabs() str.strip() bytes.strip() str.lstrip() str.rstrip() bytes.lstrip() bytes.rstrip() Translation and Encoding str.translate() bytes.translate() str.maketrans() bytes.maketrans() str.encode() bytes.decode() Text Sequence Type — str ¶ Textual data in Python is handled with str objects, or strings . Strings are immutable sequences of Unicode code points. String literals are written in a variety of ways: Single quotes: 'allows embedded "double" quotes' Double quotes: "allows embedded 'single' quotes" Triple quoted: '''Three single quotes''' , """Three double quotes""" Triple quoted strings may span multiple lines - all associated whitespace will be included in the string literal. String literals that are part of a single expression and have only whitespace between them will be implicitly converted to a single string literal. That is, ("spam " "eggs") == "spam eggs" . See String and Bytes literals for more about the various forms of string literal | 2026-01-13T08:48:43 |
https://docs.suprsend.com/docs/react-native-create-user | Manage Users - 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 Manage Users Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog React Native Manage Users OpenAI Open in ChatGPT Methods to create user and set their mobile push token and other communication channels for sending notifications in ReactNative application. OpenAI Open in ChatGPT How Suprsend identifies a user SuprSend identifies users with immutable distinct_id . It’s best to map the same identifier in your DB with distinct_id in SuprSend. Do not use identifiers that can be changed like email or phone number. You can view synced users by searching distinct_id on Users page . Identify user and Set Push token 1 Create/Identify a new user You can identify a user using the suprsend.identify() method. iospsuh token is automatically set in user’s profile when this method is called. Call this method as soon as you know the identity of user, that is after login authentication. If you don’t call this method, user will be identified using distinct_id (uuid) that SDK generates internally. We internally create an event called $user_login . You can see this event on SuprSend workflows event list and you can configure a workflow on it. javascript Copy Ask AI suprsend . identify ( distinct_id ); //Sample Values suprsend . identify ( "291eaa13-62f5-4d52-b2dd" ); Parameters Type Description distinct_id int, bigint, string, UUID mandatory Unique identifier for a user across devices or between multiple logins. 2 Call reset to clear user data on log out As soon as the user logs out, call suprsend.reset() method to clear data attributed to a user. This allows you to handle multiple user logins on a single device and keep their data isolated from each other. javascript Copy Ask AI suprsend . reset (); Don’t forget to call reset on user logout. If not called, users’ distinct_id will not reset and multiple tokens and channels will get added to the distinct_id who logged in first on the device. Set communication channels Mobile Push tokens automatically gets updated in user profile on suprsend.identify() call. All you have to do is to integrate push notification service in your application to start sending mobile push notification. To set other communication channels, use below methods: Add User Channels Add user channels on signup, or whenever a user updates their communication channels in the application flow. Javascript Copy Ask AI suprsend . user . setEmail ( " [email protected] " ); // To add Email suprsend . user . setSms ( "+91XXXXXXXXXX" ); // To add SMS, mandatory to pass country code suprsend . user . setWhatsApp ( "+91XXXXXXXXXX" ); // To add Whatsapp, mandatory to pass country code Remove User Channels Copy Ask AI suprsend.user.unSetEmail(" [email protected] "); // To remove Email suprsend.user.unSetSms("+91XXXXXXXXXX"); // To remove SMS suprsend.user.unSetWhatsApp("+91XXXXXXXXXX"); // To remove Whatsapp Set user properties ( currently not available in iOS SDK ) You can sync other user properties in SuprSend and use it to pass dynamic content in template or add in workflow conditions. Set Set is used to add property. Set is upsert function and will override existing values corresponding to a key. javascript Copy Ask AI // for single property suprsend . user . set ( key , value ); suprsend . user . set ( "name" , "john doe" ); // for multiple properties suprsend . user . set ( property_obj ); suprsend . user . set ({ "name" : "john doe" , "age" : "27" }); Key should not start with $ or ss_ , as we have reserved these symbols for our internal events and property names. Set Once Works just like user.set , except it will not overwrite existing property values. This is useful for properties like First login date javascript Copy Ask AI suprsend . user . setOnce ( key , value ); // for single property suprsend . user . setOnce ( properties ); // for multiple properties // Sample values for setting once a single property: suprsend . user . setOnce ( "first_login" , "2021-11-02" ); // Sample values for setting once multiple properties: suprsend . user . setOnce ({ "first_login" : "2021-11-02" , "DOB" : "1991-10-02" }); Unset This will remove a property key javascript Copy Ask AI suprsend . user . unSet ( key ); // for single property suprsend . user . unSet ( property_list ); // for multiple properties // Sample values for unsetting a single property: suprsend . user . unSet ( "wishlist" ); // Sample values for unsetting multiple properties: suprsend . user . unSet ([ "wishlist" , "cart" ]); Append This method will append a value to an array javascript Copy Ask AI suprsend . user . append ( key , value ); suprsend . user . append ( property_obj ); // for multiple properties // Sample values for appending a single property: suprsend . user . append ( "wishlist" , "iphone12" ); // Sample values for appending multiple properties: suprsend . user . append ({ "wishlist" : "iphone12" , "wishlist" : "Apple airpods" }); Remove This will remove value from an array but not remove property key javascript Copy Ask AI // for single property suprsend . user . remove ( key , value ); suprsend . user . remove ( "wishlist" , "iphone12" ); // for multiple properties suprsend . user . remove ( property_obj ); suprsend . user . remove ({ "wishlist" : "iphone12" , "wishlist" : "Apple airpods" }); Increment Increase or decrease integer values on consecutive action, like login count. To reduce a property, provide a negative number for the value. javascript Copy Ask AI // for single property suprsend . user . increment ( key , value ); suprsend . user . increment ( "login_count" , 1 ); // for multiple properties suprsend . user . increment ( property_obj ); suprsend . user . increment ({ "login_count" : 1 , "order_count" : 1 }); // Sample values for incrementing a single property: // Sample values for incrementing multiple properties: Was this page helpful? Yes No Suggest edits Raise issue Previous Sync Events Methods for sending events from your react native app to the SuprSend platform to trigger workflows. Next ⌘ I x github linkedin youtube Powered by On this page How Suprsend identifies a user Identify user and Set Push token Set communication channels Set user properties | 2026-01-13T08:48:43 |
https://docs.suprsend.com/docs/integrate-python-sdk#content-area | Integrate Python SDK - 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 Python SDK Integrate Python SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Node.js SDK Java SDK Go SDK SuprSend Client SDK 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 Python SDK Integrate Python SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Python SDK Integrate Python SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Python SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation 1 Install 'libmagic' system package. You can skip this step if you already have this package installed in your system. bash Copy Ask AI # if you are using linux / debian based systems sudo apt install libmagic # If you are using macOS brew install libmagic 2 Install 'suprsend-py-sdk' using pip bash Copy Ask AI $ pip install suprsend-py-sdk # to upgrade to latest SDK version $ pip install suprsend-py-sdk --upgrade Python version 3.7 or later is required If your python3 version is lower than 3.7, upgrade it. Schema Validation Support : If you’re using schema validation for workflow payloads, you need Python SDK v0.15.0 or later. The API response format was modified to support schema validation, and older SDK versions may not properly handle validation errors. Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). python Copy Ask AI from suprsend import Suprsend # Initialize SDK supr_client = Suprsend( "WORKSPACE KEY" , "WORKSPACE SECRET" ) Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Create, update, & manage user profiles and communication channels using Python SDK methods. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:48:43 |
https://docs.python.org/3/glossary.html#term-iterable | Glossary — Python 3.14.2 documentation Theme Auto Light Dark Previous topic Deprecations Next topic About this documentation This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » Glossary | Theme Auto Light Dark | Glossary ¶ >>> ¶ The default Python prompt of the interactive shell. Often seen for code examples which can be executed interactively in the interpreter. ... ¶ Can refer to: The default Python prompt of the interactive shell when entering the code for an indented code block, when within a pair of matching left and right delimiters (parentheses, square brackets, curly braces or triple quotes), or after specifying a decorator. The three dots form of the Ellipsis object. abstract base class ¶ Abstract base classes complement duck-typing by providing a way to define interfaces when other techniques like hasattr() would be clumsy or subtly wrong (for example with magic methods ). ABCs introduce virtual subclasses, which are classes that don’t inherit from a class but are still recognized by isinstance() and issubclass() ; see the abc module documentation. Python comes with many built-in ABCs for data structures (in the collections.abc module), numbers (in the numbers module), streams (in the io module), import finders and loaders (in the importlib.abc module). You can create your own ABCs with the abc module. annotate function ¶ A function that can be called to retrieve the annotations of an object. This function is accessible as the __annotate__ attribute of functions, classes, and modules. Annotate functions are a subset of evaluate functions . annotation ¶ A label associated with a variable, a class attribute or a function parameter or return value, used by convention as a type hint . Annotations of local variables cannot be accessed at runtime, but annotations of global variables, class attributes, and functions can be retrieved by calling annotationlib.get_annotations() on modules, classes, and functions, respectively. See variable annotation , function annotation , PEP 484 , PEP 526 , and PEP 649 , which describe this functionality. Also see Annotations Best Practices for best practices on working with annotations. argument ¶ A value passed to a function (or method ) when calling the function. There are two kinds of argument: keyword argument : an argument preceded by an identifier (e.g. name= ) in a function call or passed as a value in a dictionary preceded by ** . For example, 3 and 5 are both keyword arguments in the following calls to complex() : complex ( real = 3 , imag = 5 ) complex ( ** { 'real' : 3 , 'imag' : 5 }) positional argument : an argument that is not a keyword argument. Positional arguments can appear at the beginning of an argument list and/or be passed as elements of an iterable preceded by * . For example, 3 and 5 are both positional arguments in the following calls: complex ( 3 , 5 ) complex ( * ( 3 , 5 )) Arguments are assigned to the named local variables in a function body. See the Calls section for the rules governing this assignment. Syntactically, any expression can be used to represent an argument; the evaluated value is assigned to the local variable. See also the parameter glossary entry, the FAQ question on the difference between arguments and parameters , and PEP 362 . asynchronous context manager ¶ An object which controls the environment seen in an async with statement by defining __aenter__() and __aexit__() methods. Introduced by PEP 492 . asynchronous generator ¶ A function which returns an asynchronous generator iterator . It looks like a coroutine function defined with async def except that it contains yield expressions for producing a series of values usable in an async for loop. Usually refers to an asynchronous generator function, but may refer to an asynchronous generator iterator in some contexts. In cases where the intended meaning isn’t clear, using the full terms avoids ambiguity. An asynchronous generator function may contain await expressions as well as async for , and async with statements. asynchronous generator iterator ¶ An object created by an asynchronous generator function. This is an asynchronous iterator which when called using the __anext__() method returns an awaitable object which will execute the body of the asynchronous generator function until the next yield expression. Each yield temporarily suspends processing, remembering the execution state (including local variables and pending try-statements). When the asynchronous generator iterator effectively resumes with another awaitable returned by __anext__() , it picks up where it left off. See PEP 492 and PEP 525 . asynchronous iterable ¶ An object, that can be used in an async for statement. Must return an asynchronous iterator from its __aiter__() method. Introduced by PEP 492 . asynchronous iterator ¶ An object that implements the __aiter__() and __anext__() methods. __anext__() must return an awaitable object. async for resolves the awaitables returned by an asynchronous iterator’s __anext__() method until it raises a StopAsyncIteration exception. Introduced by PEP 492 . atomic operation ¶ An operation that appears to execute as a single, indivisible step: no other thread can observe it half-done, and its effects become visible all at once. Python does not guarantee that high-level statements are atomic (for example, x += 1 performs multiple bytecode operations and is not atomic). Atomicity is only guaranteed where explicitly documented. See also race condition and data race . attached thread state ¶ A thread state that is active for the current OS thread. When a thread state is attached, the OS thread has access to the full Python C API and can safely invoke the bytecode interpreter. Unless a function explicitly notes otherwise, attempting to call the C API without an attached thread state will result in a fatal error or undefined behavior. A thread state can be attached and detached explicitly by the user through the C API, or implicitly by the runtime, including during blocking C calls and by the bytecode interpreter in between calls. On most builds of Python, having an attached thread state implies that the caller holds the GIL for the current interpreter, so only one OS thread can have an attached thread state at a given moment. In free-threaded builds of Python, threads can concurrently hold an attached thread state, allowing for true parallelism of the bytecode interpreter. attribute ¶ A value associated with an object which is usually referenced by name using dotted expressions. For example, if an object o has an attribute a it would be referenced as o.a . It is possible to give an object an attribute whose name is not an identifier as defined by Names (identifiers and keywords) , for example using setattr() , if the object allows it. Such an attribute will not be accessible using a dotted expression, and would instead need to be retrieved with getattr() . awaitable ¶ An object that can be used in an await expression. Can be a coroutine or an object with an __await__() method. See also PEP 492 . BDFL ¶ Benevolent Dictator For Life, a.k.a. Guido van Rossum , Python’s creator. binary file ¶ A file object able to read and write bytes-like objects . Examples of binary files are files opened in binary mode ( 'rb' , 'wb' or 'rb+' ), sys.stdin.buffer , sys.stdout.buffer , and instances of io.BytesIO and gzip.GzipFile . See also text file for a file object able to read and write str objects. borrowed reference ¶ In Python’s C API, a borrowed reference is a reference to an object, where the code using the object does not own the reference. It becomes a dangling pointer if the object is destroyed. For example, a garbage collection can remove the last strong reference to the object and so destroy it. Calling Py_INCREF() on the borrowed reference is recommended to convert it to a strong reference in-place, except when the object cannot be destroyed before the last usage of the borrowed reference. The Py_NewRef() function can be used to create a new strong reference . bytes-like object ¶ An object that supports the Buffer Protocol and can export a C- contiguous buffer. This includes all bytes , bytearray , and array.array objects, as well as many common memoryview objects. Bytes-like objects can be used for various operations that work with binary data; these include compression, saving to a binary file, and sending over a socket. Some operations need the binary data to be mutable. The documentation often refers to these as “read-write bytes-like objects”. Example mutable buffer objects include bytearray and a memoryview of a bytearray . Other operations require the binary data to be stored in immutable objects (“read-only bytes-like objects”); examples of these include bytes and a memoryview of a bytes object. bytecode ¶ Python source code is compiled into bytecode, the internal representation of a Python program in the CPython interpreter. The bytecode is also cached in .pyc files so that executing the same file is faster the second time (recompilation from source to bytecode can be avoided). This “intermediate language” is said to run on a virtual machine that executes the machine code corresponding to each bytecode. Do note that bytecodes are not expected to work between different Python virtual machines, nor to be stable between Python releases. A list of bytecode instructions can be found in the documentation for the dis module . callable ¶ A callable is an object that can be called, possibly with a set of arguments (see argument ), with the following syntax: callable ( argument1 , argument2 , argumentN ) A function , and by extension a method , is a callable. An instance of a class that implements the __call__() method is also a callable. callback ¶ A subroutine function which is passed as an argument to be executed at some point in the future. class ¶ A template for creating user-defined objects. Class definitions normally contain method definitions which operate on instances of the class. class variable ¶ A variable defined in a class and intended to be modified only at class level (i.e., not in an instance of the class). closure variable ¶ A free variable referenced from a nested scope that is defined in an outer scope rather than being resolved at runtime from the globals or builtin namespaces. May be explicitly defined with the nonlocal keyword to allow write access, or implicitly defined if the variable is only being read. For example, in the inner function in the following code, both x and print are free variables , but only x is a closure variable : def outer (): x = 0 def inner (): nonlocal x x += 1 print ( x ) return inner Due to the codeobject.co_freevars attribute (which, despite its name, only includes the names of closure variables rather than listing all referenced free variables), the more general free variable term is sometimes used even when the intended meaning is to refer specifically to closure variables. complex number ¶ An extension of the familiar real number system in which all numbers are expressed as a sum of a real part and an imaginary part. Imaginary numbers are real multiples of the imaginary unit (the square root of -1 ), often written i in mathematics or j in engineering. Python has built-in support for complex numbers, which are written with this latter notation; the imaginary part is written with a j suffix, e.g., 3+1j . To get access to complex equivalents of the math module, use cmath . Use of complex numbers is a fairly advanced mathematical feature. If you’re not aware of a need for them, it’s almost certain you can safely ignore them. concurrency ¶ The ability of a computer program to perform multiple tasks at the same time. Python provides libraries for writing programs that make use of different forms of concurrency. asyncio is a library for dealing with asynchronous tasks and coroutines. threading provides access to operating system threads and multiprocessing to operating system processes. Multi-core processors can execute threads and processes on different CPU cores at the same time (see parallelism ). concurrent modification ¶ When multiple threads modify shared data at the same time. Concurrent modification without proper synchronization can cause race conditions , and might also trigger a data race , data corruption, or both. context ¶ This term has different meanings depending on where and how it is used. Some common meanings: The temporary state or environment established by a context manager via a with statement. The collection of keyvalue bindings associated with a particular contextvars.Context object and accessed via ContextVar objects. Also see context variable . A contextvars.Context object. Also see current context . context management protocol ¶ The __enter__() and __exit__() methods called by the with statement. See PEP 343 . context manager ¶ An object which implements the context management protocol and controls the environment seen in a with statement. See PEP 343 . context variable ¶ A variable whose value depends on which context is the current context . Values are accessed via contextvars.ContextVar objects. Context variables are primarily used to isolate state between concurrent asynchronous tasks. contiguous ¶ A buffer is considered contiguous exactly if it is either C-contiguous or Fortran contiguous . Zero-dimensional buffers are C and Fortran contiguous. In one-dimensional arrays, the items must be laid out in memory next to each other, in order of increasing indexes starting from zero. In multidimensional C-contiguous arrays, the last index varies the fastest when visiting items in order of memory address. However, in Fortran contiguous arrays, the first index varies the fastest. coroutine ¶ Coroutines are a more generalized form of subroutines. Subroutines are entered at one point and exited at another point. Coroutines can be entered, exited, and resumed at many different points. They can be implemented with the async def statement. See also PEP 492 . coroutine function ¶ A function which returns a coroutine object. A coroutine function may be defined with the async def statement, and may contain await , async for , and async with keywords. These were introduced by PEP 492 . CPython ¶ The canonical implementation of the Python programming language, as distributed on python.org . The term “CPython” is used when necessary to distinguish this implementation from others such as Jython or IronPython. current context ¶ The context ( contextvars.Context object) that is currently used by ContextVar objects to access (get or set) the values of context variables . Each thread has its own current context. Frameworks for executing asynchronous tasks (see asyncio ) associate each task with a context which becomes the current context whenever the task starts or resumes execution. cyclic isolate ¶ A subgroup of one or more objects that reference each other in a reference cycle, but are not referenced by objects outside the group. The goal of the cyclic garbage collector is to identify these groups and break the reference cycles so that the memory can be reclaimed. data race ¶ A situation where multiple threads access the same memory location concurrently, at least one of the accesses is a write, and the threads do not use any synchronization to control their access. Data races lead to non-deterministic behavior and can cause data corruption. Proper use of locks and other synchronization primitives prevents data races. Note that data races can only happen in native code, but that native code might be exposed in a Python API. See also race condition and thread-safe . deadlock ¶ A situation in which two or more tasks (threads, processes, or coroutines) wait indefinitely for each other to release resources or complete actions, preventing any from making progress. For example, if thread A holds lock 1 and waits for lock 2, while thread B holds lock 2 and waits for lock 1, both threads will wait indefinitely. In Python this often arises from acquiring multiple locks in conflicting orders or from circular join/await dependencies. Deadlocks can be avoided by always acquiring multiple locks in a consistent order. See also lock and reentrant . decorator ¶ A function returning another function, usually applied as a function transformation using the @wrapper syntax. Common examples for decorators are classmethod() and staticmethod() . The decorator syntax is merely syntactic sugar, the following two function definitions are semantically equivalent: def f ( arg ): ... f = staticmethod ( f ) @staticmethod def f ( arg ): ... The same concept exists for classes, but is less commonly used there. See the documentation for function definitions and class definitions for more about decorators. descriptor ¶ Any object which defines the methods __get__() , __set__() , or __delete__() . When a class attribute is a descriptor, its special binding behavior is triggered upon attribute lookup. Normally, using a.b to get, set or delete an attribute looks up the object named b in the class dictionary for a , but if b is a descriptor, the respective descriptor method gets called. Understanding descriptors is a key to a deep understanding of Python because they are the basis for many features including functions, methods, properties, class methods, static methods, and reference to super classes. For more information about descriptors’ methods, see Implementing Descriptors or the Descriptor How To Guide . dictionary ¶ An associative array, where arbitrary keys are mapped to values. The keys can be any object with __hash__() and __eq__() methods. Called a hash in Perl. dictionary comprehension ¶ A compact way to process all or part of the elements in an iterable and return a dictionary with the results. results = {n: n ** 2 for n in range(10)} generates a dictionary containing key n mapped to value n ** 2 . See Displays for lists, sets and dictionaries . dictionary view ¶ The objects returned from dict.keys() , dict.values() , and dict.items() are called dictionary views. They provide a dynamic view on the dictionary’s entries, which means that when the dictionary changes, the view reflects these changes. To force the dictionary view to become a full list use list(dictview) . See Dictionary view objects . docstring ¶ A string literal which appears as the first expression in a class, function or module. While ignored when the suite is executed, it is recognized by the compiler and put into the __doc__ attribute of the enclosing class, function or module. Since it is available via introspection, it is the canonical place for documentation of the object. duck-typing ¶ A programming style which does not look at an object’s type to determine if it has the right interface; instead, the method or attribute is simply called or used (“If it looks like a duck and quacks like a duck, it must be a duck.”) By emphasizing interfaces rather than specific types, well-designed code improves its flexibility by allowing polymorphic substitution. Duck-typing avoids tests using type() or isinstance() . (Note, however, that duck-typing can be complemented with abstract base classes .) Instead, it typically employs hasattr() tests or EAFP programming. dunder ¶ An informal short-hand for “double underscore”, used when talking about a special method . For example, __init__ is often pronounced “dunder init”. EAFP ¶ Easier to ask for forgiveness than permission. This common Python coding style assumes the existence of valid keys or attributes and catches exceptions if the assumption proves false. This clean and fast style is characterized by the presence of many try and except statements. The technique contrasts with the LBYL style common to many other languages such as C. evaluate function ¶ A function that can be called to evaluate a lazily evaluated attribute of an object, such as the value of type aliases created with the type statement. expression ¶ A piece of syntax which can be evaluated to some value. In other words, an expression is an accumulation of expression elements like literals, names, attribute access, operators or function calls which all return a value. In contrast to many other languages, not all language constructs are expressions. There are also statement s which cannot be used as expressions, such as while . Assignments are also statements, not expressions. extension module ¶ A module written in C or C++, using Python’s C API to interact with the core and with user code. f-string ¶ f-strings ¶ String literals prefixed with f or F are commonly called “f-strings” which is short for formatted string literals . See also PEP 498 . file object ¶ An object exposing a file-oriented API (with methods such as read() or write() ) to an underlying resource. Depending on the way it was created, a file object can mediate access to a real on-disk file or to another type of storage or communication device (for example standard input/output, in-memory buffers, sockets, pipes, etc.). File objects are also called file-like objects or streams . There are actually three categories of file objects: raw binary files , buffered binary files and text files . Their interfaces are defined in the io module. The canonical way to create a file object is by using the open() function. file-like object ¶ A synonym for file object . filesystem encoding and error handler ¶ Encoding and error handler used by Python to decode bytes from the operating system and encode Unicode to the operating system. The filesystem encoding must guarantee to successfully decode all bytes below 128. If the file system encoding fails to provide this guarantee, API functions can raise UnicodeError . The sys.getfilesystemencoding() and sys.getfilesystemencodeerrors() functions can be used to get the filesystem encoding and error handler. The filesystem encoding and error handler are configured at Python startup by the PyConfig_Read() function: see filesystem_encoding and filesystem_errors members of PyConfig . See also the locale encoding . finder ¶ An object that tries to find the loader for a module that is being imported. There are two types of finder: meta path finders for use with sys.meta_path , and path entry finders for use with sys.path_hooks . See Finders and loaders and importlib for much more detail. floor division ¶ Mathematical division that rounds down to nearest integer. The floor division operator is // . For example, the expression 11 // 4 evaluates to 2 in contrast to the 2.75 returned by float true division. Note that (-11) // 4 is -3 because that is -2.75 rounded downward . See PEP 238 . free threading ¶ A threading model where multiple threads can run Python bytecode simultaneously within the same interpreter. This is in contrast to the global interpreter lock which allows only one thread to execute Python bytecode at a time. See PEP 703 . free variable ¶ Formally, as defined in the language execution model , a free variable is any variable used in a namespace which is not a local variable in that namespace. See closure variable for an example. Pragmatically, due to the name of the codeobject.co_freevars attribute, the term is also sometimes used as a synonym for closure variable . function ¶ A series of statements which returns some value to a caller. It can also be passed zero or more arguments which may be used in the execution of the body. See also parameter , method , and the Function definitions section. function annotation ¶ An annotation of a function parameter or return value. Function annotations are usually used for type hints : for example, this function is expected to take two int arguments and is also expected to have an int return value: def sum_two_numbers ( a : int , b : int ) -> int : return a + b Function annotation syntax is explained in section Function definitions . See variable annotation and PEP 484 , which describe this functionality. Also see Annotations Best Practices for best practices on working with annotations. __future__ ¶ A future statement , from __future__ import <feature> , directs the compiler to compile the current module using syntax or semantics that will become standard in a future release of Python. The __future__ module documents the possible values of feature . By importing this module and evaluating its variables, you can see when a new feature was first added to the language and when it will (or did) become the default: >>> import __future__ >>> __future__ . division _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192) garbage collection ¶ The process of freeing memory when it is not used anymore. Python performs garbage collection via reference counting and a cyclic garbage collector that is able to detect and break reference cycles. The garbage collector can be controlled using the gc module. generator ¶ A function which returns a generator iterator . It looks like a normal function except that it contains yield expressions for producing a series of values usable in a for-loop or that can be retrieved one at a time with the next() function. Usually refers to a generator function, but may refer to a generator iterator in some contexts. In cases where the intended meaning isn’t clear, using the full terms avoids ambiguity. generator iterator ¶ An object created by a generator function. Each yield temporarily suspends processing, remembering the execution state (including local variables and pending try-statements). When the generator iterator resumes, it picks up where it left off (in contrast to functions which start fresh on every invocation). generator expression ¶ An expression that returns an iterator . It looks like a normal expression followed by a for clause defining a loop variable, range, and an optional if clause. The combined expression generates values for an enclosing function: >>> sum ( i * i for i in range ( 10 )) # sum of squares 0, 1, 4, ... 81 285 generic function ¶ A function composed of multiple functions implementing the same operation for different types. Which implementation should be used during a call is determined by the dispatch algorithm. See also the single dispatch glossary entry, the functools.singledispatch() decorator, and PEP 443 . generic type ¶ A type that can be parameterized; typically a container class such as list or dict . Used for type hints and annotations . For more details, see generic alias types , PEP 483 , PEP 484 , PEP 585 , and the typing module. GIL ¶ See global interpreter lock . global interpreter lock ¶ The mechanism used by the CPython interpreter to assure that only one thread executes Python bytecode at a time. This simplifies the CPython implementation by making the object model (including critical built-in types such as dict ) implicitly safe against concurrent access. Locking the entire interpreter makes it easier for the interpreter to be multi-threaded, at the expense of much of the parallelism afforded by multi-processor machines. However, some extension modules, either standard or third-party, are designed so as to release the GIL when doing computationally intensive tasks such as compression or hashing. Also, the GIL is always released when doing I/O. As of Python 3.13, the GIL can be disabled using the --disable-gil build configuration. After building Python with this option, code must be run with -X gil=0 or after setting the PYTHON_GIL=0 environment variable. This feature enables improved performance for multi-threaded applications and makes it easier to use multi-core CPUs efficiently. For more details, see PEP 703 . In prior versions of Python’s C API, a function might declare that it requires the GIL to be held in order to use it. This refers to having an attached thread state . global state ¶ Data that is accessible throughout a program, such as module-level variables, class variables, or C static variables in extension modules . In multi-threaded programs, global state shared between threads typically requires synchronization to avoid race conditions and data races . hash-based pyc ¶ A bytecode cache file that uses the hash rather than the last-modified time of the corresponding source file to determine its validity. See Cached bytecode invalidation . hashable ¶ An object is hashable if it has a hash value which never changes during its lifetime (it needs a __hash__() method), and can be compared to other objects (it needs an __eq__() method). Hashable objects which compare equal must have the same hash value. Hashability makes an object usable as a dictionary key and a set member, because these data structures use the hash value internally. Most of Python’s immutable built-in objects are hashable; mutable containers (such as lists or dictionaries) are not; immutable containers (such as tuples and frozensets) are only hashable if their elements are hashable. Objects which are instances of user-defined classes are hashable by default. They all compare unequal (except with themselves), and their hash value is derived from their id() . IDLE ¶ An Integrated Development and Learning Environment for Python. IDLE — Python editor and shell is a basic editor and interpreter environment which ships with the standard distribution of Python. immortal ¶ Immortal objects are a CPython implementation detail introduced in PEP 683 . If an object is immortal, its reference count is never modified, and therefore it is never deallocated while the interpreter is running. For example, True and None are immortal in CPython. Immortal objects can be identified via sys._is_immortal() , or via PyUnstable_IsImmortal() in the C API. immutable ¶ An object with a fixed value. Immutable objects include numbers, strings and tuples. Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an important role in places where a constant hash value is needed, for example as a key in a dictionary. Immutable objects are inherently thread-safe because their state cannot be modified after creation, eliminating concerns about improperly synchronized concurrent modification . import path ¶ A list of locations (or path entries ) that are searched by the path based finder for modules to import. During import, this list of locations usually comes from sys.path , but for subpackages it may also come from the parent package’s __path__ attribute. importing ¶ The process by which Python code in one module is made available to Python code in another module. importer ¶ An object that both finds and loads a module; both a finder and loader object. interactive ¶ Python has an interactive interpreter which means you can enter statements and expressions at the interpreter prompt, immediately execute them and see their results. Just launch python with no arguments (possibly by selecting it from your computer’s main menu). It is a very powerful way to test out new ideas or inspect modules and packages (remember help(x) ). For more on interactive mode, see Interactive Mode . interpreted ¶ Python is an interpreted language, as opposed to a compiled one, though the distinction can be blurry because of the presence of the bytecode compiler. This means that source files can be run directly without explicitly creating an executable which is then run. Interpreted languages typically have a shorter development/debug cycle than compiled ones, though their programs generally also run more slowly. See also interactive . interpreter shutdown ¶ When asked to shut down, the Python interpreter enters a special phase where it gradually releases all allocated resources, such as modules and various critical internal structures. It also makes several calls to the garbage collector . This can trigger the execution of code in user-defined destructors or weakref callbacks. Code executed during the shutdown phase can encounter various exceptions as the resources it relies on may not function anymore (common examples are library modules or the warnings machinery). The main reason for interpreter shutdown is that the __main__ module or the script being run has finished executing. iterable ¶ An object capable of returning its members one at a time. Examples of iterables include all sequence types (such as list , str , and tuple ) and some non-sequence types like dict , file objects , and objects of any classes you define with an __iter__() method or with a __getitem__() method that implements sequence semantics. Iterables can be used in a for loop and in many other places where a sequence is needed ( zip() , map() , …). When an iterable object is passed as an argument to the built-in function iter() , it returns an iterator for the object. This iterator is good for one pass over the set of values. When using iterables, it is usually not necessary to call iter() or deal with iterator objects yourself. The for statement does that automatically for you, creating a temporary unnamed variable to hold the iterator for the duration of the loop. See also iterator , sequence , and generator . iterator ¶ An object representing a stream of data. Repeated calls to the iterator’s __next__() method (or passing it to the built-in function next() ) return successive items in the stream. When no more data are available a StopIteration exception is raised instead. At this point, the iterator object is exhausted and any further calls to its __next__() method just raise StopIteration again. Iterators are required to have an __iter__() method that returns the iterator object itself so every iterator is also iterable and may be used in most places where other iterables are accepted. One notable exception is code which attempts multiple iteration passes. A container object (such as a list ) produces a fresh new iterator each time you pass it to the iter() function or use it in a for loop. Attempting this with an iterator will just return the same exhausted iterator object used in the previous iteration pass, making it appear like an empty container. More information can be found in Iterator Types . CPython implementation detail: CPython does not consistently apply the requirement that an iterator define __iter__() . And also please note that free-threaded CPython does not guarantee thread-safe behavior of iterator operations. key function ¶ A key function or collation function is a callable that returns a value used for sorting or ordering. For example, locale.strxfrm() is used to produce a sort key that is aware of locale specific sort conventions. A number of tools in Python accept key functions to control how elements are ordered or grouped. They include min() , max() , sorted() , list.sort() , heapq.merge() , heapq.nsmallest() , heapq.nlargest() , and itertools.groupby() . There are several ways to create a key function. For example. the str.casefold() method can serve as a key function for case insensitive sorts. Alternatively, a key function can be built from a lambda expression such as lambda r: (r[0], r[2]) . Also, operator.attrgetter() , operator.itemgetter() , and operator.methodcaller() are three key function constructors. See the Sorting HOW TO for examples of how to create and use key functions. keyword argument ¶ See argument . lambda ¶ An anonymous inline function consisting of a single expression which is evaluated when the function is called. The syntax to create a lambda function is lambda [parameters]: expression LBYL ¶ Look before you leap. This coding style explicitly tests for pre-conditions before making calls or lookups. This style contrasts with the EAFP approach and is characterized by the presence of many if statements. In a multi-threaded environment, the LBYL approach can risk introducing a race condition between “the looking” and “the leaping”. For example, the code, if key in mapping: return mapping[key] can fail if another thread removes key from mapping after the test, but before the lookup. This issue can be solved with locks or by using the EAFP approach. See also thread-safe . lexical analyzer ¶ Formal name for the tokenizer ; see token . list ¶ A built-in Python sequence . Despite its name it is more akin to an array in other languages than to a linked list since access to elements is O (1). list comprehension ¶ A compact way to process all or part of the elements in a sequence and return a list with the results. result = ['{:#04x}'.format(x) for x in range(256) if x % 2 == 0] generates a list of strings containing even hex numbers (0x..) in the range from 0 to 255. The if clause is optional. If omitted, all elements in range(256) are processed. lock ¶ A synchronization primitive that allows only one thread at a time to access a shared resource. A thread must acquire a lock before accessing the protected resource and release it afterward. If a thread attempts to acquire a lock that is already held by another thread, it will block until the lock becomes available. Python’s threading module provides Lock (a basic lock) and RLock (a reentrant lock). Locks are used to prevent race conditions and ensure thread-safe access to shared data. Alternative design patterns to locks exist such as queues, producer/consumer patterns, and thread-local state. See also deadlock , and reentrant . loader ¶ An object that loads a module. It must define the exec_module() and create_module() methods to implement the Loader interface. A loader is typically returned by a finder . See also: Finders and loaders importlib.abc.Loader PEP 302 locale encoding ¶ On Unix, it is the encoding of the LC_CTYPE locale. It can be set with locale.setlocale(locale.LC_CTYPE, new_locale) . On Windows, it is the ANSI code page (ex: "cp1252" ). On Android and VxWorks, Python uses "utf-8" as the locale encoding. locale.getencoding() can be used to get the locale encoding. See also the filesystem encoding and error handler . magic method ¶ An informal synonym for special method . mapping ¶ A container object that supports arbitrary key lookups and implements the methods specified in the collections.abc.Mapping or collections.abc.MutableMapping abstract base classes . Examples include dict , collections.defaultdict , collections.OrderedDict and collections.Counter . meta path finder ¶ A finder returned by a search of sys.meta_path . Meta path finders are related to, but different from path entry finders . See importlib.abc.MetaPathFinder for the methods that meta path finders implement. metaclass ¶ The class of a class. Class definitions create a class name, a class dictionary, and a list of base classes. The metaclass is responsible for taking those three arguments and creating the class. Most object oriented programming languages provide a default implementation. What makes Python special is that it is possible to create custom metaclasses. Most users never need this tool, but when the need arises, metaclasses can provide powerful, elegant solutions. They have been used for logging attribute access, adding thread-safety, tracking object creation, implementing singletons, and many other tasks. More information can be found in Metaclasses . method ¶ A function which is defined inside a class body. If called as an attribute of an instance of that class, the method will get the instance object as its first argument (which is usually called self ). See function and nested scope . method resolution order ¶ Method Resolution Order is the order in which base classes are searched for a member during lookup. See The Python 2.3 Method Resolution Order for details of the algorithm used by the Python interpreter since the 2.3 release. module ¶ An object that serves as an organizational unit of Python code. Modules have a namespace containing arbitrary Python objects. Modules are loaded into Python by the process of importing . See also package . module spec ¶ A namespace containing the import-related information used to load a module. An instance of importlib.machinery.ModuleSpec . See also Module specs . MRO ¶ See method resolution order . mutable ¶ An object with state that is allowed to change during the course of the program. In multi-threaded programs, mutable objects that are shared between threads require careful synchronization to avoid race conditions . See also immutable , thread-safe , and concurrent modification . named tuple ¶ The term “named tuple” applies to any type or class that inherits from tuple and whose indexable elements are also accessible using named attributes. The type or class may have other features as well. Several built-in types are named tuples, including the values returned by time.localtime() and os.stat() . Another example is sys.float_info : >>> sys . float_info [ 1 ] # indexed access 1024 >>> sys . float_info . max_exp # named field access 1024 >>> isinstance ( sys . float_info , tuple ) # kind of tuple True Some named tuples are built-in types (such as the above examples). Alternatively, a named tuple can be created from a regular class definition that inherits from tuple and that defines named fields. Such a class can be written by hand, or it can be created by inheriting typing.NamedTuple , or with the factory function collections.namedtuple() . The latter techniques also add some extra methods that may not be found in hand-written or built-in named tuples. namespace ¶ The place where a variable is stored. Namespaces are implemented as dictionaries. There are the local, global and built-in namespaces as well as nested namespaces in objects (in methods). Namespaces support modularity by preventing naming conflicts. For instance, the functions builtins.open and os.open() are distinguished by their namespaces. Namespaces also aid readability and maintainability by making it clear which module implements a function. For instance, writing random.seed() or itertools.islice() makes it clear that those functions are implemented by the random and itertools modules, respectively. namespace package ¶ A package which serves only as a container for subpackages. Namespace packages may have no physical representation, and specifically are not like a regular package because they have no __init__.py file. Namespace packages allow several individually installable packages to have a common parent package. Otherwise, it is recommended to use a regular package . For more information, see PEP 420 and Namespace packages . See also module . native code ¶ Code that is compiled to machine instructions and runs directly on the processor, as opposed to code that is interpreted or runs in a virtual machine. In the context of Python, native code typically refers to C, C++, Rust or Fortran code in extension modules that can be called from Python. See also extension module . nested scope ¶ The ability to refer to a variable in an enclosing definition. For instance, a function defined inside another function can refer to variables in the outer function. Note that nested scopes by default work only for reference and not for assignment. Local variables both read and write in the innermost scope. Likewise, global variables read and write to the global namespace. The nonlocal allows writing to outer scopes. new-style class ¶ Old name for the flavor of classes now used for all class objects. In earlier Python versions, only new-style classes could use Python’s newer, versatile features like __slots__ , descriptors, properties, __getattribute__() , class methods, and static methods. non-deterministic ¶ Behavior where the outcome of a program can vary between executions with the same inputs. In multi-threaded programs, non-deterministic behavior often results from race conditions where the relative timing or interleaving of threads affects the result. Proper synchronization using locks and other synchronization primitives helps ensure deterministic behavior. object ¶ Any data with state (attributes or value) and defined behavior (methods). Also the ultimate base class of any new-style class . optimized scope ¶ A scope where target local variable names are reliably known to the compiler when the code is compiled, allowing optimization of read and write access to these names. The local namespaces for functions, generators, coroutines, comprehensions, and generator expressions are optimized in this fashion. Note: most interpreter optimizations are applied to all scopes, only those relying on a known set of local and nonlocal variable names are restricted to optimized scopes. optional module ¶ An extension module that is part of the standard library , but may be absent in some builds of CPython , usually due to missing third-party libraries or because the module is not available for a given platform. See Requirements for optional modules for a list of optional modules that require third-party libraries. package ¶ A Python module which can contain submodules or recursively, subpackages. Technically, a package is a Python module with a __path__ attribute. See also regular package and namespace package . parallelism ¶ Executing multiple operations at the same time (e.g. on multiple CPU cores). In Python builds with the global interpreter lock (GIL) , only one thread runs Python bytecode at a time, so taking advantage of multiple CPU cores typically involves multiple processes (e.g. multiprocessing ) or native extensions that release the GIL. In free-threaded Python, multiple Python threads can run Python code simultaneously on different cores. parameter ¶ A named entity in a function (or method) definition that specifies an argument (or in some cases, arguments) that the function can accept. There are five kinds of parameter: positional-or-keyword : specifies an argument that can be passed either positionally or as a keyword argument . This is the default kind of parameter, for example foo and bar in the following: def func ( foo , bar = None ): ... positional-only : specifies an argument that can be supplied only by position. Positional-only parameters can be defined by including a / character in the parameter list of the function definition after them, for example posonly1 and posonly2 in the following: def func ( posonly1 , posonly2 , / , positional_or_keyword ): ... keyword-only : specifies an argument that can be supplied only by keyword. Keyword-only parameters can be defined by including a single var-positional parameter or bare * in the parameter list of the function definition before them, for example kw_only1 and kw_only2 in the following: def func ( arg , * , kw_only1 , kw_only2 ): ... var-positional : specifies that an arbitrary sequence of positional arguments can be provided (in addition to any positional arguments already accepted by other parameters). Such a parameter can be defined by prepending the parameter name with * , for example args in the following: def func ( * args , ** kwargs ): ... var-keyword : specifies that arbitrarily many keyword arguments can be provided (in addition to any keyword arguments already accepted by other parameters). Such a parameter can be defined by prepending the parameter name with ** , for example kwargs in the example above. Parameters can specify both optional and required arguments, as well as default values for some optional arguments. See also the argument glossary entry, the FAQ question on the difference between arguments and parameters , the inspect.Parameter class, the Function definitions section, and PEP 362 . path entry ¶ A single location on the import path which the path based finder consults to find modules for importing. path entry finder ¶ A finder returned by a callable on sys.path_hooks (i.e. a path entry hook ) which knows how to locate modules given a path entry . See importlib.abc.PathEntryFinder for the methods that path entry finders implement. path entry hook ¶ A callable on the sys.path_hooks list which returns a path entry finder if it knows how to find modules on a specific path entry . path based finder ¶ One of the default meta path finders which searches an import path for modules. path-like object ¶ An object representing a file system path. A path-like object is either a str or bytes object representing a path, or an object implementing the os.PathLike protocol. An object that supports the os.PathLike protocol can be converted to a str or bytes file system path by calling the os.fspath() function; os.fsdecode() and os.fsencode() can be used to guarantee a str or bytes result instead, respectively. Introduced by PEP 519 . PEP ¶ Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python or its processes or environment. PEPs should provide a concise technical specification and a rationale for proposed features. PEPs are intended to be the primary mechanisms for proposing major new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. See PEP 1 . portion ¶ A set of files in a single directory (possibly stored in a zip file) that contribute to a namespace package, as defined in PEP 420 . positional argument ¶ See argument . provisional API ¶ A provisional API is one which has been deliberately excluded from the standard library’s backwards compatibility guarantees. While major changes to such interfaces are not expected, as long as they are marked provisional, backwards incompatible changes (up to and including removal of the interface) may occur if deemed necessary by core developers. Such changes will not be made | 2026-01-13T08:48:43 |
https://zh-hans.react.dev/ | React 官方中文文档 React v 19.2 搜索 ⌘ Ctrl K 教程 参考 社区 博客 React 用于构建 Web 和原生交互界面的库 学习 React API 参考 用组件创建用户界面 React 让你可以通过组件来构建用户界面。你可以创建像 Thumbnail 、 LikeButton 和 Video 这样的组件。然后将它们组合成整个应用程序。 Video.js function Video ( { video } ) { return ( < div > < Thumbnail video = { video } /> < a href = { video . url } > < h3 > { video . title } </ h3 > < p > { video . description } </ p > </ a > < LikeButton video = { video } /> </ div > ) ; } My video Video description 无论你是独自工作还是与成千上万的其他开发人员合作，使用 React 的感觉都是相同的。它旨在让你轻松地组合由独立开发者、团队或组织编写的组件。 用代码和标签编写组件 React 组件是 JavaScript 函数。想要有条件地显示一些内容吗？使用 if 语句。 想要展示一个列表？尝试使用数组的 map() 方法。学习 React 就是学习编程。 VideoList.js function VideoList ( { videos , emptyHeading } ) { const count = videos . length ; let heading = emptyHeading ; if ( count > 0 ) { const noun = count > 1 ? 'Videos' : 'Video' ; heading = count + ' ' + noun ; } return ( < section > < h2 > { heading } </ h2 > { videos . map ( video => < Video key = { video . id } video = { video } /> ) } </ section > ) ; } 3 Videos First video Video description Second video Video description Third video Video description 这种标签语法被称为 JSX。它是由 React 推广的 JavaScript 语法扩展。将 JSX 标签与相关的渲染逻辑放在一起，使得创建、维护和删除 React 组件变得容易。 在任何地方添加交互 React 组件接收数据并返回应该出现在屏幕上的内容。你可以通过响应交互（例如用户输入）向它们传递新数据。然后，React 将更新屏幕以匹配新数据。 SearchableVideoList.js import { useState } from 'react' ; function SearchableVideoList ( { videos } ) { const [ searchText , setSearchText ] = useState ( '' ) ; const foundVideos = filterVideos ( videos , searchText ) ; return ( < > < SearchInput value = { searchText } onChange = { newText => setSearchText ( newText ) } /> < VideoList videos = { foundVideos } emptyHeading = { `No matches for “ ${ searchText } ”` } /> </ > ) ; } example.com / videos.html React Videos A brief history of React Search 5 Videos React: The Documentary The origin story of React Rethinking Best Practices Pete Hunt (2013) Introducing React Native Tom Occhino (2015) Introducing React Hooks Sophie Alpert and Dan Abramov (2018) Introducing Server Components Dan Abramov and Lauren Tan (2020) 你也可以不用 React 去构建整个页面，而只是将 React 添加到现有的 HTML 页面中，在任何地方呈现交互式的 React 组件。 将 React 添加到你已有的页面中 使用框架 进行全栈开发 React 是一个库。它允许你将组件放在一起，但不关注路由和数据获取。要使用 React 构建整个应用程序，我们建议使用像 Next.js 或 React Router 这样的全栈 React 框架。 confs/[slug].js import { db } from './database.js' ; import { Suspense } from 'react' ; async function ConferencePage ( { slug } ) { const conf = await db . Confs . find ( { slug } ) ; return ( < ConferenceLayout conf = { conf } > < Suspense fallback = { < TalksLoading /> } > < Talks confId = { conf . id } /> </ Suspense > </ ConferenceLayout > ) ; } async function Talks ( { confId } ) { const talks = await db . Talks . findAll ( { confId } ) ; const videos = talks . map ( talk => talk . video ) ; return < SearchableVideoList videos = { videos } /> ; } example.com / confs/react-conf-2021 React Conf 2021 React Conf 2019 Search 19 Videos React Conf React 18 Keynote The React Team React Conf React 18 for App Developers Shruti Kapoor React Conf Streaming Server Rendering with Suspense Shaundai Person React Conf The First React Working Group Aakansha Doshi React Conf React Developer Tooling Brian Vaughn React Conf React without memo Xuan Huang (黄玄) React Conf React Docs Keynote Rachel Nabors React Conf Things I Learnt from the New React Docs Debbie O'Brien React Conf Learning in the Browser Sarah Rainsberger React Conf The ROI of Designing with React Linton Ye React Conf Interactive Playgrounds with React Delba de Oliveira React Conf Re-introducing Relay Robert Balicki React Conf React Native Desktop Eric Rozell and Steven Moyes React Conf On-device Machine Learning for React Native Roman Rädle React Conf React 18 for External Store Libraries Daishi Kato React Conf Building Accessible Components with React 18 Diego Haz React Conf Accessible Japanese Form Components with React Tafu Nakazaki React Conf UI Tools for Artists Lyle Troxell React Conf Hydrogen + React 18 Helen Lin React 也是一种架构。实现它的框架可以在服务端甚至是构建阶段使用异步组件来获取数据，也可以从文件或数据库读取数据，并将其传递给交互式组件。 使用框架开始一个新项目 博采众长 人们因为不同的原因偏好 Web 应用或原生应用。React 让你使用相同的技能构建 Web 应用程序和原生应用程序。它依赖于每个平台独特的优势，使你的界面就像原生一样。 example.com 不忘初心 人们期望网页加载速度更快。在服务器上，React 可以让你在获取数据的同时开始流式传输 HTML，在任何 JavaScript 代码加载之前逐步填充剩余内容。在客户端，即使是在渲染过程中，React 也会使用标准的 Web API 使 UI 快速响应。 2:59 AM 开发真正的原生应用 人们希望原生应用程序都有和自己使用的平台相一致的体验。 React Native 和 Expo 让你可以使用 React 构建 Android、iOS 等应用程序。它们的样式和体验都和原生应用程序一样，因为它们的用户界面是真正的原生用户界面。这不是一个 Web 视图——你的 React 组件由平台提供的真实 Android 或 iOS 视图来渲染。 使用 React，你可以成为 Web 和原生应用的开发人员。 你的团队可以在不牺牲用户体验的情况下发布到各个平台。你的组织可以忽略平台差异，并拥有端到端的全部功能。 为原生平台构建 充分测试，安心升级 React 非常谨慎地处理每个改动。每个 React 提交都在拥有超过十亿用户的关键业务页面上进行测试。Meta 的 10 万个 React 组件帮助验证每种迁移策略。 React 团队始终在研究如何改进 React。一些研究需要数年才能得到回报。React 对将研究想法转化为生产具有高标准要求，只有经过证明的方法才能成为 React 的一部分。 阅读更多 React 新闻 最新 React 新闻 Vulnerability in React Server Components December 03, 2025 React Conf 2025 Recap October 16, 2025 React Compiler v1.0 October 7, 2025 Introducing the React Foundation October 7, 2025 阅读更多 React 新闻 加入数百万人的社区 你并不孤单。每个月有来自世界各地的两百万开发者访问 React 文档。React 可以让人们达成共识。 这就是为什么 React 不仅仅是一个库、一种架构，甚至不只是一个生态系统。React 是一个社区。在这里你可以寻求帮助，发现机会并结交新朋友。你将会遇到开发者和设计师、初学者和专家、研究人员和艺术家、教师和学生等各行各业的人士。我们的背景可能非常不同，但 React 让我们所有人都能够共同创建用户界面。 欢迎来到 React 社区 开始 React 之旅 Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 学习 React 快速入门 安装 描述 UI 添加交互 状态管理 脱围机制 API 参考 React API React DOM API 社区 行为准则 团队 文档贡献者 鸣谢 了解更多 博客 React Native 隐私政策 条款 | 2026-01-13T08:48:43 |
https://docs.suprsend.com/docs#introduction-to-workflows | What is SuprSend? - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:48:43 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.